Beruflich Dokumente
Kultur Dokumente
For
Supply and Sale
Version 1.2
Revision History
SS_1.1
04-August- 2016
SS_1.2
05-August- 2016
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 )
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 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
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.
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
Chapter 3
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
Requirement ID
FR.S.6
Requirement Name
Products name
Description
Requirement ID
FR.S.7
Requirement Name
Customers Info
Description
Requirement ID
FR.S.8
Requirement Name
Vat Info
Description
Requirement ID
FR.S.9
Requirement Name
Delivery Range
Description
Requirement ID
FR.S.10
Requirement Name
Shop Address
Description
Requirement ID
FR.S.11
Requirement Name
Website
Description
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
Requirement ID
FR.S.14
Requirement Name
Description
Requirement ID
FR.S.15
Requirement Name
Vault
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
Requirement ID
FR.M.6
Requirement Name
Products name
Description
Requirement ID
FR.M.7
Requirement Name
Customers Info
Description
Requirement ID
FR.M.8
Requirement Name
Vat Info
Description
Requirement ID
FR.M.9
Requirement Name
Delivery Range
Description
Requirement ID
FR.M.10
Requirement Name
Shop Address
Description
Requirement ID
FR.M.11
Requirement Name
Website
Description
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
Requirement ID
FR.M.14
Requirement Name
Description
Requirement ID
FR.M.15
Requirement Name
Vault
Description
Chapter 4
4.Use Case Diagram
Chapter 5
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
Frm.login.button
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
Frm.maintab.button4
Frm.maintab.button5
Frm.maintab.button6
Frm.maintab.button7
Frm.maintab.button8
Frm.maintab.button9
Frm.maintab.button10
Frm.maintab.button11
Frm.maintab.button3
Frm.maintab.button12
Frm.maintab.button13
Frm.maintab.button14
Chapter 6
6. Database Example
Objects
Product
Purpose
To get the values of above
mentioned terms
Validation Criteria
Only above mentioned terms
can be viewed
Objects
Customers Info
Purpose
To get the values of above
mentioned terms
Validation Criteria
Only above mentioned terms
can be viewed
Objects
Purpose
Validation Criteria
Accounts
Chapter 7
Traceability Matrix
Serial
1
2
Functional Req
FR.C.1
FR.C.2
Trace
Frm.Login
Frm.Main Tab