Você está na página 1de 64

SOFTWARE REQUIREMENTS SPECIFICATION

Online Retail Supply Chain System

Version: Draft
September 17, 2008

Prepared by:

Mohammed Tareq AC073031

Oryza Safutra AC070312

Iqbal Ahada AC070301

Alvino Yulian AC070290

Aditya Wirmansyah AC070288

Muhammad Ikhsan Arif AC060003

This document is adapted from Software Project Survival Guide by Steve McConnell
(Microsoft Press, 1998). The document template used to create this document, related
documents, plans, and other materials can be downloaded from the survival guide website
at http://www.construx.com/survivalguide/.
Software Requirements Specification (SRS)

REVISION CHART

Version Primary Author(s) Description of Version Date Completed


Mohammed Tareq
Oryza Safutra
Initial draft created for
Iqbal Ahada
Draft distribution and 12/09/2008
Alvino Yulian
review comments
Aditya Wirmansyah
Muhammad Ikhsan
Mohammed Tareq
Second draft
Oryza Safutra
incorporating initial
Iqbal Ahada
Preliminary review comments, 15/09/2008
Alvino Yulian
distributed for final
Aditya Wirmansyah
review
Muhammad Ikhsan
Mohammed Tareq
Oryza Safutra
First complete draft,
Iqbal Ahada
Final which is placed under 17/09/2008
Alvino Yulian
change control
Aditya Wirmansyah
Muhammad Ikhsan

SRS –Online Retail Supply Chain System Page 2


Software Requirements Specification (SRS)

CONTENTS

1. INTRODUCTION ...............................................................................................................7
PURPOSE......................................................................................................................7
SCOPE.........................................................................................................................7
DEFINITIONS, ACRONYMS, AND ABBREVIATIONS...................................................................7
REFERENCES.................................................................................................................8
WEBSITES : ...............................................................................................................8
OVERVIEW....................................................................................................................9

2. OVERALL DESCRIPTION..................................................................................................10
PRODUCT PERSPECTIVE.................................................................................................10
2.1.1 User Interfaces........................................................................................ .............10
2.1.2 Software Interfaces..................................................................................... ..........10
PRODUCT FUNCTIONS....................................................................................................11
2.1.3 Login..................................................................................................... ...............13
2.1.4 Checkout Customer............................................................................. .................13
2.1.5 Oversee Current Stock...................................................................................... ....14
2.1.6 Place an Order...................................................................................... ...............14
2.1.7 View Order Status.......................................................................................... .......14
2.1.8 Make an Order Payment...................................................................................... .14
2.1.9 View Order................................................................................ ...........................14
2.1.10 Confirm Order............................................................................................... .....14
2.1.11 Bill Store Manager........................................................................ .....................14
2.1.12 Update Order Status......................................................................................... ..15
USER CHARACTERISTICS................................................................................................15

3. SPECIFIC REQUIREMENTS...............................................................................................16
SOFTWARE PRODUCT FEATURES......................................................................................16
3.1.1 Login Use Case...................................................................................... ..............16
3.1.1.1 Brief Description....................................................................................................16
3.1.1.2 Flow of Events.......................................................................................................16
3.1.1.3 Basic Flow - Login.................................................................................................16
3.1.1.4 Alternative Flows...................................................................................................16
3.1.1.4.1 Forget Password........................................................................................... .....16
3.1.1.5 Special Requirements............................................................................................17
3.1.1.6 Preconditions.........................................................................................................17
3.1.1.7 Postconditions........................................................................................................17
3.1.1.8 Login Sequence Diagram......................................................................................17
3.1.1.9 Login Activity Diagram.........................................................................................18
3.1.2 Check Out Customer Use Case......................................................... ...................20
3.1.2.1 Brief Description....................................................................................................21

SRS –Online Retail Supply Chain System Page 3


Software Requirements Specification (SRS)

3.1.2.2 Flow of Events.......................................................................................................21


3.1.2.3 Basic Flow - Check Out Customer........................................................................21
3.1.2.4 Alternative Flows...................................................................................................21
3.1.2.5 Special Requirements............................................................................................21
3.1.2.6 Preconditions.........................................................................................................21
3.1.2.7 Postconditions........................................................................................................22
3.1.2.8 Check Out Customer Sequence Diagram..............................................................23
3.1.2.9 Check Out Customer Activity Diagram................................................................24
3.1.3 Oversee Current Stock Use Case....................................................................... ...24
3.1.3.1 Brief Description....................................................................................................25
3.1.3.2 Flow of Events.......................................................................................................25
3.1.3.3 Basic Flow .............................................................................................................25
3.1.3.4 Alternative Flows...................................................................................................25
3.1.3.5 Special Requirements............................................................................................25
3.1.3.6 Preconditions.........................................................................................................26
3.1.3.7 Postconditions........................................................................................................26
3.1.3.8 Oversee Current Stock Sequence Diagram...........................................................27
3.1.3.9 Oversee Current Stock Activity Diagram..............................................................29
3.1.4 Place an Order Use Case....................................................................... ..............29
3.1.4.1 Brief Description....................................................................................................30
3.1.4.2 Flow of Events.......................................................................................................30
3.1.4.3 Basic Flow – Place an Order.................................................................................30
3.1.4.4 Alternative Flows...................................................................................................30
3.1.4.5 Special Requirements............................................................................................30
3.1.4.6 Preconditions.........................................................................................................31
3.1.4.7 Postconditions........................................................................................................31
3.1.4.8 Place an Order Sequence Diagram........................................................................31
3.1.4.9 Place an Order Activity Diagram..........................................................................34
3.1.5 View Order Status Use Case........................................................................... ......35
3.1.5.1 Brief Description....................................................................................................35
3.1.5.2 Flow of Events.......................................................................................................35
3.1.5.3 Basic Flow .............................................................................................................36
3.1.5.4 Alternative Flows...................................................................................................36
3.1.5.5 Special Requirements............................................................................................36
3.1.5.6 Preconditions.........................................................................................................36
3.1.5.7 Postconditions........................................................................................................36
3.1.5.8 View Order Status Sequence Diagram..................................................................37
3.1.5.9 View Order Status Activity Diagram.....................................................................38
3.1.6 Make an Order Payment Use Case...................................................................... .39
3.1.6.1 Brief Description....................................................................................................39
3.1.6.2 Flow of Events.......................................................................................................39
3.1.6.3 Basic Flow..............................................................................................................39
3.1.6.4 Alternative Flows...................................................................................................39
3.1.6.5 Special Requirements............................................................................................40
3.1.6.6 Preconditions.........................................................................................................40
3.1.6.7 Postconditions........................................................................................................40
3.1.6.8 Make an Order Payment Sequence Diagram........................................................40
3.1.6.9 Make an Order Payment Activity Diagram...........................................................41
3.1.7 View Order Use Case................................................................. ..........................42
3.1.7.1 Brief Description....................................................................................................42
3.1.7.2 Flow of Events.......................................................................................................42
3.1.7.3 Basic Flow..............................................................................................................42
3.1.7.4 Alternative Flows...................................................................................................42
3.1.7.5 Special Requirements............................................................................................42

SRS –Online Retail Supply Chain System Page 4


Software Requirements Specification (SRS)

3.1.7.6 Preconditions.........................................................................................................43
3.1.7.7 Postconditions........................................................................................................43
3.1.7.8 View Order Sequence Diagram............................................................................43
3.1.7.9 View Order Activity Diagram................................................................................44
3.1.8 Confirm Order Use Case................................................................................... ...45
3.1.8.1 Brief Description....................................................................................................45
3.1.8.2 Flow of Events.......................................................................................................45
3.1.8.3 Basic Flow..............................................................................................................45
3.1.8.4 Alternative Flows...................................................................................................45
3.1.8.5 Special Requirements............................................................................................45
3.1.8.6 Preconditions.........................................................................................................45
3.1.8.7 Postconditions........................................................................................................45
3.1.8.8 Confirm Order Sequence Diagram........................................................................46
3.1.8.9 Confirm Order Activity Diagram..........................................................................47
3.1.9 Bill Store Manager Use Case................................................................... ............48
3.1.9.1 Brief Description....................................................................................................48
3.1.9.2 Flow of Events.......................................................................................................48
3.1.9.3 Basic Flow..............................................................................................................48
3.1.9.4 Alternative Flows...................................................................................................48
3.1.9.5 Special Requirements............................................................................................49
3.1.9.6 Preconditions.........................................................................................................49
3.1.9.7 Postconditions........................................................................................................49
3.1.9.8 Bill Store Manager Sequence Diagram.................................................................54
3.1.9.9 Bill Store Manager Activity Diagram...................................................................55
3.1.10 Update Order Status Use Case.......................................................................... .56
3.1.10.1 Brief Description..................................................................................................56
3.1.10.2 Flow of Events.....................................................................................................56
3.1.10.3 Basic Flow............................................................................................................56
3.1.10.4 Alternative Flows.................................................................................................56
3.1.10.5 Special Requirements..........................................................................................57
3.1.10.6 Preconditions.......................................................................................................57
3.1.10.7 Postconditions......................................................................................................57
3.1.10.8 Update Order Status Sequence Diagram.............................................................58
3.1.10.9 Update Order Status Activity Diagram...............................................................59
NON FUNCTIONAL REQUIREMENTS..................................................................................60
3.1.11 Usability............................................................................................ .................60
3.1.11.1 Windows Compliance..........................................................................................60
3.1.11.2 Designs for Ease-of-Use.......................................................................................60
3.1.11.3 Online Help..........................................................................................................60
3.1.12 Reliability................................................................................................. ..........60
3.1.12.1 Availability...........................................................................................................61
3.1.12.2 Mean Time between Failures...............................................................................61
3.1.13 Performance........................................................................................... ............61
3.1.13.1 Simultaneous Users..............................................................................................61
3.1.13.2 Database Access Response Time.........................................................................61
3.1.13.3 Transaction Response Time.................................................................................61

4. INDEX..........................................................................................................................63

SRS –Online Retail Supply Chain System Page 5


Software Requirements Specification (SRS)

LIST OF FIGURES

Figure 1 : Online Retail Supply Chain System Use Case Diagram........................................... .....9
Figure 2: Online Retail Supply Chain System Activity Diagram………………………..……… 12
Figure 3 : Login Sequence Diagram........................................................................ ....................16
Figure 4 : Login Activity Diagram............................................................................... ................17
Figure 5 : Check Out Customer Sequence Diagram........................................... .........................20
Figure 6 : Check Out Customer Activity Diagram .................................................. ....................21
Figure 7 : Oversee Current Stock Sequence Diagram......................................................... .........24
Figure 8 : Oversee Current Stock Activity Diagram ................................................................ ...25
Figure 9 : Place an Order Sequence Diagram........................................................................... ..28
Figure 10 : Place an Order Activity Diagram.............................................................. ................29
Figure 11 : View Order Status Sequence Diagram..................................................................... ..31
Figure 12 : View Order Status Activity Diagram................................................................. ........32
Figure 13 : Make an Order Payment Sequence Diagram..................................................... ......34
Figure 14 : Make an Order Payment Activity Diagram............................................................. ..35
Figure 15 : View Order Sequence Diagram............................................................................. ....37
Figure 16 : View Order Activity Diagram....................................................... ............................38
Figure 17 : Confirm Order Sequence Diagram.................................................................. ........40
Figure 18 : Confirm Order Activity Diagram.......................................................................... .....41
Figure 19 : Bill Store Manager Sequence Diagram.................................................. ...................44
Figure 20 : Bill Store Manager Activity Diagram.......................................................... .............45
Figure 21 : Update Order Status Sequence Diagram........................................................... ........48
Figure 22 : Update Order Status Activity Diagram................................................................... ...49

SRS –Online Retail Supply Chain System Page 6


Software Requirements Specification (SRS)

1.INTRODUCTION

Purpose
The purpose of this document is to specify the software requirement specifications to develop the
Online Retail Supply Chain System. This document outlines a brief description about what
functions are to be performed on what data to produce what results at what location for whom.

Scope
This document specifies software requirement specifications for Online Retail Supply Chain
System. This has been achieved through developing Use Case Diagrams for each function and for
the system as a whole using Unified Modeling Language. It also explain the flow of events
(process) of the whole system through activity diagram. Moreover, This document states each Use
Case through several steps including brief description, flow of events, basic flow, alternative flows,
special requirements, preconditions, postconditions, activity diagram and sequence diagram.
Activity and sequence diagrams( Interaction diagrams ) are used in this document to describe
exemplary how groups of objects collaborate in some behavior. They capture the behavior of a
single use case. In addition, it specifies non-functional requirements for the system such as
usability, reliability and performance which are considered as the constraints on the system’s
functions or services.

Definitions, Acronyms, and Abbreviations


• ID – Identity
• O.R.S.C.S.- Online Retail Supply Chain System
• SDP – Software Development Plan
• SPMP – Software Project Management Process
• SRS – Software Requirement Specification

SRS –Online Retail Supply Chain System Page 7


Software Requirements Specification (SRS)

• UML – Unified Modeling Language


• MTTF – Mean Time To Failure

References
Websites :
• http://www.wikipedia.com
• http://www.google.com
• http://www.jusco.com.my

References book :
• Sommerville, Ian. 2006. Software Engineering 8th edition. England: Addison-Wesley

SRS –Online Retail Supply Chain System Page 8


Software Requirements Specification (SRS)

Overview
This is the Use Case Diagram for Online Retail Supply Chain System.

Login Check out Customer


Cashier

Ov ersee Current Stock

Place an Order

View Order Status


User Store Manager

Make an Order Pay ment

View Order

Supplier Conf irm Order

Bill Store Manager

Update Order Status

Figure 1 : Online Retail Supply Chain System Use Case Diagram

SRS –Online Retail Supply Chain System Page 9


Software Requirements Specification (SRS)

2.OVERALL DESCRIPTION

Product Perspective
This product is dependent with the Jasco website and the ID database. Only cashier, store manager
and supplier that has an ID can access the system. However, the data involved in the Online Retail
Supply Chain System is independent and self-contained. The user can only view information
provided from the system.

2.1.1User Interfaces

1. Login form (for any user).

2. Cashier form (for cashier interface).

3. Store manager form (for store manager interface).

4. Supplier form (for supplier interface).

5. Order form (for store manager interface).

6. Billing order form (for supplier interface).

7. Payment form (for store manager interface).

8. Check out customer form (for cashier interface).

9. View order information (for supplier interface).

10. View stock information (for store manager interface).

11. View order status information (for store manager interface).

2.1.2Software Interfaces

1. Windows Vista

SRS –Online Retail Supply Chain System Page 10


Software Requirements Specification (SRS)

2. Microsoft FrontPage

3. Microsoft Access 2003

Product Functions
The major functions of this system are to checkout customer, oversee current stock, place an order,
view order status, make an order payment, view order, confirm order, bill store manager, and
update order status. The name of this system is Online Retail Supply Chain System which can be
accessed by cashier, store manager and supplier provided in the system’s website. In this software,
users which are the cashier, store manager and supplier should have ID and password to login to
the system. The cashier will be able to login and checks out customer, so the system will send alerts
to store manager automatically. The Store Manager will be able to login, oversees current stock. If
it is under re-order level he will place an order. The Store Manager also can view order status
during the process. The supplier will view order, then he will decide weather to approve or reject
the order. If he decided to approve an order he has to bill the store manager. The supplier will be
able to update order status regularly in this software. This document also explains about the bill
payment and payment method that will be used. The benefit of this system is to help both store
manager and supplier to have a good arrangement in this system.

Online Retail Supply Chain System Activity Diagram:


This diagram shows the flow of events in Online Retail Supply Chain System through the whole
process.

SRS –Online Retail Supply Chain System Page 11


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 12


Software Requirements Specification (SRS)

Start Onl ine Retail Supply Chain


System

Check out Make an Order


Customer Payment

Oversee Current Update Order


Stock Status(again)

Place an Order
View Order
Status(again)

View Order
End Online Retail Supply Chain
System

Order rejected
Confirm Order

Order approved
Bill Store
Manager

Update Order
Status

Order rejected Order approved and invoiced


View Order
Status

Figure 2 : Online Retail Supply Chain System Activity Diagram

2.1.3Login

This use case will ask a user to enter ID and password to login to the system.

2.1.4Checkout Customer

This use case allows user, who is cashier, to rings up the goods or services that
the consumer wishes to purchase. After all of the goods have been rung up, the cashier then
collects payment for the goods or services exchanged.

SRS –Online Retail Supply Chain System Page 13


Software Requirements Specification (SRS)

2.1.5Oversee Current Stock

This use case allows the system to check the items in stock. Then, it will display to the user, which
is the store manager, whether the items are under or above re-order level.

2.1.6Place an Order

This use case allows the store manager to reorder items. He or She will reorder items after the
system show the out-of-stock items or goods to the user, which is the store manager.

2.1.7View Order Status

This use case allows the store manager to check the status of items that already have been ordered.
This use case can be done by checking the order status in the order database.

2.1.8Make an Order Payment

This use case allows the user, which is store manager, to make the order payment. Payment for
orders can be done through two ways; One way is online payment, such as by pay pal, master card,
visa card or online balance transfer. Another way is manual. The applicant will go to bank to make
a draft and send it to the university’s account that has been given on the system..

2.1.9View Order

This use case allows the supplier to view orders that has been placed by the customer or store
manager. This use case can be done by checking order database.

2.1.10Confirm Order

This use case allows supplier to confirm the order from customer or store manager. The supplier
will confirm which items or goods that have been ordered by the customer or store manager after
checking his/her stock.

2.1.11Bill Store Manager

This use case allows supplier to send the payment bill to the customer or store manager. The
payment bill can be sent by e-mail or the other internet services or by the system itself.

SRS –Online Retail Supply Chain System Page 14


Software Requirements Specification (SRS)

2.1.12Update Order Status

This use case allows the supplier to update the status of the order. It will be done after each service
has been done to the order; e.g. store manager will update order status after confirming and billing
store manager.

User Characteristics
This system can be accessed by two types of users:

1. Customer, which are the cashier, store manager and supplier.

2. Administrator, who work in Jasco Shopping Center.

Customer should have an ID and password to login to the system and do his/her particular
task.

Administrator also should have an ID and password to login to the system, maintain the
order, item, and stock database. They also require having skills in Microsoft Access, SQL,
and basic programming in PHP or ASP.

SRS –Online Retail Supply Chain System Page 15


Software Requirements Specification (SRS)

3.SPECIFIC REQUIREMENTS

Software Product Features


3.1.1Login Use Case

Login
User

3.1.1.1Brief Description

This use case describes how a user logs into the Online Retail Supply Chain System. The actors
starting this use case are cashier, store manager and supplier

3.1.1.2Flow of Events

The use case begins when the actor types his/her name and password on the login form.

3.1.1.3Basic Flow - Login

1. The user enters ID and password


2. The system validates the user password and logs him/her into the system.
3. The system displays the Main Form and the use case ends.

3.1.1.4Alternative Flows

3.1.1.4.1FORGET PASSWORD

1. The user open the website

2. Select “Forget password”

3. Type email user

4. The system sent password user to email

SRS –Online Retail Supply Chain System Page 16


Software Requirements Specification (SRS)

3.1.1.4.2 Invalid Password


If user submits incorrect ID and password, the error message will be displayed. The user must re-
enter ID and password again.

3.1.1.5Special Requirements

The ID must begin by alphabet and contain number 0-9. The passwords at least 8 characters and
contain alphabet and number. And also email, the system will be asked again if user not put correct
email using .com, .my or etc.

3.1.1.6Preconditions

The user must have an account.

3.1.1.7Postconditions

The user is logged in the system.

3.1.1.8Login Sequence Diagram

: Login Form : Login Ctl : User : User Form


: User
1.fill in login form()

2.get user info(integer,string)

3.is valid()

4.open()

Sequence Diagram:
Login/E--2:Forget
password

Sequence Diagram:
Login/E-1:Invalid
User Info
Figure 3 : Login Sequence Diagram

SRS –Online Retail Supply Chain System Page 17


Software Requirements Specification (SRS)

3.1.1.9Login Activity Diagram

SRS –Online Retail Supply Chain System Page 18


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 19


Software Requirements Specification (SRS)

Start Login Use Case

Fill in Login
Form

If a user forgot his/her


password, they must get
it first from the system by Select Submit
typing their e-mail.

Incorrect ID or Passward Display Error


Message

Open User Form

End Login Use Case

Figure 4 : Login Activity Diagram

3.1.2Check Out Customer Use Case

Check out Customer


Cashier

SRS –Online Retail Supply Chain System Page 20


Software Requirements Specification (SRS)

3.1.2.1Brief Description

This use case describes how a cashier checks out a customer. The actors starting this use case is
cashier.

3.1.2.2Flow of Events

The use case begins when the cashier get item from costumer

3.1.2.3Basic Flow - Check Out Customer

1. Press new sale button


2. Press open transaction button
3. Scan item
4. Enter quantity
5. Calculate item price
6. Get total
7. Press end sale button
8. Press close transaction button
9. Press payment button
10. Receive payment
11. Return remaining
12. Deduct stock
13. Press receipt button
14. Customer has been checked out

3.1.2.4Alternative Flows

There is no alternative flow associated with this use case.

3.1.2.5Special Requirements

There are no special requirements associated with this use case.

3.1.2.6Preconditions

There are no preconditions associated with this use case.

SRS –Online Retail Supply Chain System Page 21


Software Requirements Specification (SRS)

3.1.2.7Postconditions

The customer has been check out

SRS –Online Retail Supply Chain System Page 22


Software Requirements Specification (SRS)

3.1.2.8Check Out Customer Sequence Diagram

: CashierForm : Transiction : Item


: Cashier : Bar Code
Scanner
1.newSale()

2.new(ID)

3.getItemCode()

4.getItem(code)

5.enterQuantity(integer)

6.calculateItemPrice()

7.insertItem(item,quantity,price)

8.endSale()

9.closeTransiction(total)

10.getTotal(total)

11.enterPayment()

12.deductTotal()

13.returnRemaining()

14.deductStock()

15.produceReceipt()

Figure 5 : Check out Customer Sequence Diagram

SRS –Online Retail Supply Chain System Page 23


Software Requirements Specification (SRS)

3.1.2.9Check Out Customer Activity Diagram

Start check out customer use


case

Select Close
Select New Sale
Transiction

Select Payment
Select Open
Transiction

Receive
Scan Item Payment

Return
Enter Quantity Remaining

Calculate Item Deduct Stock


Price

Did not submit


Produce
Receipt

Get Total Price


Customer Has Been
Checked out

Select End Sale


End check out customer use
case

Figure 6 : Check out Customer Activity Diagram

3.1.3Oversee Current Stock Use Case

SRS –Online Retail Supply Chain System Page 24


Software Requirements Specification (SRS)

Store Manager Oversee Current Stock

3.1.3.1Brief Description

This use case describes user, which is the store manager, to oversee the stock in the store by login
to the system.

3.1.3.2Flow of Events

The use case begins when the user or the store manager login to the system and press stock button.

3.1.3.3Basic Flow

1. Log in to the system

2. Press stock button

3. Press stock alert button

4. View stock alerts

5. Press stock information button

6. Check stock

7. Confirm request

8. Press submit button

9. Alerts have been confirmed

3.1.3.4Alternative Flows

After the store manager view alert, the store manager also will check the stock, if they are still have
stock mean the system stock alert is error and the store manager simply ignore the alert and
continue without confirm request, press submit button and alert have been confirmed.

3.1.3.5Special Requirements

This system only can access by store manager.

SRS –Online Retail Supply Chain System Page 25


Software Requirements Specification (SRS)

3.1.3.6Preconditions

Before this use case begins the user, which is store manager, has to log on to the system.

3.1.3.7Postconditions

The use case ends when the information about current stock is displayed.

SRS –Online Retail Supply Chain System Page 26


Software Requirements Specification (SRS)

3.1.3.8Oversee Current Stock Sequence Diagram

SRS –Online Retail Supply Chain System Page 27


Software Requirements Specification (SRS)

: Stock Form : Stock Ctl : Stock DB


: Store Manager

1.viewStockAlerts()

2.getStockInfo()

3.stockInfo.

4.checkStock()

Sequence Diagram:
Oversee Current Stock/
5.confirmRequests()
E-1 :Alert is not true

6.senData()

7.alertsConfirmed()

Figure 7 : Oversee Current Stock Sequence Diagram

SRS –Online Retail Supply Chain System Page 28


Software Requirements Specification (SRS)

3.1.3.9Oversee Current Stock Activity Diagram

Start oversee current stock use


case

Select Stock

Select Stock
Alert

View Stock
Alerts

Select Stock
Info.

Alert is not true Check Stock

Ignore Alert Confirm


Request

Submit
Confirmation

Alerts have been


confirmed

End oversee current stock use


Figure 8 : Oversee Current Stock case Activity Diagram

3.1.4Place an Order Use Case

SRS –Online Retail Supply Chain System Page 29


Software Requirements Specification (SRS)

Store Manager Place an Order

3.1.4.1Brief Description

When the store manager log in using ID and password into the system, there are application status
menu. In that menu, they can see application supplier option. In this application, the store manager
can select supplier, view catalog, view item, and price.

3.1.4.2Flow of Events

The use case begins when the store manager select supplier button menu.

3.1.4.3Basic Flow – Place an Order

1. Press supplier button menu


2. View supplier
3. Select supplier
4. Press catalog button
5. View catalog
6. Fill in user information
7. Select item
8. Select amount
9. Select delivery date
10. Submit order
11. Order has been submitted

3.1.4.4Alternative Flows

If the store manager didn’t complete order information, an error massage is displayed. The system
will back to fill in user information until the user complete fill in user information or cancel the
transaction.

3.1.4.5Special Requirements

There is no special requirement associated with this use case.

SRS –Online Retail Supply Chain System Page 30


Software Requirements Specification (SRS)

3.1.4.6Preconditions

The user must have ID and password to enter the system

3.1.4.7Postconditions

The user submit the order item through the system

3.1.4.8Place an Order Sequence Diagram

SRS –Online Retail Supply Chain System Page 31


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 32


Software Requirements Specification (SRS)

:Supplier Form :Order Ctl :Supllier DB


: Store Manager

1.viewSuppliers()

2.selectSupplier()

3.getSupplierInfo.()

4.supplierInfo.()

5.getSupplierCatalog()

6.supplierCatalog()

7.viewCatalog()

8.fill inOrderForm()

9.sendData()

10.orderSubmitted()

Sequence Diagram:
Place an Order/E-1:
Incompleted Information

SRS –Online Retail Supply Chain System Page 33


Software Requirements Specification (SRS)

Start Place an
Order Use Case

Select
Suppliers

View Suppliers
Figure 9 :Place an Order Sequence Diagram

Select Supplier

3.1.4.9Place an Order Activity Diagram


Select Catalog

View Catalog

Fill in User Info.

Select Item

Select Amount

Items >1

Select Delivery
Date

Submit Order

Did not complete order information Dispaly Error


Message

Order has been


submitted
SRS –Online Retail Supply Chain System Page 34

End Place an Order Use Case


Software Requirements Specification (SRS)

Figure 10 :Place an Order Activity Diagram

3.1.5View Order Status Use Case

Store Manager View Order Status

3.1.5.1Brief Description

This use case describes user, which is the store manager, to view the order status by login to the
system.

3.1.5.2Flow of Events

The use case begins when the user or the store manager press view order status button menu

SRS –Online Retail Supply Chain System Page 35


Software Requirements Specification (SRS)

3.1.5.3Basic Flow

1. Press view order status button menu

2. View orders, open order, view order status and close order (if orders > 1, then back to open
order) do all at once.

3. Press OK button

4. Order status has been viewed

5. End view order status

3.1.5.4Alternative Flows

There is an alternative flow associated with this use case.

3.1.5.5Special Requirements

If status show pending, the problem maybe with the internet connection. Users must wait at least
one day. If still pending, they must reorder item from another supplier.

3.1.5.6Preconditions

Before this use case begins the user, which is store manager, has to log on to the system.

3.1.5.7Postconditions

The use case ends when the information about order status is displayed.

SRS –Online Retail Supply Chain System Page 36


Software Requirements Specification (SRS)

3.1.5.8View Order Status Sequence Diagram

:Store Manager :View Ctl :Order DB


: Store Manager
Form

1.organizeOrders(delivery date)

2.ViewOrders()

3.openOrder()
4.getOrderInfo.()

5.orderInfo.()

6.viewOrderStatus()

7.closeOrder()

8.sendData()

9.orderStatusViewed()

SRS –Online Retail Supply Chain System Page 37


Software Requirements Specification (SRS)

Figure 11 :View Order Status Sequence Diagram

3.1.5.9View Order Status Activity Diagram

Start View Order Status Use


Case

Select View Order


Status

View Orders Open Order

View Order
Status

Close Order Orders >1

Select Ok

Order Status has


been viewed

SRS –Online Retail Supply Chain System End View Order Status Use Page 38
Case
Software Requirements Specification (SRS)

Figure 12 :View Order Status Activity Diagram

3.1.6Make an Order Payment Use Case

Store Manager Make an order Payment

3.1.6.1Brief Description

After completing the place an order form the user make an order payment. The user will pay order
by online payment with pay pal, master card, visa card or online balance transfer.

3.1.6.2Flow of Events

The use case begins when the user select payment button menu.

3.1.6.3Basic Flow

1. Press payment button menu


2. Select method
3. Fill in required information
4. Submit payment (if order > 1, then back to payment button menu)
5. Payment has been submitted
6. End make an order payment

3.1.6.4Alternative Flows

If required information not completed properly, error massage will be display and will highlight the
empty field information.

SRS –Online Retail Supply Chain System Page 39


Software Requirements Specification (SRS)

3.1.6.5Special Requirements

The user must have account bank to make a payment.

3.1.6.6Preconditions

The user must have account to enter the system.

3.1.6.7Postconditions

The payment has been submitted

3.1.6.8Make an Order Payment Sequence Diagram

:Payment Form :Payment Ctl :Payment DB


: Store Manager

1.newPayment()

2.selectPaymentMethod()

3.getMethodInfo.()

4.methodInfo.()

5.fill inRequiredInfo()

6.submitPayment()

7.orderPaid()

Sequence Diagram:
Make an order
Payment /E-1:
Incompleted Info.

Figure 13 :Make an Order Payment Sequence Diagram

SRS –Online Retail Supply Chain System Page 40


Software Requirements Specification (SRS)

3.1.6.9Make an Order Payment Activity Diagram

Start Make an Order Payment


Use Case

Select Payment

Select Method

Fill in Required
Information

Orders >1 Submit


Payment

Did not complete Information Display Error


Message

Payment has
been submited

End Make an Order Payment


Use Case

Figure 14 :Make an Order Payment Activity Diagram

SRS –Online Retail Supply Chain System Page 41


Software Requirements Specification (SRS)

3.1.7View Order Use Case

Supplier View Order

3.1.7.1Brief Description

This use case describes about how to view order information in the system. The actor in this use
case is supplier.

3.1.7.2Flow of Events

The use case begins when the supplier select press inbox button menu.

3.1.7.3Basic Flow

1. Press inbox button menu

2. View order, open order, close order (orders > 1, back to open order)

3. Priorities Orders

4. Press Ok button

5. Orders have been viewed

6. End view orders

3.1.7.4Alternative Flows

There is no alternative flow associated with this use case.

3.1.7.5Special Requirements

The user must be the supplier and have ID and password to login the system.

SRS –Online Retail Supply Chain System Page 42


Software Requirements Specification (SRS)

3.1.7.6Preconditions

The supplier must have ID and password to enter the system

3.1.7.7Postconditions

The supplier have been view all orders.

3.1.7.8 View Order Sequence Diagram

:Supplier Form :View Ctl :Order DB


: Supplier

1.organizeOrders(delivery date)

2.viewOrders()

3.openOrder()

4.getOrderInfo.()

5.orderInfo.()

6.closeOrder()

7.prioritiseOrders(delivery date,retailer)

8.sendData()

9.ordersViewed()

Figure 15 :View Order Sequence Diagram

SRS –Online Retail Supply Chain System Page 43


Software Requirements Specification (SRS)

3.1.7.9View Order Activity Diagram

Start View Order Use Case

Select Inbox

View Orders Open Order

Close Order
Orders >1

Prioritise Orders

Select Ok

Order has been


viewed

End View Order Use Case

Figure 16 :View Order Activity Diagram

SRS –Online Retail Supply Chain System Page 44


Software Requirements Specification (SRS)

3.1.8Confirm Order Use Case

Supplier
Confirm Order

3.1.8.1Brief Description

The supplier will make confirm or reject from every order. The supplier will send confirm or reject
order to the user account.

3.1.8.2Flow of Events

The use case begins when the supplier press confirmation button menu.

3.1.8.3Basic Flow

1. Press confirmation button menu


2. Press order button
3. View order, Press stock information button, and check stock
4. Confirm order
5. Press submit button
6. Order has been confirmed (orders > 1, back to press order button)
7. End confirm orders

3.1.8.4Alternative Flows

If stock insufficient, the supplier will reject user order and will sent to user account

3.1.8.5Special Requirements

For make the user satisfied. The supplier must have enough stock and good price.

3.1.8.6Preconditions

The supplier must have ID and password to access the system.

3.1.8.7Postconditions

The supplier has been confirm the order

SRS –Online Retail Supply Chain System Page 45


Software Requirements Specification (SRS)

3.1.8.8Confirm Order Sequence Diagram

:Supplier Fom :Confirmation :Stock :Stock DB :Order DB


: Supplier
Ctl

1.viewOrder()

2.getStockInfo.()

3.StockInfo.()

4.checkStock()

5.is Sufficient(amount)

6.confirmOrder()

7.sendData()

8.orderConfirmed()

Sequence Diagram :
confirm Orders/E-1:
Insufficient Stock Amount

Figure 17 :Confirm Order Sequence Diagram

SRS –Online Retail Supply Chain System Page 46


Software Requirements Specification (SRS)

3.1.8.9Confirm Order Activity Diagram

Start Confirm Order Use Case

Select Confirmation

Select Order

View Order Select Stock


Info

Check Stock

Stock is Insufficient

Confirm Order

Reject
Order
Submit
Confirmation

Orders >1 Order has been


confirmed

Figure 18 :Confirm Order End Confirm Order Use Case Activity


Diagram

SRS –Online Retail Supply Chain System Page 47


Software Requirements Specification (SRS)

3.1.9Bill Store Manager Use Case

Supplier
Bill Store Manager

3.1.9.1Brief Description

The supplier will calculate item order and make invoice. And then, the supplier will send invoice to
user account.

3.1.9.2Flow of Events

The use case begins when the supplier press invoice button menu.

3.1.9.3Basic Flow

1. Press invoice button menu


2. Press open transaction button
3. Open order
4. Enter item
5. Enter quantity
6. Calculate item price (items > 1, back to enter item)
7. Press close transaction button
8. Get total price
9. Fill in user information
10. Fill in retailer information
11. Submit invoice
12. Invoice has been submitted
13. End bill store manager

3.1.9.4Alternative Flows

If the user didn’t complete invoice information, error will displayed into the system and back to fill
in information.

SRS –Online Retail Supply Chain System Page 48


Software Requirements Specification (SRS)

3.1.9.5Special Requirements

The supplier must have item ordered, user information and retailer information

3.1.9.6Preconditions

Before making invoice the supplier must login to the system.

3.1.9.7Postconditions

The supplier has been submit invoice to user account

SRS –Online Retail Supply Chain System Page 49


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 50


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 51


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 52


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 53


Software Requirements Specification (SRS)

3.1.9.8Bill Store Manager Sequence Diagram

:Supplier Form :Transiction :Order DB :Invoice Ctl :Invoice DB


: Supplier

1.newInvoice()

2.newID( )

3.getOrderInfo.()

4.orderInfo.()

5.enterItem()

6.enterQuantity(integer)

7.calculateItemPrice()

8.insertItem(item,quantity,price)

9.closeTransiction(total)

10.getTotal(total)

11.fill inUserInfo.()

12.fill inRetailerInfo.()

13.submitInvoice()

14.invoice has been submitted()

Sequence Diagram:
Bill Store Manager/E-1
:Incompleted Information

Figure 19 : Bill Store Manager Sequence Diagram

SRS –Online Retail Supply Chain System Page 54


Software Requirements Specification (SRS)

3.1.9.9Bill Store Manager Activity Diagram

Start Bill Store Manager Use


Case

Select Invoice Select Close


Transiction

Select Open Get Total Price


Transiction

Open Order Fill in User


Information

Enter Item Fill in Retailer


Information

Enter Quantity
Submit Invoice

Items >1 Calculate Item Did not complete Invoice Information Display Error
Price Message

Invoice has
been submitted

End Bill Store Manager Use


Case

Figure 20 : Bill Store Manager Activity Diagram

SRS –Online Retail Supply Chain System Page 55


Software Requirements Specification (SRS)

3.1.10Update Order Status Use Case

Supplier Update Order Status

3.1.10.1Brief Description

After supplier confirm order or reject order, supplier will make update order status. This use case
describe about the step to update order status

3.1.10.2Flow of Events

The use case begins when the supplier press update order status button menu

3.1.10.3Basic Flow

1. Press update order status button(1)


2. Select approve
3. Submit order status(1)
4. Press update order status button(2)
5. Select invoice
6. Submit order status(2)
7. Press update order status button(3)
8. Select Paid
9. Submit order status(3)
10. Press order button menu
11. View orders
12. Select order
13. Press update order status button(4)
14. Select delivered
15. Submit order status(4)
16. End update order status

3.1.10.4Alternative Flows

If the supplier reject order, the update order status never change.

SRS –Online Retail Supply Chain System Page 56


Software Requirements Specification (SRS)

3.1.10.5Special Requirements

Before the supplier update order status, supplier must approve order, make invoice, paid, order,
and delivered.

3.1.10.6Preconditions

The supplier must have ID and password to access the system for update status order.

3.1.10.7Postconditions

The supplier has been submit order status

SRS –Online Retail Supply Chain System Page 57


Software Requirements Specification (SRS)

3.1.10.8Update Order Status Sequence Diagram

:Update Order :Status Ctl :Order DB


: Supplier
Status Form

1.selectApproved()

2.sendData()
Sequence Diagram:
Update Order Status/E-1:
Select Rejected 3.orderApproved()

4.selectInvoiced()

5.sendData()

Sequence Diagram:
Update Order Status/E-2:
6.orderInvoiced()
Select Uninvoiced

7.selectPaid()

8.sendData()

Sequence Diagram:
Update Order Status/E-3:
9.orderPaid( )
Select Unpaid

10.viewOrders( )

11.selectOrder()

12.selectDelivered( )

13.sendData( )
Sequence Diagram:
Update Order Status/E-4:
Select Undelivered 14.orderDelivered( )

Figure 21 : Update Order Status Sequence Diagram

SRS –Online Retail Supply Chain System Page 58


Software Requirements Specification (SRS)

3.1.10.9Update Order Status Activity Diagram

Start Update Order Status Use


Case

Select Update Order After Order has Submit Order


Status (1) been confirmed Status (3)

Select Rejected

Select Orders
Select Approved After Order has
Submit Order been delivered
Status(1)

Submit Order View Orders


Status (1)
After Order has
been invoiced
Select Update Order
Status (2) Select Order

Select Invoiced
Select Update Order
Status (4)

Submit Order
Status (2)
Select Delivered
Select Update Order After Order has
Status (3) been paid
Submit Order
Status (4)
Select Paid

End Update Order Status Use


Case

Figure 22 : Update Order Status Activity Diagram

SRS –Online Retail Supply Chain System Page 59


Software Requirements Specification (SRS)

Non Functional Requirements


3.1.11Usability

3.1.11.1Windows Compliance

The desktop user-interface must be Windows 95/98 and above OS environment compliant for
access the system.

3.1.11.2Designs for Ease-of-Use

This system make very compatible to user with slow connection. Also not much
application in this system so can make user easy to access. The system also easy for
remember and shall be used by people with no training, and possibly no understanding of
English.

3.1.11.3Online Help

Online documents that capture and condense “how to” perform some behavior, operation, or
function with a system, serve as a semi-structured narrative that assert or imply end-user
requirements. “Formal” How-to’s descriptions include explicit declarations of their purpose as a
How-to and may be identified as a system tutorial. Community participants may seek these formal
How-to’s when they need to add a system module or class structure, or contribute other resources
or efforts to the open software project. In contrast, informal How-to’s may appear as a selection,
composition, or decomposition of any of the proceeding. These informal How-to guides may be
labeled as a “FAQ”; that is, as a list of frequently asked questions about how a system operates,
how to use it, where to find its development status, which developed what, known bugs and
workarounds, etc. However, most FAQs do not indicate how frequently any of the questions may
have been asked, or if effort has been made to measure or track FAQ usage/reference.

3.1.12Reliability

Reliability is complex concept that should always be considered at the system rather than the
individual component level. Because the components in a system are interdependent, a failure in
one component can be propagated through the system and affect the operation of other component.

SRS –Online Retail Supply Chain System Page 60


Software Requirements Specification (SRS)

3.1.12.1Availability

The probability that the system is available for use at a given time. Availability of 0.998 means
that the system is likely to be available for 998 of every 1000 time units. This metric should be
used in non-stop systems where users expect the system to deliver a continuous service. Examples
of such systems are telephone switching system and railway signaling systems.

3.1.12.2Mean Time between Failures

The average time between observed system failures. An MTTF of 500 means that one failure can
be expected every 500 time unit. This metric should be used in systems where there are long
transaction; that is, where people use the system for long time. The MTTF should be longer than
the average length of each transaction. Example of system where this metric may be used are word
processor systems and CAD systems.

3.1.13Performance

3.1.13.1Simultaneous Users

Online retail supply chain system can support 10000 simultaneous users against the central
database at any given time and up to 4000 simultaneous users against the local servers at any one
time.

3.1.13.2Database Access Response Time

The system provides access to the legacy course catalog database with no more than 7 second
latency.

3.1.13.3Transaction Response Time

The user can access the system in 30 second and when the user login the system take 15 seconds.
The system provide several optional such as log out, order item, contact us etc. and to login every
optional the system take 1 minute. The system takes 1 minute 45 seconds to complete 85% all
transaction. This also depends with internet connection. For complete all transactions the system
requires the user have 50 Mbps internet connection.

SRS –Online Retail Supply Chain System Page 61


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 62


Software Requirements Specification (SRS)

4.INDEX

A
S L V
Abbreviations,
Scope,7 7 Login,10
View Order Activity Diagram,36
Acronyms, 7 Users,49
Simultaneous LoginView
activity diagram,15
Order Sequence Diagram,35
Administrator,7
Software Product Features,14 LoginView
Sequence
OrderDiagram,14
Status Activity Diagram,30
Alternative Flow13,17,20,24,28,31,34,37,40,45 Login
Special Requirements14,17,21,23,28,31,34,37,41,42,45 Usecase,13
View Order Status Sequence Diagram,29
Appendices
Specific Requirements,13 View Order Status Use Case,28
Availability,49 View Order Status,11
T M View Order Use Case,34
B
Transaction Response Time,50 MakeView
an Order Payment Activity Diagram,33
Order,11
Basic Flow13,16,20,28,26,31,34,37,40,44 Make an Order Payment Sequence Diagram,32
Bill Store Manager,11
U MakeW an Order Payment Use Case,31
Bill Store Manager Activity Diagram,43
Update Order Status Activity Diagram,47 Make an Order Compliance,48
Windows Payment,11
Bill Store Manager Sequence Diagram,42
Update Order Status Sequence Diagram,46 Mean Time Between Failures,49
Bill Store Manager Use Case,40
Update Order Status Use Case,44
Brief Description13,16,20,24,28,31,34,37,40,44
Update Order Status,11 N
Usability,48 Non Functional Requirements,48
C
User Characteristics,11
Check Out Customer,10 O
Check Out Customer Activity Diagram,19 Online Help,48
Check Out Customer Sequence Diagram,18 Overall Description,10
Check Out Customer Use Case,16 Oversee Current Stock Activity Diagram,23
Confirm Order,11 Oversee Current Stock Sequence Diagram,22
Confirm Orders Activity Diagram,39 Oversee Current Stock Use Case,20
Confirm Orders Sequence Diagram,38 Oversee Current Stock,10
Confirm Orders Use Case,37 Overview,9

D P
Database Access Response Time,49 Performance,49
Definitions,7 Place an Order Activity Diagram,27
Design for ease of use,48 Place an Order Sequence Diagram,26
Diagram15,18,22,25,28,31,34,37,41,45 Place an Order Use Case,24
Place an Order,10
E Postconditions,14,17,21,25,29,32,35,38,41,45
Extension Points14,16,20,27,30,33,36,39,43 Preconditions,14,17,21,25,29,31,34,37,41,45
Product Functions,10
F Product Perspective,10
Flow of Events13,16,20,24,28,31,34,37,40,44 Purpose,6
Forget Password,13
R
I References,8
Index,49 Reliability,49
Introduction,7
Invalid Password,14

SRS –Online Retail Supply Chain System Page 63


Software Requirements Specification (SRS)

SRS –Online Retail Supply Chain System Page 64