Title | ||
---|---|---|
Up and out: scaling formal analysis using model-based development and architecture modeling. |
Abstract | ||
---|---|---|
Systems are naturally constructed in hierarchies in which design choices made at higher levels of abstraction ``flow down'' to requirements on system components at lower levels of abstraction. Thus, whether an aspect of the system is a design choice or a requirement depends largely on one's vantage point within the hierarchy of system components. Furthermore, systems are often constructed middle-out rather than top-down; compatibility with existing systems and architectures, or availability of specific components influences high-level requirements. We believe that requirements and architectural design should be more closely aligned: that requirements models must account for hierarchical system construction, and that architectural design notations must better support specification of requirements for system components. In this presentation, I describe tools supporting iterative development of architecture and verification based on software models. We represent the hierarchical composition of the system in the Architecture Analysis & Design Language (AADL), and use an extension to the AADL language to describe requirements at different levels of abstraction for compositional verification. To describe and verify component-level behavior, we use Simulink and Stateflow and multiple analysis tools. |
Year | DOI | Venue |
---|---|---|
2013 | 10.1145/2527269.2527293 | HILT |
Keywords | Field | DocType |
hierarchical system construction,requirements model,architecture analysis,architecture modeling,architectural design notation,aadl language,design choice,system component,formal analysis,hierarchical composition,compositional verification,model-based development,architectural design,cyber physical systems | Design language,Hierarchical control system,Programming language,Computer science,Systems design,Requirements analysis,Real-time computing,Stateflow,System requirements specification,Software requirements specification,Non-functional requirement | Conference |
Volume | Issue | ISSN |
33 | 3 | 1094-3641 |
Citations | PageRank | References |
0 | 0.34 | 5 |
Authors | ||
1 |
Name | Order | Citations | PageRank |
---|---|---|---|
Michael W. Whalen | 1 | 1096 | 70.54 |