Skip to main content

Domain Engineering: a “Radical Innovation” for Software and Systems Engineering?

A Biased Account

  • Chapter
Verification: Theory and Practice

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 2772))

Abstract

Some facts: Before software and computing systems can be developed, their requirements must be reasonably well understood. Before requirements can be finalised the application domain, as it is, must be fairly well understood.

Some opinions: In today’s software and computing systems development very little, if anything is done, we claim, to establish fair understandings of the domain. It simply does not suffice, we further claim, to record assumptions about the domain when recording requirements. Farmore radical theories of application domains must be at hand before requirements development is even attempted.

In this presentation we advocate a strong rôle for domain engineering. We argue that domain descriptions are far more stable than are requirements prescriptions for support of one or another set of domain activities. We further argue, that once, given extensive domain descriptions, it is comparatively faster to establish trustworthy and stable requirements than it is today. We finally argue that once we have a sufficient (varietal) collection of domain specific, ie. related, albeit distinct, requirements, we can develop far more reusable software components than using current approaches.

Thus, in this contribution we shall reason, at a meta-level, about major phases of software engineering: Domain engineering, requirements engineering, and software design.

We shall suggest a number of domain and requirements engineering as well as software design concerns, stages and steps, notably: Domain facets, including domain intrinsics, support technologies, management & organisation, rules & regulations, as well as human behaviour. Requirements: Domain requirements, interface requirements, and machine requirements. Specifically: Domain requirements projection, determination, extension, and initialisation.

We shall then proceed to “lift” our methodological concerns to encompass the more general ones of abstraction and modelling; of informal as well as formal description; of the more general issues of documentation: Informative, descriptive/prescriptive, and analytical; and hence of the importance of semiotics: Pragmatics, semantics, and syntax. The paper concludes with a proposal for a ‘Grand Challenge’ for computing science [62, 89, 19].

This paper was first drafted in connection with a US DoD Workshop held at Venezia, Italy, October 7-1, 2002. Sections of the present paper relate to the Call for that Workshop.

The research behind and the presentation of this paper is partially, respectively fully funded under the 5th EU/IST Framework Programme (http://www.cordis.lu/fp5/home.html) of the European Commission, Contract Reference IST-2001-33123: CoLogNET: Network of Excellence in Computational Logic: http://www.eurice.de/colognet/

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Special Issue on Scenario Management. IEEE Trans. on Software Engineering, December 1998.

    Google Scholar 

  2. G. Abowd, R. Allen, and D. Garlan. Using style to understand descriptions of software architecture. SIGSOFT Software Engineering Notes, 18(5):9–20, December 1993.

    Article  Google Scholar 

  3. G. Abowd, R. Allen, and D. Garlan. Formalizing style to understand descriptions of software architecture. ACM Transactions on Software Engineering and Methodology, 4(4):319–364, Oct 1995.

    Article  Google Scholar 

  4. J.-R. Abrial. The B-Book: Assigning Programs to Meanings. Cambridge University Press, 1996.

    Google Scholar 

  5. R. Allen and D. Garlan. A formal approach to software architectures. In IFIP Transactions A (Computer Science and Technology); IFIP Wordl Congress; Madrid, Spain, volume vol.A-12, pages 134-141, Amsterdam, Netherlands, 1992. IFIP, North Holland.

    Google Scholar 

  6. R. Allen and D. Garlan. Formalizing architectural connection. In 16th International Conference on Software Engineering (Cat. No.94CH3409-0); Sorrento, Italy, pages 71-80, Los Alamitos, CA, USA, 1994. IEEE Comput. Soc. Press.

    Google Scholar 

  7. R. Allen and D. Garlan. A case study in architectural modeling: the AEGIS system. In 8th International Workshop on Software Specification and Design; Schloss Velen, Germany, pages 6-15, Los Alamitos, CA, USA, 1996. IEEE Comput. Soc. Press.

    Google Scholar 

  8. R. Barden, S. Stepney, and D. Cooper. Z in Practice. BCS Practitioner Series. Prentice Hall, 1994.

    Google Scholar 

  9. J. Bicarregui, J. Fitzgerald, P. Lindsay, R. Moore, and B. Ritchie. Proof in VDM: A Practitioner’s Guide. FACIT. Springer-Verlag, 1994. ISBN 3-540-19813-X.

    Google Scholar 

  10. J. C. Bicarregui, J. S. Fitzgerald, R. Moore, and B. Ritchie. Proof in VDM: Reader’s Notes. The Universities of Newcastle upon Tyne and Manchester, and the Rutherford Appleton Laboratory, UK, 1994. Hardcopy available from JSF at The Dept. of Computing Science, University of Newcastle upon Tyne, NE1 7RU, UK, or from BR or JCB at The Informatics Dept., Rutherford Appleton Laboratory, Oxfordshire OX11 0QX, UK. Compressed Postscript is available by ftp from ftp.cs.man.ac.uk in directoty/pub/Proof-in-VDM.

  11. D. Bjøner and C. Jones, editors. Formal Specification and Software Development. Prentice-Hall International, 1982.

    Google Scholar 

  12. D. Bjørner. Prospects for a Viable Software Industry — Enterprise Models, Design Calculi, and Reusable Modules. In First ACM Japan Chapter Conference, Singapore, March 7–9 1994. World Scientific Publ. Appendix in collaboration with Søren Prehn and Dong Yulin.

    Google Scholar 

  13. D. Bjørner. FISH: A Fisheries Infrastructure — Hardware/Software Concept. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 1998. This document provides a basis for an M.Sc. Thesis project carried out by Audur Thorun Rügnvaldsdottir, Sept. 1998 — Aug. 1999.

    Google Scholar 

  14. D. Bjørner. A Triptych Software Development Paradigm: Domain, Requirements and Software. Towards a Model Development of A Decision Support System for Sustainable Development. In E.-R. Olderog and B. Steffen, editors, Festschrift to Hans Langmaack: Correct Systems Design: Recent Insight and Advances, volume 1710 of Lecture Notes in Computer Science, pages 29-60. University of Kiel, Germany, Springer-Verlag, October 1999. Postscript document8.

    Google Scholar 

  15. D. Bjørner. Project Information, Monitoring and Control Systems — A Domain Analysis. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 1999.

    Google Scholar 

  16. D. Bjørner. Domain Modelling: Resource Management Strategics, Tactics & Operations, Decision Support and Algorithmic Software. In J. Davies, B. Roscoe, and J. Woodcock, editors, Millenial Perspectives in Computer Science, Cornerstones of Computing (Ed.: Richard Bird and Tony Hoare), pages 23-40, Houndmills, Basingstoke, Hampshire, RG21 6XS, UK, 2000. Palgrave (St. Martin’s Press). An Oxford University and Microsoft Symposium in Honour of Sir Anthony Hoare, September 13-14, 1999. Postscript document9.

    Google Scholar 

  17. D. Bjørner. Formal Software Techniques in Railway Systems. In E. Schnieder, editor, 9th IFAC Symposium on Control in Transportation Systems, pages 1-12, Technical University, Braunschweig, Germany, 13-15 June 2000. VDI/VDE-Gesellschaft Mess-und Automatisieringstechnik, VDI-Gesellschaft für Fahrzeug-und Verkehrstechnik. Invited talk. Postscript document10.

    Google Scholar 

  18. D. Bjørner. Domain Models of “The Market” — in Preparation for E-Transaction Systems. In Practical Foundations of Business and System Specifications (Eds.: Haim Kilov and Ken Baclawski), page 34 pages, The Netherlands, December 2002. Kluwer Academic Press.

    Google Scholar 

  19. D. Bjørner. UToPiA: Coherent Sets of Computing Systems Development Methods, A Grand Challenge for Computing Science, August 2002.

    Google Scholar 

  20. D. Bjørner. Domain Engineering — A Prerequisite for Requirements Engineering — Principles and Techniques. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 29, 23, 21, 24, 27, 28, 22]. DRAFT Postscript document.

    Google Scholar 

  21. D. Bjørner. E-Business. Towards a Domain Theory for Work Flow Systems. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 20, 29, 23, 24, 27, 28, 22].

    Google Scholar 

  22. D. Bjørner. Financial Service Institutions: Banks, Securities Trading, Insurance, &c. Towards a Domain Theory for Work Flow Systems. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 20, 29, 23, 21, 24, 28, 27].

    Google Scholar 

  23. D. Bjørner. Health-care Systems. Towards a Domain Theory for Work Flow Systems. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 20, 29, 21, 24, 27, 28, 22].

    Google Scholar 

  24. D. Bjørner. Logistics. Towards a Domain Theory for Work Flow Systems. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Pe-tersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 20, 29, 23, 21, 27, 28, 22].

    Google Scholar 

  25. D. Bjørner. Models, Semiotics, Documents and Descriptions — Towards Software Engineering Literacy. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [26, 20, 29, 23, 21, 24, 27, 28, 22]. DRAFT Postscript document.

    Google Scholar 

  26. D. Bjørner. Principles and Techniques of Abstract Modelling — Some Basic Classifications. — Towards a Methodology of Software Engineering. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 20, 29, 23, 21, 24, 27, 28, 22]. DRAFT Postscript document.

    Google Scholar 

  27. D. Bjørner. Projects & Production: Planning, Plans & Execution. Towards a Domain Theory for Work Flow Systems. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 20, 29, 23, 21, 24, 28, 22].

    Google Scholar 

  28. D. Bjørner. Railways Systems: Towards a Domain Theory. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 20, 29, 23, 21, 24, 27, 22].

    Google Scholar 

  29. D. Bjørner. Requirements Engineering — Some Principles and Techniques — Bridging Domain Engineering and Software Design. Technical report, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, 2003. This paper is one of a series of papers currently being submitted for publication: [25, 26, 20, 23, 21, 24, 27, 28, 22]. DRAFT Postscript document.

    Google Scholar 

  30. D. Bjørner. The SE Book: Principles and Techniques of Software Engineering, volume I: Abstraction & Modelling (750 pages), II: Descriptions and Domains (est.: 500 pages), III: Requirements, Software Design and Management (est. 450 pages). [Publisher currently (June 2003) being negotiated], 2003–2004.

    Google Scholar 

  31. D. Bjørner, C. George, and S. Prehn. Scheduling and Rescheduling of Trains, chapter 8, pages 157-184. Industrial Strength Formal Methods in Practice, Eds.: Michael G. Hinchey and Jonathan P. Bowen. FACIT, Springer-Verlag, London, England, 1999. Postscript document11.

    Google Scholar 

  32. D. Bjørner, D. Y. Lin, and S. Prehn. Domain Analyses: A Case Study of Station Management. In KICS’94: Kunming International CASE Symposium, Yunnan Province, P. R. of China. Software Engineering Association of Japan, 16–20 November 1994.

    Google Scholar 

  33. D. Bjørner, S. Prehn, and C. W. George. Formal Models of Railway Systems: Domains. Technical report, Dept. of IT, Technical University of Denmark, Bldg. 344, DK-2800 Lyngby, Denmark, September 23 1999. Presented at the FME Rail Workshop on Formal Methods in Railway Systems, FM’99 World Congress on Formal Methods, Toulouse, France. Avaliable on CD ROM. Postscript document12.

    Google Scholar 

  34. D. Bjørner, S. Prehn, and C. W. George. Formal Models of Railway Systems: Requirements. Technical report, Dept. of IT, Technical University of Denmark, Bldg. 344, DK-2800 Lyngby, Denmark, September 23 1999. Presented at the FME Rail Workshop on Formal Methods in Railway Systems, FM’99 World Congress on Formal Methods, Toulouse, France. Avaliable on CD ROM. Postscript document13.

    Google Scholar 

  35. D. Bjørner, V. Rosario, and M. Helder. A Normative Model of Concrete Banking Operations — Banking Rules & Regulations and Staff/Client Behaviours. Research, Informatics and Mathematical Modelling, Building 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs.Lyngby, Denmark, June 1998. (Need be revised: Some typos etc.!).

    Google Scholar 

  36. L. Bottaci and J. Jones. Formal Specification Using Z: A Modelling Approach. International Thomson Publishing, London, 1995.

    Google Scholar 

  37. J. P. Bowen. Formal Specification and Documentation Using Z: A Case Study Approach. International Thomson Computer Press, 1996.

    Google Scholar 

  38. A. Bryant and L. Semmens, editors. Methods Integration, Electronic Workshops in Computing. Springer-Verlag, 1996.

    Google Scholar 

  39. M. J. Butler. Feature interaction analysis using Z. Åbo Akademi University, Finland, 1994.

    Google Scholar 

  40. Z. Chaochen and M. R. Hansen. Duration Calculus: A formal approach to real-time systems. Monographs in Theoretical Computer Science. Springer-Verlag, 2002 (2003). A 238 page manuscript was sent to the potential publisher Monday 15 July 2002. This book collects the work of the main originator and one of the main contributors to the theory of duration calculi. As such the book represents a dozen years of research.

    Google Scholar 

  41. G. Clemmensen and O. Oest. Formal specification and development of an Ada compiler — a VDM case study. In Proc. 7th International Conf. on Software Engineering, 26.–29. March 1984, Orlando, Florida, pages 430-440. IEEE, 1984.

    Google Scholar 

  42. I. Craig. The Formal Specification of Advanced AI Architectures. AI Series. Ellis Horwood, Sept. 1991.

    Google Scholar 

  43. C. J. e. D. Bjørner. The Vienna Development Method: The Meta-Language, volume 61 of Lecture Notes in Computer Science. Springer-Verlag, 1978.

    Google Scholar 

  44. A. Dardenne, S. Fikas, and A. van Lamsweerde. Goal-Directed Concept Acquisition in Requirements Elicitation. In Proc. IWSSD-6, 6th Intl. Workshop on Software Specification and Design, pages 14-21, Como, Italy, 1991. IEEE Computer Society Press.

    Google Scholar 

  45. A. Dardenne, A. van Lamsweerde, and S. Fikas. Goal-Directed Requirements Acquisition. Science of Computer Programming, 20:3–50, 1993.

    Article  MATH  Google Scholar 

  46. R. Darimont and A. van Lamsweerde. Formal Refinement Patterns for Goal-Driven Requirements Elaboration. In Proc. FSE’4, Fourth ACM SIGSOFT Symp. on the Foundations of Software Enginering, pages 179-190. ACM, October 1996.

    Google Scholar 

  47. A. Diller. Z: An Introduction to Formal Methods. John Wiley & Sons, 1990.

    Google Scholar 

  48. A. Diller. Z: An Introduction to Formal Methods. John Wiley & Sons, 2nd edition, 1994.

    Google Scholar 

  49. M. Feather, S. Fikas, A. van Lamsweerde, and C. Ponsard. Reconciling System Requirements and Runtime Behaviours. In Proc. IWSSD’98, 9th Intl. Workshop on Software Specification and Design, Isobe, Japan, April 1998. IEEE Computer Society Press.

    Google Scholar 

  50. J. Fitzgerald and P. G. Larsen. Software System Design: Formal Methods into Practice. Cambridge University Press, The Edinburgh Building, Cambridge CB2 2RU, UK, 1997. To appear.

    Google Scholar 

  51. D. Garlan. Formal approaches to software architecture. In Studies of Software Design. ICSE’ 93 Workshop. Selected Papers, pages 64-76, Berlin, Germany, 1996. Springer-Verlag.

    Google Scholar 

  52. D. Garlan and M. Shaw. An introduction to software architecture, pages 1-39. World Scientific, Singapore, 1993.

    Google Scholar 

  53. C. George, P. Haff, K. Havelund, A. Haxthausen, R. Milne, C. B. Nielsen, S. Prehn, and K. R. Wagner. The RAISE Specification Language. The BCS Practitioner Series. Prentice-Hall, Hemel Hampstead, England, 1992.

    Google Scholar 

  54. C. George, A. Haxthausen, S. Hughes, R. Milne, S. Prehn, and J. S. Pedersen. The RAISE Method. The BCS Practitioner Series. Prentice-Hall, Hemel Hampstead, England, 1995.

    Google Scholar 

  55. C. W. George, H. D. Van, T. Janowski, and R. Moore. Case Studies using The RAISE Method. FACTS (Formal Aspects of Computing: Theory and Software) and FME (Formal Methods Europe). Springer-Verlag, London, 2002. This book reports on a number of case studies using RAISE (Rigorous Approach to Software Engineering). The case studies were done in the period 1994–2001 at UNU/IIST, the UN University’s International Institute for Software Technology, Macau (till 20 Dec., 1997, Chinese Teritory under Portuguese administration, now a Special Administrative Region (SAR) of (the so-called People’s Republic of) China).

    Google Scholar 

  56. J. A. Goguen and M. Girotka, editors. Requirements Engineering: Social and Technical Issues. Academic Press, 1994.

    Google Scholar 

  57. J. A. Goguen and C. Linde. Techniques for Requirements Elicitation. In Proc. RE’93, First IEEE Symposium on Requirements Engineering, pages 152-164, San Diego, Calif., USA, 1993. IEEE Computer Society Press.

    Google Scholar 

  58. S. J. Greenspan, J. Mylopoulos, and A. Borgida. Capturing More World-Knowledge in Requirements Specification. In Proc. 6th ICSE: Intl. Conf. on Software Engineering, Tokyo, Japan, 1982. IEEE Computer Society Press.

    Google Scholar 

  59. S. J. Greenspan, J. Mylopoulos, and A. Borgida. A Requirements Modelling Language. Information Systems, 11(1):9–23, 1986. (About RML).

    Article  Google Scholar 

  60. P. Haff, editor. The Formal Definition of CHILL. ITU (Intl. Telecmm. Union), Geneva, Switzerland, 1981.

    Google Scholar 

  61. I. J. Hayes. Specification Case Studies. Prentice Hall International Series in Computer Science, 2nd edition, 1993.

    Google Scholar 

  62. C. Hoare. A Grand Challenge for Computer Science. Presented at the UNU/IIST 10th Anniversary Symposium, Lisboa, Portugal, March 19, 2002, and at the IFIP WG2.3 Meeting, Åbo/Turku, Finland, August 12, 2002. March, August 2002.

    Google Scholar 

  63. C. Hoare and H. J. Feng. Unifying Theories of Programming. Prentice Hall, 1997.

    Google Scholar 

  64. A. Hunter and B. Nuseibeh. Managing Inconsistent Specifications: Reasoning, Analysis and Action. ACM Transactions on Software Engineering and Methodology, 7(4):335–367, October 1998.

    Article  Google Scholar 

  65. M. Imperato. An Introduction to Z. Chartwell-Bratt, 1991.

    Google Scholar 

  66. J. Jacky. The Way of Z: Practical Programming with Formal Methods. Cambridge University Press, 1997.

    Google Scholar 

  67. C. Jones. Systematic Software Development Using VDM. Prentice-Hall, 1986.

    Google Scholar 

  68. C. Jones. Teaching notes for systematic software development using vdm. Technical Report UMCS 86-4-2, Univ. of Manchester, 1986.

    Google Scholar 

  69. C. B. Jones. Software Development A Rigorous Approach. Prentice-Hall International, Englewood Cliffs, New Jersey, 1980.

    MATH  Google Scholar 

  70. D. Lightfoot. Form al Specification using Z. Macmillan, 1991.

    Google Scholar 

  71. Z. Manna and A. Pnueli. The Temporal Logic of Reactive Systems: Specifications. Addison Wesley, 1991.

    Google Scholar 

  72. Z. Manna and A. Pnueli. The Temporal Logic of Reactive Systems: Safety. Addison Wesley, 1995.

    Google Scholar 

  73. J. A. McDermid and P. Whysall. Formal System Specification and Implementation using Z. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1992. Withdrawn.

    Google Scholar 

  74. M. A. McMorran and S. Powell. Z Guide for Beginners. Blackwell Scientific, 1993.

    Google Scholar 

  75. J. Mylopoulos. Information Modelling in the Time of revolution. Information Systems, 23(3/4):127–155, 1998.

    Article  Google Scholar 

  76. J. Mylopoulos, L. Chung, and B. Nixon. Representing and Using Non-Functional Requirements: A Process-oriented Approach. IEEE Trans. on Software Engineering, 18(6):483–497, June 1992.

    Article  Google Scholar 

  77. J. Mylopoulos, L. Chung, and E. Yu. From Object-Oriented to Goal-Oriented Requirements Analysis. CACM: Communications of the ACM, 42(1):31–37, January 1999.

    Article  Google Scholar 

  78. B. Nuseibeh, J. Kramer, and A. Finkelstein. A Framework for Expressing the Relationships between Multiple Views in Requirements Specifications. IEEE Transactions on Software Engineering, 20(10):760–773, October 1994.

    Article  Google Scholar 

  79. O. Oest. VDM from research to practice. In H.-J. Kugler, editor, Information Processing’ 86, pages 527–533. IFIP World Congress Proceedings, North-Holland Publ.Co., Amsterdam, 1986.

    Google Scholar 

  80. H. M. Petersen. Agents and Speech Acts: A Semantic Analysis. Master’s thesis, Informatics and Mathematical Modelling, Computer Science and Engineering, Bldg. 322, Richard Petersens Plads, Technical University of Denmark, DK-2800 Kgs. Lyngby, Denmark, 20 June 2002.

    Google Scholar 

  81. B. F. Potter, J. E. Sinclair, and D. Till. An Introduction to Formal Specification and Z. Prentice Hall International Series in Computer Science, 1991.

    Google Scholar 

  82. B. F. Potter, J. E. Sinclair, and D. Till. An Introduction to Formal Specification and Z. Prentice Hall International Series in Computer Science, 2nd edition, 1996.

    Google Scholar 

  83. D. Rann, J. Turner, and J. Whitworth. Z: A Beginner’s Guide. Chapman & Hall, London, 1994.

    Google Scholar 

  84. B. Ratcliff. Introducing Specification Using Z: A Practical Case Study Approach. International Series in Software Engineering. McGraw-Hill, 1994.

    Google Scholar 

  85. C. Shekaran, D. Garlan, and et al. The role of software architecture in requirements engineering. In First International Conference on Requirements Engineering (Cat. No.94TH0613-0); Colorado Springs, CO, USA, pages 239-245, Los Alamitos, CA, USA, 1994. IEEE Comput. Soc. Press.

    Google Scholar 

  86. D. Sheppard. An Introduction to Formal Specification with Z and VDM. International Series in Software Engineering. McGraw Hill, 1995.

    Google Scholar 

  87. J. M. Spivey. Understanding Z: A Specification Language and its Formal Semantics, volume 3 of Cambridge Tracts in Theoretical Computer Science. Cambridge University Press, Jan. 1988.

    Google Scholar 

  88. J. M. Spivey. The Z Notation: A Reference Manual. Prentice Hall International Series in Computer Science, 2nd edition, 1992.

    Google Scholar 

  89. M. Thomas. A Grand Challenge for Computer Science. Presented at the CoLogNET/-FME Industry Day, August 25, 2002, at the FLoC’02 Federated Logic Conference, Copenhagen, Denmark. July 2002.

    Google Scholar 

  90. A. van Lamsweerde. Requirements Engineering in the Year 00: A Research Perspective. In Proceedings 22nd International Conference on Software Engineering, ICSE’2000. IEEE Computer Society Press, 2000.

    Google Scholar 

  91. A. van Lamsweerde, R. Darimont, and E. Letier. Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Transaction on Software Engineering, 1998. Special Issue on Inconsistency Management in Software Development.

    Google Scholar 

  92. A. van Lamsweerde and E. Letier. Integrating Obstacles in Goal-Driven Requirements Engineering. In Proc. ICSE-98: 20th International Conference on Software Enginereering, Kyoto, Japan, April 1998. IEEE Computer Society Press.

    Google Scholar 

  93. A. van Lamsweerde and L. Willemet. Inferring Declarative Requirements Specification from Operational Scenarios. IEEE Transaction on Software Engineering, pages 1089-1114, 1998. Special Issue on Scenario Management.

    Google Scholar 

  94. A. van Lamsweerde and L. Willemet. Handling Obstacles in Goal-Driven Requirements Engineering. IEEE Transaction on Software Engineering, 2000. Special Issue on Exception Handling.

    Google Scholar 

  95. J. C. P. Woodcock. Using Standard Z. International Series in Computer Science. Prentice Hall, Hemel Hempstead, Hertfordshire, UK, 1993. In preparation.

    Google Scholar 

  96. J. C. P. Woodcock and J. Davies. Using Z: Specification, Proof and Refinement. Prentice Hall International Series in Computer Science, 1996.

    Google Scholar 

  97. J. C. P. Woodcock and M. Loomes. Software Engineering Mathematics. Addison-Wesley Publishing Company, 1989.

    Google Scholar 

  98. J. B. Wordsworth. Software Development with Z: A Practical Approach to Formal Methods in Software Engineering. Addison-Wesley Publishing Company, 1993.

    Google Scholar 

  99. E. Yu and J. Mylopoulos. Understanding ”why” in Software Process Modelling, Analysis and Design. In Proc. 16th ICSE: Intl. Conf. on Software Engineering, Sorrento, Italy, 1994. IEEE Press.

    Google Scholar 

  100. P. Zave. Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys, 29(4):315–321, 1997.

    Article  Google Scholar 

  101. P. Zave and M. A. Jackson. Techniques for partial specification and specification of switching systems. In S. Prehn and W. Toetenel, editors, VDM’91: Formal Software Development Methods, volume 551 of LNCS, pages 511-525. Springer-Verlag, 1991.

    Google Scholar 

  102. P. Zave and M. A. Jackson. Requirements for telecommunications services: an attack on complexity. In Proceedings of the Third IEEE International Symposium on Requirements Engineering (Cat. No.97TB100086), pages 106-117. IEEE Comput. Soc. Press, 1997.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2003 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Bjørner, D. (2003). Domain Engineering: a “Radical Innovation” for Software and Systems Engineering?. In: Dershowitz, N. (eds) Verification: Theory and Practice. Lecture Notes in Computer Science, vol 2772. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-39910-0_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-39910-0_5

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-21002-3

  • Online ISBN: 978-3-540-39910-0

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics