Developing Process Models and Use Cases
Be more effective in your requirement gathering techniques and communicate more precisely the needs of the future state solution with use cases and process models, two of the most powerful tools in business analysis.
A use case is a written description of the needs a stakeholder group has for a system as well as the means by which the system will meet those needs. A process model is a visual description of the actions, objects, and relationships acted upon in the system. Together, these two tools help teams communicate and build easy-to-use, high-performing systems. In this applied course you’ll use the classroom as a learning laboratory, crafting a variety of simple to complex use cases and process models.
Who Should Attend
Business analysts, software developers, new product developers and managers, process improvement specialists, project managers.
Continuing Education Units
This course provides 1.4 Continuing Education Units (CEUs)
How You Will Benefit
- Develop process diagrams in helping stakeholders understand operational flows
- Use essential features of BPMN to draw process diagrams
- Develop use cases in varied formats using stakeholder input that describes the needs of complex system activity
- Leverage use cases to provide value in solution design
- Practice facilitating sessions to elicit and document user needs
- Leverage use case content to provide value in solution design
Day 1 - Process Modeling
- Process modeling and BPMN: history of BPMN, where BPMN is not a good fit for modeling, comparing UML and BPMN diagrams
- Parts of the process model: activities (tasks and sub-processes), flow types, swim lanes (pools and lanes), gateways (exclusive, inclusive, parallel, complex), gateway usage (bad, better, best), events and artifacts, representative BPMN symbols, business case (scoping diagram)
Day 2 - Use Cases
- What is a use case and why should you write one: the importance of stories; use case types (usage narrative, summary, and detail); categories of requirements and use cases; how use cases help stakeholders, analysts, developers, and testers
- The use case process: solution process scope; use case titles; identifying actor and actor’s goals; developing main process steps; developing alternate and exception process steps; scope and stakeholder interests; triggers, assumptions, and conditions; what is a business rule; project artifacts developed from use cases
- Leveraging use cases in database and UI design
- Facilitating story writing workshops
- Case analysis: applying visual and written requirements elicitation tools
- Action planning and gaining organizational buy-in
Joe is a senior business analyst and project manager at the University of Wisconsin-Madison Division of Information Technology (DoIT).
Joe's background includes significant work in providing solutions to public and private organizations in sectors including agriculture, accounting, education, manufacturing, retail, public housing, law enforcement, judicial courts, public health, and natural resources. Over a 35-year career, he served clients while employed at several software development companies, a regional accounting and consulting firm, and an international computer vendor, in addition to his work as an independent consultant.
He began designing and developing systems to help people in 1978. Since starting work on campus in 2004, he has improved DoIT's effectiveness in project management, business analysis, and testing. He continues to mentor and support campus staff interested in a career in business analysis and project management.
Joe reduces project costs and improves outcomes by eliciting, validating, and communicating requirements. He serves as a pathfinder, helping teams to identify the problem they face, to imagine a better future, and to find an appropriate pathway to that future. He is a trusted adviser to his customers and peers in business analysis, project management, solution design, and process improvement. Joe has many years of experience as a sought-after group facilitator, teacher, mentor, and team leader.
Program: 8:15 a.m.-5 p.m.
Lunch and Breaks are Included with Program Registration
Program Check-In will be 7:30-8:15 a.m. on the first day of the program.