0% found this document useful (0 votes)
36 views2 pages

UWI Software Engineering Assignment #1

COMP 2606 ASG1

Uploaded by

joshua sankar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views2 pages

UWI Software Engineering Assignment #1

COMP 2606 ASG1

Uploaded by

joshua sankar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Software Engineering

Assignment #1
Date Due: February 28, 2024 @4:00 p.m.

1. The assignment is to be completed by your project groups.


2. Only one student needs to submit the solution to the assignment box in the DCIT office.
3. Your solution must contain a cover page detailing
 Your group name and project name.
 Each group member’s UWI student id and name.
 Each group member’s contribution to the assignment.
 All references used.
4. A Turnitin report must be submitted.
5. No late or emailed submissions will be accepted.

These activities are based on the project idea you selected.

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.

Characteristics of a user story


A user story template often follows the same format. The three components of a user story
are:
Who. This is typically a job role, customer or type of user, also known as the user persona.
What. This is the goal that the user wants the product to accomplish or implement.
Why. This is the reason the user needs the feature or functionality.
The result is a sentiment like,
“As a <who>, I want <what> so that <why>.”

Examples of user stories


Following the above format, a few examples of a user story are:
 As a user, I want to upload photos so that I can share photos with others.
 As an administrator, I want to approve photos before they are posted so that I can make
sure they are appropriate.
 As a social media manager, I want to tag the photos under specific categories so that I
can filter and search the photos for future use.

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)

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy