Changes between Version 4 and Version 5 of stood
- Timestamp:
- 07/28/09 08:52:44 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
stood
v4 v5 2 2 STOOD is a Software design tool that complies to both AADL and HOOD standards. AADL models can be defined to specify the complete host system of the applicative Software. Each identified AADL Process can then be refined down to target source code thanks to the HOOD detailed design process. 3 3 [[BR]] 4 4 5 [[Image(wiki:stood:img1.png)]] 5 6 == Requirements traceability == 6 7 Stood includes a simple and efficient mean to insure an up to date traceability between the System and Software models and the initial requirements, that can be imported from plain text files or remote tools: 7 8 [[BR]] 9 8 10 [[Image(wiki:stood:img2.png)]] 9 11 == Architectural Design == 10 12 Stood graphical editor is used to build architectural models of the Software and its environment (libraries, execution platform, ...). Stood graphical models do not intend to show all the details of the System or Software being developed, but aim at focusing the design effort on architectural issues. In addition, the graphical modeling languages that are supported by stood are hierarchical, which allows use of this technology for designing the architecture of large scale applications.[[BR]] 13 11 14 [[Image(wiki:stood:img3.png)]] 12 15 == Instance models == … … 16 19 Stood detailed design activity is based on the concept of HOOD Object Description Skeleton (ODS), that has been made fully customizable in order to support AADL properties ans user defined configurations. 17 20 An ODS can be attached to each component of the architectural model. At the end of the detailed design activity, the Stood model is exhaustive and can become the reference for the application, from which consistent code and documentation can be automatically produced.[[BR]] 21 18 22 [[Image(wiki:stood:img4.png)]] 19 23 == Stood design checkers == … … 27 31 * Requirements coverage analysis 28 32 In addition, user customized verification tools can be added in a "plug and play" way, so that Stood can support project specific verification activities.[[BR]] 33 29 34 [[Image(wiki:stood:img5.png)]] 30 35 == Remote analysis tools == 31 36 In addition to the design checkers that included in Stood, remote model analysis tools can easily be connected to Stood thanks to its AADL interface. Currently such a connection have already been developed with Cheddar, a powerful real-time performance analysis tool developed by the University of Brest, and another one is in progress with multi-agents real-time simulator that is developed in collaboration with Virtualys.[[BR]] 37 32 38 [[Image(wiki:stood:img6.png)]] 33 39 == Automatic code generation == 34 40 At any time during the modeling activities, it is possible to activate one of the provided automatic code generators to build a "ready to compile" set of source files and the corresponding makefile. 35 41 Supported target language are Ada, C and C++. However, support of real-time operating systems in C and C++ require some customization of the code generators that are developed with the LMP technology.[[BR]] 42 36 43 [[Image(wiki:stood:img7.png)]] 37 44 == Round-trip engineering and reverse engineering == … … 41 48 Production of documentation is an important and time-consuming activity for most projects. With Stood, it is possible to automatically generate a full design documentation that is consistent by construction with the source code that has also been generated from the same design reference. 42 49 Stood documentation tool can generate documents in PDF, HTML, RTF and MIF formats. Some existing generators can be customized and additional ones can be developed thanks to the LMP technology.[[BR]] 50 43 51 [[Image(wiki:stood:img8.png)]]
