E-Commerce Super Solutions - Design Specification | CS 430, Study Guides, Projects, Research of Software Engineering

Download E-Commerce Super Solutions - Design Specification | CS 430 and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

Contact: [email protected]; [email protected]

E-

Com

merc

e

Supe

r

Solut

ions

Design

Specificati

on: CS

E. Christopher

Caynor

Jesse

Musgrove

Tyler Sigley

Emerson Sklar

Contents

6.3 State Transition Diagrams................................................................................................................ 56 6.3.1 Customer Diagram.................................................................................................................... 56 6.3.2 Sales Manager Diagram............................................................................................................ 57 6.3.3 Warehouse Manager Diagram.................................................................................................. 58

1.0 Introduction

1.1 Project Explanation

We have been contracted to develop a streamlined sales solution for a corporate partner of the West Virginia University Bookstores. We will not only manage the current supply of books available in the system through our database solution, but also complete sales transactions on the web interface for the company.

1.2 Scope

The system will be required to accept sales orders from customers. It will also need to return information from the databases to customers and employees wishing to search the products. It will be required to display sales information and allow for the modification of product information by a sales manager. It will also have to access the warehouse system to display orders and to allow for the status of the order to change upon shipping. It is important to realize that data will be almost exclusively modified, added, and deleted through the use of SQL Queries and Results. These commands will be hidden in the HTML code built through the use of Visual C.

1.3 Context

The system is going to be centralized within the company infrastructure at a main location. This system will be accessible through a web-based interface. Warehouses must be able to individually interact with the databases from external locations. The software will be reliant on user input. The credit system will be automated; sales processed by the system will use an HTML structure. The software itself is very reliant on communication with the system's database that will store all books and records. The system itself is primarily a link between that database and the customers or bookstore employees.

1.4 Constraints

A great deal of data is processed by the system. This will require advanced hardware to handle to amount of data transfer and regular interfaces from the internet. The stock will regularly change as individual universities make changes to their course curriculum. There is also a security concern which must be addressed. The database and web-server must be carefully managed to prevent outside individuals from accessing the data without permission.

1.5 Desired Outcome

We wish, through the use of a rapid prototyping design model, to produce a working web-based e- commerce solution by the end of April 2008. Our system will access a database on the company’s servers to control and manage stock information. All sales will be completed through the web-based interface and the warehouse will be able to access information about sales in need of shipping through their database control. To allow for expansion, our system will be developed with ease of updating in mind. Ideally, updating a single set of files on the company’s server will allow the entire system to be modified and improved.

2.0 Data Design

2.1 Global Data Structure

2.1.1 Context Diagram

E-Commerce System Sales Administration Warehouse Administration Customer Banking System Login Logout Query Sold Book Shipped Acknowledge Receipt Query Incoming Functionality Sold Books Incoming Books Billing Request Credit Passed Modify Book Remove Book Add Book Query Books Request Sales Reset Sales Import Data Search Customers Remove Customer Modify Customer Modify Feedback Remove Feedback Book Information Customer Information Functionality Login Logout Register Search Checkout Browse Add Item Remove Item Empty Cart Change Quantity Save Cart Feedback Restock Notice Book Information Detailed Book Information Functionality E-Mail Logout Login

2.2 Database Structure

SalesItem PK itemid itemname isbn quantityinstock new author publisher copyright edition coursenumbers ordercost restock feedbackids warehouseids CustomerAccount PK customerid customername creditcardinfo mailingaddress billingaddress phonenumber FK 1 cartid restocktitles email pendingorderids pastorderids feedbackids Feedback PK feedbackid FK 1 customerid information rating WarehouseStatistics PK warehouseid pendingorders statusreport contactphone contactaddress OrderInformation PK orderid FK 1 customerid orderdate shippingdate orderstatus comments trackingnumbers itemids ShoppingCart PK cartid FK 1 customerid itemids

2.2.1 SalesItem

The sales items will be made up of the following collection of information. ItemID – The ID number used by the system. ItemName – The title of the product. ISBN – The ISBN used to identify the product. QuantityInStock – The quantity in stock, this must be attached to the individual warehouse. New – This is a true/false for whether the book is new or used. Author – The author(s) of the product. Publisher – The publisher of the product.

Copyright – The copyright date of the product. Edition – The edition of the product. CourseNumbers – The course numbers that are identified with the product. The courses that will require the text. OrderCost – The price the product costs the company. Restock – When the book is restocked, this is set to true. The system will notify all users who wished to be notified upon restocking of the product and this will then be set to false. FeedbackIDs – The ID number used by the system. There can be multiples of these. WarehouseIDs – The ID number used by the system. There can be multiples of these.

2.2.2 CustomerAccount

Customer accounts will be made up of the following information. CustomerID – The ID number used by the system. CustomerName – The customer’s name. CreditCardInfo – The customer’s stored credit card information. This is optional information. MailingAddress – The customer’s mailing address. BillingAddress – The customer’s billing address. PhoneNumber – The customer’s phone number. CartID – The ID number used by the system. RestockTitles – A list of products that the customer has requested to be informed when they return to stock. E-mail – The customer’s e-mail. PendingOrderIDs – The ID number used by the system. There can be many of these. PastOrderIDs – The ID number used by the system. There can be many of these. FeedbackIDs – The ID number used by the system. There can be many of these.

2.2.3 Feedback

The feedback will be created from the following items. FeedbackID – The ID number used by the system.

CustomerID – The ID number used by the system. ItemIDs – The ID number used by the system. Multiple items may exist in one order.

3.0 Architecture and Program Design

3.1 Program Architecture

The program is structured into two separate components. The database structure is a repository as laid out in the concept of data-centered design. The actual control software can be controlled through three individual interfaces. The customer uses an e-commerce web solution to access the functions that drive their typical actions. The sales manager and warehouse manager(s) use web-based interfaces designed specifically for the functionality needed by each position. These interfaces interact with the SQL-based code, which in turn, accesses the database to make queries or modify the data within.

Database

Website/Customer Interaction

Sales

Administration

Warehouse

Administration

3.2 Component Descriptions

3.2.1 Administrative Functions

Only the administrator has access to these functions. These functions allow the administrator to communicate with the other systems and the database server.

3.2.1.1 login

Description

This function allows the Administrator to attempt to login to the system.

Input

Username and Password

Source of Input

Administrator

Output

Administrative GUI and functionality or error message

Destination of Output

To the interface that attempted to log in

Processing

Queries the database comparing the input to any employee entry with administrative access

Requirements

In order to have access to the login function, the user logging in must have access to a computer on the network. No device that is not directly connected to the network may access this function.

Pre-conditions

None

Post Conditions

Administrative access

Side Effects

User status will be shown as active.

Stability

Stable

Necessity

Mandatory

3.2.1.3 importSchoolData

Description

This function allows the Administrator to import data from a file into the system. The data must consist of the appropriate format for class and section numbers linked to books.

Input

Import signal (mouse or keyboard input) Class and Book data

Source of Input

Administrator CSV file (Comma Separated Value file) of the data

Output

Current school data

Destination of Output

Database Server

Processing

This function imports data from a CSV file, processes it, and generates SQL commands to put the information into the database.

Requirements

The file must be of the appropriate format. The user must have administrative functionality to access this function (must be logged in).

Pre-conditions

The required books must already be in the system.

Post Conditions

SQL database updated with new information.

Side Effects

N/A

Stability

Stable

Necessity

Optional

3.2.1.4 addNewBook

Description

This function allows the Administrator to log enter a new book entry into the database

Input

Relevant book information

Source of Input

Administrator

Output

SQL Command

Destination of Output

Database server

Processing

This function takes the input from the user and generates a SQL command to send to the database.

Requirements

The user must be logged in with administrative functionality.

Pre-conditions

N/A

Post Conditions

New book in the database

Side Effects

Customers will be able to view, inform of, or purchase the new book from the website.

Stability

Stable

Side Effects

N/A

Stability

Stable

Necessity

Mandatory

3.2.1.6 modifyBook

Description

This function allows the Administrator to modify a book’s information.

Input

New book values

Source of Input

Administrator

Output

SQL Command

Destination of Output

Database

Processing

This function converts user input into SQL commands to update the database.

Requirements

The user must be logged in with administrative privileges. Also, a book must be selected from the search results.

Pre-conditions

N/A

Post Conditions

Updated book information

Side Effects

N/A

Stability

Stable

Necessity

Optional

3.2.1.7 removeBook

Description

This function allows the Administrator to remove a book’s entry from the database.

Input

Removal signal (mouse or keyboard input).

Source of Input

Administrator

Output

SQL Command

Destination of Output

Database server

Processing

This function sent the database a SQL command to delete the book entry corresponding to the selected book.

Requirements

The user must be logged in with administrative privileges, and a book must be selected.

Pre-conditions

Selected book must exist.

Post Conditions

Book is removed from the database.

Side Effects

N/A

Post Conditions

Customers that match the search criteria (if they exist) are displayed.

Side Effects

N/A

Stability

Stable

Necessity

Mandatory

3.2.1.9 modifyBook

Description

This function allows the Administrator to modify a customer’s information.

Input

New customer information

Source of Input

Administrator

Output

SQL Command

Destination of Output

Database

Processing

This function converts user input into SQL commands to update the database.

Requirements

The user must be logged in with administrative privileges. Also, a customer must be selected from the search results.

Pre-conditions

N/A

Post Conditions

Updated customer information

Side Effects

N/A

Stability

Stable

Necessity

Optional

3.2.1.10 removeBook

Description

This function allows the Administrator to remove a customer’s entry from the database.

Input

Removal signal (mouse or keyboard input).

Source of Input

Administrator

Output

SQL Command

Destination of Output

Database server

Processing

This function sent the database a SQL command to delete the customer entry corresponding to the selected customer.

Requirements

The user must be logged in with administrative privileges, and a customer must be selected.

Pre-conditions

Selected customer must exist in the database.

Post Conditions

Customer is removed from the database.