Business System Analysis Bookstore
In Association with Amazon.com
Help PicoSearch
Looking for Business Analysis Training

Requirements Engineering

Buy the Book
Summary TOC Preface Look Inside Comments
Elizabeth Hull, Ken Jackson, Jeremy J. Dick, P. M. Cohn
September 2002, Springer Verlag, Paperback, 213 pages, ISBN 1852335777

Instructor-led, virtual, and self-paced training for Business Analysts What Do Business Analysts Do?
How to Gather, Analyze, and Define Business System Requirements
How to Write Effective, Understandable Business Requirement Statements
How to Write Effective Business Requirements for IT Projects
How to Model, Analyze, and Improve Business Processes
How to Manage Changing Business Requirements
How to Model and Analyze Business System Data
How to Model Business Data from the Business Perspective
How to Jump-Start Requirements Gathering with User Stories
How to Discover and Develop Use Cases
How to Develop and Use UML Models for Business Analysis
How to Capture and Clarify Requirements with State Diagrams
How to Support and Document a Successful JAR/JAD Session
How to Plan, Prepare, and Execute User Acceptance Testing
Business Analysis and Requirements Gathering Blitz
e-Learning, virtual workshops and webinars Try our new Virtual Workshops and e-Coaching
for today's Business System Analysts (BA's) and Subject Matter Experts (SME's)

Summary
Buy the book

Using the latest research and driven by practical experience from industry, Requirements Engineering gives useful hints to practitioners on how to write and structure requirements.

The text explains the importance of Systems Engineering and the creation of effective solutions to problems, and describes the underlying representations used in systems modeling

  • data flow diagrams, statecharts object-oriented approaches.
  • It also covers a generic multi-layer requirements process and discusses key elements of effective requirements management;
  • Presents the latest techniques from practising requirements engineers.
  • Introduces a flexible process for a variety of system development contexts.
  • Introduces the requirements management tool
  • DOORS.
  • Explains the important new concept of Rich Traceability.
  • Suitable for courses on Computer Science, Software Engineering and Systems Engineering.

Keywords:
DOORS, HCI, requirements engineering, requirements management, systems engineering, systems requirements

 
analysis bookstore top
BA books: Table of Contents
Buy the book

General

Chapter 1 Introduction

1.1 Introduction to requirements

1.2 Introduction to systems engineering

1.3 Requirements and quality

1.4 Requirements and the lifecycle

1.5 Requirements traceability

1.6 Requirements and modelling

1.7 Requirements and Testing

1.8 Requirements in the Problem and Solution Domains

1.9 How to read this book


Chapter 2 A Generic Process for Requirements Engineering


2.1 Introduction

2.2 Developing systems

2.3 Generic process context

 

2.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

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 State transition diagrams
3.2.4 Statecharts
3.2.5 Object-Oriented Approaches

3.3 Representations and information

3.4 Methods

3.4.1 What is in a method?
3.4.2 Structured methods
3.4.3 O-O methods
3.4.4 Formal methods

3.5 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 requirements

4.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.3 Scoping the system

5.5 Derive Requirements

5.5.1 Define structure
5.5.2 Capture Requirements
5.5.3 Define acceptance criteria
5.5.4 Define qualification strategy

5.6 Summary


Chapter 6 Requirements Engineering in the Solution Domain

6.1 What is the solution domain

6.2 Engineering requirements from Stakeholder Requirements to System requirements

6.2.1 Producing the System Model
6.2.2 Creating System Models to derive System Requirements
6.2.3 Banking example
6.2.4 Car example
6.2.5 Deriving requirements from a System Model
6.2.6 Agreeing the system requirements with the design team

6.3 Engineering requirements from system requirements to subsystems

6.3.1 Creating a system architecture model
6.3.2 Deriving requirements from an architectural design model

6.4 Other transformations using a design architecture

6.5 Summary


Chapter 7 Advanced Traceability

7.1 Introduction

7.2 Elementary traceability

7.3 Satisfaction arguments

7.4 Requirements allocation

7.5 Reviewing traceability

7.6 The language of satisfaction arguments

7.7 Rich traceability analysis

7.8 Rich traceability for qualification

7.9 Implementing rich traceability

7.9.1 Single-layer rich traceability
7.9.2 Multi-layer rich traceability

7.10 Metrics for traceability

7.10.1 Breadth
7.10.2 Depth
7.10.3 Growth
7.10.4 Balance
7.10.5 Latent change

7.11 Summary


Chapter 8 Management Aspects of Requirements Engineering

8.1 Introduction to management

8.2 Requirements management problems

8.2.1 Summary of requirement management problems

8.3 Managing requirements in an Acquisition Organisation

8.3.1 Planning
8.3.2 Monitoring
8.3.3 Changes

8.4 Supplier organisations

8.4.1 Bid management
8.4.2 Development

8.5 Product organisations

8.5.1 Planning
8.5.2 Monitoring
8.5.3 Changes

8.6 Summary

8.6.1 Planning
8.6.2 Monitoring

8.6.3 Changes


Chapter 9 DOORS: A Tool to Manage Requirements

9.1 Introduction

9.2 The Case for Requirements Management

9.3 DOORS Architecture

9.4 Projects, Modules and Objects

9.4.1 DOORS Database window
9.4.2 Formal Modules
9.4.3 Objects
9.4.4 Pictures
9.4.5 Tables

9.5 History and version control

9.5.1 History
9.5.2 Baselining

9.6 Attributes and Views

9.6.1 Attributes
9.6.2 Views

9.7 Traceability

9.7.1 Links
9.7.2 Traceability reports

9.8 Import and Export

9.9 Summary

 
analysis bookstore top
Preface
Buy the book
Requirements Engineering is common sense, but it is perceived to be difficult and is not well understood. For these reasons it is generally not very well done. The ever-increasing pressures on an organisation are often given as the main reasons for not introducing a more disciplined approach to requirements engineering. However, it is these very pressures that make it even more important for the requirements engineer to help the organisation do the job properly.
Systems engineering is critical in today's industry and requirements engineering is an important aspect of that overall process. A good process is key to requirements engineering - it determines how efficiently and rapidly products can be generated. This is particularly important in a global competitive market where the 'time to market' and meeting stakeholder requirements are the key success factors.

Requirements engineering is also about management and hence issues in relation to requirements and management blend to show how requirements can be used to manage systems development.

The book is concerned with engineering requirements and how systems engineers may be helped to create better requirements. A generic process is presented which assists the reader in gaining a good understanding of the essence of requirements engineering. The process is then instantiated for the problem and solution domains of development. The book also addresses the concept of system modelling and presents various techniques and methods which are widely used. An important feature of the book is the presentation of approaches to traceability, the way in which it is captured and metrics which can be derived from traceability. Finally the book presents an overview of DOORS which is a tool for requirements management. A case study is used to illustrate the process presented in the book and the features of the tool.

This book should be read by those systems and requirements engineers in industry, who, as practitioners, are keen to gain knowledge of using requirements engineering for system development. The book will also be of interest to final year undergraduate students in Computer Science, Software Engineering and Systems Engineering studying a course in Requirements Engineering and also to postgraduate research students in Computer Science or and other flavours of Engineering.

The approach taken in the book is based on current research in Requirements Engineering, however it has not only taken the academic view but has also built substantially on current experience of working in industry to enable system engineers to manage requirements (and projects) more successfully. It provides a snapshot, in this rapidly evolving subject, of what we see as best practice in Requirements Engineering today.

Elizabeth Hull
Ken Jackson
Jeremy Dick

May 2002

 
analysis bookstore top
 
NEW RELEASES
Agile
Benchmarking
Best Practices
Business Systems Analysis
CASE
Data Analysis
  Data Models
Data Normalization
Data Repository
Entity Relationship Diagrams
Miscellaneous
Data Warehouse
Enterprise Architecture
Enterprise Resource Planning (ERP)
  Peoplesoft
SAP
Miscellaneous
Humor
Internet
  E-Commerce
Miscellaneous
Interviewing Techniques
Methodologies
  Information Engineering
Structured System Development
System Development Life Cycle (SDLC)
Miscellaneous
Object Oriented
  Business Objects
Object Oriented Analysis
Object Oriented Design
Object Oriented Modeling
Object Oriented Testing
State Transition Diagrams
Problem Analysis
Process Analysis
  Data Flow Diagrams
Decision Tables
Event Response Diagrams
Flowcharts
Process Models
Miscellaneous
Process Improvement (BPI)
Related Topics
  Knowledge Management
Philosophies
Request for Proposal (RFP)
Risk Management
Six Sigma
Software Reuse
Strategic Planning
Requirements
  Business Rules
Prototyping
Requirements Analysis
Requirements Definition
Requirements Documentation
Requirements Engineering
Requirements Gathering
Requirements Management
Requirements Traceability
System Specifications
User Interfaces
Miscellaneous
Test Management
  Defect Tracking
Test Planning
Testing Methodologies
Testing Tools
Validation & Verification
Miscellaneous
Testing Phases
  Acceptance Testing
Configuration Testing
Integration Testing
Performance Testing
System Testing
Unit Testing
Usability Testing
Testing Techniques
  Black Box Testing
Object Oriented Testing
Regression Testing
Test Cases
Test Data Engineering
Walkthroughs
White Box Testing
Miscellaneous
Unified Modeling Language (UML)
Usability Engineering
  Prototyping
Task Analysis
Usability Testing
User Interfaces
Miscellaneous
Use Cases
Workflow Analysis
Working in Teams
  Conducting Meetings
Facilitation
JAD
Rapid Application Development (RAD)
Miscellaneous
Search:
Keywords:
Home Links Add a book Request Link Exchange BA Skills Test Training Needs Assessment