Abstract | ||
---|---|---|
In our experience at NASA, system engineers generally follow the Twin Peaks approach when developing safety-critical systems. However, iterations between the peaks require considerable manual, and in some cases duplicate, effort. A significant part of the manual effort stems from the fact that requirements are written in English natural language rather than a formal notation. In this work, we propose an approach that enables system engineers to leverage formal requirements and automated test generation to streamline iterations, effectively \"bridging the peaks\". The key to the approach is a formal language notation that a) system engineers are comfortable with, b) is supported by a family of automated V&V tools, and c) is semantically rich enough to describe the requirements of interest. We believe the combination of formalizing requirements and providing tool support to automate the iterations will lead to a more efficient Twin Peaks implementation at NASA. |
Year | DOI | Venue |
---|---|---|
2014 | 10.1145/2593861.2593863 | TwinPeaks |
Keywords | Field | DocType |
formalization,model-based development,requirements,requirements/specifications,architecture,iteration,computer programming,model based development | Notation,Architecture,Formal language,Software engineering,Computer science,Bridging (networking),Theoretical computer science,Model-based design,Natural language,Formal notation,Computer programming | Conference |
Citations | PageRank | References |
2 | 0.36 | 9 |
Authors | ||
7 |
Name | Order | Citations | PageRank |
---|---|---|---|
Neha Rungta | 1 | 563 | 27.72 |
Oksana Tkachuk | 2 | 225 | 15.83 |
Suzette Person | 3 | 583 | 27.41 |
Jason Biatek | 4 | 12 | 1.94 |
Michael W. Whalen | 5 | 1096 | 70.54 |
Joseph Castle | 6 | 2 | 0.36 |
Karen Gundy-Burlet | 7 | 150 | 6.81 |