|
Provided by: Boston University Corporate Education Center Gathering and Documenting User Requirements with Use CasesUnfiled |
 |
Learn state-of-the-art practices for gathering and documenting requirements based on the Use Case approach. You will facilitate requirements-gathering sessions and document the results over the course of a case-study project with an emphasis on the textual aspects of the documentation. This course covers what the facilitator needs to accomplish in each requirements-gathering session (goals, agenda, who to invite, artifacts, etc.) as the project progresses - starting from Business Use Case sessions that focus on the business context through to those that focus on user-IT interactions. You will also learn advanced techniques (extension, generalized and inclusion Use Cases) that result in requirements documentation that is easy to revise when business rules change.
The clear style and organization of Use Cases makes them well-suited as a source of test cases and for communicating with both business stakeholders and developers. Use Cases are a central aspect of iterative development methodologies such as IBM s RUP and Microsoft s MSF.
The Use Case approach improves outcomes by providing effective solutions to challenges such as:
- Inexperienced BAs are often unclear about what level of requirements to capture at each phase of a project
- BAs are often unsure how to divide a large project up into Use Cases
- Ineffective facilitation of requirements gathering sessions
- Confusion over the role of text vs. diagrams
- Confusion over the level of detail to include in the written requirements
- Small changes to the business environment often lead to big changes in the documentation
This course will help you solve these problems, and provide practical experience in employing this state-of-the-art technology to the requirements elicitation phase of a project. By working on a realistic case study in a small group that simulates an actual analysis team, you will gain a skill-set that can be effectively applied on the job.
Mapping to the IIBA Body of Knowledge
Boston University is a Charter Endorsed Education Provider of the International Institute of Business Analysis (IIBA). This course supports understanding of the following knowledge areas as defined by the IIBA in the draft of the Body of Knowledge (BOK) released in July of 2006:
- Enterprise Analysis
- Requirements Elicitation
- Requirements Analysis and Documentation
- Requirements Communication
Who should attend
- IT Business Analysts
- Project Leaders
- Facilitators who will be leading requirements gathering sessions
- Business Users who will be explaining business requirements to software developers
- Systems Analysts expanding their role into the business realm
What you will achieve
Upon completion of this course, you will be able to:
- Facilitate requirements gathering sessions with Use Cases
- Examine the impact of the project on the enterprise through Business Use Case analysis
- Create detailed textual requirements with the Use Case Description Template
- Decrease software bugs and omissions introduced in the analysis phase of your project by employing powerful techniques that reduce redundancies and inconsistencies in the documentation
- Communicate effectively with the development team, through the use of the widely accepted UML 2 documentation standard
- Model high-level requirements with Use Case diagrams
- Understand how Use Cases are used in the context of iterative development
- Link other relevant material to Use Cases such as business entities, non-functional requirements and activity diagrams
What you will learn
Introduction to Use Cases
- History of Use Cases
- Use Cases and the Business Requirements Document
Criteria for selecting projects
Facilitating Requirements Gathering Sessions with Use Cases
- Rules for conducting Use Case workshop sessions
- Preparation
- Who should attend
- Roles
- Defining the Deliverables: When to best introduce and create:
- Stakeholder Interest Table
- Use Case Packages
- Role Maps
- Use Case Diagrams
- Use Case Text
Eliciting and documenting detailed user requirements
- Use Case Description Template
- Writing guidelines
- Numbering the requirements
- Defining the users of the system
- Role Map
- Defining generalized and specialized actors
- Triggers
- Preconditions and Postconditions
Basic (Normal) Flow - Alternate and Exceptional Flows
Working with stakeholders to discover and document the textual requirements
Organizing the documentation for maximum reuse with inclusion, extension and generalized Use Cases
Links to other documentation
- Data dictionary
- Entity classes and class diagrams
- Activity Diagrams
- Non-functional requirements
Avoiding common errors
Standard solutions for common situations
- Customer IVR identification
- CRUD (Create/ Read/ Update/Delete)
- Login
- Technology variations
- Customer self-service
- Geographical sub-sites within an e-commerce application
Agenda
Day 1:
- Introduction to Use Cases
- The Kick-off Meeting - analyzing stakeholders and interests; identifying high and mid-level objectives
- Analyzing Business Use Cases
- Structuring System Use Cases
Day 2
- Eliciting and Documenting System Use Cases/ Context and Basic Flow
- Eliciting and Documenting Alternate and Exception Flows
- Documenting Inclusion, Extension and Generalized Use Cases
- Linking Use Cases to Other Project Artifacts (Documentation and Models)
|
|
||||||||||
