Shopping cart Acceptance plan
Version: 1.1 Date: 29 Jan 2002
Shopping cart Acceptance plan
Version 1.1
Revision History
Date 29 Jan 2002 2 Feb 2002 Version 1.0 1.1 First draft Customer requirement take into account: Plan items added Description Author Sapozhnikov Andrey Sapozhnikov Andrey
Public
EleWise ltd, 2002
Page 1
Shopping cart Acceptance plan
Version: 1.1 Date: 29 Jan 2002
Table of Contents
1. Introduction 1.1 Scope 1.2 Overview Responsibilities Product Acceptance Criteria 3.1 Customer related functions 3.2 Customer with premium account related functions 3.3 User related functions 3.4 System administrator related functions 3.5 Non-functional criteria Product Acceptance procedure 3 3 3 3 3 3 4 5 5 5 6
2. 3.
4.
Public
EleWise ltd, 2002
Page 2
Shopping cart Acceptance plan
Version: 1.1 Date: 29 Jan 2002
Software Requirements Specification
1. Introduction
This document is the Product Acceptance Plan (referred to hereinafter as PAP) for Shopping cart service providing, performed with reference to mutual understandings between EleWise ltd. and Customer. This plan provides clear and detailed information regarding expected timeframes, fulfilling the requirements set forth between us originally. 1.1 Scope This Product Acceptance Plan focuses on full version of Shopping cart service providing. 1.2 Overview The primary objective of the acceptance plan is to accept criteria stated in 3.Product Acceptance Criteria..
2. 3.
Responsibilities Product Acceptance Criteria
Acceptance Criteria System must allow for customer select name and password (or say that name already used), and then ask personal details. System must accept correct login name and password and show main user interface. System must allow review customer detail, entered in registration and edit it. If customer changes fonts size and color, background, logotype, system messages, timezone, time/date format, currency into cart setup, these changes must be appropriative reflected into user cart page. Customer must have ability to define rules for next total order value components: discounts with value calculated as percentage or as fixed value per order or item, applied to all orders or orders over some value or items quantity; shipping value calculation, in depends of delivery zone, items weight and quantity; tax calculation, in depends of shipping zone and tax basis; vouchers with discount as fixed value or percentage or free shipping. Result of this rules execution must be reflected as appropriative total order value, in depends of products set and count in order and delivery zone. System must list user orders with main order information (date, user first- and last name, payment method, product name, quantity and price, order status), allow select one of order and review all order details, entered by user, allow delete order from list and select new order status. System must allow change order status from one state only to available subsets of states as show in diagram into SRS 3.1.1.5 item. Page 3
3.1 Customer related functions Function Register Customer should be able register into system. Customer must enter here personal details and select login name and password that will be later user for login into admin area. View/edit personal details Customer should be able change personal details entered in registration form. Manage cart presentation Customer should be able customize appearance of user order area. Presentation customization include look & feel customization and locale customizations. Manage order price calculation Customer should be able define set of rules for order price calculation. This rules cover discounts, vouchers discounts, tax, shipping value.
Manage orders Customer may review submitted orders (as list with main order details or review individual order detailed), delete all or selected orders, or change order status.
Public
EleWise ltd, 2002
Shopping cart Acceptance plan
Version: 1.1 Date: 29 Jan 2002
Participate in communication Customer should be able subscribe/unsubscribe to mailing list and write/read messages on message board where discussed service related issues.
Manage notification Customer should be able setup mail notification - new order submission may be notified both to customer and user.
Generate HTML code for site Customer may use helper application for generating HTML code by customer id, product name and price, ect that may be inserted into customer site and displayed as button or link that point to user order area. Product name and description structure should allow customer organize families of product, where one product item may have several modifications, such as color, size, version or another variable attribute. Define required order fields Customer may define set of order fields that user must fill before order will be submitted. Upgrade to premium account Customer with free standard account should be able at any time upgrade his account to Premium type.
Manage payment options Customer should be able select one or several payment options and configure it.
Customer must have ability turn on and off ability receive messages from mailing list. If subscription is turned on, customer must receive mailing list messages to mail address pointed into personal details. Customer must have ability view messages list in message board (subject, date, author), select message and review message body, reply to any message and create new messages. New messages should be show in messages list. Customer must have ability turn on or off new order notifications, create/edit notification message body template separately for user and for self-notifications. If notification is turned on, system must send notification to user and customer about new order to email address pointed into customer personal details and users order detail. Customer must have ability open page where he will be asked for product details (description, price, quantity), presentation details (show as link, as button, as image button; text on link or button, link to image), turn on or off necessarily collect product list page visit statistics. System must generate HTML code that can be inserted into customer product list page. This code must be displayed in appropriative way (as link or button) and user, by clicking here, must be redirected to order page into system site, and this order must have appropriative product. Customer must have ability mark subset of order fields as required. In this case user must not have ability submit order while this fields is empty. Customer must have ability select special link and he will be asked for credit card info and, if this info has the correct format, customer immediately must have ability use premium options and notified by e-mail address from personal details that his account type was changed. Customer must have ability select one or more payment method as available payment method for submitted orders, and setup this method, or create custom payment method. User must have ability use only method marked by customer as available. Configuration for concrete payment method must be reflected in order payment page behavior – for example if customer define list of acceptable credit cards, then user must have ability use only this credit cards.
3.2 Customer with premium account related functions Use payment gateway Customer with Premium account has ability perform online payment processing with help of one of existing payment processing system. Use premium options Customers with Premium account also able use some Customer with premium account must have ability select payment gateway from list or setup own. If user selects payment by credit card, this card must be charged with help of selected payment processing system. Customer with premium account must have ability mark all orders (or some orders subset), select format (CSV.
Public
EleWise ltd, 2002
Page 4
Shopping cart Acceptance plan
Version: 1.1 Date: 29 Jan 2002
additional futures of system: download orders in the convenient format, upload/manage product list, view statistics.
HTML) and download selected orders information into this format. Customer with premium account must have ability upload file with product information, where should be listed product attributes, and then use just product ID (instead of full attributes set) to define product in HTML wizard. System must allow delete product info from this list and edit it. Customer with premium account must have ability look at visits statistic for order page and for product list (if customer had decision insert counter into HTML code). Statistics must show visits count, ordered product count, orders value, with ability to split stats values by date/time/product and ability review correlation between order statistics and product list statistics.
3.3 User related functions Add product to order At the product list into customer site use may press link or button near to product to open order page. Edit order Here user may edit products quantity and use vouchers codes. Then user may return and continue shopping, or complete order: enter invoice/delivery details and then select one of available payment method (credit card, check, cache on delivery, ect) and then enter info for this method. 3.4 System administrator related functions Manage customers Administrator should be able review list of customers and main customer's details. For customers with premium accounts it should be possible review credit card info and view/change account payment state - last card charging date, next charging date. Send messages to users in mailing list Administrator can send messages to mailing list. System must allow for administrator review list of customers, find customer by name, review personal details of selected customer, and show account type; for customer with premium account – view credit card info, set last/next charging data. System should allow for administrator change customer type, or delete customer from customer list. Administrator has ability compose and send message to all customers who was subscribed to mailing list. System must deliver this message to all subscribed customers to address pointed in personal details. This action must open order page on Shopping cart system site where user may review product list with product quantity and prices (for each products and with shipping, tax and discount). User must have ability edit product quantity, enter vouchers codes. User may temporary leave order page and continue shopping later. Then system must allow complete order submission, add this order to customers orders list and (if selected credit card processing) process payment.
3.5 Non-functional criteria User interface Response time, help. System must process request in reasonable time (no more 2-3 seconds for main operations like order editing/submission, cart setup, orders review and no more 6-10 seconds for rare operations like operations in admin area). EleWise ltd, 2002
Public
Page 5
Shopping cart Acceptance plan
Version: 1.1 Date: 29 Jan 2002
Security Personal data storing
Distributive package Ability install application and another server
System must contain online help in form of comments for most sophisticated system area. System must have simple and intuitive-understandable user interface everywhere it possible. System must store credit card info and passwords in crypt and hashed form. For third-party person it should not be possible view this information even this person has physical access to storage devices. Release must be packaged in distributive that doesn’t require third-party components and libraries (except java virtual machine, servlet/JSP engine and database) for installation and has installation instruction that allow for technical person install this system.
System Release is a fully functional application. It has passed final testing stage. It is an end product ready for deployment.
4.
Product Acceptance procedure
4.1 Customer will declare acceptance in writing if the acceptance procedure was successfully carried out and all specifications and requirements according to 3.Product Acceptance Criteria have been complied with. Otherwise, Customer will refuse acceptance in a written defects report. Such a report pursuant to this Sub-section shall be hereinafter: “Defect Report”. 4.2 If acceptance of the Product results is refused by Customer in Defects Report, Customer shall assess within five (5) days whether a defect attributable to EleWise exists. EleWise shall remedy any detected defects without undue delay. Customer will provide EleWise with the necessary time and opportunity for such remedying of defects. If remedy of defects is not possible, or is not reasonable in view of the low impact of the defect, EleWise undertakes to provide for intermediary solutions in order to by-pass the defect. The acceptance procedure is repeated after remedying of the defects specified in Defects Report.
Public
EleWise ltd, 2002
Page 6