Managing Systems Requirements : Methods, Tools, and Cases |
|
|
|
|
| Stephen J. Andriole |
| June 1996, McGraw Hill Text, Hardcover, 318 pages, ISBN 0070019746
|
|
|
|
 |
|
This volume provides a complete blueprint for aligning business
process objectives, covering methods for modeling existing processes,
extracting and modeling systems requirements, and designing and
evaluating prototypes. IS managers, process analysts, and systems
planners, designers, and developers, will find how-to guidelines
throughout, explaining a practical methodology for the technical
reengineering of today's software-intensive industries.
The author includes
-
recommended software solutions that are off-the-shelf;
-
a programmer-friendly "methods, tools, and cases" approach;
-
private and public sector case studies; and
-
both high level requirements modeling and functional requirements
analysis.
This is the first book to get down to brass tacks with practical
methods, real life case studies, and commercial software tools for
the job of technical reengineering today's business processes.
|
Part
I: Process Modeling and Requirements Management Process Improvement
The Systems Situation
Requirements Management Process Improvement
Part
II: Requirements Management Process
Requirements Management Overview
Requests and Definitions
Requirements Analysis and Modeling
Requirements Change Management and the Requirements Agreement
Part III: Requirements Management Tools
Overview of Requirements Management Tools
The Tools Database
Part
IV: Case Studies
The Outreach Project
The E2C Requirements Project
Process Reengineering Case Studies
Part V: Afterthoughts.
|
|
 |
|
A ground-breaking new approach to practical systems requirements
management...
Here is the first book to offer a practical way to identify systems
requirements and manage them when budgets and schedules are tight.
It describes a process that leads from fuzzy, ill-defined requirements
that can be modeled and prototyped. Managing
Systems Requirements presents methods for communicating requirements
and achieving buy-in from system users and owners before expensive
programming begins.
There are techniques, tools, and software suggestions for project
managers and systems analysts, plus case studies that illustrate
how the whole requirements gathering process works. The cornerstone
of the book is its practicality; it combines in one place a suite
of methods, templates, off-the-shelf computer-based tools, and real-world
examples that software developers can use to get a handle on software
requirements and solve the problems they face every day on the job.
IS managers, system project managers, systems analysts, and programmers
will find the book indispensable and value how it integrates technical
methods with organizational realities.
|
|