Online Shopping
Online Shopping
Online Shopping
{Surjyendu Ray}
4. Project deliverables:
Page: 2
{Surjyendu Ray}
A. Online or offline help to above said users, Application deployment executive and developer B. Application archive (.war/.ear) with source code C. Database backup and DDL Script The project deliverables will also include final versions of the following documents: Project Initiation Document Software Requirements Specification Document Project Reports Progress and Status Reports as and when required. User manual, etc.
5. Project constraints:
Hardware and software constraints to be discussed later.
{Surjyendu Ray}
24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension Advertisement space where it will effectively catch the customers attention and as a source of revenue. Initial reporting needs that are to be answered will be: o Category wise items that are sold more and the brand names for the same o Which brand is more popular in each category of products o Who are the customers who visit often( to facilitate them by making them Premier customers ) o Discounts given to the Premier customers The following user interface priorities will be considered since for this type of application the user and web interface will serve as one the major turning points: Professional look and feel Use of AJAX at least with all registration forms Use of Graphical tool to show strategic data to admin Reports exportable in .XLS, .PDF or any other desirable format
8. Log of risks:
To be discussed later.
{Surjyendu Ray}
1. About Online Shopping Mall( OSM) Users: The application identifies three types of usersMall Administrator, Shop Owner and Mall Customereach with different privileges. (This is only an initial tentative list) Mall Administrato r The Mall Administrator is the super user and has complete control over all the activities that can be performed. The application notifies the administrator of all shop creation requests, and the administrator can then approve or reject them. The administrator also manages the list of available product categories. The administrator can also view and delete entries in the guestbook. Any user can submit a shop creation request through the application. When the request is approved by the Mall Administrator, the requester is notified, and from there on is given the role of Shop Owner. The Shop Owner is responsible for setting up the shop and maintaining it. The job involves managing the subcategories of the items in the shop. Also, the shop owner can add or remove items from his shop. The Shop Owner can view different reports that give details of the sales and orders specific to his shop. The Shop Owner can also decide to close shop and remove it from the mall. A Mall Customer can browse through the shops and choose products to place in a virtual shopping cart. The shopping cart details can be viewed and items can be removed from the cart. To proceed with the purchase, the customer is prompted to login. Also, the customer can modify personal profile information (such as phone number and shipping address) stored by the application. The customer can also view the status of any previous orders, and cancel any order that has not been shipped yet. The basic use case diagram will be: -
Shop Owner
Mall Customer
Page: 5
{Surjyendu Ray}
Page: 6
{Surjyendu Ray}
A sample database schema of what the data required for the project will look like can be given as: -
10.
Project plan:
Page: 7
{Surjyendu Ray}
To be discussed later.
11.
We will be strictly following the New BSD License. We will also follow the spirit of Open Source throughout the design and implementation of the project wherever possible. The New BSD License can be obtained at http://www.opensource.org/licenses/bsd-license.php
Signatures:
Signature: Date:
Student
Project supervisor
Page: 8