Table Of Contents

The following are links to the process documents in PDF format. Links are updated as content becomes available.

The contents of this document are:

Introduction             Describes how MS Office is being used by the examples contained in this work.

Chapter 1           Is an overview of the major problems that the process is attempting to solve. This section introduces the reader to some best practices for helping to solve the major problems that an analyst might encounter with software requirements management.

Chapter 2         Is all about use cases. The types of use case described, are business use cases (BUCs) and application use cases (AUCs). This chapter identifies the difference between the 2 types of use case and introduces templates for writing use cases

Chapter 3            Defines a notation for modeling use cases with use case diagrams.

Chapter 4            Contains a notation for detailing activity diagrams. It describes how UML activity diagrams may be used to capture the different components of a BUC and an AUC.

Chapter 5            Contains guidelines for modeling classes with a logical model.

Chapter 6            Introduces the reader to states. In particular it describes a notation for modeling classes with State Transition diagrams.

Chapter 7            Contains examples of Business and Application use cases.

Chapter 8             Contains ideas for organizing artifacts of an iterative development process. In particular it describes a method for organizing a requirements repository such that software applications may be developed in parallel.

Chapter 9             Describes best practices for managing a glossary. The importance of maintaining a glossary for your project, what the glossary comprises, tools for maintaining the glossary and how to use the glossary in conjunction with documentation.

Chapter 10        Describes the Business Vision in terms of a vision template, the contents of the vision, its purpose and how it is used on a project.

Chapter 11         Contains an example of a Business Model, including business architecture rules and business use cases.

Chapter 12         Describes how to progress through the lifecycle from a BUC model to an AUC model.

Chapter 13         Contains guidelines for producing a class (logical) model from the details of the AUC.

Chapter 14         Describes how to model the logical model with state transition diagrams.

Chapter 15        Introduces use case realizations. It describes how to realize AUCs with sequence diagrams.

Chapter 16   Concludes requirements capture with some best practices for writing software requirements. It includes guidelines for detailing the requirements that were captured by the AUC model.

Chapter 17     Describes Use Case storyboards. These are useful for gaining feedback from the stakeholders about the user interface functionality associated with the use cases.

Chapter 18       Describes the contents of a requirements management plan; It contains Ideas for managing requirements and traceability using a document management tool, such as MOSS.

Chapter 19        Is a summary. It includes an overview of the complete process.

Afterword          Contains a series of ramblings related to the work in this book.

Appendices       Contains a glossary of terms used within this book, and it includes a complete analysis model of the Automated Menu System project. Diagrams represent all stages of the process from the business Vision through to use case realizations.