Behavior Engineering - A Scalable Modeling and Analysis Method
- 1 September 2010
- conference paper
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15510255,p. 31-40
- https://doi.org/10.1109/sefm.2010.12
Abstract
The impact of failing to develop a shared understanding of the requirements describing and constraining large, complex projects and programs with many, possibly distributed, stakeholders and suppliers is enormous. Traditional engineering methods provide little in the way of taming complexity when synthesising, analysing and communicating the requirements of such projects. The Behavior Engineering method, developed at Griffith University, and employed on a number of large, complex and nationally critical defence, aerospace, transport and government projects and programs addresses the problems of scale and complexity head on. The Behavior Engineering method is presented in this paper as an efficient and effective method for modeling, analysing, evaluating and communicating large requirements specifications comprising thousands of requirements as well as a method that facilitates the synthesis of requirements from operational scenarios. It is demonstrated through analysis of industry data, that Behavior Engineering facilitates the development and communication of a deep, accurate and holistic understanding of the system needs, significantly reducing the risk of failure to capture and preserve intent in the development of large and complex systems.Keywords
This publication has 4 references indexed in Scilit:
- Pick and Mix: Selecting Flowering Plants to Meet the Requirements of Target Biological Control InsectsPublished by Wiley ,2012
- Formal methods: the very idea: Some thoughts about why they work when they workScience of Computer Programming, 2002
- The Team Software Process (TSP)Published by Defense Technical Information Center (DTIC) ,2000
- Comparing Detection Methods For Software Requirements Inspections: A Replication Using Professional SubjectsEmpirical Software Engineering, 1998