Project: Aqua Duck/Online Merchandising Company (OMC)

Team No.: Team 1

Class: CSE 3310; Spring 2010

Module: System Requirements Analysis (SRA)

Deliverable: SRA Document

Version: [1.2] Date: [05/03/2010]

Contributors:

Jason BeereJustin Hundt

Juan PlacenciaSandip Shrestha

Revision HistoryVersion number

Date Originator Reason for change

High level description of changes

1.0 03/04/2010 Team 1 Initial draft1.1 04/01/2010 Team 1 Modificaions per

Dr. Khalili’s request

Project Context Diagram: add order status & add

reports Assumptions & Constraints: add credit card constraint

Delivery & Schedule: rearrange table

1.2 05/03/2010 Team 1 Design Change Modifications

Search 2: removed display item ID

Shopping 1: remove modify shipping information

Inventory Management 1: remove sort items by

category; remove Item quantity (on order)

Inventory Management 3: remove item quantity (on

order)Checkout: remove checkout cancel for empty shopping

cart during registration; remove more items order

than availableSales Data: remove

projected salesWebsite Management:

remove on sale item flagCheckout UML: remove

check login condition

TABLE OF CONTENTS

1. INTRODUCTION & PROJECT OVERVIEW....................................................3

2. OBJECTIVES...................................................................................................42.1 BUSINESS Objectives..........................................................................................................4

2.2 SYSTEM Objectives.............................................................................................................5

4. SYSTEMS REQUIREMENTS...........................................................................74.1 Requirements Overview.......................................................................................................7

4.2 Login/Registration Requirements.........................................................................................7

4.3 Account Maintenance Requirements....................................................................................8

4.4 Search Requirements...........................................................................................................9

4.5 Shopping Cart Requirements.............................................................................................11

4.6 Inventory Management Requirements................................................................................12

4.7 Checkout Requirements.....................................................................................................15

4.8 Sales Data Requirements...................................................................................................16

4.9 Website Management Requirements..................................................................................17

5. SOFTWARE PROCESSES AND INFRASTRUCTURE.................................185.1 Hardware and Infrastructure...............................................................................................18

5.2 UML Diagrams.................................................................................................................... 18

5.3 Conceptual Data Model – Database...................................................................................23

5.4 Screen Shots......................................................................................................................24

5.5 Test Plan............................................................................................................................ 24

6. ASSUMPTIONS AND CONSTRAINTS..........................................................256.1 Assumptions.......................................................................................................................25

6.2 Constraints......................................................................................................................... 25

6.3 Out of Scope material.........................................................................................................25

7. DELIVERY AND SCHEDULE........................................................................26

8. STAKEHOLDER APPROVAL FORM............................................................27

APPENDIX:.........................................................................................................28

ii

1. Introduction & Project Overview

J3S (Team 1) is partnering with Aqua Duck to come up with an online system to help Aqua Duck sell their merchandise online. The proposed system does not require any direct interaction between Aqua Duck’s customers and their company; all transactions will take place via this website. The system should be versatile and easy to change, so Aqua Duck can use the website to sell different merchandise at different times through the year. At this time, the system is designed to sell swimwear products. The proposed system should be up and operational by the first week in May 2010 in preparation for the summer shopping season, as long as the SRA is signed by the due date. J3S made additional recommendations in functionality, based on their previous experience and research, to Aqua Duck’s minimum set of requirements.

3

2. Objectives

2.1 BUSINESS OBJECTIVES

The following is a list of business objectives:

Objective 1: Login – System will be password-protected accessible through customer and employee login

Objective 2: Account Maintenance – Customer may create, edit, and view personal account information. Customer may view order history. Customer and employee may change own password

Objective 3: Search – Customer and employee may search for merchandise

Objective 4: Shopping Cart – Customer may add and manage items for purchase

Objective 5: Inventory Management – Authorized employee may create & cancel orders, manage inventory, and set up low inventory alerts

Objective 6: Checkout – Registered customer can purchase items in shopping cart by providing payment and shipping information

Objective 7: Sales data – Authorized employee may view profits, sales, and financial data

Objective 8: Website management – Authorized employee may add and edit website content

4

2.2 SYSTEM OBJECTIVES

The following is a list of system objectives:

Objective 1: System will be web-based

Objective 2: System will support Mozilla Firefox 2.0+ and Microsoft Internet Explorer 6.0+ browsers

Objective 3: Web server running Apache 2 and PHP 5.2

Objective 4: Database server running MySQL 5.1

Objective 5: System hosting will be later determined by team 1

5

3. Project Context Diagram

A user may browse and surf the website prior to login, represented by the area outside the dotted boxes. However, the user is required to login to perform any action within dotted box. The box defines the outer limits of authority level available to customer and employee. The search functions represented on the diagram are the same and can be accessed before and after a user logs on.

6

4. Systems Requirements

4.1 REQUIREMENTS OVERVIEW

A summary of the detailed requirements are specified below.

4.2 LOGIN/REGISTRATION REQUIREMENTS

Project Title: CSE 3310/Spring 2010/OMC Form Type: Requirement

Requirement Title: Login/RegistrationSequence No: 1Short description: Provide User with an interface to login/RegisterDescription: • Provide a space to enter login information (user ID and

password)• Provide ‘Submit’ button to verify• Provide a link for new user registration • Provide fields to enter required information for new users• Provide a check box to verify user is at least 18 years old• Provide a field to enter valid email address for user ID[User ID: valid email address][Password: 6-18 alphanumeric characters]• Provide field to enter customer full name• Provide two fields to enter and re-enter password• Provide field to enter customer’s current address:- House/Building number & Street Address [alphanumeric, 1-256 characters]- City [alphanumeric, 1-256 characters]- State/Province [alphanumeric, 1-256 characters]- Zip/Postal Code [alphanumeric, 1-256 characters]- Country [alphanumeric, 1-256 characters]• Provide ‘Register’ button to process registration• Redirect user to registration page if passwords don’t match or any information is invalid in the fields above (with appropriate error message)• Provide temporary account suspension notice for 30 minutes upon 5 unsuccessful attempts• Provide a button to cancel login or registration page

7

4.3 ACCOUNT MAINTENANCE REQUIREMENTS

The system should provide easy user interface for the user to modify his/her account as per requirement. The basic functionality and requirements for account modification are enlisted below.

Project Title: CSE 3310/Spring 2010/OMC Form Type: Requirement

Requirement Title: Modify User AccountSequence No: 1Short description: Provides a means for a user to change their user account

informationDescription: • Provide space for user to enter their password [6-18 characters]

• Upon successful password validation, provide area to print current version of following user account information:- Username/Email Address [valid email-address]- First name [alphanumeric, 1-256 characters]- Last name [alphanumeric, 1-256 characters]- Billing Address [alphanumeric, space for street address, street name, town, state/province, zip code, country]- Shipping Address [alphanumeric, space for street address, street name, town, state/province, zip code, country]- Preferred payment method [enumeration: credit card, check, COD]- Order History [table format, include: item, date shipped, price, order status]• Temporarily suspend account after 5 unsuccessful password attempts• Provide button to modify account information• Provide button to change password• Upon account information modification, provide space for the following:- Change username/email address [valid email-address]- Change first name [alphanumeric, 1-256 characters]- Change last name [alphanumeric, 1-256 characters]- Change billing address [alphanumeric, space for street address, street name, town, state/province, zip code, country]- Change shipping address [alphanumeric, space for street address, street name, town, state/province, zip code, country]- Change payment method [enumeration: credit card, check, COD]- Provide buttons to save and cancel changes• For items not yet delivered, provide a button for a user to cancel an item in their order history• Upon requesting to change password, provide the following- A space to enter new password [6-18 characters]- A space to confirm new password [required to be exact same entry as abovenew password space]• All changes to user account information shall be validated to ensure they conform to requirements field requirements• If validation fails, return user to account information modification area and notify user of error• Changes to username must not violate a unique username policy• Upon successful data validation, modify appropriate data fields within database, notify user of status, and display current user information• Employee account management allows employee to change own password

Pre-Conditions: User must already be logged in

8

4.4 SEARCH REQUIREMENTS

The system should allow various options for searching items. The user should be able to search items by supplying relevant information on a search box provided by the system. Search result items will be displayed with item name, ID, color, size, and price. The requirements for the search functionality are:

9

10

11

4.5 SHOPPING CART REQUIREMENTS

Shopping cart allows a customer-end user to group items they wish to purchase. Items can be added, removed, or changed. Information on items and group can be shown, and when ready the user can pay for their items.

Project Title: CSE 3310/Spring 2010/OMC Form Type: Requirement

Requirement Title: Shopping cartSequence No: 1Short description: Provide a way to group items that a person intends to purchaseDescription: • Shopping cart can contain zero or more items

• Shopping cart can check inventory items for availability, and make changes based on inventory. A notification will be displayed when a quantity for an item in the shopping cart decreases due to a reduction in inventory.

• Provide user with options to modify items in shopping cart:- Add item to shopping cart- Remove item from shopping cart- Change order details for item in shopping cart- Clear all items from shopping cart• Quantity of a single item in shopping cart must be greater or

equal to 1. Items with a quantity of 0 are removed from shopping cart and a notification displayed

• If an unidentified person logs in as customer, current shopping cart overwrites last saved shopping cart. If unidentified customer has an empty shopping cart, last saved shopping cart is loaded

• Display subtotal, shipping cost, and grand total of items in shopping cart

• Changes to a shopping cart while a registered user is logged aresaved

12

4.6 INVENTORY MANAGEMENT REQUIREMENTS

Inventory management allows employees to see the number of items in stock, and modify the quantity. Employees may modify certain property fields like item name and sale price.

13

Project Title: CSE 3310/Spring 2010/OMC Form Type: Requirement

Requirement Title: Inventory ManagementSequence No: 2Short description: Order InventoryDescription: Provide link to order inventory

Provide an electronic form to order inventory with the following fields:

- Item name [alphanumeric 0-20 characters]- Item product code (UPC) [0-20 numbers]- Item Id [alphanumeric]- Price per unit [currency]- Item quantity [number]- Total price for items [currency]- Grand total for entire order [currency]- Manufacturer Name (supplying entity)[alphanumeric] - Manufacturer Address [alphanumeric (include street address,

street name, city, state/province, postal code, country] - Client Name (ordering entity) [alphanumeric]- Client Mailing address [see manufacturer address]- Note/Remarks [up to 64k characters] Form must allow multiple item types to be ordered from the

same manufacturer. Provide link submit order Upon form submission, the form shall be validated to ensure

ordered items are in database Upon successful validation, a confirmation notice shall appear

that allows user to review their order form. Upon validation failure, notify user to remedy problem Upon confirmation, update database with order Provide functionality to print confirmed order form Provide link in confirmation area to return to administration

pagePre-Conditions: User must be logged in

User must be an employee

14

4.7 CHECKOUT REQUIREMENTS

Checkout allows a customer-end user to purchase items in their shopping cart. After providing billing and shipping information, items are deducted from inventory and an order receipt is generated for the user.

15

Project Title: CSE 3310/Spring 2010/OMC Form Type: Requirement

Requirement Title: CheckoutSequence No: 1Short description: Provide user a way to purchase all items in shopping cartDescription: • Only registered user can continue to complete purchase.

Unregistered users must login/register• A registered user must supply valid payment information:- Shipping name [alphanumeric 0-256 characters]- Shipping address [alphanumeric 0-256 characters]- Billing name [alphanumeric 0-256 characters]- Billing address [alphanumeric 0-256 characters]- Billing method and information (credit card only if billing address is international)• Charges are processed after successful completion of the order• For each item, if the quantity of an item ordered is less than the remaining inventory, item is deducted from inventory and shipping dateis generated.• Unique order number is generated after a successful order• An order receipt is generated and saved to user’s account. It includes:- Order date [MM/DD/YYYY]- Order number [numeric, 1-20 characters]- Shipping name [alphanumeric 0-256 characters]- Shipping address [alphanumeric 0-256 characters]- Billing name [alphanumeric 0-256 characters]- Billing address [alphanumeric 0-256 characters]- Partial billing information [alphanumeric 0-256 characters]- Information on purchased items [Item name, item UPC, Item ID, …]- Subtotal [US currency]- Shipping cost [US currency]- Grand total [US currency]- Shipping date [MM/DD/YYYY]

16

4.8 SALES DATA REQUIREMENTS

Sales data may be easily viewed by an employee. Employee can login to review sales data. Employee should be able to assess current sales, projected sales & gross profit. Employee will be able to view data by order number, customer name, sales date, shipping/delivery date, and payment type. The basic functionality and sales data related requirements are:

17

4.9 WEBSITE MANAGEMENT REQUIREMENTS

Employees and managers can log in to a special website to administer the website. Employees and manager may add items, update item properties, change the quantity of items in stock, put items on sale, create/edit/delete promotions, and change their own password. In addition, managers may create/delete employee & manager, change other users’ passwords, and change the website template.

18

5. Software Processes and Infrastructure

5.1 HARDWARE AND INFRASTRUCTURE

If the system is hosted by team 1, system will be hosted on an HP Pavillion running a virtual machine, labeled the primary host. The virtual machine will be running Ubuntu 9.10, which provides web-hosting and database services. A backup web host will be hosted on a Dell Inspiron, mirroring the primary host. Database will be backed up from the primary host to an external system. If the system is not hosted by team 1, the system will be hosted on a web service provider that will be determined at a later date.

5.2 UML DIAGRAMS

Figure 1: Overall UML Diagram

19

Figure 2: State Transition UML for Login

Figure 3: State Transition UML for Account Maintenance

20

Figure 4: State Transition UML for Search

Figure 5: Class UML for Shopping Cart

21

Figure 6: State Transition UML for I nventory M anagement

Figure 7: State Transition UML for Checkout

22

Figure 8: Class UML for Sales Data

Figure 9: Class UML for Website Management

23

5.3 CONCEPTUAL DATA MODEL – DATABASE

The database structure is being determined at this time. A tentative model that represents part of the database has been created. This portion represents the elements associated with a user on the system.

Figure 10: Partial Database Model

24

5.4 SCREEN SHOTS

A framework that represents locations of major elements of the user interface is shown below. Each section is labeled with its intended functionality. This framework is tentative and may change.

Figure 11: A Framework for Web Page Layout

5.5 TEST PLAN

A test plan will be provided at a later stage of the project.

25

6. Assumptions and Constraints

6.1 ASSUMPTIONS

The following is a list of assumptions:

Ignore deliver details such as dealing with UPS and FedEx

Only people older than 18 can order

System up-time requirements are not considered

Sales outside the USA require credit card

Customers must login to system prior to placing an order

Ignore contract negotiation and legal concerns

User will have compatible browser

6.2 CONSTRAINTS

The following is a list of constraints:

Uptime percentage is not guaranteed

Delivery date may change if additional requirements are added after SRA is signed

Credit card validation ignored

6.3 OUT OF SCOPE MATERIAL

The following is a list of “out of scope” material:

Post Project maintenance is not covered

26

7. Delivery and Schedule

Task/Milestone Description

Anticipated Start Date

Anticipated End Date

Status Comments

Prepare Requirements and UML diagram

2-2-2010 3-2-2010 Complete

SRA document (Includes project objectives, Requirements and UML diagrams)

2-2-2010 3-4-2010 Complete Deliverable will be the SRA document. All stakeholders agree on the content of the SRA by signing in section 8.

Presentation of SRA

3-2-2010 3-4-2010 Complete

Database Design 2-28-2010 3-16-2010 In progress

Framework 3-4-2010 3-22-2010 In progress

HTML Storyboards 3-4-2010 3-22-2010 To be started

Coding Implementation

3-16-2010 4-27-2010 To be started

External Documentation (i.e. User Manual)

3-30-2010 4-27-2010 To be started

Test Data Entry 4-15-2010 5-1-2010 To be started

Test Plan Delivery TBD TBD TBD

Final Milestone: project delivery

5-6-2010

27

8. Stakeholder Approval Form

Stakeholder Name Stakeholder Role Stakeholder Comments

Stakeholder Approval Signature

and Date

Bahram Khalili Development Mgr

Mirza Elahi Project Assistant

Jason Beere Developer

Justin Hundt Developer

Juan Placencia Developer

Sandip Shrestha Developer

28

Appendix:

None

29