software requirment specification

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

Draft

Mohammed Tareq

Oryza Safutra

Iqbal Ahada

Alvino Yulian

Aditya Wirmansyah

Muhammad Ikhsan

Initial draft created for

distribution and

review comments

12/09/2008

Preliminary

Mohammed Tareq

Oryza Safutra

Iqbal Ahada

Alvino Yulian

Aditya Wirmansyah

Muhammad Ikhsan

Second draft

incorporating initial

review comments,

distributed for final

review

15/09/2008

Final

Mohammed Tareq

Oryza Safutra

Iqbal Ahada

Alvino Yulian

Aditya Wirmansyah

Muhammad Ikhsan

First complete draft,

which is placed under

change control

17/09/2008

SRS –Online Retail Supply Chain System


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.................................................................................................102.1.1 User Interfaces........................................................................................ .............102.1.2 Software Interfaces..................................................................................... ..........10

PRODUCT FUNCTIONS....................................................................................................112.1.3 Login..................................................................................................... ...............132.1.4 Checkout Customer............................................................................. .................132.1.5 Oversee Current Stock...................................................................................... ....142.1.6 Place an Order...................................................................................... ...............142.1.7 View Order Status.......................................................................................... .......142.1.8 Make an Order Payment...................................................................................... .142.1.9 View Order................................................................................ ...........................142.1.10 Confirm Order............................................................................................... .....142.1.11 Bill Store Manager........................................................................ .....................142.1.12 Update Order Status......................................................................................... ..15

USER CHARACTERISTICS................................................................................................15

3. SPECIFIC REQUIREMENTS...............................................................................................16

SOFTWARE PRODUCT FEATURES......................................................................................163.1.1 Login Use Case...................................................................................... ..............16

3.1.1.1 Brief Description....................................................................................................163.1.1.2 Flow of Events.......................................................................................................163.1.1.3 Basic Flow - Login.................................................................................................163.1.1.4 Alternative Flows...................................................................................................16

3.1.1.4.1 Forget Password........................................................................................... .....163.1.1.5 Special Requirements............................................................................................173.1.1.6 Preconditions.........................................................................................................173.1.1.7 Postconditions........................................................................................................173.1.1.8 Login Sequence Diagram......................................................................................173.1.1.9 Login Activity Diagram.........................................................................................18

3.1.2 Check Out Customer Use Case......................................................... ...................203.1.2.1 Brief Description....................................................................................................21



3.1.2.2 Flow of Events.......................................................................................................213.1.2.3 Basic Flow - Check Out Customer........................................................................213.1.2.4 Alternative Flows...................................................................................................213.1.2.5 Special Requirements............................................................................................213.1.2.6 Preconditions.........................................................................................................213.1.2.7 Postconditions........................................................................................................223.1.2.8 Check Out Customer Sequence Diagram..............................................................233.1.2.9 Check Out Customer Activity Diagram................................................................24

3.1.3 Oversee Current Stock Use Case....................................................................... ...243.1.3.1 Brief Description....................................................................................................253.1.3.2 Flow of Events.......................................................................................................253.1.3.3 Basic Flow .............................................................................................................253.1.3.4 Alternative Flows...................................................................................................253.1.3.5 Special Requirements............................................................................................253.1.3.6 Preconditions.........................................................................................................263.1.3.7 Postconditions........................................................................................................263.1.3.8 Oversee Current Stock Sequence Diagram...........................................................273.1.3.9 Oversee Current Stock Activity Diagram..............................................................29

3.1.4 Place an Order Use Case....................................................................... ..............293.1.4.1 Brief Description....................................................................................................303.1.4.2 Flow of Events.......................................................................................................303.1.4.3 Basic Flow – Place an Order.................................................................................303.1.4.4 Alternative Flows...................................................................................................303.1.4.5 Special Requirements............................................................................................303.1.4.6 Preconditions.........................................................................................................313.1.4.7 Postconditions........................................................................................................313.1.4.8 Place an Order Sequence Diagram........................................................................313.1.4.9 Place an Order Activity Diagram..........................................................................34

3.1.5 View Order Status Use Case........................................................................... ......353.1.5.1 Brief Description....................................................................................................353.1.5.2 Flow of Events.......................................................................................................353.1.5.3 Basic Flow .............................................................................................................363.1.5.4 Alternative Flows...................................................................................................363.1.5.5 Special Requirements............................................................................................363.1.5.6 Preconditions.........................................................................................................363.1.5.7 Postconditions........................................................................................................363.1.5.8 View Order Status Sequence Diagram..................................................................373.1.5.9 View Order Status Activity Diagram.....................................................................38

3.1.6 Make an Order Payment Use Case...................................................................... .393.1.6.1 Brief Description....................................................................................................393.1.6.2 Flow of Events.......................................................................................................393.1.6.3 Basic Flow..............................................................................................................393.1.6.4 Alternative Flows...................................................................................................393.1.6.5 Special Requirements............................................................................................403.1.6.6 Preconditions.........................................................................................................403.1.6.7 Postconditions........................................................................................................403.1.6.8 Make an Order Payment Sequence Diagram........................................................403.1.6.9 Make an Order Payment Activity Diagram...........................................................41

3.1.7 View Order Use Case................................................................. ..........................423.1.7.1 Brief Description....................................................................................................423.1.7.2 Flow of Events.......................................................................................................423.1.7.3 Basic Flow..............................................................................................................423.1.7.4 Alternative Flows...................................................................................................423.1.7.5 Special Requirements............................................................................................42



3.1.7.6 Preconditions.........................................................................................................433.1.7.7 Postconditions........................................................................................................433.1.7.8 View Order Sequence Diagram............................................................................433.1.7.9 View Order Activity Diagram................................................................................44

3.1.8 Confirm Order Use Case................................................................................... ...453.1.8.1 Brief Description....................................................................................................453.1.8.2 Flow of Events.......................................................................................................453.1.8.3 Basic Flow..............................................................................................................453.1.8.4 Alternative Flows...................................................................................................453.1.8.5 Special Requirements............................................................................................453.1.8.6 Preconditions.........................................................................................................453.1.8.7 Postconditions........................................................................................................453.1.8.8 Confirm Order Sequence Diagram........................................................................463.1.8.9 Confirm Order Activity Diagram..........................................................................47

3.1.9 Bill Store Manager Use Case................................................................... ............483.1.9.1 Brief Description....................................................................................................483.1.9.2 Flow of Events.......................................................................................................483.1.9.3 Basic Flow..............................................................................................................483.1.9.4 Alternative Flows...................................................................................................483.1.9.5 Special Requirements............................................................................................493.1.9.6 Preconditions.........................................................................................................493.1.9.7 Postconditions........................................................................................................493.1.9.8 Bill Store Manager Sequence Diagram.................................................................543.1.9.9 Bill Store Manager Activity Diagram...................................................................55

3.1.10 Update Order Status Use Case.......................................................................... .563.1.10.1 Brief Description..................................................................................................563.1.10.2 Flow of Events.....................................................................................................563.1.10.3 Basic Flow............................................................................................................563.1.10.4 Alternative Flows.................................................................................................563.1.10.5 Special Requirements..........................................................................................573.1.10.6 Preconditions.......................................................................................................573.1.10.7 Postconditions......................................................................................................573.1.10.8 Update Order Status Sequence Diagram.............................................................583.1.10.9 Update Order Status Activity Diagram...............................................................59

NON FUNCTIONAL REQUIREMENTS..................................................................................603.1.11 Usability............................................................................................ .................60

3.1.11.1 Windows Compliance..........................................................................................603.1.11.2 Designs for Ease-of-Use.......................................................................................603.1.11.3 Online Help..........................................................................................................60

3.1.12 Reliability................................................................................................. ..........603.1.12.1 Availability...........................................................................................................613.1.12.2 Mean Time between Failures...............................................................................61

3.1.13 Performance........................................................................................... ............613.1.13.1 Simultaneous Users..............................................................................................613.1.13.2 Database Access Response Time.........................................................................613.1.13.3 Transaction Response Time.................................................................................61

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



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



1.INTRODUCTION

PurposeThe 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.

ScopeThis 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



• 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


http://www.jusco.com.my/

http://www.google.com/

http://www.wikipedia.com/

Login

User

Check out CustomerCashier

View Order

Conf irm Order

Bill Store Manager

Update Order Status

Supplier

Ov ersee Current Stock

Place an Order

Make an Order Pay ment

View Order StatusStore Manager


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

Figure 1 : Online Retail Supply Chain System Use Case Diagram



2.OVERALL DESCRIPTION

Product PerspectiveThis 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



2. Microsoft FrontPage

3. Microsoft Access 2003

Product FunctionsThe 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.


Start Onl ine Retail Supply Chain System

Check out Customer

Oversee Current Stock

Place an Order

View Order

Confirm Order

Bill Store Manager

Order approved

Update Order Status

Order rejected

View Order Status

Make an Order Payment

Update Order Status(again)

View Order Status(again)

End Online Retail Supply Chain System

Order rejected Order approved and invoiced


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.



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.



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 CharacteristicsThis 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.


User Login


3.SPECIFIC REQUIREMENTS

Software Product Features

3.1.1Login Use Case

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


: User: Login Form : Login Ctl : User : User Form

1.fill in login form()

2.get user info(integer,string)

3.is valid()

4.open()

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

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


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

Figure 3 : Login Sequence Diagram



3.1.1.9Login Activity Diagram


Start Login Use Case

Fill in Login Form

Select Submit

Display Error Message

Incorrect ID or Passward

Open User Form

End Login Use Case

If a user forgot his/her password, they must get it first from the system by typing their e-mail.


Figure 4 : Login Activity Diagram

3.1.2Check Out Customer Use Case


CashierCheck out Customer



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

cashier.


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


There is no alternative flow associated with this use case.


There are no special requirements associated with this use case.


There are no preconditions associated with this use case.




The customer has been check out


: Cashier: CashierForm : Transiction : Item

: Bar Code Scanner

1.newSale()

2.new(ID)

5.enterQuantity(integer)

8.endSale()

9.closeTransiction(total)

11.enterPayment()

15.produceReceipt()

4.getItem(code)

7.insertItem(item,quantity,price)

6.calculateItemPrice()

10.getTotal(total)

12.deductTotal()

13.returnRemaining()

14.deductStock()

3.getItemCode()


3.1.2.8Check Out Customer Sequence Diagram

Figure 5 : Check out Customer Sequence Diagram


Start check out customer use case

Select New Sale

Select Open Transiction

Scan Item

Enter Quantity

Calculate Item Price

Get Total Price

Select End Sale

Select Close Transiction

Select Payment

Receive Payment

Return Remaining

Deduct Stock

Produce Receipt

Customer Has Been Checked out

End check out customer use case

Did not submit


3.1.2.9Check Out Customer Activity Diagram

Figure 6 : Check out Customer Activity Diagram

3.1.3Oversee Current Stock Use Case




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

to the system.


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


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.


This system only can access by store manager.


Oversee Current StockStore Manager



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


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



3.1.3.8Oversee Current Stock Sequence Diagram


: Store Manager: Stock Form : Stock Ctl : Stock DB

1.viewStockAlerts()

5.confirmRequests()

Sequence Diagram: Oversee Current Stock/ E-1 :Alert is not true

6.senData()

7.alertsConfirmed()

2.getStockInfo()

3.stockInfo.

4.checkStock()


Figure 7 : Oversee Current Stock Sequence Diagram


Start oversee current stock use case

Select Stock

View Stock Alerts

Select Stock Info.

Select Stock Alert

Check Stock

Confirm Request

Submit Confirmation

Ignore Alert

Alert is not true

End oversee current stock use case

Alerts have been confirmed


3.1.3.9Oversee Current Stock Activity Diagram

Figure 8 : Oversee Current Stock Activity Diagram

3.1.4Place an Order Use Case




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.


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


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.


There is no special requirement associated with this use case.


Store Manager Place an Order



The user must have ID and password to enter the system


The user submit the order item through the system

3.1.4.8Place an Order Sequence Diagram


: Store Manager:Supplier Form :Order Ctl :Supllier DB

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



Start Place an Order Use Case

Select Suppliers

View Suppliers

Select Supplier

Select Catalog

View Catalog

Fill in User Info.

Select Item

Select Amount

Select Delivery Date

Order has been submitted

End Place an Order Use Case

Submit Order

Items >1

Dispaly Error Message

Did not complete order information


Figure 9 :Place an Order Sequence Diagram

3.1.4.9Place an Order Activity Diagram



Figure 10 :Place an Order Activity Diagram

3.1.5View Order Status Use Case


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

system.


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


Store Manager View Order Status


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


There is an alternative flow associated with this use case.


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.


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


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


: Store Manager:Store Manager

Form:View Ctl :Order DB

1.organizeOrders(delivery date)

2.ViewOrders()

3.openOrder()

4.getOrderInfo.()

5.orderInfo.()

6.viewOrderStatus()

7.closeOrder()

8.sendData()

9.orderStatusViewed()


3.1.5.8View Order Status Sequence 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

End View Order Status Use Case


Figure 11 :View Order Status Sequence Diagram

3.1.5.9View Order Status Activity Diagram



Figure 12 :View Order Status Activity Diagram

3.1.6Make an Order Payment Use Case


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.


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


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

empty field information.


Make an order PaymentStore Manager

: Store Manager:Payment Form :Payment Ctl :Payment DB

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.



The user must have account bank to make a payment.


The user must have account to enter the system.


The payment has been submitted

3.1.6.8Make an Order Payment Sequence Diagram

Figure 13 :Make an Order Payment Sequence Diagram


Start Make an Order Payment Use Case

Select Payment

Select Method

Fill in Required Information

Submit Payment

Payment has been submited

End Make an Order Payment Use Case


Did not complete Information

Orders >1


3.1.6.9Make an Order Payment Activity Diagram

Figure 14 :Make an Order Payment Activity Diagram



3.1.7View Order Use Case


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

case is supplier.


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


There is no alternative flow associated with this use case.


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


Supplier View Order

: Supplier:Supplier Form :View Ctl :Order DB

2.viewOrders()

3.openOrder()

4.getOrderInfo.()

5.orderInfo.()

6.closeOrder()

7.prioritiseOrders(delivery date,retailer)

8.sendData()

9.ordersViewed()

1.organizeOrders(delivery date)



The supplier must have ID and password to enter the system


The supplier have been view all orders.

3.1.7.8 View Order Sequence Diagram

Figure 15 :View Order Sequence Diagram


Start View Order Use Case

End View Order Use Case

Start View Order Use Case

Select Inbox

View Orders Open Order

Close Order

End View Order Use Case

Prioritise Orders

Select Ok

Order has been viewed

Orders >1


3.1.7.9View Order Activity Diagram

Figure 16 :View Order Activity Diagram



3.1.8Confirm Order Use Case


The supplier will make confirm or reject from every order. The supplier will send confirm or reject

order to the user account.


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


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


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


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


The supplier has been confirm the order


SupplierConfirm Order

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

: Supplier:Supplier Fom :Confirmation

Ctl:Stock :Stock DB :Order DB

1.viewOrder()

2.getStockInfo.()

3.StockInfo.()

4.checkStock()

5.is Sufficient(amount)

6.confirmOrder()

7.sendData()

8.orderConfirmed()


3.1.8.8Confirm Order Sequence Diagram

Figure 17 :Confirm Order Sequence Diagram


Start Confirm Order Use Case

Select Confirmation

Select Order

View Order Select Stock Info

Check Stock

Confirm Order

Submit Confirmation

Order has been confirmed

End Confirm Order Use Case

Reject Order

Orders >1

Stock is Insufficient


3.1.8.9Confirm Order Activity Diagram

Figure 18 :Confirm Order Activity

Diagram



3.1.9Bill Store Manager Use Case


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

user account.


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


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

in information.


SupplierBill Store Manager



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


Before making invoice the supplier must login to the system.


The supplier has been submit invoice to user account


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

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


3.1.9.8Bill Store Manager Sequence Diagram

Figure 19 : Bill Store Manager Sequence Diagram


Start Bill Store Manager Use Case

Select Invoice

Select Open Transiction

Open Order

Enter Item

Enter Quantity

Calculate Item Price

Items >1

Select Close Transiction

Get Total Price

Fill in Retailer Information

Submit Invoice

Fill in User Information

End Bill Store Manager Use Case

Invoice has been submitted


Did not complete Invoice Information


3.1.9.9Bill Store Manager Activity Diagram

Figure 20 : Bill Store Manager Activity Diagram



3.1.10Update Order Status Use Case


After supplier confirm order or reject order, supplier will make update order status. This use case

describe about the step to update order status


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)


5. Select invoice



8. Select Paid


10. Press order button menu

11. View orders

12. Select order


14. Select delivered


16. End update order status


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


Supplier Update Order Status



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

and delivered.


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


The supplier has been submit order status


: Supplier:Update Order Status Form

:Status Ctl :Order DB

1.selectApproved()

2.sendData()

3.orderApproved()

4.selectInvoiced()

5.sendData()

6.orderInvoiced()

7.selectPaid()

8.sendData()

9.orderPaid( )

12.selectDelivered( )

13.sendData( )

14.orderDelivered( )

10.viewOrders( )

11.selectOrder()

Sequence Diagram: Update Order Status/E-1: Select Rejected

Sequence Diagram: Update Order Status/E-2: Select Uninvoiced

Sequence Diagram: Update Order Status/E-3: Select Unpaid

Sequence Diagram: Update Order Status/E-4: Select Undelivered


3.1.10.8Update Order Status Sequence Diagram

Figure 21 : Update Order Status Sequence Diagram


Start Update Order Status Use Case

Select Update Order Status (1)

Select Approved

Submit Order Status (1)


Select Invoiced



Select Paid

Select Rejected

Submit Order Status(1)


Select Orders

View Orders

Select Order

Select Delivered



End Update Order Status Use Case

After Order has been confirmed

After Order has been invoiced

After Order has been paid

After Order has been delivered


3.1.10.9Update Order Status Activity Diagram

Figure 22 : Update Order Status Activity Diagram



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.



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.



4.INDEX

SScope,7Simultaneous Users,49Software Product Features,14Special Requirements14,17,21,23,28,31,34,37,41,42,45Specific Requirements,13

TTransaction Response Time,50

UUpdate Order Status Activity Diagram,47Update Order Status Sequence Diagram,46Update Order Status Use Case,44Update Order Status,11Usability,48User Characteristics,11

VView Order Activity Diagram,36View Order Sequence Diagram,35View Order Status Activity Diagram,30View Order Status Sequence Diagram,29View Order Status Use Case,28View Order Status,11View Order Use Case,34View Order,11

WWindows Compliance,48


AAbbreviations, 7Acronyms, 7Administrator,7Alternative Flow13,17,20,24,28,31,34,37,40,45AppendicesAvailability,49

BBasic Flow13,16,20,28,26,31,34,37,40,44Bill Store Manager,11Bill Store Manager Activity Diagram,43Bill Store Manager Sequence Diagram,42Bill Store Manager Use Case,40Brief Description13,16,20,24,28,31,34,37,40,44

CCheck Out Customer,10Check Out Customer Activity Diagram,19Check Out Customer Sequence Diagram,18Check Out Customer Use Case,16Confirm Order,11Confirm Orders Activity Diagram,39Confirm Orders Sequence Diagram,38Confirm Orders Use Case,37

DDatabase Access Response Time,49Definitions,7Design for ease of use,48Diagram15,18,22,25,28,31,34,37,41,45

EExtension Points14,16,20,27,30,33,36,39,43

FFlow of Events13,16,20,24,28,31,34,37,40,44Forget Password,13

IIndex,49Introduction,7Invalid Password,14

LLogin,10Login activity diagram,15Login Sequence Diagram,14Login Usecase,13

MMake an Order Payment Activity Diagram,33Make an Order Payment Sequence Diagram,32Make an Order Payment Use Case,31Make an Order Payment,11Mean Time Between Failures,49

NNon Functional Requirements,48

OOnline Help,48Overall Description,10Oversee Current Stock Activity Diagram,23Oversee Current Stock Sequence Diagram,22Oversee Current Stock Use Case,20Oversee Current Stock,10Overview,9

PPerformance,49Place an Order Activity Diagram,27Place an Order Sequence Diagram,26Place an Order Use Case,24Place an Order,10Postconditions,14,17,21,25,29,32,35,38,41,45Preconditions,14,17,21,25,29,31,34,37,41,45Product Functions,10Product Perspective,10Purpose,6

RReferences,8Reliability,49

software requirment specification

Documents