Packed with hands-on exercises, this industry-endorsed 1-day course provides the student with a solid foundation of the basic structure and techniques to write effective use cases with confidence. The course presents a holistic view of Use Case Modeling that consists of two main components: (1) Graphical view, represented by the Use Case Diagram, and (2) Textual view, represented by the Use Case Specification. The student learns how to apply a 3-step approach to Use Case Modeling. Within the documented, repeatable Requirements Management Process, the Requirements Producer (any individual who is responsible for eliciting, analyzing, representing, validating, and managing changes to the requirements) may utilize Use Case Modeling as another form of “Representing” requirements. “They [Use Cases] constitute only a fraction (perhaps a third) of all the requirements…,” says Allistair Cockburn in his book Writing Effective Use Cases, Addison-Wesley, 2001. The student will gain knowledge regarding when and when not to apply Use Cases for representing requirements. This course combines lecture, delivered by an expert practitioner, a playful and fun learning environment, small-group and individual practical exercises, and class discussions on real-life requirements problems and solutions.
Practical Techniques Presented
- User Role Analysis to identify any person or any thing that interacts with the system being developed.
- User Goal Analysis to identify the value each User Role gains from interacting with the system.
- Unified Modeling Language (UML) as an industry set of symbols used in modeling.
- Use Case Diagramming to graphically identify the User Roles of the system and their respective goals.
- Use Case Formatting to logically group and organize the requirements in a manner that is easy to read.
- User Scenario Analysis to identify all possible sequences of actions that illustrate
the system behavior.
- Pre-condition and Post-condition Analysis to identify the Use Case success criteria.
- Use Case Pitfall Analysis is used to identify and correct problems with writing the Use Case.
Objectives
- Understand Use Case Modeling.
- Gain knowledge of industry best-practice techniques for representing requirements using Use Case Modeling (Use Case Diagram and Use Case Specification).
- Understand the 3-step approach to Use Case Modeling.
- Apply several learned techniques through hands-on exercises to give participants the confidence to use the techniques following their education experience.
Intended Audiences
Business Analysts, System Analysts, Business Technologists, Technical Analysts, Requirements Analysts, Business Process Analysts, and Product Design Developers.
Use Cases That Get Used
Packed with hands-on exercises, this industry-endorsed 1-day course provides the student with a solid foundation of the basic structure and techniques to write effective use cases with confidence. The course presents a holistic view of Use Case Modeling that consists of two main components: (1) Graphical view, represented by the Use Case Diagram, and (2) Textual view, represented by the Use Case Specification. The student learns how to apply a 3-step approach to Use Case Modeling. Within the documented, repeatable Requirements Management Process, the Requirements Producer (any individual who is responsible for eliciting, analyzing, representing, validating, and managing changes to the requirements) may utilize Use Case Modeling as another form of “Representing” requirements. “They [Use Cases] constitute only a fraction (perhaps a third) of all the requirements…,” says Allistair Cockburn in his book Writing Effective Use Cases, Addison-Wesley, 2001. The student will gain knowledge regarding when and when not to apply Use Cases for representing requirements. This course combines lecture, delivered by an expert practitioner, a playful and fun learning environment, small-group and individual practical exercises, and class discussions on real-life requirements problems and solutions.
Practical Techniques Presented
Objectives
Intended Audiences
Business Analysts, System Analysts, Business Technologists, Technical Analysts, Requirements Analysts, Business Process Analysts, and Product Design Developers.