Abstract
Requirements definition and design decisions are highly coupled for mechatronic systems, and heavily influenced by prior knowledge. Upfront engineering of requirements and design is often addressed by inefficient, ad-hoc iterative methods. We propose a methodology to perform concurrent engineering of high level requirements and design along with prior knowledge by using a "common constraint framework" to describe the requirements, design and knowledge precisely. Then an upfront symbolic simultaneous analysis of all the constraints allows us to identify infeasibilities.
Next we define a design architecture that can be used to extend the above constraint framework to include temporal aspects leading to an ability to define low level requirements and test scenarios under which these requirements can be verified. Importantly the low level requirements and test scenarios can be specified independent of the final implementation. These provide the critical link between upfront requirements engineering process and downstream implementation verification.
Finally we define "mappings" between implementations and the design architecture that allows definitions of executable tests in the implementation environment that in turn can be used to verify the low level requirements.
We demonstrate the above methodologies using the tool DRIP.
- Markus Völter, Bernd Kold, "An integrated specification environment for structural, behavioral and non-functional aspects of technical systems", http://system-specification.com/, 2015.Google Scholar
- Markus Völter, "DSL Engineering: Designing, Implementing and Using Domain-Specific Languages", 2013, http://dslbook.orgGoogle Scholar
- Swaminathan Gopalswamy, "eXtreme Model Based Development", MBD Conference, Chubu, Japan, 2014 http://www.cybernet.co.jp/event/mbdchubu/documents/pdf/pmb3-2.pdfGoogle Scholar
- Meta Programming System: https://www.jetbrains.com/mps/Google Scholar
- mbeddr: mbeddr.comGoogle Scholar
- The Mathworks, MATLAB/Simulink R2014a, Natick, MAGoogle Scholar
Recommendations
Usability requirements for requirement engineering tools
IHM '14: Proceedings of the 26th Conference on l'Interaction Homme-MachineRequirement engineering (RE) tools are necessary for several reasons: they allow engineers to manage an increasing amount of information, to maintain traceability between requirements, solution and tests, and to evaluate requirement change impact on the ...
A process for goal oriented requirement engineering
SE '08: Proceedings of the IASTED International Conference on Software EngineeringThere is an increasing emphasis and use of "goals" within requirements engineering. Work done in Goal-Oriented Requirement Engineering (GORE) have also been applied effectively in Business Process Re-engineering (BPR), specifically dealing with NFRs, ...






Comments