Custom cover image
Requirements Engineering / by Elizabeth Hull, Ken Jackson, Jeremy Dick
Contributor(s): Resource type: Ressourcentyp: Buch (Online)Book (Online)Language: English Publisher: London : Springer-Verlag London Limited, 2011Edition: 3. edDescription: Online-Ressource : v.: digitalISBN:- 9781849964050
- 005.12
- 005.1 23
- QA76.758
Contents:
Summary: Written for those who want to develop their knowledge of requirements engineering process, whether practitioners or students. Using the latest research and driven by practical experience from industry, this book gives useful hints to practitioners on how to write and structure requirements. - Explains the importance of Systems Engineering and the creation of effective solutions to problems - Describes the underlying representations used in system modeling - data flow diagrams, statecharts, object-oriented approaches - Covers a generic multi-layer requirements process - Discusses the key elements of effective requirements management - Includes a chapter written by one of the developers of rich traceability - Introduces an overview of DOORS - a software tool which serves as an enabler of a requirements management processAdditional material and links are available at: http://www.requirementsengineering.info'In recent years we have been finding ourselves with a shortage of engineers with good competence in requirements engineering. Perhaps this is in part because requirements management tool vendors have persuaded management that a glitzy tool will solve their requirements engineering problems. Of course, the tools only make it possible for engineers who understand requirements engineering to do a better job. This book goes a long way towards building a foundational set of skills in requirements engineering, so that today's powerful tools can be used sensibly. Of particular value is a recognition of the place software requirements have within the system context, and of ways for dealing with that sensitive connection. This is an important book. I think its particular value in industry will be to bring the requirements engineers and their internal customers to a practical common understanding of what can and should be achieved.PPN: PPN: 638208041Package identifier: Produktsigel: ZDB-2-SCS | ZDB-2-SEB | ZDB-2-SXCS | ZDB-2-SEB
Chapter 1: Introduction; 1.1 Introduction to Requirements; 1.2 Introduction to Systems Engineering; 1.3 Defining Requirements Engineering; 1.3.1 Definition of a Requirement; 1.3.2 Definition of a Stakeholder; 1.3.3 Definition of Requirements Engineering; 1.4 Requirements and Quality; 1.5 Requirements and the Lifecycle; 1.6 Requirements Tracing; 1.7 Requirements and Modelling; 1.8 Requirements and Testing; 1.9 Requirements in the Problem and Solution Domains; 1.10 How to Read this Book; Chapter 2: A Generic Process for Requirements Engineering; 2.1 Introduction; 2.2 Developing Systems
2.3 Generic Process Context2.3.1 Input Requirements and Derived Requirements; 2.3.2 Acceptance Criteria and Qualification Strategy; 2.4 Generic Process Introduction; 2.4.1 Ideal Development; 2.4.2 Development in the Context of Change; 2.5 Generic Process Information Model; 2.5.1 Information Classes; 2.5.2 Agreement State; 2.5.3 Qualification State; 2.5.4 Satisfaction State; 2.5.5 Information Model Constraints; 2.6 Generic Process Details; 2.6.1 Agreement Process; 2.6.2 Analyse and Model
2.6.3 Derive Requirements and Qualification Strategy Fig. 2.13 Portrays the Process for Deriving Requirements and Qualifica2.6.3.1 Deriving Requirements; 2.6.3.2 Deriving the Qualification Strategy; 2.7 Summary; Chapter 3: System Modelling for Requirements Engineering; 3.1 Introduction; 3.2 Representations for Requirements Engineering; 3.2.1 Data Flow Diagrams; 3.2.2 Entity-Relationship Diagrams; 3.2.3 Statecharts; 3.2.4 Object-Oriented Approaches; 3.2.4.1 Class Diagrams; 3.2.4.2 Use Cases; 3.3 Methods; 3.3.1 Viewpoint Methods; 3.3.1.1 Controlled Requirements Expression (CORE)
3.3.1.2 Structured Analysis and Design Technique (SADT)3.3.1.3 Viewpoint-Oriented Requirements Definition (VORD); 3.3.2 Object-Oriented Methods; 3.3.2.1 OOA; 3.3.2.2 OMT; 3.3.2.3 Booch; 3.3.2.4 Objectory; 3.3.2.5 The UML; 3.3.3 The UML Notation; 3.3.4 Formal Methods; 3.3.4.1 Z-A Model-Based Formal Method; 3.4 Summary; Chapter 4: Writing and Reviewing Requirements; 4.1 Introduction; 4.2 Requirements for Requirements; 4.3 Structuring Requirements Documents; 4.4 Key Requirements; 4.5 Using Attributes; 4.6 Ensuring Consistency Across Requirements; 4.7 Value of a Requirement
4.8 The Language of Requirements4.9 Requirement Boilerplates; 4.10 Granularity of Requirements; 4.11 Criteria for Writing Requirements Statements; 4.12 Summary; Chapter 5: Requirements Engineering in the Problem Domain; 5.1 What is the Problem Domain?; 5.2 Instantiating the Generic Process; 5.3 Agree Requirements with Customer; 5.4 Analyse & Model; 5.4.1 Identify Stakeholders; 5.4.2 Create Use Scenarios; 5.4.2.1 Characteristics of Use Scenarios; 5.4.3 Scoping the System; 5.5 Derive Requirements; 5.5.1 Define Structure; 5.5.2 Capture Requirements; 5.5.2.1 Sources of Stakeholder Requirements
5.5.2.2 Stakeholder Interviews
No physical items for this record
Electronic reproduction; Available via World Wide Web
Online-Ausg.. (Springer eBook Collection. Computer Science). Electronic reproduction; Available via World Wide Web