This Course introduces use-case modeling and explains why you would want to use it. It provides a concise overview of the basic concepts employed in use-case modeling, and describes why use cases provide a superior way to capture the behavior of a system. The basic idea behind use-case modeling is quite simple: To gel to the heart of what a system must do, you must first focus on who (or what) will use it, or be used by it. After you do this, look at what the system must do for those users in order to do something useful.
The key topics of this Course are: 1. Explaining a Use Case Model, High Level Use Cases and Expanded Use Cases. 2. Modeling a Use Case Diagram using the UML. 3. Effectively defining Use Cases and soliciting functional requirements with the and Finally describing how Use Cases are used in planning, testing and Object-Oriented Analysis and Design
Learning Objective:
To give system analysts the knowledge and confidence to undertake requirements modeling using the UML. With the appropriate use of UML diagrams and model views, analysts will be able to produce requirements specifications for accurate and unambiguous communications with the project stakeholders and with software developers.
This Course consists of two Parts:
In Part I, we provides a general introduction of the use-case approach covers all the notation, key elements of use case modeling and basic techniques for conducting use case analysis and design for people who may or may not familiar with use-case modeling.
We will then return to these concepts for a more in-depth look in Part II which covers the process of how to elaborate use cases into scenarios and these scenarios details main, alternative and exception of use case paths. Finally, the course will also cover the skill and techniques of writing use case description and preparing use case template for further use case development.
Part I: Use Case Modeling And Analysis
Table of Contents
1. The Costs of Software Project Failure
- IS Development Project Track Recor
- Software Project Failure Surveys
- Modeling System Requirements
- A Funny Cartoon Of Software Project Failure
2. What is is Requirement?
- Type ofn Requirements
- Requirement Analysis
- Viewpoint of Stakeholder
- Transform Need to Requirments
3. User-Centered Development and Use Case Modeling
- How to Conduct Use Case Analysis?
- What is a Use Case?
- Usae Case Definition
- Why Use Case?
- Steps for Use Case Analysis
- System Boundary
- Use Case are System Operations
- Use Case vs. Traditional Feature Specification
- Architecture of 4+1 View Model
4. Use Case Capture Requirements
- Use Case Driven Development
- Design and Implementation: Use Case Design
- Use Case Realization: Components
- Use Case for Testing
- Use Cases Partition the System
5. Role of Use Case Modeling
- Benefits of Use Case Modeling
6. Use Case diagram
- Use Cases
- Naming Use Cases
- Example Use Cases
- Primary vs Secondary
- Essential vs. Concrete
7. What is Actors?
- Actor: Role of the User
- Relationships between Actors
- Actor Relationships: An Example
- Actopr Types
- Identify Acotrs
8. Recording Use Cases
- Video Store System Example
- Finding Actors
- Video Store Example: Finding Use Cases
- Video Store System: Other Actors.
- Identify Use Case
- Identify Additional Use Cases
- System Boundary
9. ATM Example
10. Structuring Use Case by Relationships:
- Include and Extend
- Generalization Relationship
- Concrete and Abstract
Part II: Scenario Wrting Techniques
Table of Contents
1. Describing Use Case with Scenarios
2. Use Case vs. Scenario
3. Benefits of Scenario Analysis
4. Type of Scenarios
5. Mapping of Scenario with Extend and Include Use Cases
6. Coruse Registration Example
- Flow of Events - Normal Scneario
- Alternative Scenario
7. Identifying Use Case Scenarios.
8. Guidelines for Detailing Use Cases
9. Documenting Use Cases
10. ATM: Use Case Model
- ATM withdraw fund use case
- Main and Alternative Scenarios
- Validate Pin Use Case & Sceanrios
Course Content:
