Home

Stood 5.3 AADL User Manual

1. Stood for the AADL Stood 5 3 AADL User Manual STOOD AADL User Manual Ellidiss October 2011 page 1 x Stood for the AADL Pierre Dissaux Ellidiss Technologies page 2 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL Contents 3 3A ADL EN ee 18 FEE RE REE ENTEN 20 EEE Ev SEES EE AE 22 EEE Go RR NN ER EEEN 24 3 4 3 AADL Thread groups RR EON 25 EEE ESN 26 3 4 S AADL Subprogram componentS rrsssrrrrrnsrrrrrnnsrssnnnnnevrnnnnnvsssnnnnssssnnnnevsnnnnnssssnnnssssnnnnnessnnnnnesssnnneenn 2 SR NE 28 ETEN UR EE 28 JAREN eo RE 29 29 JJ EEE i a a 30 ENE 0 OURE 30 KR 31 JE ee ee ee 32 SEE ERE cn eh pee oe might NE Ne 33 3 10 Behavior ANeX 2 cccccccesccsccsscssecescesccuscesessscusecsecussssacussssecuecusssuscsadsesssssussusssuscussauscusssussussaussussnes 36 4Processing of AADL models uuuumsnmisunumsnen nvnnnjjajgn dd adsl kid m id dk de 38 MN NNN nc 38 STOOD AADL User Manual O Ellidiss October 2011 page 3 x Stood for the AADL 4 2Generate textual AADL COde cccccsccssscsscssccssssscessssscessssssessssssussssssussesssuscssssusssssssseussussssussuss 4 3Generate Ada source code 41 42 Me Gio iis EE REE page 4 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL 1 Introduction The Architecture Analysis and Design Language AADL standard document was prepared by the SAE AS 2C Ar
2. Change into k In i Out Add to feature group In Out Remove from feature group i Dat rt Delete is Event port Event Data port Subprogram When a port is selected in the graphical editor its formal declaration is shown in the text input area E PORTS and SUBPROGR new thread __ rea p rt cInew port Export or subpg desc port or subpg decla EE 4 m worst case executl REQUIRED INTERFACE DATAFLOWS IMPLEMENTATION port or subpg declaration in PROPERTIES new port Event in TI Event Flow in T Flow BEHAVIOR page 28 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL In a Stood design model AADL ports are stored as operations with parameters An event or event data port has an Event parameter A data port or event data port has a parameter which name must be other than Event Default name for a data parameter is Flow and may be changed as well as its parameter type which is set to T Flow by default Removing or renaming the Event parameter will remove the event nature of the port To validate a change in the port declaration section it is mandatory to use the Save text button or contextual menu or the Ctrl S keyboard shortcut 3 5 2 AADL Feature groups To create a new feature group use the corresponding button of the tool bar It is then possible to drag new ports or other feature groups inside the two enclosing brackets delimitating the feature group
3. Use Design New design from aadl in the main menu or New from aadl contextual menu of the project area to create a new design model from an existing AADL specification This opens a standard file navigator asking a textual AADL file to be selected Files are recognized to be textual AADL files if they have a aad1 extension STOOD AADL User Manual Ellidiss October 2011 page 17 x Stood for the AADL The result of this action will be to analyse all the textual AADL files located within the same directory as the selected file and to create a design model having the same name as the selected file The newly created design model will be added to the list in the project area but will not be automatically loaded Please refer to paragraph 3 1 2 to know how to do to load a design model Note that Stood makes the assumption that the selected file has the same name as the root of the AADL component or package hierarchy to be imported When the textual AADL source contains several AADL hierarchies it is necessary to create several design models after having either selected the appropriate file in the source directory or properly renamed the unique input file 3 2 5 Create a new design from existing Ada or C source files It is possible to reverse engineer existing Ada or C source code into Stood This legacy code is transformed into a Stood design model thanks to an embedded Ada and C syntactic analyser and a set of semantic transfo
4. A feature group may be open or close as shown in the pictures below rew thread rew thread gp lg EEE I r pisi rip Pt i T em Ty sit p fuil To open a closed feature group double click on its name or use enter contextual menu To close an opened feature group double click on its name or use exit contextual menu To include a feature to a feature group drag it inside the opened port group or use add to feature group contextual menu To remove a feature from a feature group drag it outside the opened feature group or use remove from feature group contextual menu 3 5 3 AADL Subprogram features To create a new subprogram feature use the corresponding button of the tool bar A new subprogram is created without any parameter by default To edit the parameters list of a subprogram feature use the port or subpg declaration section of the ODS STOOD AADL User Manual Ellidiss October 2011 page 29 ods ada c cpp aadl test checks DESCRIPTION A Fr PROVIDED INTERFACE PROPERTIES PORT GROUPS PORTS and SUBPROGRAMS muserver subprogram port or subpg description port or subpg declaration mu worst case execution time REQUIRED INTERFACE DATAFLOWS IMPLEMENTATION PROPERTIES BEHAVIOR FUNCTIONAL BEHAVIOR x Stood for the AADL new_Threed Pome ee ee ee ee ee eee port or subpg declaration server subprogram argl in T param arg out T param To validate a change in
5. component contextual menu Exit New component Rename Change into Undelete Open state diagram Go up in the hierarchy New sub package or subcomponent Change component category Delete undelete component I Rename component Open state diagram page 10 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL 2 5 3 AADL sub package or subcomponent contextual menu Li mi F cy m Enter Rename Change into Ering to front Send to back Delete Open state diagram Set public Export 1 Go down in the hierarchy S d T Change component category E Delete undelete component HI Connect to subcomponent feature 2 5 4 AADL feature contextual menu STOOD AADL User Manual Ellidiss October 2011 page 11 SET layer d Rename C Fi ri ect vi Left alignment Right alignment Change into Add to feature group Remove from feature group Delete 2 6 AADL textual editor x Stood for the AADL In Out In Out Data port Event port Event Data port Subprogram The AADL textual editor of Stood is a customized configuration of the generic structured design editor called ODS editor in Stood terminology The ODS is used to store in a well structured way all the features and properties for each AADL component or package The ODS can also hold additional design information like sketches and textual comments The ODS
6. of the tool bar In addition it is possible to launch external tools that will process or analyse the textual AADL specification that has been generated For instance it is possible to use OSATE to transform textual AADL generated by Stood into XML AADL files Note that the analysis tool AADL Inspector is automatically launched after AADL code generation It is possible to make changes in theses source files using the text input area Changes must be saved with Save text button or contextual menu or the Ctrl S keyboard shortcut page 40 STOOD AADL User Manual Ellidiss October 2011 a Kred x Stood for the AADL design shared data Requirements Graphic Design Detailed Design Checkers Code Documentation Deployment design Base_ Types aao aoa design Data_Model SR design HW p aad a lidesign shared_data I PACKAGE Shared Mara ar aif PUBLIC S WITH HW my process Check AADL syntax SYSTEM shared data END shared data ods ada c cpp Sad teat checks Launch OSATE i TYPE SUBCOMPONENTS PRES vw platform SYSTEM HW RMA board IMPLEMENTATION ET 7 mong Launch AADL my process PROCESS my process others pragmas PROPERTIES Inspector code file header Actual Processor Binding gt reference my platform cpu applies tc AADL CODE Stood Box Position gt X1 gt 500 Y1 gt 200 X2 gt 914 Y2 gt 600 mn extraction messages END shared data others KIevE
7. option first select the component on which it should apply then click on the add pragma button and select the appropriate pragma in the list When a pragma 1s set its name is preceded by a gt gt tick The list of all the currently set pragmas is shown in the editing area where it is possible to remove or dupplicate them and change the value of their arguments Supported pragmas for the AADL code generator are listed in the next sections If no pragma is set default code generation rules will be applied i 1 Set generation opti Requirements Graphic Design Detailed E K TE 2 Start code generation Save text Previous Next pragmas To start the generation of the textual AADL code select Tools Code Full extraction in the main menu or simply press full extraction button in the tool bar then select OK in the dialog box When completed the result of the code generation process is shown in another view of the code sub window showing the result of the generation process By default this view shows generation log messages if the root component is selected in the project area For each package or component of the design model select the aadl section in the component area to edit the corresponding generated AADL code If the pragma one file per component was not set then the whole AADL specification will be shown when the root component or package is selected The AADL syntax can be checked with the check aadl button
8. the subprogram declaration section it is mandatory to use the Save text button or contextual menu or the Ctrl S keyboard shortcut 3 6 AADL connections The new connection button of the tool bar must be used to create e a connection between two ports e a connection between two feature groups e an access connection between a data component and a thread component 3 7 AADL properties The list of all the predefined AADL properties is included into the ODS To insert the property value for the selected component or feature select the corresponding property name in the list and write the value in the text editing area page 30 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL ods ada c cpp aadi test checks F COMPONENT DESCRIPTION TYPE FEATURE GROUPS FEATURES PROPERTIES Predeclared Deployment Properties Fredeclared Thread Properties Fredeclared Timing Properties Fredeclared Communication properties Fredeclared Memory Properties Source Data Size Fredeclared Programming Properties Fredeclared Modeling Properties x User Defined Component Type Properties aad IMPLEMENTATION EN pragmas To validate a change in the property section it is mandatory to use the Save text button or contextual menu or the Ctrl S keyboard shortcut Hext Source Code Size 3 7 1 Stood property set In order to be able to propagate graphical information through AADL specifications S
9. CATION REPORT LA begin check Wed Jan 4 15 15 32 2006 check messages gt rule L032 checked Lecheck comments gt rule L034 checked Hem hood rules hood checker gt rule L108 checked T m ee Halt Program terminated normally L ea caLegality rule end check Wed Jan 4 15 15 32 2006 eametrics metric checker database database checker 4 en scheduling scheduling checker i mg requirements requirements checker 3 Select a result file to view pen errors red gauge means check prolog description AADL CROSS REFS empty file and no error PSEUDO CODE CROSS REFS Ada CROSS REFS AMDAM Meee HHE 4 2 Generate textual AADL code Textual AADL code can be generated at any time from the current design model To activate the AADL code generator switch the ife cycle selector to the code tab Requirements Graphic Design Detailed Design Checkers Documentation Deployment If aadl has been specified as the default target language then this will automatically open the AADL code generator Else it may be necessary to select the aadl tab in the property selector ods ada c ee checks STOOD AADL User Manual Ellidiss October 2011 page 39 x Stood for the AADL The first view of the code sub window gives access to generation options called pragmas in Stood terminology and that are described below To set an
10. EHAVIOR fn eabehavior description state transition diagram MODES TRANSITIONS start GENERATION running suspended 3 restart Following AADL code will be generated from this model PROCESS new process FEATURES Stare IN EVENT PORT stop IN EVENT PORT restart IN EVENT PORT END new process PROCESS IMPLEMENTATION new process others SUBCOMPONENTS new thread THREAD new thread MODES init INITIAL MODE running MODE suspended MODE init stare gt running running L stop J gt suspended suspended restart gt running END new process others 3 9 AADL flows Stood can be used to declare flow specifications There is however currently no support for flow implementations and end to end flows Stood represents internally AADL data ports as operations with parameters The name of the operation is used for the port name if not Event the type of the parameter is used for the data port classifier and the name of the parameter is used to specify flows Default value for a data port operation parameter is Flow There will be no flow specification generated for default values of this parameter however if this parameter name is changed to the name of a flow then STOOD AADL User Manual Ellidiss October 2011 page 33 x Stood for the AADL corresponding flow specifications will be generated in terms of flow paths flow sources and flow sinks example The vario
11. NTS PROPERTIES BEHAVIOR FUNCTIONAL BEHAVIOR ATTRIBUTES attribute attribute page 26 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL On the contrary data components that are created as subcomponents of a process thread group or thread are mapped to a shared protected object in the Stood model Use of data access connections in the AADL graphical notation will show the actual data sharing new_pPiracees reading threcd EEE EG EN shored data eg SC ECS es bee ee ew ee ew eee ee ee ed 3 4 5 AADL Subprogram components In most cases subprogram components will be automatically created during the AADL code generation from the definition of subprogram features example AADL generated code from the diagram above will contain the definition of the two subprogram components read and write although they don t appear in the diagram DATA shared data FEATURES read SUBPROGRAM read write SUBPROGRAM write END shared data SUBPROGRAM read END read SUBPROGRAM write END write STOOD AADL User Manual Ellidiss October 2011 page 27 x Stood for the AADL 3 5 AADL features 3 5 1 AADL Ports To create a port use the new port button in the tool bar New ports are created as in event by default Use the Change into contextual menu to change the port kind and direction set layer Rename Connect Left alignment Right alignment
12. PS Secure Handheld EXTENDS GPS Handheld END GPS Secure Handheld 3 4 1 AADL Processes To create an AADL process instance use Design New design aadl process in the main menu Enter Rename Change into Delete The AADL code that is generated for an empty process is as follow SYSTEM tests END tests SYSTEM IMPLEMENTATION tests others SUBCOMPONENTS new process PROCESS new process END tests others page 22 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL PROCESS new process PROPERTIES Stood Br Position gt VIL 222701 gt LX gt OIGA gt SULT END new process Note that an AADL process is necessarily represented by a Stood design that is a root of a hierarchy of software components that will be transformed into an executable application or a linkable library at the end of the software development process If the project contains several processes it is thus mandatory to create several design models It is possible to represent the interface of other remote processes or used packages in the enclosing system These components or packages act as proxy of the actual processes or packages that must correspond to other design models of the same project To create these proxies also called environment components in Stood terminology create sibling components to the main process and give them the name of an existing design model of the project example The mine hunti
13. ation of package hierarchies a sub package will be graphically represented as being contained by its parent package Exit New sub component 55 Thread Group Rename n Change into Subpro Data Undelete Package PACKAGE new package PUBLIC DATA void END void END new package PACKAGE new package new subpackage PUBLIC DATA void STOOD AADL User Manual Ellidiss October 2011 page 19 x Stood for the AADL END void END new package new subpackage 3 4 AADL components In Stood AADL components represent in effect subcomponents that are instances of component types or implementations During AADL code generation component type name will be set by default to subcomponent name and component implementation name will be set to others It is of course possible to change these default names so that several subcomponents can share a same type or implementation The renames dialog box can be used for this purpose Si Rename Component extension is not shown during the design process in most cases The AADL code generation pragma extend must be used to specify that the specified component holds a type or implementation extension Refer to chapter 4 2 to get more details about theses AADL code generation pragmas Note that it is possible to describe graphically data component extensions when they are declared in a package and with the help of the UML editor inheritanc
14. chitecture Description Language Subcommittee Embedded Computing Systems Committee Aerospace Avionics Systems Division Release 1 0 of the AADL standard SAE AS5506 has been issued in November 2004 and Release 2 0 SAE AS5506A in January 2009 A set of annexes SAE AS5506 2 has been published in January 2011 that includes in particular the Behavior Annex AADL is a language used to describe the software and hardware components of a system and the interfaces between those components The language can describe functional interfaces to components such as data inputs and outputs and non functional aspects of components such as timing The language can describe how components are combined such as how data inputs and outputs are connected or how software components are allocated to hardware components More detailed information about this language may be found at www aadl info Stood is a software design tool that is used for the same families of mission critical systems as those for which AADL has been developed Like AADL Stood promotes Model Driven Engineering MDE together with a Component Based modelling approach This manual describes the features that have been added to Stood in order to let software designers benefit from AADL Some of the most important advantages of Stood are that it offers a very good support of the modelling process and brings a large set of development features that have already been in use on many large scale indus
15. e cycle selector to be used as a switch for the main activities of the development process The project area component area text input area and main editing area also offer a contextual menu that usually simply recalls items of the main menu 2 4 Stood life cycle selector Stood covers all the life cycle steps from requirements capture to target source code generation Stood features that are available to support these various activities can be activated thanks to the life cycle selector Requirements Graphic Design Detailed Design Checkers Code Documentation Deploy Opens the HW SW binding editor Opens Opens the Opens the he Opens AADL AADL Opens the document graphical en the AADL generator editor AADL code editor checker generator 2 5 AADL graphical editor The AADL graphical editor of Stood is mainly composed of a button tool bar and a contextual menu in the graphical edition area The contextual menu varies according to the current selection depending on it 1s e an AADL component or package e an AADL subcomponent or sub package e an AADL feature STOOD AADL User Manual Ellidiss October 2011 page 9 x Stood for the AADL 2 5 1 AADL tool bar Hood UML fe AADL New port New feature group New subprogram New connection KA Print diagram on default printer New sub package or subcomponent Help Zoom out Zoom in Open state diagram 2 5 2 AADL package or
16. e link example page 20 STOOD AADL User Manual Ellidiss October 2011 ek Stood for the AADL In the design model below following AADL generation pragmas have been set Subcomponent type_name implementation nam extends e GPS GPS Basic GPS PS GPS Handheld Handheld GPS Basic GPS Secure endel GES Secure Handheld GPS Handheld design ComponentNames design ComponentNames ComponentNames GPS GPS Basic GPS Handheld GPS Secure GPS Secure Handheld ods ada C cpp aadl test checks COMPONENT DESCRIPTION PROVIDED INTERFACE REQUIRED INTERFACE DATAFLOWS IMPLEMENTATION GENERATION mn pragmas Requirements Graphic Design Detailed Design Checkers Code Documentation Deployment Hood Mi HEA E z ming 2 ST Rag AADL Comparentilomss ps EPE Secure I pm Fesses ER ee go SSS Ses ess f ss5 pragmas PRAGMA type name name gt GPS Secure PRAGMA implementation name name gt Handheld PRAGMA extends package name gt ancestor gt GP5 Handheld The corresponding textual AADL code that is generated 1s THREAD GPS END EPS THREAD IMPLEMENTATION GPS Basic END GPS Basic STOOD AADL User Manual Ellidiss October 2011 page 21 x Stood for the AADL THREAD IMPLEMENTATION GPS Handheld EXTENDS GPS Basic END GPS Handheld THREAD GPS Secure EXTENDS GPS END GPS Secure THREAD IMPLEMENTATION G
17. ect Use File Add to project resp Remove from project in the main menu or the Add resp Remove contextual menu of the project view to let an existing design model be visible resp invisible within the current project A newly added design model will be added to the list in the project area but will not be automatically loaded Please refer to paragraph 3 1 2 to know how to do to load a design model A newly removed design model will be hidden in the project area but will not be deleted 3 2 3 Create a new design model Use Design New design aadl in the main menu or the New design contextual menu of the project area to create a new design model This opens a dialog box asking the name of the design model to be entered The result of this action will be to create a new Stood design subdirectory with the given name in the same directory as the project A directory can be recognized as a Stood design if it contains a file named Stood sto The newly created design model will be added to the list in the project area but will not be automatically loaded Please refer to paragraph 3 1 2 to know how to do to load a design model 3 2 4 Create a new design model from an existing AADL specification It is possible to import an existing AADL specification into Stood This AADL specification is transformed into a Stood design model thanks to an embedded textual AADL 1 0 syntactic analyser and a set of semantic transformation rules
18. ed padlock should be visible at a lower level in the components hierarchy El Stood for AADL beta mine hunting File Edit Design Component Feature Tools design mine field design GPS design mh types design mine field mine field data types amp design mine hunter design om shore center X XIX design rta design sonar types generic antenna 3 2 Create new models Not loaded Loaded read only unlocked Loaded read write locked Loaded read only partially locked Loaded read only locked by someone else Any design model must be edited within a project It is possible to create a new design model inside an existing project refer to paragraph 3 1 1 otherwise it 1s necessary to firstly create a new project 3 2 1 Create a new project Use File New project in the main menu to create a new project This opens a dialog box asking the name of the project to be entered The result of this action will be to create a new Stood system configuration file with the given name and a syc extension in the default working directory page 16 STOOD AADL User Manual Ellidiss October 2011 x Stood su for the AADL This newly created project is empty by defaults This means that the project area will be empty It is necessary to either add existing design models to the project or create new design models within this project 3 2 2 Add or remove design models in a proj
19. er Manual Ellidiss October 2011 page 43 Ellidiss Five omaiss con www ellidiss com stood ellidiss com Ellidiss Software Ellidiss Technologies Triad House Mountbatten Court 24 quai de la douane Worall Street 29200 Brest Congleton Brittany Cheshire France CW12 1DT UK 44 1260 291 449 33 298 451 870 www aadl info
20. erse messages sad PROCESS my process mu makefile END my process ma prolog description In addition if the pragma reverse was set any changes in the generated source files that are done between the round trip engineering tags will be fed back to the design model thanks to the round trip engineering feature of Stood To activate this feature you must press the reverse button of the tool bar Note that this feature is currently active for Behavior Annex behavioural sections only refer to chapter 3 10 The AADL source files can also be edited directly from the file system Default location of generated code is the _aad1 subdirectory in the directory of the design To open it from Stood use Tools Open directory Design directory in the main menu 4 3 Generate Ada source code Ada source code can be generated at any time from the current design model To activate the Ada code generator switch the life cycle selector to the code tab Requirements Graphic Design Detailed Design ese Ct case Deployment If ada has been specified as the default target language then this will automatically open the Ada code generator Else it may be necessary to select the ada tab in the property STOOD AADL User Manual Ellidiss October 2011 page 41 x Stood for the AADL selector od ada cpp aadi test checks Se 4 4 Generate C source code C source code can be generated at any time from the current design model T
21. his area may be empty 3 1 2 Load a design model When a project is open the design models it contains are not automatically loaded When a design model is not loaded its name is shown in black in the project view Perform a single click on the name of a design model to load it in a read only mode This changes the colour of the name in the project view into blue and initializes the other areas of the window with the contents of the loaded design model However no change will be permitted and most menus and buttons will be inactive Perform a double click on the name of a design model or use the Lock contextual menu or Design Lock design in the main menu to load it in a read write mode This has the same effect as a single click but a green padlock will be displayed at the left of the name in the project area and changes will be allowed STOOD AADL User Manual Ellidiss October 2011 page 15 x Stood for the AADL The green padlock means that the design model is locked for all the other concurrent sessions thus providing a simple and efficient protection in a multi user environment It may happen that a red padlock is displayed at the left of the name of a design model This means that this model is currently in use by another user and that it will not be possible to lock it until it is released It may also happen that a yellow padlock is shown This means that the design model is partially locked In that case a green or r
22. is at the same time a guide for entering details into an AADL design model and a frame for producing the AADL design documentation Next picture shows an example of the ODS of an AADL component This list is displayed within the component area and is automatically updated when features or properties are created or deleted and according to the category of the current component page 12 STOOD AADL User Manual Ellidiss October 2011 ods ada c cpp 990 COMPONENT DESCRIPTION PROBLEM w Statement of the Problem ga Sketch of the Problem ma Referenced Documents SOLUTION e General Strategy ma Sketch of the Solution identification of subcomponents ei Justification of Design Decisi r PROVIDED INTERFACE PROPERTIES PORT GROUPS PORTS and SUBPROGRAMS minput global pos port or subpg description w port or subpg declaration Worst case execution time stat mission moutput mission report output pulse cx nput reflection minput reverberation Em input noise REQUIRED INTERFACE DATAFLOWS IMPLEMENTATION SUBCOMPONENTS PORT GROUPS PORTS Input global pos connected to start Mission output mission report output pulse Input reflection Input reverberation Input noise BEHAVIOR ro behavior description co state transition diagram MODES TRANSITIONS GENERATION x Stood The ODS tab is selected The ODS describes only one component or package Informal textual description Informal graphical description List of AADL
23. ition diagram MODES TRANSITIONS BEHAVIORAL CODE Epes code aadi obcs code ada obcs code c obcs code cpp FUNCTIONAL BEHAVIOR mE pragmas To validate a change in a Behavior Annex section it is mandatory to use the Save text button or contextual menu or the Ctrl S keyboard shortcut page 36 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL Next obes code aadi states a initial complete final state transitions t 3 on dispatch gt 3 Dl lt computation 3 ms D2 1 lt D2 15 Dl gt The AADL code that is generated is as follow THREAD IMPLEMENTATION T il PROPERTIES Dispatch Protocol gt Periodic Compute Execution Time gt Sms Sme Period gt 15 ms SLOOd BOx POSICION gt 266 333 449 516 ANNEX Behavior Specification 1 States S initial complete final state transitions cb amp 06 dispatch gt S 1 DL I lt Foot ion 5 me Da tas D2 1 D1 gt Li KR i END Telly STOOD AADL User Manual Ellidiss October 2011 page 37 x Stood for the AADL 4 Processing of AADL models 4 1 Generate design verification reports To enter the design verification mode select the Checkers tab in the life cycle selector Requirements Graphic Design Detailed mir te Code Documentation Deployment Stood includes an internal cross reference table and several embedded design model verification tools e requirements t
24. ng project is composed of 8 design models In the current session process mine hunter is being designed and is locked A proxy of processes GPS mine field and on shore center is used to show the interaction of the 4 processes within the system associated to the project Additionally 2 packages mh types and sonar types are made visible so that the various data types they are exporting will be recognized as port or subprogram parameter classifiers Note that 2 other design models are not shown graphically because their role is different antenna is a generic component that is intanciated at a lower level in the design hierarchy whereas rta represents an library package used during Ada code generation STOOD AADL User Manual Ellidiss October 2011 page 23 x Stood for the AADL G Stood for AADL beta mine_hunting x File Edit Design Component Feature Tools Help design mine_hunter Requirements Graphic Design Detailed Design Checkers Code Documentation Deployment design GPS C Hood x p 605 53 weal g l EN Process being designed design amp design design on Skor gt ce design rta li eres i p design nar types gt utpui global position generic Atenna N mine hunter input global p s gt Istart mission output I mission report p input reflect F sur reverberetio ni ods ada c cpp aadi test checks E PROJECT es Pr
25. nt contextual menu Stood also allows temporarily defining a thread subcomponent within a thread component The container thread will then be automatically changed into a thread group STOOD AADL User Manual Ellidiss October 2011 page 25 x Stood for the AADL 3 4 4 AADL Data Data components created within a package are mapped to a class in the Stood model It will be sometimes more appropriate to use the UML editor to better show class structure attributes and operations and their relationships inheritance aggregation Next pictures show both views for the same model design new package blide all Hood Mn OME Er Rs STS JS or 7B QQ new data KMS az superclass erne aggregate ae design new_process mn ods ada c cpp aadi test checks rs EE COMPONENT DESCRIPTION PROVIDED INTERFACE aggregate REQUIRED INTERFACE DATAFLOWS IMPLEMENTATION ee new data em SUBCOMPONENTS ar T PROPERTIES BEHAVIOR SUBCOMPONENTS FUNCTIONAL BEHAVIOR ATTRIBUTES attribute attribute design new package lel Se A lt a a new_package S ee f gy bo Lp new_data Hi superclass L aggregate ae design new_process Interfaces new packoge nen pockoge si Operations superckess COMPONENT DESCRIPTION Constante attribute attrib PROVIDED INTERFACE lt lt Exceptions s REQUIRED INTERFACE DATAFLOWS IMPLEMENTATION m new_data gm SUBCOMPONE
26. o activate the C code generator switch the life cycle selector to the code tab Requirements Graphic Design Detailed Design mda Conran Deployment If c has been specified as the default target language then this will automatically open the C code generator Else it may be necessary to select the c tab in the property selector ods ad pr aadi test checks 4 5 Generate design documentation To enter the documentation production mode select the documentation tab in the life cycle selector Requirements Graphic Design Detaled Design Checkers Code Gran ni To create a full printable document from the current design model operate as follow e stepl select the components to be printed or select all with the appropriate button e step2 select the output format among HTML MIF for FrameMaker PDF PostScript RTF for Word or ODT For OpenOffice e step3 click on the print button This opens a standard file dialog asking an output file name to be entered Default location for generated documentation is the doc subdirectory of the current design model directory The current design directory can be opened from Stood by choosing Tools Open directory design directory in the main menu page 42 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL Stood for AADL beta mine_hunting a x File Edit Design Component Feature Tools Help design mine_hunter Re
27. ocessing 1 THREAD flow processing l flow processing 2 THREAD flow processing 2 CONNECTIONS PORT datal gt ilow processing L cons PORT input gt Flow processing L 1npuc PORT flow processing 2 dutpult gt Output PORT Flow processing 2 prod gt dataz PORT flow processing l output gt flow processing 2 inpuc PROPERTIES LOOUr 80 Position gt 361 212 719 456 END new process others THREAD FLOW processing I FEATURES cons IN DATA PORT T Flow input IN DATA PORT I external O ULDUC OUT DATA PORT T internal FLOWS aFlowPath FLOW PATH input gt output aFlowSink FLOW SINK cons PROPERTIES Dispatch Protocol gt Aperi1ocd1c SLOOd Box Position gt 590 115 G32 295 END flow processing 1 THREAD flow processing 2 FEATURES input IN DATA PORT T internal output OUI DAIA PORT I external prod OUT DATA PORT T Flow FLOWS STOOD AADL User Manual Ellidiss October 2011 page 35 x Stood for the AADL aFlowPath FLOW PATH input gt output aFlowSource FLOW SOURCE prod PROPERTIES Dispatch Protocol gt Aperiodio SPOGAL BOR Position gt 575 410 G89 565 END flow processing 2 3 10 Behavior Annex The ODS contains sections that can be used to insert AADL Behavior Annex code for Thread and Subprogram components ods ada c cpp aad test checks COMPONENT DESCRIPTION TYPE IMPLEMENTATION PROPERTIES BEHAVIOR behavior description ostate trans
28. oject file syc It is of course also possible to launch the tool from the Windows start up menu or even directly from the installation directory However in these last cases if the default initialization file is not customized new projects and design models will be created within the installation directory Stood is a multi user environment It is thus possible to launch several concurrent sessions of the tool on a same project Stood automatically manages the protection locks for the shared parts of the project To close a session simply use File Quit in the main menu STOOD AADL User Manual Ellidiss October 2011 page 7 x Stood for the AADL 2 3 Overview of Stood After the initialization process has completed Stood main window is displayed This paragraph provides information about the organization and the main features of this window This window is composed of the following parts e a window title showing a customizable message and the name of the current project e amain menu bar grouping all the main non graphical possible user actions e aproject area showing the structure of the current project e acomponent area showing details for the selected component in the Project area e a property selector acting as a filter for components details G Stood for AADL beta mine_hunting MEX File Edit Design Component Feature Tools Help window title design mine_hunter design GPS design mh ty
29. oject Description output reflected signal Project Sketch Pr List of Requirements Design Tree Inheritance Tree el Proxy of a remote process i Proxy of a used package LSave text Project Description This project simulates an underwater mine hunting system The system is composed of a mine hunting ship the mine_hunter a mission base where data is collected the on shore center a global positioning system the GPS 3 4 2 AADL Threads To create a new thread in a process or a thread group use the new AADL component button in the tool bar or the New sub component contextual menu To create a new thread in a package only use the New sub component contextual menu as the button always creates a data component page 24 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL Exit New sub component Thread Group Rename ee Change into subpro Data Undelete Open state diagram Threads are created with aperiodic dispatch protocol It is however possible to specify a periodic or sporadic dispatch protocol with the Change into contextual menu FEN ONCE r ew thread Enter Rename DEP Change into Delete 7 Open state diagram Periodic Thread Sporadic Thread Subprogram Data 3 4 3 AADL Thread groups To create a new thread group in a process a thread group or a package use the New sub compone
30. pes design mine field design mine hunter mine hunter sonar le p selecta op center output global postrrer nav center localization mine field mine hunter on shore center p finput global pos tool bar GPS gt fstart mission output_mission_repo output puls mh types Se p inp rehectic AA In n rderation sonar types 4 marg pi design on_shore_center design rta obo AR ao fdacinn i canar trnac j onar_ty main re ada c cpp aadl est checks nine E COMPONENT SoG edad yeverberatioh r DESCRIPTION output rer eflected signal b linput incidert signal E PROBLEM Statement of the Problem onshore center Sketch of the Problem en Referenced Documents alement of the Problem The mine hunter operates on a mine field to detect localize and classify underwater mines PROPERTIES Identified targets are reported to the on shore center PORT GROUPS text input REQUIRED INTERFACE DATAFLOWS area IMPLEMENTATION GENERATION page 8 STOOD AADL User Manual Ellidiss October 2011 Opens the requirements traceability editor x Stood for the AADL e amain editing area where the various graphical and textual editors are plugged e a text input area that is displayed when a graphical editor is shown in the Main editing area e a contextual and customizable tool bar e a project lif
31. properties List of AADL port groups List of AADL ports and subprograms Informal description of this port Formal declaration of this port Compute Execution Time property List of subcomponents Connections down the hierarchy for the AADL Informal description for the operational modes State diagram for the operational modes AADL generation options STOOD AADL User Manual Ellidiss October 2011 page 13 x Stood DD for the AADL The colorized gauge at the left side of an ODS section shows the completeness of the design model A red gauge means that the corresponding section is still empty a green gauge means that some information is available and a yellow gauge for a non terminal section states that there are still empty subsections The ODS text offers the following contextual menu Items of this menu may be greyed if they are not appropriate for the current selection in the list Contextual help for selected ODS section Storage information about selected ODS section Help es vo i Definition eta information about selected ODS section Print for diagrams only Create a new feature or property Rename Delete Rename feature or property Delete undelete feature or property Several filters may be defined on the global ODS descriptor Next picture shows the filtered view that is shown after textual AADL code has been generated It is also possible to access this view at any time by choosing the aadl tab in the
32. property selector The AADL tab is selected COMPONENT Er PROVIDED INTERFACE EL IMPLEMENTATION GENERATION Eu pragmas encode file header Textual AADL code generation options AADL CODE AADL generation log file w extraction messages reverse messages mm aad AADL generated file ca makefile ga prolog description page 14 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL 3 Edition of AADL models 3 1 Load existing models 3 1 1 Open a project Design models are related to a project A given design model may belong to several projects but it 1s always necessary to select and open a project before loading a design model In Stood terminology the current project is called the system configuration often named system to make it short Although there are many similarities a Stood system doesn t always match an AADL system Use File Open project in the main menu to open an existing project This opens a standard file navigator asking a Stood system configuration file to be selected These files contain a list of references to design models and are identified by a syc file extension When a project has been properly loaded its name is displayed in the window title and the list of the design models that are visible within this project is shown in the top left area of Stood This area is called the project area If the project is empty or if the design model references cannot be resolved t
33. quirements Graphic Design Detailed Design Checkers Code Documentation Deployment design GPS 2 design mh types design mine field amp design mine hunter default mine hunter default sonar default transmitter default pulse generator default power amplifier trans array receiver detector classifier sequencer op center Configuration List of Reqhyements Design Tree Inheritance Tree 1 or click on AADL Diagram E COMPONENT select all instance parameter button in the DESCRIPTION PROBLEM tool bar Statement of 3 start printing 2 select the output format XX XX XX XX CU On O Qi nav center mm Sketch ofthe Problem K Incalizatinn Referenced Documents ods ada c cpp aadi test checks SOLUTION Sort components alphabetically General Strategy Sketch ofthe Solution liek h Identification of Subcomponents Breadth traversal 1 click on the printer AADL Diagram icon to enable Justification of Design Decisions as fi h E PROVIDED INTERFACE printing tor eac H PROPERTIES individual component real time properties property name property description property definition aadl constant pre declaration ada constant definition ada constant definition c constant definition cpp um am MART AMAI IMA Depth traversal Alphabetic traversal STOOD AADL Us
34. raceability matrix e schedulability analysis basic test only e design architecture metrics e HOOD rules compliancy e AADL legality rules compliancy under development To activate one of these verification tools perform the following sequence of actions e step select the set of rules to verify in the component area e step2 click on the check design button in the tool bar e step3 select a result file in the component area If a red gauge is shown this means that the result file 1s empty and that there is no error page 38 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL Gi Stood for AADL beta mine_hunting ok File Edit Design Component Feature Tools Help Requirements Graphic Design Detailed Design Checkers Code Documentation Deployment design GPS F Dan s AADL ADA C C Pseudo design mh_types SE design mine field language aad sort by Component upto date yes amp design mine hunter mine_hunter mine_field on_shore_center GPS mh_types sonar_types 2 Press check design on_shore_center lt pa gt mine desi n button in design rta 1 Select the set of 11579 OS 8 design sonar types i lt pa gt position the tool bar 5 rules to verify lt pa gt raw signal lt pa gt receive lt pa gt reflection is used by ig symbol KKK generic antenna fee ods ada c cpp aadi test checks check messages aadl checker E DESIGN VERIFI
35. rmation rules Use Design New design from ada resp c in the main menu or New from ada resp c contextual menu of the project area to create a new design model from legacy Ada resp C code This opens a standard file navigator asking an Ada resp C file to be selected Files are recognized to be Ada resp C files if they have a ads or adb resp h or c extension The result of this action will be to analyse all the source files located within the same directory as the selected file and to create a design model having the same name as the selected file Note that Stood makes the assumption that the selected file has the same name as the main source code file to be imported The newly created design model will be added to the list in the project area but will not be automatically loaded Please refer to paragraph 3 1 2 to know how to do to load a design model 3 3 AADL packages To create anew AADL package use Design New design aadl package in the main menu A package represents a library of reusable components Unlike within a process these page 18 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL components are not instantiated If no component has been defined inside a package then a dummy data component type will be generated to comply with the AADL syntax PACKAGE empty package PUBLIC DATA void END void END empty package Although the AADL specifies a flat represent
36. s for Stood A Stood working directory should ideally contain e A link Windows shortcut or Unix shell script to the Stood executable file Windows shortcuts must have their start up property set to the current working directory so that new models will be created there e a stood ini on Windows or stoodre On Unix initialization file containing only the user s properties that differ from the default initialization file located in the installation directory e aset of project files and design model directories A typical empty Stood working directory on Windows looks like as shown in the following pictures page 6 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL C Tni Stood workdir ole dr Fichier Edition Affichage Favoris Outils Q Pr c dente Rechercher Adresse C Tni Stood workdir men de stood exe RE G n ral Raccourci Compatibilit al stood exe Ca Type de cible Application Emplacement bin w32 Cible C Tni Stood bin w32 stood exe D marrer dans CATniStoodlworkdir Touche de Aucun ES raccourci Ex cuter Fen tre normale Commentaire Rechercher la cible Changer d ic ne 2 2 Start and quit a session It is recommended to launch Stood from one of the pre set working directories refer to paragraph 2 1 by double clicking on the Stood executable shortcut or on a local pr
37. tood AADL code generator automatically introduces a few specific properties Generation of these properties may be avoided by using the pragma no_ graphics property set Stood is Box Position aadlotring applies to system data subprogram thread thread group STOOD AADL User Manual Ellidiss October 2011 page 31 x Stood for the AADL process memory processor bus device Link Position aadlstring applies to connections end Stood 3 8 AADL modes Stood offers an incomplete support for AADL modes It is possible graphically define the operational modes of a process thanks to a state transition diagram However There is currently no support of the in modes statements Use the mode diagram button of the tool bar or choose open state diagram in the contextual menu when the main process component is selected in the AADL diagram The process must provide one or several event ports that may be used as transition triggers Enter Few _ Drees Rename Change into Delete Open state diagram When the state transition diagram is open a specific tool bar is available to create an initial mode standard modes and transitions When a transition is selected use the select transition event button to associate one of the provided event ports of the process page 32 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL E IMPLEMENTATION SUBCOMPONENTS te PORT GROUPS PORTS B
38. trial projects With the AADL customization of Stood it is possible to e Import legacy specifications written in textual AADL aad1 files e Edit graphically new or imported AADL models and generate corresponding textual AADL specification e Transform software AADL architecture AADL Process into HOOD designs to perform detailed software design activities e Produce design documentation Ada and C C source code from design models This manual is not a complete User Manual for Stood It only provides a brief description of the main features that can be useful for AADL projects developments STOOD AADL User Manual Ellidiss October 2011 page 5 x Stood for the AADL 2 General information 2 1 Installation of Stood Stood can be easily and quickly installed on a Windows or a Unix workstation On Windows follow the instructions given by the guided installation program On Unix uncompress and expand the installation archive in an appropriate directory On Windows default installation procedure will associate the following file extensions in the registry syc Stood project file sto Stood design model file sts Stood command file In addition to this installation it is recommended but not mandatory to also create one or several working directories properly separated from the installation directory These working directories will be used to store user s models and set up user s specific initialization propertie
39. us ports that are shown in the example below have the following Stood port or subpg declaration in their ODS section In process new process datal aFlowSink in T Flow inpul allowPath amp in T external output r lovPatn amp Out T external dataz aFlowsource out T Flow In thread flow processing 1 cons aFlowSink in T Flow input FlowP th amp in T external CuLpUL arlowPach OL T internal In thread flow processing 2 input ablowPath an T internal output aFloWPatn 7 out I External prod aFlowSource out T Flow COMPONENT A DESCRIPTION a PROBLEM co Statement of the Problem Sketch ofthe Problem c Referenced Documents SOLUTION PROVIDED INTERFACE PROPERTIES PORT GROUPS PORTS and SUBPROGRAMS cons input mn port or subpg description lt ul w port or subpg declaration P Pg EE port or subpg declaration mu worst case execution time m output input aFlowPath in T external The AADL code that is generated is as follow page 34 STOOD AADL User Manual Ellidiss October 2011 x Stood for the AADL PROCESS new process FEATURES datal IN DATA PORT T Flow input IN DATA PORT T external output OUT DATA PORT T external dataZ OUT DATA PORT I Flow FLOWS aFlowPath FLOW PATH input gt output aFlowSource FLOW SOURCE data2 aFlowSink FLOW SINK datal END new process PROCESS IMPLEMENTATION new process others SUBCOMPONENTS flow pr

Stood 5.3 AADL User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents