UWI Software Engineering Assignment #1
UWI Software Engineering Assignment #1
Assignment #1
Date Due: February 28, 2024 @4:00 p.m.
User stories
A user story is a tool used to capture a description of a software feature from a user's
perspective. The user story describes the type of user, what they want and why. A user story
helps to create a simplified description of a requirement with no technical detail.
Task
Create 10 user stories.
1
Requirements
Functional requirements
These are statements of services the system should provide, how the system should react to
particular inputs, and how the system should behave in particular situations (What the system
should do). In some cases, the functional requirements may also explicitly state what the system
should not do.
For example:
The system shall allow users to log into their account by entering their email and
password.
The system shall allow user to upload photos to their account.
Non-functional requirements
These are constraints on the services or functions offered by the system. They include timing
constraints, constraints on the development process, and constraints imposed by standards.
Non-functional requirements often apply to the system as a whole rather than individual system
features or services.
For example:
When the submit button is pressed, the confirmation screen must load within 2 seconds
Database security must meet HIPAA requirements.
Task
What are the functional and non-functional requirements for your system?
Use Case
Task
Draw one use case diagram capturing all the requirements and actors of the system.
Rank the use cases using the priority matrix (see Expanded Use Case and Use Case
Ranking on myeLearning)
For the top-ranking use case, create the expanded use case. (see Expanded Use Case and
Use Case Ranking on myeLearning)