|
|
|
|
|
| I. Introduction |
| | Opening introductions, establishing the workshop rules, and discussions of the objectives. |
| | | (a) Introduction to the Workshop |
| | | (b) Getting the Most out of the Workshop |
| | | (c) Workshop Objectives and Agenda |
| |
| II. Workshop Context |
| | To manage workshop expectations, we need to establish the scope of the material. We need to understand where it fits in the development life cycle and the project management process. This section also provides some definitions, terminology and structure. |
| | | (a) The Definition and Purpose of Requirements |
| | | (b) Workshop Focus |
| | | (c) The Analysis Process |
| | | (d) Developing a Requirements Specification |
| | | (e) Creating and Using Models |
| | | (f) Model Notation and Strategy |
| | | (g) What Makes Effective Requirements |
| |
| III. Identifying the Scope and Context (High-Level View) |
| | The first step is to attempt to determine the scope of the project and establish the boundaries. This may be uncertain or incomplete at this stage but there are some techniques and models to provide a starting point. |
| | | (a) Project Scope Definition |
| | | (b) Diagraming the High-Level View — Context Diagram |
| | | (c) Identifying Functionality |
| | | (d) Subdividing the Scope into Business Use Cases |
| | | (e) Definition and Concepts of Use Cases |
| | | (f) Introduction to the Case Study |
| | | | Assignment: Find business use cases. |
| | | (g) Events, Triggers, and Deliverables |
| | | (h) Functional Process Map |
| | | | Assignment: Define events, stimuli and deliverables. |
| |
| IV. Specifying Business Process |
| | Business process drives the need for data and is the most readily understood. As we dive down to the detail level, the process models form the foundation of the documentation and of the communication process. This section examines the style, format and structure of the information gathering and process modeling. |
| | | (a) Business Use Case Models |
| | | (b) Introduction to the Model Components |
| | | (c) Creating the Narrative |
| | | (d) Exceptions and Alternatives |
| | | (e) Adding Non-Functional requirements |
| | | | Assignment: Create a Use Case narrative. |
| |
| V. Discovering Business Data |
| | | (a) The Object Participation Diagram — Description and Notation |
| | | (b) Participating Objects and Attributes |
| | | (c) Discovering Objects and Identifying the Data |
| | | | Assignment: Create an Object Participation Diagram. |
| | | (d) Evaluating Relationships |
| | | (e) Developing the Collaboration Table |
| | | | Assignment: Develop a Collaboration Table. |
| |
| VI. Specifying Business Data |
| | Once the business processes are agreed and understood, the data necessary to support the processes can be studied. Data is strongly tied to the business objects recognized by the end users. The section reveals the techniques for accurately establishing the data requirements and modeling them clearly through business objects. |
| | | (a) Object Specifications — Description, Rules, Data, Operations |
| | | (b) Data Attribution |
| | | (c) Object Identity |
| | | (d) Data Representation |
| | | | Assignment: Create an Object Specification. |
| | | (e) Discovering Operations |
| | | (f) Defining Operations as Functional Requirements |
| | | | Assignment: Develop a set of operations. |
| | | (g) Object State Diagrams |
| |
| VII. Identifying Business Rules |
| | | (a) Understanding Business Rules |
| | | (b) Discovering Business Rules |
| | | (c) Types of Business Rules — Constraints, Guidelines, Action Enablers, Computations, Inferences. |
| | | (d) Documenting Business Rules |
| | | (e) Business Rules Catalog |
| |
| VIII. Specifying User Interfaces |
| | Having established the structure of the requirements, they need to be made visible to the end user. The visibility of the system is through the human interfaces. This section shows how to capture the logic of the proposed interfaces and make the interactions clearly visible to all participants. This has a very significant impact by greatly reducing the number of changes produced later in the project. |
| | | (a) Finding the Human Interfaces |
| | | (b) Separating Manual and Automated Processes |
| | | (c) Creating an Interface Logic Chart |
| | | (d) Security, Integrity, and Control Requirements |
| | | (e) Reports and Inquiries |
| | | | Assignment: Create an Interface Logic Chart. |
| |
| IX. Managing Requirements Elicitation |
| | It is important to understand who the customer is and to communicate regularly. This section takes a look at the communications process and then reviews the project tools and techniques for managing the communication. |
| | | (a) Requirements Elicitation Process |
| | | (b) Elicitation Challenges |
| | | (c) Communication Skills |
| | | (d) Interviewing |
| | | (e) Asking the Right Questions |
| | | (f) Communicating with Models |
| | | (g) Traceability |
| | | (h) Information Gathering Methods |
| | | (i) Bridge the Gap with Facilitated Sessions |
| | | (j) The Steps, Participants, and Facility |
| | | (k) The Sessions — Opening, Controlling, Closing |
| | | (l) An Examination of the Benefits |
| |
| X. Developing a Requirements Specification (Putting it All Together) |
| | A final review of all the parts. This section looks at the requirements document as a whole and the various model and sequence of steps in the context of the big picture. The participants will carry out a major assignment to create a requirements specification from scratch. |
| | | (a) The Model Components |
| | | (b) Model Validation |
| | | (c) Modeling Sequence |
| | | (d) The Complete Requirements Specification Document |
| | | (e) Modeling Effort |
| | | | Assignment: Create a complete requirements specification. |
| |
| XI. Summary and Conclusion |
| | A wrap-up session to review the lessons learned and an opportunity for discussion and how to apply the lessons in the real world. |
| | | (a) Objectives Revisited |
| | | (b) Lessons Learned |
| | | (c) Discussion |
| | | (d) Wrap-Up |
