About this class
This 2-day course provides a strong foundation in the mechanics of use case diagramming and writing textual descriptions of use cases. In this highly interactive workshop, you will learn how to enhance and refine your use case skills, how to involve your stakeholders in the use case process, and how to develop use cases that provide valuable information to the designers and testers. Use cases that meet the needs of designers can be too technical and too detailed for other stakeholders. Use cases that satisfy business users are usually not very helpful to designers and testers. How do you satisfy these two disparate interests? And how do you handle the details like business rules, data validations and user interface specifications?
What you'll be able to do
- Use Cases are an industry best practice for defining, documenting, and analyzing
- functional requirements. A use case approach is a user - centered approach for developing
- a solution to your business needs. Unfortunately, methods for developing use cases vary
- Instructor - led
- industry. What information belongs in a use case? How can a use
- case be utilized to capture all the desired functionality? Are use cases applicable to all
- projects? Is there a template for writing use cases that is considered best practice? If
- you've ever been involved in a project involving use cases, you've probably encountered
- to these questions
- from one of the pioneers in Object Oriented Analysis. We have been developing and
- sharing best practices in use cases since the early 1990s.
- This 2- day course provides a strong foundation in the mechanics of use case diagramming
- and writing textual descriptions of use cases. In this highly interactive workshop, you will
- enhance and refine your use case skills, how to involve your stakeholders in
- the use case process, and how to develop use cases that provide valuable information to
- the designers and testers. Use cases that meet the needs of designers can be too
- technical and too detailed for other stakeholders.
- Understanding of business analysis
- Knowledge areas of BABOK® Guide
- Module 2: Overview of Use Cases
- Describe the purpose and value of a use case approach
- Use case terminology
- Introducing a use case approach
- Module 3: Strategy Analysis
- Purpose of Needs Assessment
- Needs Assessment and use cases
- Defining and understanding the strategic goals and objectives
- Understanding the business process
- Identifying actors Identifying business information
- Analyzing locations and operations
- Drawing the business use case diagram
- Building the business architecture
- Defining solution options
- Module 4: Defining System Scope
- Product scope/project scope
- System actors versus business actors
- Analyzing the business process model
- Analyzing business use cases
- Identifying candidate use cases
- Identifying scenarios
- Diagramming use cases
- Draw a use case diagram
- Create a use case catalog
- Module 5: Evaluating, Prioritizing, and Packaging Use Cases
- Iterative nature of this work
- Evaluating use cases
- Use case priority
- Use case risk
- Use case complexity
- Use case dependencies
- Evaluate and Prioritize use cases
- Dividing work up between releases
- Packaging
- A process for how to perform packaging
- Module 6: Writing the main success scenario
- Use case descriptions
- Primary and secondary goals
- Assumptions
- Pre - conditions
- Triggers
- Post - conditions
- Scenario example
- Main success scenario
- Conditional execution
- se cases and requirements
- Best practices for writing a use case description
- Module 7: Writing the other scenarios
- Scenarios and flows
- Alternate scenarios and flows
- Alternate vs. basic flow
- Guidelines for alternate flows
- Exception flows
- Failed post conditions
- Write alternate and exception flows
- Module 8: Process Modeling to describe use case flows
- UML® Activity Diagram Notation
- Sequencing activities
- Developing an activity diagram
- Facilitated sessions
- Draw a UML® Activity Diagram
- Module 9: Module 9 Using Advanced Diagramming
- Techniques
- Commonality
- Dependency Relationships
- I ncl udes
- Ext e nds
- Identify < includes > and < extends > relationships
- Comparing the different relationships
- Module 10: Developing a Requirements Specification
- Requirements and use cases
- Detailed requirements
- Common approaches to specifications
- Non - functional requirements
- Write non- functional requirements
- User interface requirements
- UI data descriptions
- Business rules
- Decision tables and inference rules
- How to document simple calculations
- Reporting requirements
- Data requirements
- Data accessibility requirements
- Traceability
- Module 11: Course Summary
- Wrap- up
- Finding more information
Course outline
Develop a Business Use Case Diagram Identify system actors and distinguish between a primary and secondary actor Templates for common Strategy Analysis techniques . candidate system use cases Develop a System Use Case Diagram and learn to write a brief description Evaluate use case risk, complexity, priority, and dependencies to: Describe how to organize use case packages Write the steps of the main success scenario Identify and develop alternate scenarios and flows Explain how a UML Activity Diagram supports a use case approach
Module 1Introduction
Download the full outline (PDF)
Before you attend
Knowledge of requirements process and requirements elicitation techniques . Student Materials How do you satisfy these two disparate interests? And how do you handle the details like business rules, data validations and user interface specif i cations?
Run this for a team
Private cohorts run on your dates, at your site or online, with the labs pointed at your environment. Above about four people it usually costs less than buying seats.
More business analysis classes
Agile Fundamentals
- $795 per seat
3 dates on the calendar
Building Better Business Cases
- $795 per seat
Business Analysis & Mastering the Requirements: Bring Success to Projects
- $2,595 per seat