Online Shopping Mall Software Requirements Specification

Revision History Date Version Description Author

Table of Contents

1. Introduction 1.1 1.2 1.3 1.4 1.5 Scope Purpose of Document Project Overview Definitions, Acronyms and Abbreviations Technologies to be used

2. Functional Requirements 3. System Architecture

Software Requirements Specification

1. Introduction
1.1 Scope
The document is developed within the framework of the Shopping cart system project on the basis of standard pattern RUP and intended for use by participants and auditors of the given project.

1.2 Purpose
The Online Shopping Mall (OSM) web application is intended to provide complete solutions for vendors as well as customers through a single get way using the internet as the sole medium. It will enable vendors to setup online shops, customer to browse through the shop and purchase them online without having to visit the shop physically. The administration module will enable a system administrator to approve and reject requests for new shops and maintain various lists of shop category This document is meant to delineate the features of OSM, so as to serve as a guide to the developers on one hand and a software validation document for the prospective client on the other. 1.3 Project Overview System that is described by this document is a shopping cart that allows customers easily add shopping cart facility for own sites. Shopping cart system will be website that will be placed outside customer site and will allow add ability for sites visitors perform shopping without significant changes of customer sites. Site visitors (users) will be able select some products from customer site, then user will be redirected to order area inside Shopping cart system site and will be able refine order it includes ability modify products quantity, enter invoice/delivery details, use vouchers and enter payment info. Customer will be able visit system admin area and collect users orders. Customer will process orders and payments manually, for free account, or customer may upgrade account to premium type and use external payment processing systems. Also admin area will allow for customer set-up own account that means ability define rules for order price calculations (with shipping value, tax, discounts, vouchers); modifying look & feel (fonts, colours, buttons, ect) and localization (currency, messages, ect) for user order area; define participation in affiliate programmes. System also will include set of additional services like ability subscribe to mailing list, participate in message boards conversation, generate HTML code for site. Currently system doesnt include facility for online payments, but it is the subject for future system evolution.

1.4 Definitions, Acronyms and Abbreviations

SLA: Service Level Agreement or SLA is a formal written agreement made between two parties, the service provider & the service recipient. It defines the term of engagement - the fundamental rules that will govern the relationship. EJB: Enterprise Java Beans. JAVA EE: Java Enterprise Edition 5 is a programming platform part of the Java Platform-for developing and running distributed multi-tier architecture Java applications, based largely on modular software components running on an application server. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between a web browser & a Web Server.
HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).

TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.

1.5 Technologies to be used

Programming languages: JAVA EE: Java Enterprise Edition is a programming platform part of the Java Platform-for developing and running distributed multi-tier architecture Java applications, based largely on modular software components running on an application server. HTML, XML: Hyper Text Markup Language and Extensible markup Language are the predominant markup languages for web pages. It provides a means to describe the structure of text-based information in a document and to supplement that text with interactive forms, embedded images, and other objects. JavaScript: A client side scripting language used to create dynamic web content and user interface. Tools & Development Environment Apache Tomcat 6.0.18 Server: Apache Tomcat is a Servlet container developed by the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the JavaServer Pages (JSP) specifications from Sun Microsystems, and provides a "pure Java" HTTP web server environment for Java code to run. ECLIPSE J2EE: Eclipse is a toolkit which is designed for the creation of complex projects, providing fully dynamic web application utilizing EJBs. This consist of EJB tools , CMP ,data mapping tools & a universal test client that is designed to aid testing of EJBs.

2. Functional Requirements Initial functional requirements will be: Secure registration and profile management facilities for Customers Browsing through the e-Mall to see the items that are there in each category of products like Apparel, Kitchen accessories, Bath accessories, Food items etc. Adequate searching mechanisms for easy and quick access to particular products and services. Creating a Shopping cart so that customers can shop n no. of items and checkout finally with the entire shopping carts Regular updates to registered customers of the OSM about new arrivals. Uploading Most Purchased Items in each category of products in the Shop like Apparel, Kitchen accessories, Bath accessories, Food items etc. Strategic data and graphs for Administrators and Shop owners about the items that are popular in each category and age group. Maintaining database of regular customers of different needs. Shop employees are responsible for internal affairs like processing orders, assure home delivery, getting customer's delivery-time feedback, updating order's status and answering client's queries online. Feedback mechanism, so that customers can give feedback for the product or service which they have purchased. Also facility rating of individual products by relevant customers. Also feedback can be given on the performance of particular vendors and the entire mall as well. Adequate payment mechanism and gateway for all popular credit cards, cheques and other relevant payment options, as available from time to time.

For the previous paragraph, depicting the functions of the system, from the perspective of the various users of the system, the following colour codes has been used : RED for administrator BLUE for customer of the shopping mall GREEN for the employees. Initial non functional requirements will be: Secure access of confidential data (users details). SSL can be used. 24 X 7 availability Better component design to get better performance at peak time Advertisement space where it will effectively catch the customers attention and as a source of revenue. In addition to the above mentioned points, due to the highly evolving nature of the project, the following are planned to be delivered if deemed necessary: Warehousing within the very ambits of the project More payment gateways. Dynamic price model by which prices can be changed based on demand and supply Dynamic Storefront: Each customer will have a web page personalized based on his or her recent purchases. This is the equivalent of having a unique storefront for each customer in hopes of drawing in as many return customers as possible. This list is by no means, a final one. The final list will be dictated by implementation constraints, market forces and most importantly, by end user demands for whom this is being built. 3. System Architecture 4.