This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Executable Specs: What Makes One, and How are They Used?
Technical Paper
2006-01-1357
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
Model-based systems development relies upon the concept of an executable specification. A survey of published literature shows a wide range of definitions for executable specifications [1, 2, 3, 4, 5, 6, 7, 8, 9 and 10]. In this paper, we attempt to codify the essential starting elements for a complete executable specification-based design flow. A complete executable specification that includes a functional model as well as test cases, in addition to a traditional prose document, is needed to transfer requirements from a customer to a supplier, or from a systems engineer to electrical hardware and software engineers. In the complete form demonstrated here, sub-components of a functionally-decomposed system manifest as modular reuse blocks suitable for publication in functional libraries. The overarching definition provided by product architecture and by software architecture must also be harmoniously integrated with design and implementation. Using seven specific automotive examples, we illustrate effective ways in which executable specifications have been used in production-ready applications. Benefits of model-based development are captured, including earlier and more thorough testing, automatic document generation, and autocode generation.
Recommended Content
| Technical Paper | Challenges in Managing ISO 26262 Software Development Projects |
| Technical Paper | “Standardizing the Datasheet” Towards Auto-Code Generation Efficiency |
| Technical Paper | Better Reuse of Architecture Models: Profits and Costs |
Authors
Topic
Citation
Schubert, P., Vitkin, L., and Winters, F., "Executable Specs: What Makes One, and How are They Used?," SAE Technical Paper 2006-01-1357, 2006, https://doi.org/10.4271/2006-01-1357.Also In
SAE 2006 Transactions Journal of Passenger Cars: Electronic and Electrical Systems
Number: V115-7; Published: 2007-03-30
Number: V115-7; Published: 2007-03-30
References
- “Model Based Systems Development in Automotive,” Mutz M. Huhn M. Goltz U. Kromke C. SAE World Congress 2002, paper 03B-128
- “Zero Hand Coding Approach for Controller Development,” Saikalis G. Oho S. Zunft S. “SAE 2002 World Congress, paper 2002-01-0142
- “Trends of Future Powertrain Development and the Evolution of Powertrain Control Systems,” Ueda T. Ohata A. SAE Convergence 2004, 2004-21-0063
- “Model-Based Tools Update,” The Hansen Report on Automotive Electronics June 2001 14 5
- “A System-Design Methodology: Executable-Specification Refinement,” Gajski D. Vahid F. Narayan S. European Design and Test Conference, 1994 Proceedings March 1994
- “Systematic Model-Based Testing of Embedded Automotive Software” Conrad M. Frey I. Sadeghipour S. Electronics Notes in Theoretical Computer science 111 2005 13 26
- “Incorporating Autocode Technology into Software Development Process” Vitkin L. Jestin T.K. ICSE 2004 51 57
- “Managing the Challenges of Automotive Embedded Software Development Using Model-Base Methods for Design and Specification” Yeaton M SAE 2004-01-0720
- “Integration of the Code Generation Approach in the Model-Based Development Process by Means of Tool Certification” Sturmer I. Journal of Integrated Design and Process Science 8 2 1 11 2004
- “Automotive Software development: A model Based Approach” Rappl M. Braun P. von der Beek M. Schroder C. SAE 2002-01-0875
- “Design and Implementation of a Rollover Algorithm in Production,” Schubert P. dSPACE User Conference 2004
- “Design Process Changes Enabling Rapid Development” Winters F Mielenz C Hellestrand G Convergence 2004-21-0085
- “Reuse Methodology Manual For System On Chip Designs” Keating M. Bricaud P.