| Unit: | Requirements Process and Use-Case Modeling |
Unit Identifier: OO2003
Unit Overview:
This unit provides a detailed description of the use case modeling technique. It covers use case notation, procedural steps in developing use cases, and practical ideas for using use case models to guide and document analysis and design. It also addresses how use cases can be utilized to develop system and acceptance test plans and test cases for a project.
The use case technique offers a relatively easy, low cost method for documenting requirements and capturing analysis and design facts. The technique is especially suited for iterative, evolutionary development characterized by the object-oriented approach. Documented system features can easily be identified and changed as the system evolves toward completion.
This unit supports the early phases of the project. Use case skills should be learned and applied during requirements gathering, analysis, and design phases of the project. The testing team can also benefit from this technique by utilizing approved use case in test planning and design.
Unit Duration: 8 hours
Unit Objectives:
Students will begin to build practical skills in using the technique to support Object-Oriented analysis and design. They will also learn to more effectively perform requirements gathering, analysis, and design
- Explain what a use case is and how it is used in the requirements definition, analysis, and design processes
- Define the seven parts of a use case and explain how they are each used
- Understand how use case relationships can be expressed as inheritance and composition relationships in order to facilitate their reuse
- Break down business processes into use cases and correctly document the use case using basic textual notation
- Understand the relationship between use cases and scenarios. Be able to create scenarios for defined use cases
- Learn use case diagramming techniques and be able to relate several use cases to a system user (actor) with a use case diagram
- Understand the values of use cases in requirements gathering, analysis, design, and testing. Be able to leverage documented use cases in order to facilitate these development processes
Unit Outline:
- 1. What Are Use Cases?
- Definition
- Value to a development project
- How they are used
- Identify and define classes, behaviors, messages
- Documentation of requirements
- Input to test planning and design
- Seven Parts of a Use Case
- Name/Identifier
- Purpose
- Uses
- Extends
- Extended By
- Typical Course of Events
- Alternative Courses of Events
- Guidelines for Preparing Use Cases
- Segmentation of business process
- Identification of alternative courses of events
- Using inheritance and composition relationships with use case
- Preparing a Use Case and Scenarios
- Define use case scenarios
- Review the process
- Use Case Diagramming
- Definition and description of notation
- How diagrams are used in a development project
- Value added
