Thursday, August 22, 2019

Sample website specification document Essay Example for Free

Sample website specification document Essay This project will involve creating an e-commerce web site for the purpose of selling electronic such as desktop, laptop, TV, DVD player, camera .etc. This system will provide a web interface for customer to create an account, make an order, check status and cancel an order. Database system will be used in customer and product management. The system will be developed on behalf of electronic retailer who currently operates as an online store only and limited delivery to nationwide. The efficient design of the site will allow the customer quickly order online and saving time if compare to order a product by regular mail. Furthermore, if the customer does not have an internet connection, he can order by phone and one of the customer representatives will be available to help him. It is fast and convenient. Products are to be shipped directly from the inventory to the address as the customer provide when he made an order, via UPS or FedEx. System must be informative, robust, responsive, user-friendly and secure. System should be designed to allow possible future expansion, for an example more product lines, and for potential porting to other retail businesses. The Specification Document I. Input/Output Specifications A. Input Specifications (Customer’s View) An on-line web site will be designed that allows the user to input the following information from any computer with internet access: Their customer profile information: (account registration) Customer name (string format, 40 characters max.) Street address (string format, 40 characters max.) City (string format, 15 characters max) State (string format, 2 alpha characters) Zip code (numeric format, 5 digits required) Area code (numeric format, 3 digits required) Telephone number (numeric format, 7 digits required) Email address (string format, 40 characters max) User name (string format, 5 characters min and 20 max.) Password (string format, 6 characters min and 20 max.) Payment information: (optional only) Type of credit card: Visa and MasterCard. Name on the card (string format, 40 characters max.) Credit card number (numeric format, 16 digits required) Expiration month (numeric format, 2 digits max) Expiration year (numeric format, 4 digits required) Shipping information: (when place an order) Ship-to name (string format, 40 characters max.) Street address (string format, 40 characters max.) City (string format, 15 characters max.) State (string format, 2 alpha characters.) Zip code (numeric format, 5 digits requires) Electronic style and quantities to be purchased: Brand and models will be viewed and selected from an online catalog. After a selection, the product will automatically add to the customer cart and the cart review page will be pop-up. Quantity field will be in the cart review page. It allows up to 10 of each model to be purchased. B. Output Specification (Customer’s View) The system will output information to the user’s screen, with the option to format selected information so that the user can direct it to a printer. Multiple web screens will be used, including: A main â€Å"logon† screen, so that the user’s customer profile can be created and/or recalled from the server. A catalog screen, where various electronic models can be browsed, and selected for ordering if desired. An order summary screen (shopping cart review) where the user can review the products they have chosen to purchase, and confirm that their order is complete. A payment information screen, where the user can input their payment method and billing information. A shipping information screen, where the user can choose a desired shipper, and view shipping costs for their order. An order summary screen, which the user can print for his/her records. Lists of products ordered and their status. A confirm page for cancel an order, if the customer decide to cancel. C. Input Specifications (Employee’s View, while customer order by phone) An internal web site will be designed that allows a customer representative to place an order, check status or cancel an order. He/she will input the following information: Place an order: Customer profile: Customer name (string format, 40 characters max.) Street address (string format, 40 characters max.) City (string format, 15 characters max) State (string format, 2 alpha characters) Zip code (numeric format, 5 digits required) Area code (numeric format, 3 digits required) Telephone number (numeric format, 7 digits required) Email address (string format, 40 characters max) Shipping information: Ship-to name (string format, 40 characters max.) Street address (string format, 40 characters max.) City (string format, 15 characters max.) State (string format, 2 alpha characters.) Zip code (numeric format, 5 digits requires) Payment information: (credit card only) Type of credit card: Visa and MasterCard. Name on the card (string format, 40 characters max.) Credit card number (numeric format, 16 digits required) Expiration month (numeric format, 2 digits max) Expiration year (numeric format, 4 digits required) Check status: (one of the following required) Customer name (string format, 40 characters max) Order number (numeric format, 20 digits max) Cancel an order: Customer name (string format, 40 characters max) Order number (numeric format, 20 digits max) D. Input Specifications (Warehouse Operator’s View) An internal web site will be designed that allows an employee working in the warehouse to select orders to be shipped. He/she will input the following information: Enter their Employee’s ID and password. Select orders to be pulled for shipment. Send packing slips to a local printer. Input order numbers that have been shipped. Input shipment information (carrier name, etc.) Update quantity available in warehouse E. Output Specification (Warehouse Operator’s View) The system will output information to the warehouse operator’s screen or to his or her local printer. Multiple web screens will be used, including: A screen showing a list of pending orders (orders for which there is sufficient quantity in the warehouse of all selected products). A screen that allows the selection and printing of formatted pages of order information suitable for warehouse picking activity. These â€Å"packing lists† would include warehouse location information for each product to be pulled for a given order. F. Exception Handling Example exception situations that the program is anticipated to encounters are: User logon and/or password are incorrect. User name must between 5 and 20 characters, include letters and/or digits, but no special punctuation marks. Password must be between 6 and 20 characters, include letters and/or digits, but no special punctuation marks. User profile information is incorrect or incomplete. User must enter first and last name At least one line of street address information must be given. A valid Zip code must be given, which will be used to determine the city and states. Products may be out of stock, back-ordered, or no longer available Notify user of stock availability issues, and confirm if back-ordered are requested. Products quantities ordered may be out of range Product quantity will be limited to 10 of any model. Payment information may be incorrect or incomplete User must select from pre-determined payment methods, and enter correct credit card information if required. II. Performance Specifications Operating environment: system will be PHP, mySQL and HTML-based, meaning it will be able to run in any mainstream web browser available to the home computer user. The client PC will not need any special software to support this application. Response time: Response time from any given screen to another screen should be limited to a maximum of 10 seconds, except in cases where response time is affected by activities out of the control of the program (such as slow response from external sources). Memory requirements: any user system that is capable of supporting a web browser will be able to access the system. III. Delivery Schedule Proposal:January 28, 2005 Planning:February 08, 2005 Design:March 01, 2005 Coding:March 22, 2005 Final Product Delivery with Documentation:April 26, 2005

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.