Table of Contents
Table of Contents………………………………………………..…......by: Bradley Shedd page 1, 2
Requirements for Veterinary Supply House……………………………..by: Erik Zimmer page 3
E/R Diagram of the System.........................…...by: Cedric Watkins see
attached PDF page 12
Data Flow Diagram……………………………….………...………………by: Jeffrey Melara page 4
Software Requirements Specification (part 1)………….……………..by: Marlon Taylor page 5
1.0
Revision History……………………………………………………………………………………..5
2.0
Introduction……………………………………………………………………………………...…..5
2.1
Purpose of this document……………………………………………………………...…...5
2.2
Scope of this document…………………………………………………………………….5
2.3
Definitions, Acronyms and Abbreviations…………………………………………..…….5
2.4
Business Context…………………………………………………………………….…….5
2.5
Overview…………………………………………………………………………………..6
3.0
General Description……………………………………………………………………………...….6
3.1
Product Perspective………………………………………………………………………..6
3.2
Product Functions…………………………………………………………………………6
3.3
User Characteristics……………………………………………………………………….6
3.4
General Constraints…………………………………………………………………….…6
3.5
Assumptions……………………………………………………………………………....7
4.0
Requirements…………………………………………………………………………………….....7
4.1
Functional Requirements………………………………………………………………….7
4.1.1 Login by
customer……………………………………………………………….….7
4.1.2 Place order by
customer………………………………………………………….…7
4.1.2.1 Introduction
………………………………………………………………..……7
4.1.2.2 Input……………………………………………………………………….…….7
Software Requirements Specification (part 2)…………….………..by: Bradley Shedd page
4.1.2.3
Processing…………………………………………………………………….....8
4.1.2.4 Outputs…………………………………………………………………….….....8
4.1.3 Order confirmed and billing statement
(invoice) processed………………….….....8
4.1.3.1
Introduction………………………………….………………………………......8
4.1.3.2
Input………………………….……………………………………………….....8
4.1.3.3
Processing…………………………………………………………………….....8
4.1.3.4 Output……………………………………………………………………….......8
4.2
Interface
Requirements……………………………………………………………….......8
4.2.1 User
Interfaces……………………………………………………………………...8
4.2.1.1
The Home Screen…………………………………………………………….....8
4.2.1.2
Login Screen…………………………………………………………………....9
4.2.1.3
Create New Customer Screen………………………………………………......9
4.2.1.4 Catalog Main
Screen…………………………………………………………....9
4.2.1.4.1 First Category Product Screen……………………………………………….9
4.2.1.4.2 Second Category Product Screen………………………………………….....9
4.2.2 Hardware
Interfaces…………………………………………………………….......9
4.2.3 Software Interfaces……………………………………………………………….....9
4.2.4
Webpage Response Time…………………………………………………………...9
4.3
Performance
Requirements…………………………………………………………….....9
4.3.1
Number of
Employees………………………………………………………….......9
4.3.2 Number
of Customers…………………………………………………………….....10
4.3.3 Web page response
time………………………………………………………….....10
4.4
Design Constraints………………………………………………………………………...10
4.4.1
Standard Compliance……………………………………………………………......10
4.4.2
Hardware Constraints…………………………………………………………….....10
4.4.3
Software Constraints………………………………………………………………...10
4.5
Operational and other
Requirements………………………………………………….......10
4.5.1
Database…………………………………………………………………………......10
4.5.1.1
Database table
retention…………………………………….……………….......10
4.5.2
Security………………………………….……………………………………..........10
4.5.3 Audit
trail………………………………………………………….………………..10
4.5.4
Recovery………………………………………………………………………........10
4.5.5 Systems
Availability…………………………………………………………….......11
4.5.6
Performance……………………………………………………………………........11
4.5.7
Capacity…………………………………………………………………………......11
4.5.8
Reporting………………………………………………………………………........11
4.5.9
Portability……………………………………………………………………….......11
4.5.10
References……………………………………………………………………........11
The Veterinary Supply Store
Lab 1 Group 3
IT 4123
By: Erik Zimmer, Cedrick Watkins, Jeffrey Melara, Marlon Taylor and Bradley
Shedd
Date: May 29, 2011
Requirements for Veterinary Supply House
Our job is to design a website
that handles transactions between veterinary clinics and our product warehouse.
We will accept payment from these clinics, and take care of shipping and
processing through the web page. It will handle the full transaction circle from
order to delivery. We will be able to track shipments all the way to the
destination, and the customer will be given an easy to use interface to track
their own shipment so they know precisely when their supplies will get to them.
In order to achieve this goal, our web page will require several needs that will
have to be achieved to enable success.
First, there must be an
authentication system that identifies legitimate veterinary offices. Affiliates
that will be able to purchase from us will need to be identified as a legitimate
veterinary clinic, and must be registered with our site. In the registration,
the clinic must be able to provide shipping address, payment options and entry,
and other input so that we can efficiently receive payment and ship the product
all via the web.
There must be a navigation system
on the home page to direct the user to the supply sections, contact information,
and any other pages that we will need to conduct the website. There must also be
a precise navigation system so that the customers will be able to browse through
the available products. On the back end, there must be a database set up with
tables with corresponding products, price, and quantities for all the supplies
that we have in stock physically. The database must also have a table for
registered veterinary clinics with information like address, email, passwords
and payment information if they wish to save it. It is crucial that the website
has functionality such that customers can put items in a shopping cart, and the
total and list will be computed before they make payment.
They will be able to see all their
desired products together, and see a total price for their products. They will
then be able to accept, decline, or alter their order. Once the order has been
confirmed, processing will be handled, and a work order will be sent to the
directed individual in the warehouse. Shipping identifiers will then be issued
so the customer can track their package.
Our website will offer everything
needed to complete a transaction completely online. The tools and hardware
mentioned above, will allow a simple interface for the customers to order
products, and a system that will make the warehouse more streamlined and
efficient.
Preparation of an SRS Document
1.0 Revision
History
|
Version Number |
Date |
Author(s) |
Comments |
|
1.0 |
5/29/05 |
Marlon Taylor and Bradley Shedd |
Original |
2.0 Introduction.
Our group is creating a website for the Veterinary Supply
House. This is going to serve as an online purchasing system that uses a
database for businesses.
2.1 Purpose
of this document
This document comprehensively defines the software requirements for the
Veterinary Supply Center Database system and its functions. The expected
audience of this document will be the professor for both IT 4123 and IT 6763.
2.2 Scope
of this document
The Veterinary Supply Center Database is designed to facilitate the
purchasing transactions between the store and clients (clinics). These vendors
could either call-in or mail-in orders for supplies. Then, the company will
either send the requested supplies with payment-on-demand or charge/payment
billing. All data will be held on the system’s database and will be held
confidential.
2.3 Definitions,
Acronyms and Abbreviations
2.4 Business
Context
The Veterinary Supply Center Database Company’s main
mission is to provide high-quality products at the lowest prices possible.
The Mission Statement of the company is:
Our
mission is to provide high quality veterinary products to our clients, and to
assure them that our exceptional customer service and innovation is unparallel
to any other veterinary supply chain.
The goals of the organization are:
·
To provide the
best customer service to our clients guaranteed.
·
To offer high
quality products to each of our clients efficiently.
·
To meet and exceed
our client’s expectations.
·
To always have the
latest innovative products available to our clients.
2.5 Overview
The remaining part of this document follows the IEEE STD
830-1993 format. Section 3 will
cover the product perspective, functions, user characteristics, constraints and
assumptions. Section 4 will cover
the functional and non-functional requirements.
Section 5 will cover the operational requirements.
3.0
General Description
3.1 Product
Perspective
This system will be developed using Dreamweaver Web Design
Software and HTML.
3.2 Product
Functions
The product will provide easy access to Veterinary Supply
Center Database for consumers to order products. The major functions of this
system are:
3.3 User
characteristics
The VSCD will consist of a homepage plus a few selections.
The first selection will include a
comprehensive search for the supplies a customer wishes to order. The consumer
will then be prompted to choose from a variety of products. Then, he/she will
have the option to choose the product, brand name, and quantity of their order.
Finally, the consumer will be asked to verify and confirm their purchase.
The second selection involves
billing options. This feature enables the consumer to either express pay or
online billing. Express pay will allow the consumer to buy the product before it
is shipped to its final destination. Online billing allows the consumer to order
products and have them shipped along with an invoice attached.
3.4 General
Constraints
3.5 Assumptions
4.0 Requirements
4.1 Functional
Requirements
The user should be able to order
all products on-line through the designed web site; make a payment (billed);
receive an order confirmation and shipping date.
4.1.1
Login by customer
4.1.2
Place Order by customer
·
Customers will select their chosen products.
·
Customers will then be prompted to confirm final
selections.
·
Customers have the option to use Express Pay or
online billing via invoice.
4.1.2.1 Introduction
The system will be able to verify
the consumer’s order. After the ordering process is complete, a confirmation
page will appear onto the next screen giving vivid details about the products
ordered. Also, this page will show the availability of the product(s) ordered.
The consumer will then have the option to confirm, edit, or cancel the order.
4.1.2.2 Inputs
|
Product Name |
Qty |
Price |
# of item in stock |
Tracking # |
|
Head collars |
100 |
$5.99 each |
500 |
0000011121 |
|
Health Wise Pet food |
25 |
$10.99 each |
1,220 |
0000012111 |
|
Stethoscopes |
100 |
$14.89 each. |
1,000 |
0000011123 |
|
First Name |
|
|
Last Name |
|
|
Address |
|
|
City |
|
|
State |
|
|
Zip |
|
|
Phone Number |
|
4.1.2.3 Processing
Customers will be validated upon
entering the system. Orders will be
verified as to product number, availability.
Orders will be updated into the database.
An electronic bill will be generated for the customer real-time.
The customer will be provided different methods for payment including
credit card or on-line check. After
accepting payment, verification of payment will be sent to bank center for
processing. After receiving
confirmation, this will be transmitted to customer and date for shipping will be
calculated and displayed.
4.1.2.4 Outputs
The consumer is then sent an
invoice with details regarding the order plus the verification of payment. Also,
the invoice will include a verification of a shipping date.
4.1.3
Order confirmed and billing statement (invoice) processed
4.1.3.1 Introduction
A conformation email will be sent once an order is placed. Then another
email will be sent to the customer when the order is processed with a shipment
notification, routing number and estimated time of arrival to the address
described.
4.1.3.2 Inputs
The inputs the customer will need to provide is their address with an
order type and quantity. The order should be paid with a credit card number that
the user will input after their total sum is displayed on the screen. The
customer will also need to input their address the order is to be shipped to.
4.1.3.3 Processing
The processing will handle the
confirmation of the order with an eligible credit card number. Then the order is
sent to shipping that processes an estimate arrival time to the customer.
4.1.3.4 Outputs
The system will output two emails to the customer. An order confirmation
email, then a shipping email with routing number and time of arrival to the
destination. After purchase, there should be a printable version of an invoice
or receipt that displays on screen.
4.2
Interface Requirements
4.2.1
User Interfaces
4.2.1.1 The Home Screen
The home screen will give general
information about the company, catalog, help, login (existing customer), new
customer and contact information.
4.2.1.2. Login Screen
This screen will accept user login
identification, or it will reject it and send the user back to this screen. The
home screen will also give information about the company with tabs located at
the top. The titles of the tabs are: catalog, help, and login, sign up, and
contact information.
4.2.1.3 Create New Customer
Screen
This screen will allow a new
customer to create a login and password. The customer can also update their
address for orders to be shipped to.
4.2.1.4 Catalog Main Screen
This screen will list the main
categories for products. Some products include special diet and allergic free
dog food (Health Wise Pet Food), collars, leashes, bowls, stethoscopes, and flea
and tick shampoo.
4.2.1.4.1 First Category
Product Screen
This screen lists the products in
the first major category. The major category will be the pet food. The food will
have the largest selection branching from the category ‘Food’.
4.2.1.4.2 Second Category Product Screen
This screen will list products
like leashes, collars, accessories, etc. The screen will be available by a one
click of the mouse. There the accessories will be viewable and when the user
scrolls over them they change to other colors available.
4.2.2
Hardware Interfaces
The hardware will consist of a
hard drive space that houses all customer information. The hardware will be
efficient enough to provide the customer to buy supplies online using a virtual
shopping cart.
4.2.3
Software Interfaces
The system shall be compatible to
work on Internet Explorer, Mozilla Firefox or Netscape web browsers.
4.2.4
Communications Interfaces
The system needs to be able to
communicate with the bank for verification of funds or credit card information.
4.3
Performance Requirements
4.3.1
Number of employees
50
4.3.2
Number of customers
The host can handle up to 1,000
customers online at once.
4.3.3
Web page response time
The page will load in less than 3
seconds.
4.4
Design Constraints
4.4.1
Standard Compliance
The IEEE format is used for the
technical documentation specification in this document.
4.4.2
Hardware Constraints
The software system runs on
Windows XP and requires an internet connection that is open.
4.4.3
Software Constraints (limitations)
The system shall meet all
performance requirements running on the VB 6.0 application with Microsoft Access
database on the hardware specified in 4.4.2.
4.5
Operational and other Requirements
4.5.1
Database
The database platform will be
Microsoft Access 2007.
4.5.1.1 Database table
retention
The database tables will be kept
for five years.
4.5.2
Security
SSL coded encryption will be used to ensure the safety of the customers
address, credit card account numbers, and personal information. The customer
will be able to make purchases with various types of debit and/or credit cards.
These accounts will be kept securely in the database.
4.5.3
Audit Trail
All shipments and user accounts will be accessible in the online
database for review and audit. Everything purchased by customers will be
recorded in the database for tax purposes and credit fraud.
4.5.4
Recovery
The Veterinary Supply House system will be backed up by using an
online database. Everything sent out of the Veterinary Supply House will be
recorded at the headquarters onto a separate hard drive space.
4.5.5
System Availability
The system will be updated for top shelf performance. The Veterinary
Supply House has an onsite IT response team that updates the system every three
months.
4.5.6
Performance
When the system is updated and critiqued every three months, the
performance will be adjusted as needed during testing and reviewing. The
database will update the website to show the new products available for
purchase.
4.5.7 Capacity
The website will have the capacity as a regular IP web address would
hold.
4.5.8 Reporting
There will be weekly reports of the sales revenue posted every Friday
before noon. There is an automatic visitor counter at the bottom of the website
to record the total number of visitors.
4.5.9 Portability
At the moment there is an I Phone and Android application in the making.
Then the customer can shop on their smart phone.
4.5.10 References
Furnetic.com. Google. 28 May 2011. Web.
<http://furnetic.com/about/productlist.html>.
Reaves, Michael J. Google. 29 August 2003. Web. 29 May
2011. <mcis.jsu.edu/studio/SRSSample.doc>.