1. Introduction
1.1 Purpose
This SRS describes the software functional and nonfunctional requirements for release 1.0 of the Online Purchase Application (OPA). This document is intended to be used by the members of the project team that will implement and verify the correct functioning of the system. Unless otherwise noted, all requirements specified here have high priority and committed for release 1.0.
1.2 Project Scope and Product Features
The OPA will permit Retailers and Warehouses (RW) to sell products directly from the Internet to consumers using a credit card transaction. A detailed project description is available in the OPA Vision and Scope Document [1]. The section in that document titled “Scope of Initial and Subsequent Releases” lists the features that are scheduled for full or partial implementation in this release.
1.3 References
1. Biskeborn, Mark. OPA Vision and Scope Document,
2. Biskeborn, Mark. Use Case Methodology Standard, Version 1.3,
3. Bachmann, Jon. OPA Business Rules Catalog
4. Bachmann, Jon. OPA Internet Application User Interface Standard, Version 2.0,
2. Overall Description
2.1 Product Perspective
The OPA is a new system that replaces the current manual and telephone processes for ordering and picking up products for small and medium sized products. The example provided in the prototype on our website (www.softwaresolutionsdesign.com), demonstrates the use of the OPA implemented to sell various categories of food to local restaurants. The context diagram in Figure 1 illustrates the external entities and system interfaces for release 1.0. The OPA is expected to evolve over several releases, ultimately connecting to the Internet ordering services for several local restaurants, suppliers, and to credit and debit card authorization services.
2.2 User Classes and Characteristics
|
Patron (favored) |
A typical Patron, targeted for this application, is a small to medium sized business buyer or a consumer, who wishes to order products online to be delivered within a given timeframe. There are thousands of potential Patrons, of which an estimated 400 for our current customers (buyers of OPA) are expected to use the OPA an average of 4 times per week each (source: current usage data). Patrons will sometimes order multiple identical products. An estimated 90 percent of orders will be placed using the Internet. All Patrons have Internet access from their offices. Some Patrons will wish to set up business accounts for discounted invoice billing, either to have the products delivered every day or, in the case of businesses like restaurants that order the same fresh products daily, to have the day’s sales special delivered automatically, depending on the type of business. In the latter case, a Patron must be able to override an order for a specific day. |
|
RW Staff |
The RW’s (Retailers or Warehouse managers at the OPA implementation site) employ order processing Staff, who receive orders from the OPA, prepare orders, package them for delivery, print delivery instructions, and request delivery. Some of the Staff, especially at new implementation sites, will need to be trained in the use of the computer, the Web browser, and the OPA. |
|
RW Manager |
The RW Manager is responsible for establishing and maintaining daily product offerings available from the OPA and, especially in the case of perishable products, the times of day that each item is available. Some products may not be available for immediate delivery. The Manager will also define the any special daily offerings. The Manager will need to edit the product information periodically to reflect changes in products, including pricing. |
|
Contracted or Staff Deliverer |
As the Staff prepares orders for delivery, they will print delivery instructions and issue delivery requests to the Deliverer, who is either another RW employee or a 3rd party contractor. The Deliverer will pick up the packaged products and delivery instructions for each order and deliver it to the Patron. The Deliverers’ primary interactions with the system will be to reprint the delivery instructions on occasion and to confirm that a package is delivered. |
2.3 Operating Environment
OE-1: The OPA shall operate with the following Web browsers: Microsoft Internet Explorer versions 5.0 and 6.0, Netscape Communicator version 4.7, and Netscape versions 6 and 7.
OE-2: The OPA shall operate on a server running the current corporate approved versions of Red Hat Linux and Apache WebServer or Microsoft IIS.
OE-3: The OPA shall permit user access from the corporate Internet and authorized for outside access through the corporate firewall, from an Internet connection at any location.
2.4 Design and Implementation Constraints
CO-1: The system’s
design, code, and maintenance documentation shall conform to the OPA Internet Development Standard, Version
1.3 [2].
CO-2: The system shall use Microsoft SQL database engine.
CO-3: All HTML code shall conform to the HTML 4.0 standard.
CO-4: All code shall be written in Microsoft .NET or in SQL Transcript.
2.5 User Documentation
UD-1: The OPA system shall provide an online hierarchical and cross-linked help system in HTML that describes and illustrates all system functions.
UD-2: The first time a new user accesses the system and on user demand thereafter, the system shall provide an online tutorial to allow users to view the process of ordering products and registering for an account, using a static (e.g. Macromedia Director) tutorial.
2.6 Assumptions and Dependencies
AS-1: The RW is open for normal local business hours every company business day in which employees are expected to be on site.
DE-1: The operation of the OPA depends on changes being made in the Inventory System or the Credit Card processes to accept payment requests for products ordered.
DE-2: The operation of the OPA depends on changes being made in the Inventory System to update the availability of products as well as product attributes, especially pricing, as orders are accepted.