Sie sind auf Seite 1von 18

Software Requirement Specification

For
Supply and Sale
Version 1.2

Revision History

SS_1.1

04-August- 2016

SS_1.2

05-August- 2016

Reason for change


User profile, Functional
requirement, non-functional
requirement, Use case
Database Example

Table of Contents

1. Chapter 1
- Introduction (1.1)
- Scope (1.2)
- Overview (1.3)
2. Chapter 2
- User Profile (2)
- Staffs User Profile ( 2.1 )
- Managers User Profile ( 2.2 )

3. Chapter 3
- List of Functional requirement ( 3.1 )
- Functional requirement: Staff ( 3.1.1 )
- Functional requirement: Staff ( 3.1.2 )
4. Chapter 4
- Use case Diagram ( 4 )
- Use case Diagram : Staff ( 4.1 )
- Use case Diagram : Manager ( 4.2 )

5. Chapter 5
- Storyboard For Staff and Manager ( 5.1 )
- Login ( 5.1.1 )
- Main Tab ( 5.1.2 )
6. Chapter 6
- Database Example ( 6 )
- Database Example : Product ( 6.1 )
- Database Example Customers Info ( 6.2 )

- Database Example Accounts ( 6.3 )

7. Chapter 7
- Traceability Matrix

1.1 Introduction
The purpose of this document is to describe the Supply and Sale module (SS)
with the release number 1.2. This document contains the functional and nonfunctional requirements of the project and also user profile, use case, Database
example and storyboard. This document contains the guidelines for system
engineers and designers to start working the project.

1.2 Scope

SS product is basically a module of a Computer software which will allow


staffs to check their product items and also to give slips to the customers by
using their Computer device.

This project is developed as a course project of SWE121: Requirement


Analysis
& Design.

SS can be used for any Departmental Store or shopping mall from where
staffs can check their product items through their computer device.

From secondary users point of view, manager can check the inter functions
done by Staffs .

1.3 Overview

Chapter 2 describes both primary and secondary user profile


Chapter 3 shows the list of functional and non-functional requirement
including mind-map and requirement prioritization.
In chapter 4, use case diagram was provided
Chapter 5 displays the storyboard
Chapter 6 labels the Database example of the system
Chapter 7 contains requirement traceability matrix.
Chapter 2

2.1 User profile: 1

User Class: Staff


User type
Age range
Number of users
Education

Characteristics
Primary
18-65
Unlimited
N/A

Requirement Implied
Must give input
Minimal Design
Bandwidth should be high
Simple interface

Language Skill
Computer/ Mobile
Knowledge
Training
Goal

English
Yes

Simple English
Type option or Touch

Not required
To check and store the
amount of daily products

Not required
Must see products list and
their specified functions.

User Class: Manager


User type
Age range
Number of users
Education
Language Skill
Computer/ Mobile
Knowledge
Training

Characteristics
Secondary
35-40
1
Higher education
English
Yes

Requirement Implied
Must see output
Minimal Design
Bandwidth should be normal
Simple interface
Simple English
Only type or click option

Required

Goal

To see what staffs have done

2 days training will be


provided
Must see overall products
functions and the full
function of SS

2.2 User profile: 2

Chapter 3

3.1 List of Functional requirement


3.1.1 Functional requirement: Staff
Requirement ID
Requirement Name
Description

FR.S.1
Login
Staffs can Login

Requirement ID
Requirement Name
Description

FR.S.2
Main Tab
Staffs can access multiple functions

Requirement ID
Requirement Name
Description

FR.S.3
Expire Date
Staffs can see the expire dates of products

Requirement ID
Requirement Name
Description

FR.S.4
Product Amount
Staffs can see the amount of products stored in the store

Requirement ID

FR.S.5

Requirement Name

Brand

Description

Staffs can see the Brands of products

Requirement ID

FR.S.6

Requirement Name

Products name

Description

Staffs can see the names of products

Requirement ID

FR.S.7

Requirement Name

Customers Info

Description

Staffs can see the infos of customers

Requirement ID

FR.S.8

Requirement Name

Vat Info

Description

Staffs can see the vat infos of the products

Requirement ID

FR.S.9

Requirement Name

Delivery Range

Description

Staffs can see from where the products have been


delivered

Requirement ID

FR.S.10

Requirement Name

Shop Address

Description

Staffs can contact with the other branches of the shop

Requirement ID

FR.S.11

Requirement Name

Website

Description

Staffs can take the orders thats been given in online

Requirement ID

FR.S.12

Requirement Name

Responsibility

Description

Staffs can see and write down the damaged items name
and its returns

Requirement ID

FR.S.13

Requirement Name

Due payments

Description

Staffs can see the Due payments

Requirement ID

FR.S.14

Requirement Name

Total Per day

Description

Staffs can store the amount earned per day

Requirement ID

FR.S.15

Requirement Name

Vault

Description

Staffs can see the amount of money in the Vault

3.1.2 Functional requirement: Manager


Requirement ID
Requirement Name
Description

FR.M.1
Log in
Manager can log in using user name

Requirement ID
Requirement Name
Description

FR.M.2
Main Tab
Manager can access multiple functions

Requirement ID
Requirement Name
Description

FR.M.3
Expire Date
Manager can see the expire dates of products

Requirement ID
Requirement Name
Description

FR.M.4
Product Amount
Manager can see the amount of products stored in the
store

Requirement ID

FR.M.5

Requirement Name

Brand

Description

Manager can see the brands of products

Requirement ID

FR.M.6

Requirement Name

Products name

Description

Manager can see the names of products

Requirement ID

FR.M.7

Requirement Name

Customers Info

Description

Manager can see the infos of customers

Requirement ID

FR.M.8

Requirement Name

Vat Info

Description

Manager can see the vat infos of the products

Requirement ID

FR.M.9

Requirement Name

Delivery Range

Description

Manager can see from where the products have been


delivered

Requirement ID

FR.M.10

Requirement Name

Shop Address

Description

Manager can contact with the other branches of the shop

Requirement ID

FR.M.11

Requirement Name

Website

Description

Manager can see the orders thats been given and


received in online

Requirement ID

FR.M.12

Requirement Name

Responsibility

Description

Manager can see the damaged items name and its returns

Requirement ID

FR.M.13

Requirement Name

Due payments

Description

Manager can see the Due payments

Requirement ID

FR.M.14

Requirement Name

Total Per day

Description

Manager can check the amount earned per day

Requirement ID

FR.M.15

Requirement Name

Vault

Description

Manager can see the amount of money in the Vault

Chapter 4
4.Use Case Diagram

4.1 Use case diagram: Staff

4.2 Use case diagram: Manager

Chapter 5

5.1 Storyboard For Staff and Manager


5.1.1 Login
Frm.login.text1

Frm.login.text2

Frm.login.button

Objects
Frm.login.text1

Purpose
This combo box will be used
to get the staffs name

Validation Criteria
Staffs cannot input texts which
is out of the conditions

Frm.login.text2

This combo box will be used


to get the time of login
Staffs will click this to go to
main tab

Only digit can be input

Frm.login.button

In one click, the next page will


be activated.

5.1.2 Main Tab


Frm.maintab.button
2
Frm.maintab.button
5

Frm.maintab.button
8
Frm.maintab.button
11

Frm.maintab.button
1

Frm.mainta
b.button12

Frm.maintab.button
4

Frm.maintab.
button13

Frm.maintab.button
6
Frm.maintab.button
3

Objects
Frm.maintab.button1

Frm.maintab.button
14

Frm.maintab.butt
on10
Frm.maintab.button
7

Purpose
This button will lead to
products expire dates

Frm.maintab.button
9

Validation Criteria
Staff will only touch or click to
the button. All expire date of
products must be available

Frm.maintab.button2

This button will lead to the


amount of products stored in
the store
This button will lead to
products brands

The button should be clicked


once

Frm.maintab.button4

This button will lead to


products Name

Only stored products name can


be viewed

Frm.maintab.button5

This button will lead to


customers infos

Only infos of customers who


have taken stuffs from the shop
can be viewed

Frm.maintab.button6

This button will lead to


products Vat info

Updated vat infos can be


viewed

Frm.maintab.button7

Clicking this button will show


the details of products from
where they have been
delivered.

Products delivered from shop


can be viewed

Frm.maintab.button8

Through this staffs may be


able to communicate with
other branches of the shop

Only able to contact with the


other branches

Frm.maintab.button9

Its for receiving orders from


online

Only customers can give


orders

Frm.maintab.button10

Damaged products will be


input in this section

Only products damaged by


staffs or customers will be
shown

Frm.maintab.button11

Payments which are due will


Only Due payments can be
be written here
viewed
Clicking this button will allow Only digits can be input
staffs to input the amount
thats been earned per day

Frm.maintab.button3

Frm.maintab.button12

Frm.maintab.button13

This will show the total


amount stored in the vault

Only Stored brands will be


shown

Only manger can access this


panel

Frm.maintab.button14

Staffs will give the slips to


customers

Only bought items name will


be written there

Chapter 6
6. Database Example

6.1 Database Example - Product

Objects
Product

Purpose
To get the values of above
mentioned terms

Validation Criteria
Only above mentioned terms
can be viewed

6.2 Database Example Customers Info

Objects
Customers Info

Purpose
To get the values of above
mentioned terms

Validation Criteria
Only above mentioned terms
can be viewed

6.3 Database Example Accounts

Objects

Purpose

Validation Criteria

Accounts

To get the values of above


mentioned terms

Only above mentioned terms


can be viewed

Chapter 7
Traceability Matrix
Serial
1
2

Functional Req
FR.C.1
FR.C.2

Trace
Frm.Login
Frm.Main Tab

Das könnte Ihnen auch gefallen