This content is not included in your SAE MOBILUS subscription, or you are not logged in.

Requirement Analysis and Development using MATLAB Models

Journal Article
2009-01-1548
ISSN: 1946-4614, e-ISSN: 1946-4622
Published April 20, 2009 by SAE International in United States
Requirement Analysis and Development using MATLAB Models
Sector:
Citation: Yang, J., Bauman, J., and Beydoun, A., "Requirement Analysis and Development using MATLAB Models," SAE Int. J. Passeng. Cars – Electron. Electr. Syst. 2(1):430-437, 2009, https://doi.org/10.4271/2009-01-1548.
Language: English

Abstract:

Requirements development and analysis for automotive electronics products have been found to be tremendously challenging to both OEMs and suppliers. Besides ambiguity, incompleteness, conflicts and other pitfalls commonly seen in requirement specifications, in some cases, a requirements document for a new electronics product may even not exist and may need to be developed from scratch. Analysis reveals that generic model-based approaches and toolsets presently available lack support for requirements development while facilitating all other development activities across the entire product development cycle.
In this work, we describe a model-based development methodology centering on requirements development, engineering, and management while supporting other development activities including requirements analysis and clarification, rapid prototyping, simulation, verification and validation, automatic code generation, and SIL/HIL testing. The methodology leverages the MATLAB® toolset features of visual conceptualization, rapid prototyping, simulation and ease of accessing model property data with m-scripts, not only to improve the traditional requirements development activities for understanding customer’s needs, abstraction and definition from concepts, requirements document elaboration, but also to make it possible to maintain a set of executable models that can be readily simulated and verified throughout the entire development process. We demonstrate that the methodology shall be particularly suitable to developing requirements from scratch and/or evolving a high-level requirements document to detail-level requirements specifications.