As a fundamental component to identifying requirements for a new system, business analysts must be able to illustrate how "actors", such as end users, stakeholders, or related systems, will be affected once the new system is implemented. This process, also known as Use Case Modelling, provides business analysts with a powerful tool for documenting functional requirements - and the interactions between these requirements - in a manner that can be easily communicated to designers, programmers, project manager and other project stakeholders.
This course provides business analysts with the required competencies for creating use case diagrams and use case scenarios, which serve as a vehicle for eliciting, analysing, documenting and communicating functional requirements. Delegates will practice creating use cases in the Unified Modelling Language (UML) to graphically represent the interactions between use cases and actors. To fully gain the benefits of UML, use case diagrams are created through an object-oriented approach, which enables business analysts to sift through the complexity of a system by breaking it down into smaller units.
Attendees of this course will gain more than just the lexicon required for use case and object oriented modelling. Through interactive exercises, they will practice writing the alternate/exception flows, arranging objects into properly named classes and reading class diagrams and most importantly, gain the ability to integrate use case modelling within the software development lifecycle to ensure that project requirements are accurate, complete and map to the objectives of the business.
Reminder: Prior to taking this course, delegates should have acquired the background as taught in Eliciting and Managing Requirements and Business Process Modeling.
Vad kommer jag att lära mig?
- Employ use cases to elicit, analyse, document and communicate functional requirements for software
- Use the Unified Modelling Language (UML) to create use case diagrams
- Determine when to employ use case modelling
- Prioritise use cases based on their importance to the business and on technical considerations
- Describe ways to develop consistent vocabulary between use cases and objects
- Ensure use case quality
Advanced Use Case Modelling Techniques
Diagramming an <<include>> relationship
Diagramming an <<exclude>> relationship
Diagramming generalisation and specialisation
Ensuring Use Case Quality
Employing quality assurance techniques
Ensuring use cases are testable
Identifying and Describing Actors
Use case actors
Business versus system actors
Mapping stakeholders to actors
Users versus actors
Identifying and Describing Use Cases
Identifying use cases
Writing a use case description
Including pre-conditions, post-conditions, assumptions and scenarios
Introduction to Use Case Modeling
Organising requirements with use cases
Use case diagrams as a UML notation
Organising the model with packages
Prioritising Use Cases
Estimating project cost with use cases
Employing prioritisation techniques
Writing Use Case Scenarios
Identifying the main success scenario
Identifying alternates and exceptions