Description

Using the same project context from your previous assignments, document your user stories and supporting swimlane diagram.

Rationale

This assignment will evaluate the following Course Learning Outcomes:

CLO1. Apply elicitation techniques to determine the requirements for a software project.

CLO2. Extract customer needs and objectives from elicitation activities.

CLO3. Develop high-quality requirements for the successful delivery of a software product.

Directions

Part 1: Describe your scope

In a paragraph, describe the solution you are building for your client - the scope of your project. Provide enough detail that the requirements you document in Parts 2 and 3 are fully contextualized.

Part 2: User Stories

You are expected to write a total of 15 user stories.

• You may organize them into as many or as few features as you choose.
• Under the heading for each feature, include a brief description of the purpose of that feature within the solution.
• Each user story should be given a unique ID.

NOTE: You are not allowed to use the same features or stories as the sample assignment.

Part 3: Swimlane diagram

Create one swimlane diagram for a process related to the project scenario you've chosen. (It does not need to be related to a particular user story, but the process should make sense in the context of your project scenario.) In a short paragraph, explain the actors, the process, and the decision point in the process.

1. Swimlane diagram must include a minimum of 2 actors.
2. Swimlane diagram must contain a minimum of 1 decision point.

You may create your diagram in any software tool of your choosing (e.g. Visio, Lucidchart, etc.). For ideas of what kind of process to diagram, refer to this documentOpens in a new tab.