Requirements engineering: from craft to discipline

ABSTRACT

Getting the right software requirements under the right environment assumptions is a critical precondition for developing the right software. This task is intrinsically difficult. We need to produce a complete, adequate, consistent, and well-structured set of measurable requirements and assumptions from incomplete, imprecise, and sparse material originating from multiple, often conflicting sources. The system we need to consider comprises software and environment components including people and devices.

A rich system model may significantly help us in this task. Such model must integrate the intentional, structural, functional, and behavioral facets of the system being conceived. Rigorous techniques are needed for model construction, analysis, exploitation, and evolution. Such techniques should support early and incremental reasoning about partial models for a variety of purposes including satisfaction arguments, property checks, animations, the evaluation of alternative options, the analysis of risks, threats, and conflicts, and traceability management. The tension between technical precision and practical applicability calls for a suitable mix of heuristic, deductive, and inductive forms of reasoning on a suitable mix of declarative and operational specifications. Formal techniques should be deployed only when and where needed, and kept hidden wherever possible. The paper provides a retrospective account of our research efforts and practical experience along this route. Problem-oriented abstractions, analyzable models, and constructive techniques were permanent concerns.

REFERENCES

• 1: Chung, L., Nixon, B., Yu E. and Mylopoulos, J., Nonfunctional requirements in software engineering. Kluwer Academic, Boston, 2000.
• 2: Christophe Damas , Bernard Lambeau , Pierre Dupont , Axel van Lamsweerde, Generating Annotated Behavior Models from End-User Scenarios, IEEE Transactions on Software Engineering, v.31 n.12, p.1056-1073, December 2005 [doi>10.1109/TSE.2005.138]
• 3: Christophe Damas , Bernard Lambeau , Axel van Lamsweerde, Scenarios, goals, and state machines: a win-win partnership for model synthesis, Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering, November 05-11, 2006, Portland, Oregon, USA [doi>10.1145/1181775.1181800]
• 4: Anne Dardenne , Axel van Lamsweerde , Stephen Fickas, Goal-directed requirements acquisition, Science of Computer Programming, v.20 n.1-2, p.3-50, April 1993
• 5: Robert Darimont , Axel van Lamsweerde, Formal refinement patterns for goal-driven requirements elaboration, Proceedings of the 4th ACM SIGSOFT symposium on Foundations of software engineering, p.179-190, October 16-18, 1996, San Francisco, California, United States
• 6: Darimont, R., Delor, E., Massonet, P. and van Lamsweerde, A., "GRAIL/KAOS: An Environment for Goal-Driven Requirements Engineering", Proc. ICSE'98 - 20th Intl. Conf. on Software Engineering, Kyoto, April 1998, vol. 2, 58--62.
• 7: Darimont, R. and Lemoine, M. "Security Requirements for Civil Aviation with UML and Goal Orientation", Proc. REFSQ'07 -- Intl. Working Conference on Foundations for Software Quality, Trondheim (Norway), LNCS 4542, Springer-Verlag, 2007.
• 8: Renaud De Landtsheer , Emmanuel Letier , Axel van Lamsweerde, Deriving tabular event-based specifications from goal-oriented requirements models, Requirements Engineering, v.9 n.2, p.104-120, May 2004 [doi>10.1007/s00766-004-0189-1]
• 9: Renaud De Landtsheer , Axel van Lamsweerde, Reasoning about confidentiality at requirements engineering time, Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering, September 05-09, 2005, Lisbon, Portugal [doi>10.1145/1081706.1081715]
• 10: Martin S. Feather, Language support for the specification and development of composite systems, ACM Transactions on Programming Languages and Systems (TOPLAS), v.9 n.2, p.198-234, April 1987 [doi>10.1145/22719.22947]
• 11: M. S. Feather , S. Fickas , A. Van Lamsweerde , C. Ponsard, Reconciling System Requirements and Runtime Behavior, Proceedings of the 9th international workshop on Software specification and design, p.50, April 16-18, 1998
• 12: Michael Jackson, The world and the machine, Proceedings of the 17th international conference on Software engineering, p.283-292, April 24-28, 1995, Seattle, Washington, United States [doi>10.1145/225014.225041]
• 13: Axel van Lamsweerde, Learning machine learning, From natural language processing to logic for expert systems: a logic based approach to artificial intelligence, John Wiley and Sons Ltd., Chichester, UK, 1991
• 14: Axel van Lamsweerde, Goal-Oriented Requirements Engineering: A Guided Tour, Proceedings of the 5th IEEE International Symposium on Requirements Engineering, p.249, August 27-31, 2001
• 15: van Lamsweerde, A., "From System Goals to Software Architecture", in Formal Methods for Software Architecture, LNCS 2804, Springer-Verlag, 2003.
• 16: Axel van Lamsweerde, Elaborating Security Requirements by Construction of Intentional Anti-Models, Proceedings of the 26th International Conference on Software Engineering, p.148-157, May 23-28, 2004
• 17: Axel van Lamsweerde, Goal-Oriented Requirements Enginering: A Roundtrip from Research to Practice, Proceedings of the Requirements Engineering Conference, 12th IEEE International, p.4-7, September 06-10, 2004 [doi>10.1109/RE.2004.25]
• 18: Axel van Lamsweerde, Requirements engineering: from craft to discipline, Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering, November 09-14, 2008, Atlanta, Georgia [doi>10.1145/1453101.1453133]
• 19: Axel van Lamsweerde , Emmanual Letier , Robert Darimont, Managing Conflicts in Goal-Driven Requirements Engineering, IEEE Transactions on Software Engineering, v.24 n.11, p.908-926, November 1998 [doi>10.1109/32.730542]
• 20: A. Van Lamsweerde , R. Darimont , P. Massonet, Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt, Proceedings of the Second IEEE International Symposium on Requirements Engineering, p.194, March 27-29, 1995
• 21: A. van Lamsweerde , B. Delcourt , E. Delor , M. C. Schayes , R. Champagne, Generic Lifecycle Support in the ALMA Environment, IEEE Transactions on Software Engineering, v.14 n.6, p.720-741, June 1988 [doi>10.1109/32.6153]
• 22: Axel van Lamsweerde , Emmanuel Letier, Handling Obstacles in Goal-Oriented Requirements Engineering, IEEE Transactions on Software Engineering, v.26 n.10, p.978-1005, October 2000 [doi>10.1109/32.879820]
• 23: van Lamsweerde, A. and Sintzoff, M., Formal Derivation of Strongly Correct Concurrent Programs. Acta Informatica Vol. 12, Springer Verlag, 1979, 1--31.
• 24: Axel van Lamsweerde , Laurent Willemet, Inferring Declarative Requirements Specifications from Operational Scenarios, IEEE Transactions on Software Engineering, v.24 n.12, p.1089-1114, December 1998 [doi>10.1109/32.738341]
• 25: Emmanuel Letier , Axel van Lamsweerde, Agent-based tactics for goal-oriented requirements elaboration, Proceedings of the 24th International Conference on Software Engineering, May 19-25, 2002, Orlando, Florida [doi>10.1145/581339.581353]
• 26: Emmanuel Letier , Axel van Lamsweerde, Deriving operational software specifications from system goals, Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering, November 18-22, 2002, Charleston, South Carolina, USA [doi>10.1145/587051.587070]
• 27: Emmanuel Letier , Axel van Lamsweerde, Reasoning about partial goal satisfaction for requirements and design engineering, Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering, October 31-November 06, 2004, Newport Beach, CA, USA
• 28: Emmanuel Letier , Jeff Kramer , Jeff Magee , Sebastian Uchitel, Deriving event-based transition systems from goal-oriented requirements models, Automated Software Engineering, v.15 n.2, p.175-206, June 2008 [doi>10.1007/s10515-008-0027-7]
• 29: Jeff Magee, Concurrency: State Models And Java Programs, John Wiley & Sons, 2006
• 30: Philippe Massonet , Axel Van Lamsweerde, Analogical Reuse of Requirements Frameworks, Proceedings of the 3rd IEEE International Symposium on Requirements Engineering (RE'97), p.26, January 05-08, 1997
• 31: Objectiver, http://www.objectiver.com.
• 32: http://www.kinetium.com/map/demo/demo_index.html.
• 33: David Lorge Parnas , Jan Madey, Functional documents for computer systems, Science of Computer Programming, v.25 n.1, p.41-61, Oct. 1995 [doi>10.1016/0167-6423(95)96871-J]
• 34: C. Ponsard , P. Massonet , J. F. Molderez , A. Rifaut , A. Van Lamsweerde , H. Tran Van, Early verification and validation of mission critical systems, Formal Methods in System Design, v.30 n.3, p.233-247, June 2007 [doi>10.1007/s10703-006-0028-8]
• 35: Hung Tran Van , Axel van Lamsweerde , Philippe Massonet , Christophe Ponsard, Goal-Oriented Requirements Animation, Proceedings of the Requirements Engineering Conference, 12th IEEE International, p.218-228, September 06-10, 2004 [doi>10.1109/RE.2004.24]
• 36: Yue, K. "What Does It Mean to Say that a Specification is Complete?", Proc. IWSSD-4, Fourth International Workshop on Software Specification and Design, Monterey, 1987.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications

General Terms:
Design, Documentation, Verification

Keywords:
formal derivation, goal orientation, lightweight analysis, operationalization, problem modeling, requirements engineering, responsibility assignment, specification construction, system design