Use Case Overview Assignment

1. About This Sprint
2. User Stories covered in this Sprint
3. Learning Material
4. Experiential Learning
- 4.1. Assignment: Use Case Overview
- 4.2. Update Course Backlog
5. Sprint Acceptance Tests

1 About This Sprint

This sprint introduces UML use cases and UML use case diagrams as a means of putting requirements into a context and understanding the interactions between users and the system.

In this sprint you start creating an overview of the UML use cases that together describe your system.

2 User Stories covered in this Sprint

As a software designer I want to document what the customer is telling me so that I can discuss my understanding of their requirements with them.
As a software designer I want to document what the customer is telling me so that I can easily continue designing based on a joint understanding.
As a software designer I want to be able to reuse common procedures between my use cases so that I only have to maintain them in one place.
As a project manager I need to decide what to focus on building right now so that I best satisfy all customers’ expectations.
As a product manager I want to make sure that we are building software of high quality.
As a student I want to have a clear overview of what I am supposed to work on so that I am able to focus on what is important.

3 Learning Material

Please review the sprints concerning

Use Cases and Use Case Diagrams

4 Experiential Learning

4.1 Assignment: Use Case Overview

PA1415 Software Design: In this part of the assignment you will continue with the requirements document that you have already created and transform your user stories into UML use cases.

PA1435 Object Oriented Design: In this part of the assignment you will write UML use cases based on the system description for the assignments.

PA1434 Basic Object Oriented Design: In this part of the assignment you will write UML use cases based on the system description for the assignments.

Tasks:

Create a Use Case Diagram
- Identify all actors that are interacting with the system.
- Identify all use cases of the system (features).
- Identify which actors are involved in each use case.
- Identify any other relations between the use cases (This may be relationships of the form includes or extends, but may also be just another heading in the use case “Related Use Cases” to be able to group use cases dealing with the same underlying feature). Please note that you do not need to have any relations. The idea is to identify the most obvious relationships, if there are any.
Briefly describe the actors in a dictionary.
Describe the use cases in a high-level description, containing:
- Use Case Name
- Primary Actor
- Brief Description
For students of PA1415 Software Design, link your user stories to the relevant use cases by adding an attribute:
- Concerned User Stories

Document Structure:

The title for this Assignment Document is: Use Case Overview for System <system name>

The assignment document shall contain the following items:

Title Page, according to the Title Page Instructions (Link)
System Description

A brief description (2-3 paragraphs) of your interpretation of what the goal of the system is.

Use Case Diagram
Description of Actors
High-Level Use Cases

Commit and push this document to your project repository.

Conditions of Satisfaction:

When marking this part of the assignment we are looking for the following:

Does the title page contain a table with authors and author contribution
Size of assignment: Are there 15-25 high-level use cases?
Are all relevant actors identified and described?
Are all relevant use cases identified and briefly described?
For each use case, are all the relevant actors linked?
Is the use case diagram well formed?
Do all the use cases have all attributes?
Do all the use cases have unique and good names?
Do all the use cases have a sufficient and proper description?
(PA1415) Are the use cases linked to the relevant user stories?
(PA1415) Are all user stories linked in at least one use case?

4.2 Update Course Backlog

How do you design a system from your use cases? What should you look for when you are trying to understand the structure of your system? What about the behaviour of the system?

Are there any other questions that you want answered? Add them, along with a brief strategy for how to find an answer.

5 Sprint Acceptance Tests

You are done with this sprint when:

You have created a “Use Case Overview” document
You have committed/pushed these documents to your project repository

You may also have

Updated your Sprint Test Plan
Updated your Course Backlog