Dtsi/SOL/ 1March 2004ETSI MTS meeting, Sophia Antipolis Methodology Chokri Mraidha, Sébastien Gérard DRT-LIST/DTSI/SOL/LLSP, CEA/Saclay, F Gif sur Yvette Cedex France Phone: ; Fax:

Dtsi/SOL/ 2March 2004ETSI MTS meeting, Sophia Antipolis Outlines Scope: Real-time and Embedded Systems development Problematic: public: help non-experts to design real-time systems How to do it ? Manage systems complexity, Improve development quality, Make easier the maintenance… … ensure reliability and effectiveness.

Dtsi/SOL/ 3March 2004ETSI MTS meeting, Sophia Antipolis Contents Outlines of the Accord/UML approach Focus on behavioral aspect modeling

Dtsi/SOL/ 4March 2004ETSI MTS meeting, Sophia Antipolis Accord/UML Methodology UML component-based methodology… … in a model-driven way Application Domain : Distributed Real-time Embedded Systems

Dtsi/SOL/ 5March 2004ETSI MTS meeting, Sophia Antipolis Outlines of the Accord/UML workbench Document describing the Accord/UML Method UML profile for SPT « Profile » UML profile for ACCORD/UML « Profile » UML profile for ACCORD/UML Process « Profile » UML profile for ACCORD/UML PAM « Profile » UML profile for ACCORD/UML DAM « Profile » UML profile for ACCORD/UML PrM « Profile » « use » User guide for Accord/UML profiles under Objecteering Virtual Machine Kernel Accord Framework « implement » ACCORD_UML_Process.prof « ProfileImplementation » ACCORD_UML_PAM.prof « ProfileImplementation » ACCORD_UML_DAM.prof « ProfileImplementation » ACCORD_UML_PrM.prof « ProfileImplementation » Methodology entirely based on UML

Dtsi/SOL/ 6March 2004ETSI MTS meeting, Sophia Antipolis Several modeler points of view System models struct. based on dev. cycle System Analyst PAM, Preliminary Analysis Rules Req. Doc. ACCORD/UML PAM System Analyst DAM, DAM Detailed Analysis Rules ACCORD/UML Spec. Valider VaM, Validation Rules ACCORD/UML VaM Prototyper PrM,TeM… Prototyping Rules ACCORD/UML PrM TeM Testing Rules ACCORD/UML Accord/UML profile ACCORD/UML

Dtsi/SOL/ 7March 2004ETSI MTS meeting, Sophia Antipolis Preliminary analysis Model Purpose « Formalize » requirements Principle The system is viewed like a black box. Contents a dictionary to have/to take the target domain in hand a use-case diagram functionalities clear identification of frontiers high level scenarios communication protocol between the Syst. and Env. With real-time constraints

Dtsi/SOL/ 8March 2004ETSI MTS meeting, Sophia Antipolis Detailed Analysis Model Three well-funded and complementary model Structural, behavioral, interaction A component based architecture ( model level) Separation of behavioral aspect Control aspect UML protocol state machine on classes Algorithmic aspect Activity diagrams Action language for operations Support of high level concurrency Real-Time Object Various communication models Strong or postponed synchronous, asynchronous or diffusion Refinement of Real-Time constraints

Dtsi/SOL/ 9March 2004ETSI MTS meeting, Sophia Antipolis Prototyping model Component-based model The system = a component Possibility of importing binary components E.g. graphical interface component, mathematical component… Assembly of components Definition of mechanisms for an automatic integration at model level or at code level Complete generation of code (structure + behavior) Include action language and associated code generators Targets: Unix, Linux and VxWorks operating systems

Dtsi/SOL/ 10March 2004ETSI MTS meeting, Sophia Antipolis Validation model Validation by exhaustive testing through symbolic execution definition of model transformations towards a formal tool called AGATHA that: calculate in an exhaustive way the dynamic behavior generate automatically tests thanks to a symbolic execution verify if PAM and DAM sequence diagrams are compatible with the set of calculated diagrams of AGATHA Ongoing PhD on schedulability analysis of UML models

Dtsi/SOL/ 11March 2004ETSI MTS meeting, Sophia Antipolis Contents Outlines of the Accord/UML approach Focus on behavioral aspect modeling

Dtsi/SOL/ 12March 2004ETSI MTS meeting, Sophia Antipolis tgSpeed : int initReg() stopReg() display() Regulator C Off On initReg[cptVit->getSpeed()=<30] /display("ON"); stopReg/display("OFF"); tm(100)/tgSpeed = cptVit->getSpeed(); [carSpeed=<30]/display("OFF"); /delta=k1*atan(tgSpeed-cuSpeed); mot->sendCmd(coupleVariation); Control Algorithmic & The Behavioral Aspect: Common Approach Usual form of UML state machine E1E1 E2E2 Evt [ guard ] / procedure List of actions Sample of usage Issues related to this situation Maintainability because of different aspects combination Reusability because of state-machine inheritance issues

Dtsi/SOL/ 13March 2004ETSI MTS meeting, Sophia Antipolis Regulator +tgSpeed : integer +initReg() +stopReg() +maintainSp() Off On initReg() stopReg() maintainSp() Class Behaviour Model = Logic aspect of behaviour Activity – describe behavioral view Method Behaviour Model = Algorithmic aspect of behavior carSpeed = cptVit.getSpeed() mot.sendCmd(coupleVariation) delta=k1*atan(tgSpeed-cuSpeed) New operation introduced to integrate algorithmic aspect Advantages of this proposition Maintainability because of separation of concerns Reusability because of availability of usual OO inheritance mechanisms UML2 protocole state machines … An action language definition

Dtsi/SOL/ 14March 2004ETSI MTS meeting, Sophia Antipolis Conclusions Accord/UML methodology gives an executable UML model A complete and clear behavioral model Separation of logic and algorithmic aspects An action language for operations modeling Model executability allows Validation at every stage of the development Performance analysis at the model level A full customization of code generation to a specific platform optimized code generation a better reusability of models a better maintability A standard UML executable model still needs a standard action language notation mapping the action semantics syntax defined in UML 2.0

Dtsi/SOL/ 15March 2004ETSI MTS meeting, Sophia Antipolis Web sites associated to the subject « MDA and DRES summer School » « SIVOES-SPT workshop on feedback on SPT profile » « SIVOES – MoDeVa workshop on Modelling, Design and Validation »