A comparison of techniques for the specification of external system behavior
Communications of the ACM
Object lifecycles: modeling the world in states
Object lifecycles: modeling the world in states
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Modeling Reactive Systems with Statecharts: The Statemate Approach
Modeling Reactive Systems with Statecharts: The Statemate Approach
An Environment for Building a System out of its Requirements
Proceedings of the 19th IEEE international conference on Automated software engineering
From Requirements Change to Design Change: A Formal Path
SEFM '04 Proceedings of the Software Engineering and Formal Methods, Second International Conference
Execution of natural language requirements using State Machines synthesised from Behavior Trees
Journal of Systems and Software
| Hi-index | 0.00 |
Individual functional requirements represent fragments of behavior, while a design that satisfies a set of functional requirements represents integrated behavior. This perspective admits the prospect of constructing a design out of its requirements. A formal representation for individual functional requirements, called behavior trees makes this possible. Behavior trees, derived by rigorous translation from individual functional requirements stated in natural language, may be composed, one at a time, to create an integrated design behavior tree (DBT). We can then transition from this problem domain representation directly and systematically to a solution domain representation of the component architecture of the system and the behavior designs of the individual components that make up the system – both are emergent properties of a DBT. The Early Warning System case study is used to illustrate this genetic design method, and show its potential for defect detection and control of complexity compared with the Statechart design method.