Software & Systems Requirements Engineering: In Practice

Proven Software & Systems Requirements Engineering Techniques "Requirements engineering is a discipline used primarily for large and complex applications. It is more formal than normal methods of gathering requirements, and this formality is needed for many large applications. The authors are experienced requirements engineers, and this book is a good compendium of sound advice based on practical experience." --Capers Jones, Chief Scientist Emeritus, Software Productivity Research Deliver feature-rich products faster, cheaper, and more reliably using state-of-the-art SSRE methods and modeling procedures. Written by global experts, Software & Systems Requirements Engineering: In Practice explains how to effectively manage project objectives and user needs across the entire development lifecycle. Gather functional and quality attribute requirements, work with models, perform system tests, and verify compliance. You will also learn how to mitigate risks, avoid requirements creep, and sidestep the pitfalls associated with large, complex projects. Define and prioritize customer expectations using taxonomies Elicit and analyze functional and quality attribute requirements Develop artifact models, meta-models, and prototypes Manage platform and product line development requirements Derive and generate test cases from UML activity diagrams Deploy validation, verification, and rapid development procedures Handle RE for globally distributed software and system development projects  Perform hazard analysis, risk assessment, and threat modeling Table of contents Chapter 1. Introduction Chapter 2. Requirements Engineering Artifact Modeling Chapter 3. Eliciting Requirements Chapter 4. Requirements Modeling Chapter 5. Quality Attribute Requirements Chapter 6. Requirements Engineering for Platforms Chapter 7. Requirements Management Chapter 8. Requirements-Driven System Testing Chapter 9. Rapid Development Techniques for Requirements Evolution Chapter 10. Distributed Requirements Engineering Chapter 11. Hazard Analysis and Threat Modeling Chapter 12. Conclusion Appendix A. Configuring and Managing a Requirements Database Index

[1]  Isabel Beichl.  Begin at the Beginning , 2009, Comput. Sci. Eng..

[2]  Martin Glinz,et al.  A Risk-Based, Value-Oriented Approach to Quality Requirements , 2008, IEEE Software.

[3]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[4]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[5]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[6]  Bernhard Rumpe,et al.  Towards a Formalization of the Unified Modeling Language , 1997, ECOOP.

[7]  Ian F. Alexander.  Capturing use cases with doors , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[8]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[9]  Daniel M. Berry,et al.  The importance of ignorance in requirements engineering , 1995, J. Syst. Softw..

[10]  Lawrence Chung,et al.  Process-Oriented Metrics for Software Architecture Adaptability , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[11]  Sangeeta Sabharwal,et al.  A Systematic Approach to Measure the Problem Complexity of Software Requirement Specifications of an Information System , 2004 .

[12]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[13]  Ronald W. Langacker,et al.  Nouns and Verbs , 1987 .

[14]  Cécile Péraire,et al.  Integrating the Unified Modeling Language with an Architecture Description Language , 1999, OOPSLA 1999.

[15]  Robert L. Nord,et al.  Generalizing a Model of Software Architecture Design from Five Industrial Approaches , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[16]  Christof Ebert,et al.  Requirements before the requirements: understanding the upstream impacts , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[17]  Thomas Olsson,et al.  Non-functional requirements in industry - three case studies adopting an experience-based NFR method , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[18]  Markus Herrmannsdörfer.  Tabular Notations for State Machine-Based Specifications , 2008 .

[19]  Brian Berenbach,et al.  Metrics for model driven requirements development , 2006, ICSE '06.

[20]  Matthias Jarke.  Scenarios for modeling , 1999, CACM.

[21]  Nenad Medvidovic,et al.  Integrating architecture description languages with a standard design method , 1998, Proceedings of the 20th International Conference on Software Engineering.

[22]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[23]  Stacy Mason,et al.  All for nothing? , 2011, Nursing standard (Royal College of Nursing (Great Britain) : 1987).

[24]  Bernd Brügge,et al.  Software Cinema-Video-based Requirements Engineering , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[25]  Sooyong Park,et al.  A semi-automated filtering technique for software process tailoring using neural network , 2006, Expert Syst. Appl..

[26]  Juha Kuusela,et al.  Requirements engineering for product families , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[27]  G. Pullum,et al.  Adjectives and Adverbs , 2002 .

[28]  Jeffrey A. Ingalsbe,et al.  Threat Modeling: Diving into the Deep End , 2008, IEEE Software.

[29]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[30]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[31]  R. E. Kurt Stirewalt,et al.  Adequate reverse engineering , 2001, Proceedings 16th Annual International Conference on Automated Software Engineering (ASE 2001).

[32]  Tetsuo Tamai,et al.  How Does Requirements Quality Relate to Project Success or Failure? , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[33]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[34]  Philipp Bucher,et al.  How Much Does It Cost? , 2009 .

[35]  P. Inverardi,et al.  A Framework for the Integration of Functional and Non-functional Analysis of Software Architectures , 2005, Electron. Notes Theor. Comput. Sci..

[36]  N. Kano,et al.  Attractive Quality and Must-Be Quality , 1984 .

[37]  Leonard J. Bass,et al.  Making Practical Use of Quality Attribute Information , 2008, IEEE Software.

[38]  K. Cox.  Taking to scenarios to improve the requirements process: an experience report , 2000 .

[39]  Colin J. Neill,et al.  How Business Goals Drive Architectural Design , 2007, Computer.

[40]  Reinhard Siegmund-Schultze.  [out of scope]. , 2008, Sudhoffs Archiv.

[41]  BevanNigel.  Quality in use , 1999 .

[42]  Brian Berenbach,et al.  The evaluation of large, complex UML analysis and design models , 2004, Proceedings. 26th International Conference on Software Engineering.

[43]  Maxime Crochemore,et al.  Direct Construction of Compact Directed Acyclic Word Graphs , 1997, CPM.

[44]  Joseph D. Schulz.  Requirements-Based UML , 2001, Proceedings 39th International Conference and Exhibition on Technology of Object-Oriented Languages and Systems. TOOLS 39.

[45]  Mark Gall,et al.  Toward a Unified Model for Requirements Engineering , 2006, 2006 IEEE International Conference on Global Software Engineering (ICGSE'06).

[46]  T. Saaty.  Analytic Hierarchy Process , 2005 .

[47]  A. Finkelstein,et al.  A comedy of errors: the London Ambulance Service case study , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[48]  Nancy G. Leveson,et al.  On the use of visualization in formal requirements specification , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[49]  Jifeng He,et al.  Formal and use-case driven requirement analysis in UML , 2001, 25th Annual International Computer Software and Applications Conference. COMPSAC 2001.

[50]  Dirk Muthig,et al.  Efficient and systematic software evolution through domain analysis , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[51]  Jane Cleland-Huang,et al.  Toward improved traceability of non-functional requirements , 2005, TEFSE '05.

[52]  Bernard Berelson,et al.  Beyond Family Planning , 1969 .

[53]  Bashar Nuseibeh,et al.  Weaving Together Requirements and Architectures , 2001, Computer.

[54]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

[55]  Alistair G. Sutcliffe,et al.  Requirements engineering for complex collaborative systems , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[56]  Joachim Karlsson,et al.  Software requirements prioritizing , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[57]  W. Hryniuk.  More is better. , 1988, Journal of clinical oncology : official journal of the American Society of Clinical Oncology.

[58]  Georg Kösters,et al.  Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications , 2001, Requirements Engineering.

[59]  Sidney DeLong.  What is a Contract , 2009 .

[60]  M. Sheehan,et al.  Optimal allocation of resources to distribution investments using the analytic hierarchy process to balance the impacts of investments on safety, customer interruption costs, levelized annual revenue requirement, contribution to margin and other considerations , 2000, 2000 Power Engineering Society Summer Meeting (Cat. No.00CH37134).

[61]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[62]  Michael Jackson,et al.  The meaning of requirements , 1997, Ann. Softw. Eng..

[63]  Matthias Jarke,et al.  CREWS: Towards Systematic Usage of Scenarios, Use Cases and Scenes , 1999, Wirtschaftsinformatik.

[64]  Jane Cleland-Huang,et al.  Goal-Centric Traceability: Using Virtual Plumblines to Maintain Critical Systemic Qualities , 2008, IEEE Transactions on Software Engineering.

[65]  Johannes Siedersleben,et al.  Analysis beyond UML , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[66]  Leonard J. Bass,et al.  Designing software architectures to achieve quality attribute requirements , 2005, IEE Proc. Softw..

[67]  Michael Jackson.  Formalism and informality in RE , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[68]  Daniel M. Berry,et al.  Distributed priority ranking of strategic preliminary requirements for management information systems in economic organizations , 2007, Inf. Softw. Technol..

[69]  Richard A. Posner,et al.  Sentence first, verdict afterwards , 1999 .

[70]  Betty H. C. Cheng,et al.  Integrating informal and formal approaches to requirements modeling and analysis , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[71]  Brian Berenbach,et al.  The automated extraction of requirements from UML models , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[72]  Eva Geisberger,et al.  Requirements Engineering Reference Model (REM) , 2007, Softwaretechnik-Trends.