Genetic Design: Amplifying Our Ability to Deal With Requirements Complexity

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.

[1]  Kirsten Winter,et al.  Formalising Behaviour Trees with CSP , 2004, IFM.

[2]  Peter A. Lindsay,et al.  An environment for building a system out of its requirements , 2004, Proceedings. 19th International Conference on Automated Software Engineering, 2004..

[3]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[4]  Adrian Woolfson,et al.  Life Without Genes , 2000 .

[5]  R. Geoff Dromey,et al.  From requirements to design: formalizing the key steps , 2003, First International Conference onSoftware Engineering and Formal Methods, 2003.Proceedings..

[6]  David Harel,et al.  Modeling Reactive Systems With Statecharts : The Statemate Approach , 1998 .

[7]  R. G. Dromey Using behavior trees to model the Autonomous Shuttle System , 2004, ICSE 2004.

[8]  Lian Wen,et al.  From requirements change to design change: a formal path , 2004, Proceedings of the Second International Conference on Software Engineering and Formal Methods, 2004. SEFM 2004..

[9]  강문설 [서평]「The Unified Modeling Language User Guide」 , 1999 .

[10]  Alan M. Davis,et al.  A comparison of techniques for the specification of external system behavior , 1988, CACM.

[11]  Peter A. Lindsay,et al.  An environment for building a system out of its requirements , 2004 .

[12]  Daniel Jackson,et al.  Alloy: a lightweight object modelling notation , 2002, TSEM.