Abstract
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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modelling Language User Guide. Addison-Wesley, Reading (1999)
Davis, A.: A Comparison of Techniques for the Specification of External System Behav-ior, Comm. Comm. ACM 31(9), 1098–1115 (1988)
Dromey, R.G.: From Requirements to Design: Formalizing the Key Steps. In: SEFM 2003, IEEE International Conference on Software Engineering and Formal Methods (Invited Keynote Address), Brisbane, September 2003, pp. 2–11 (2003)
Dromey, R.G.: Using Behavior Trees to Model the Autonomous Shuttle System, ICSE-2004. In: 3rd International Workshop on Scenarios and State Machines: Models, Algorithms and Tools (SCESM 2004), Edinburgh (May 2004)
Dromey, R.G.: Architecture as an Emergent Property of Requirements Integration. In: ICSE-2003, Software Requirements to Architecture Workshop – STRAW 2003, Portland, USA, (May 2003)
Harel, D., Politi, M.: Modeling Reactive Systems with Statecharts. McGraw-Hill, New York (1998)
Jackson, D.: Alloy: A Lightweight Object Modelling Notation, MIT Lab. for Comp. Sci. Report (1999)
Shlaer, S., Mellor, S.J.: Object Lifecycles. Yourdon Press, New Jersey (1992)
Smith, C., Winter, K., Hayes, I., Dromey, R.G., Lindsay, P., Carrington, D.: An Environ-ment for Building a System Out of Its Requirements, Tools Track. In: 19th IEEE International Conference on Automated Software Engineering, Linz, Austria (September 2004)
Wen, L., Dromey, R.G.: From Requirements Change to Design Change: A Formal Path. In: Cuellar, J.R., Liu, Z. (eds.) SEFM 2004, IEEE International Conference on Software Engineering and Formal Methods, Beijing, September 2004, pp. 104–113 (2004)
Winter, K.: Formalising Behavior Trees with CSP. In: Boiten, E.A., Derrick, J., Smith, G.P. (eds.) IFM 2004. LNCS, vol. 2999, pp. 148–167. Springer, Heidelberg (2004)
Woolfson, A.: Life Without Genes. Flamingo, London (2000)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2005 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Dromey, R.G. (2005). Genetic Design: Amplifying Our Ability to Deal With Requirements Complexity. In: Leue, S., Systä, T.J. (eds) Scenarios: Models, Transformations and Tools. Lecture Notes in Computer Science, vol 3466. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11495628_6
Download citation
DOI: https://doi.org/10.1007/11495628_6
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-26189-6
Online ISBN: 978-3-540-32032-6
eBook Packages: Computer ScienceComputer Science (R0)