- Course Topics
- Client testimonials
Who the course is for:
- Business analysts that are involved in use case modeling as part of their daily work
- Systems analysts, technical leads, database analysts and software developers who must use requirements as the basis for solution specification, development and implementation.
- Project managers and project team members who incorporate the business analysis role into their functional activity sets
By the end of this course, you will be able to:
- Employ use cases to elicit, analyze, document and communicate functional requirements for software
- Use the Unified Modeling Language (UML) to create use case diagrams
- Determine when to employ use case modeling
- Prioritize use cases based on their importance to the business and on technical considerations
- Describe ways to develop consistent vocabulary between use cases and objects
- Analyze and document detailed requirements using an object model
- Read a class diagram
- Useful and readily applicable tools
- Consistent professional terminology in the field of business analysis
- An international expert available for consultation (during and after the training course)
- Sharing experience with other participants and opportunity for business networking
- A prestigious certificate from George Washington University
- Improving your business English skills
- Bilingual training materials with additional reference materials
Recommended books from our Bookstore:
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 modeling, 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 cases and use case diagrams, which serve as a vehicle for eliciting, analyzing, documenting and communicating functional requirements.
1. Introduction to Use Case Modeling
- a. Organizing requirements with use cases
- b. Use case diagrams as a UML notation
- c. Organizing the model with packages
2. Identifying and Describing Actors
- a. Use case actors
- b. Business versus system actors
- c. Identifying actors
- d. Mapping stakeholders to actors
- e. Users versus actors
3. Identifying and Describing Use Cases
- a. Identifying use asus
- b. Writing a use case description
- c. Including preconditions, postconditions, assumptions, and scenarios
4. Writing Use Case Scenarios
- a. Identifying the main success cenerio
- b. Identifying lternatem and exceptions
- c. Indicating iteration
5. Advanced Use Case Modeling Techniques
- a. Diagramming an "include" relationship
- b. Diagramming an "exclude" relationship
- c. Diagramming generalization and specialization
- d. Considering multiplicity
6. Ensuring Use Case Quality
- a. Employing quality assurance techniques
- b. Ensuring use cases are testable
BABOK® Guide knowledge areas:
- Requirements Life Cycle Management
- Requierements Analysis and Design Definition
- Solution Evaluation
No client testimonials about this training
- IIBA® , BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis.
- CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis.
- Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
- PMI is a registered mark of the Project Management Institute, Inc.
- The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc
- PMBOK is a registered mark of the Project Management Institute, Inc.
- PMP and PMI-ACP are registered marks of the Project Management Institute, Inc.
Type of training