Business Analyst Training

Requirements elicitation, writing, analysis, and modeling by IIBA Endorsed Education Provider.

www.requirementssolutions.com

Business System Analysis Bookstore
In Association with Amazon.com
Help PicoSearch
Free Business Analyst Skills Test for CBAP Looking for Business Analysis Training

Requirements Engineering

Buy the Book
Summary TOC Preface Look Inside Comments
Elizabeth Hull, Ken Jackson, Jeremy Dick
September 2004, Springer Verlag, Hardcover, 198 pages, ISBN 1852338792

Instructor-led, virtual, and self-paced training for Business Analysts What Do Business Analysts Do?
How to Elicit (Gather), Write, and Analyze Business Requirements
How to Initiate Requirements Gathering with User Stories
How to Model, Analyze, and Improve Business Processes
How to Model, Analyze, and Improve Business Data
How to Define and Document Use Cases
How to Test an Application using Business Requirements
Writing Effective Business Requirement Statements
How to Elicit Business System Requirements
How to Write Effective Business Requirements
How to Analyze Sets of Business Requirements
How to Analyze and Improve Business Processes
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
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 modelling and introduces the UML2

- Considers the relationship between requirements and modelling

- Covers a generic multi-layer requirements process

- Discusses the key elements of effective requirements management

- Explains the important concept of rich traceability

- Introduces an overview of DOORS Version 7 - a software tool which serves as an enabler of a requirements management process

Additional material and links are available at: http://www.requirementsengineering.info

 
analysis bookstore top
BA books: Table of Contents
Buy the book
Chapter 1 Introduction 1
1.1 Introduction to Requirements 1
1.2 Introduction to Systems Engineering 3
1.3 Requirements and Quality . 6
1.4 Requirements and the Lifecycle 6
1.5 Requirements Traceability . 9
1.6 Requirements and Modelling 13
1.7 Requirements and Testing . 15
1.8 Requirements in the Problem and Solution Domains 15
1.9 How to Read This Book 18
Chapter 2 A Generic Process for Requirements Engineering 21
2.1 Introduction . 21
2.2 Developing Systems 21
2.3 Generic Process Context . 24
2.4 Generic Process Introduction . 27
2.5 Generic Process Information Model . 29
2.6 Generic Process Details 34
2.7 Summary . 40
Chapter 3 System Modelling for Requirements Engineering . 43
3.1 Introduction . 43
3.2 Representations for Requirements Engineering . 44
3.3 Methods 53
3.4 Summary . 71
Chapter 4 Writing and Reviewing Requirements . 73
4.1 Introduction . 73
4.2 Requirements for Requirements 74
4.3 Structuring Requirements Documents . 75
4.4 Key Requirements 76
4.5 Using Attributes . 76xiv Contents
4.6 Ensuring Consistency Across Requirements . 77
4.7 Value of a Requirement . 77
4.8 The Language of Requirements 80
4.9 Requirement Boilerplates . 81
4.10 Granularity of Requirements . 83
4.11 Criteria for Writing Requirements Statements 85
4.12 Summary . 86
Chapter 5 Requirements Engineering in the Problem Domain . 87
5.1 What is the Problem Domain? 87
5.2 Instantiating the Generic Process . 88
5.3 Agree Requirements with Customer . 89
5.4 Analyze and Model . 90
5.5 Derive Requirements . 95
5.6 Summary . 106
Chapter 6 Requirements Engineering in the Solution Domain . 109
6.1 What is the Solution Domain? 109
6.2 Engineering Requirements from Stakeholder
Requirements to System Requirements 110
6.3 Engineering Requirements from System
Requirements to Subsystems 125
6.4 Other Transformations Using a Design Architecture 127
6.5 Summary . 128
Chapter 7 Advanced Traceability 131
7.1 Introduction . 131
7.2 Elementary Traceability . 131
7.3 Satisfaction Arguments . 133
7.4 Requirements Allocation 137
7.5 Reviewing Traceability 137
7.6 The Language of Satisfaction Arguments 139
7.7 Rich Traceability Analysis 139
7.8 Rich Traceability for Qualification . 139
7.9 Implementing Rich Traceability . 140
7.10 Design Documents . 141
7.11 Metrics for Traceability 144
7.12 Summary . 151
Chapter 8 Management Aspects of Requirements Engineering 153
8.1 Introduction to Management 153
8.2 Requirements Management Problems 154
8.3 Managing Requirements in an Acquisition Organization . 156
8.4 Supplier Organizations 161
8.5 Product Organizations 166
8.6 Summary . 171
Chapter 9 Doors: A Tool to Manage Requirements 173
9.1 Introduction . 173
9.2 The Case for Requirements Management 173
9.3 DOORS Architecture 174
9.4 Projects, Modules and Objects 175
9.5 History and Version Control 181
9.6 Attributes and Views . 182
9.7 Traceability 183
9.8 Import and Export . 186
9.9 UML Modelling with DOORS/Analyst 188
9.10 Summary . 189
Bibliography . 191
Index . 195
Contents xv
 
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
 
Requirements
  Business Rules
Prototyping
Requirements Analysis
Requirements Definition
Requirements Documentation
Requirements Engineering
Requirements Management
Requirements Traceability
User Interfaces
Miscellaneous
Requirements Validation
  Acceptance Testing
Test Cases
Test Data Engineering
Test Planning
Testing Tools
Business Process Modeling (BPM)
  Data Flow Diagrams
Decision Tables
Process Analysis
Process Improvement (BPI)
Process Models
Facilitation
  Conducting Meetings
JAD
Miscellaneous
Data Analysis
  Data Models
Miscellaneous
NEW RELEASES
Business Systems Analysis
Best Practices
Interviewing Techniques
Methodologies
Problem Analysis
Request for Proposal (RFP)
Requirements Elicitation
Task Analysis
Unified Modeling Language (UML)
Use Cases
Workflow Analysis
Home Links CBAP Business Analyst Skills Test Business Anlayst Training Inquiry