From Domain to Requirements
We first present a summary of essentials of domain engineering, its motivation, and its modelling of abstractions of domains through the modelling of the intrinsics, support technologies, management and organisation, rules and regulations, scripts, and human behaviour of whichever domain is being described.
Then we present the essence of two (of three) aspects of requirements: the domain requirements and the interface requirements prescriptions as they relate to domain descriptions and we survey the basic operations that “turn” a domain description into a domain requirements prescription: projection, instantiation, determination, extension and fitting. An essence of interface requirements is also presented: the “merging” of shared entities, operations, events and behaviours of the domain with those of the machine (i.e., the hardware and software to be designed).
KeywordsRequirement Engineering Link State Domain Engineering Domain Extension Toll Road
Unable to display preview. Download preview PDF.
- 1.Bjørner, D.: Software Engineering: Domains, Requirements and Software Design. Texts in Theoretical Computer Science, the EATCS Series, vol. 3. Springer, Heidelberg (2006)Google Scholar
- 3.Bjørner, D.: Domain Engineering. In: Boca, P., Bowen, J. (eds.) BCS FACS Seminars, London, UK. Lecture Notes in Computer Science, the BCS FAC Series, pp. 1–42. Springer, Heidelberg (to appear, 2008)Google Scholar
- 4.Jackson, M.A.: Problem Frames — Analyzing and Structuring Software Development Problems. Addison–Wesley Longman Publishing Co., Inc, Boston, MA (2001)Google Scholar