Online Shopping Mall
Online Shopping Mall
Software Requirements Specification
Version 1.0
Team Name
Next Generation
Project Guide
Mr. Vinod Desai.
Team Members
Mr. Ahesan Ali Mukhi Mr. Bhavesh Pandav
Index & Tables
1) Introduction:...3
1.1.Purpose:………...3
1.2.Scope:………..3
1.3.Abbreviation:………..4
1.4.References:………..6
1.5.Technologies:………..6
2) Overall Description:………..7
2.1.Product Perspective………..7
2.2.Software Interface………...8
2.3.Hardware Interface………9
2.4.Communication Interface……….9
2.5.Product Function………..9
2.6.User Characteristics………10
2.7.Constrains………...10
2.8.Use-Case Modal Survey………..11
2.9.Sequence Diagram………..16
2.10. Class Diagram….……….19
2.11. Architecture Diagram……….……….20
Introduction:
1.1.
Purpose:
Online Shopping Mall is an online shopping site to manage the items in the shop and also help customerspurchase them online without having to visit the shop physically.
1.2.
Scope:
Creating different system user and assign different roles with related permissions user of the System.
A. Customers
B. Shop Employees
C. Administrators (Managers and Shop owners)
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.
Creating a Shopping cart so that customers can Shoppe ‘n’ no. of items and checkout finally with the entire shopping carts.
Customers should be able to mail the Shop about the items they would like to see in the Shop.
Updates to customers about the Recent Items in the Shop.
Uploading ‘Most Purchased’ Items in each category of products in the Shop like Apparel, Kitchen accessories, Bath accessories, Food items.
Strategic data and graphs for Administrators and Shop owners about the items that are popular in each category and age group.
Give special discounts to Premier customers.
1.3.
Abbreviation:
HTML: Hypertext Markup Language is a markup language used to design static web pages.
EJB: Enterprise Java Beans.
J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform—for developing and running distributed multitier architecture Java applications, based largely on modular software components running on an application server.
WSAD: Web sphere studio application developer is a toolkit which is designed for the creation of more complex projects, providing fully dynamic web application utilizing EJB’s. This consist of EJB tools , CMP ,data mapping tools & a universal test client that is designed to aid testing of EJB’s.
HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server.
HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).
1.4.
References:
IEEE SRS Format
Problem Definition (Provided by IBM)
Sample Synopsis (Provided by IBM)
CT Arrington. Enterprise Java with UML.OMG Press.
1.5.
Technologies:
J2EE: Application Architecture
DB2: Database
WSAD: Development Tool
WAS: Web Server
Rational Rose: Design Tool
UML: Unified Modeling Language for Object Oriented Modeling Techniques
XML:Extensible Markup Language
2. Overall Description:
Describe the general factors that affect the product and its requirements.
2.1.
Product Perspective:
The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used.
On the server side web server is for EJB and database server is for storing the information.
2.2.
Software Interface:
Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating System (any)
Web Server: WAS, Operating System (any)
Data Base Server: DB2, Operating System (any)
2.3.
Hardware Interface:Client Side
Processor RAM Disc Space Internet Explorer
512 MB 1GB (Excluding data size)
2.4.
Communication Interface:
Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.
2.5.
Product Function:
Maintain Profile Management for Customer: In this
module, information received from customer is maintained as Profile.
Maintain Category wise Item Details: In this module,
Maintain Shopping Cart Customer wise: In this module,
Shopping Cart has been maintained along with required Item Order by Customer.
Maintain Customer Order: In this module, Order has been
maintained along with credit card Details.
Maintain Customer Mail and Update Details: In this
module, maintained Information that which product customer would like to see in the shop. And also view the updated item in the shop from first page of customer logged in.
2.6.
User Characteristic:
Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.2.7.
Constraints:
GUI is only in English.
Login and password is used for identification of customer and there is no facility for guest.
This system is working for single server.
1. Administrator (Manager and Shop Owner): Responsible for managing system users, Discount Strategy View Mail and add new product in the shop.
Add New Shop Employee (Administrator and Owners):
Discount Strategy For Premier Customer: Administrators (Managers and Shop Owners) are responsible for define discount strategy item wise.
View Mail of Customer: Administrators (Managers and Shop Owners) are responsible for view mail of customer.
Add New Product into Shop: Administrators (Managers and Shop Owners) are responsible for add new product (Item) into shop.
and if sufficient balance is there in the account then shop employees allow order to be delivered.
Update Order Status: if balance is sufficient into account and order has to be delivered then shop employees change status to SELECTED other wise if balance is not sufficient then order is REJECTED and if balance is sufficient but order is not delivered then order status is PENDING.
Give Special Discount to Premier Customer: If Customer is daily purchased items from shop then shop owner has
privileges to define premier customer and shop employee provide special discount to those customer who are premier for shop.
3. Customer: Responsible for Sign up and use the order facility without reaching shopping mall physically and enjoy e shopping.
Edit Item From Cart: If Customer wants to Edit Item Qty Color or any other attribute which is possible but before place order ones order placed not a single value will change.
Remove Item From Cart: If customer wants to remove any Item from Cart than Customer has privilege to do this but before order place or order confirmed.
View All Product Update Categories wise: If Admin Update any Product into Shop or add any new Product into Shop that Update also can view by customers.
Place Order: After putting all the item into cart customer conformed their order once order confirmed not a single change is possible so be sure and then confirm order.
View Order: After putting order customer view the order but does not change any order.
* *
*
*
*
* *
*
1
1
1
1
1 1 1
1
*
2.11 Architecture Diagram:
Application Layer Data Layer
Customers Customer
2.11. Entity Relationship Diagram:
Structure Shop owner
2.12 Data Dictionary:
1. Customer Master
Fields Data Type Constraints
Cust ID String(E.g.C2008000001) Primary Key
Cust Prefix String Not Null
Cust Fname String Not Null
Cust Mname String Not Null
Cust Lname String Not Null
Cust Phone Long Allow Null
Cust Mobile Long Allow Null
Cust E-Mail ID String Not Null Cust Date Of birth Date Not Null Cust Status String(E.g. Enable/Disable) Not Null
Email ID String Foreign Key
Cust Gender String Not Null
2. Customer Address Master
Fields Data Type Constraints
Cust ID String(Eg.C2008000001) Foreign Key Primary Key Cust type String(Permanent/Billing) Primary Key
Cust Address String Not Null Cust Country String Not Null
Cust State String Not Null
Cust City String Not Null
Cust Pin code Long Not Null
3. Log in Master
Fields Data Type Constraints
Email ID String(Eg.trushen.doshi@gmail.com) Primary Key
Password String Not Null
User Cat ID String Foreign Key
5. Employee Personal Details
Fields Data type Constraints Emp ID String(e.g. E2008000001 ) Primary Key
Emp Prefix String Not Null
Emp Fname String Not Null
Emp Mname String Not Null
Emp Lname String Not Null
Emp Address String Not Null
Emp Country String Not Null
Emp State String Not Null
Emp City String Not Null
Emp Pin Code Long Not Null
Emp Phone No Long Allow Null
Emp Mobile Long Allow Null
Emp Date of Birth Date Not Null Emp Joining Date Date Not Null Emp Status String (e.g. Enable/Disable) Not Null User Cat ID String (E.G. CU,SE,Ad) Foreign Key
Emp Gender String Not Null
6. Order Master Details
Fields Data Type Constraints Order No String (e.g. O200800000001) Primary Key Order ID String (e.g. C2008000001) Foreign Key
Order Date Date Not Null
Order Tot Qty Long Not Null
Order Tot Amt Long Not Null
Order Status String(eg.Pending/Rejected/Complete ) Not Null
Payment Status String Not Null 7. Order Transaction Details
Fields Data Type Constraints Order No String(e.g. O200800000001) Primary Key
Item Code String(eg. Customer,ShopEmployee) Foreign Key
Item Qty Long Not Null
Unit Prize Long Not Null
8. Bill Master
Fields Data Type Constraints
Bill No String Primary Key
Order No String Foreign Key
Cust ID String Foreign Key
Fields Data Type Constraints Item Cat ID String (e.g. I200800000001) Primary Key
Item Name String (e.g. Apparel, Food Item) Not Null
Item Cat Status String (e.g. Enable/Disable) Not Null 10. Item Details
Fields Data Type Constraints
Item Code String Primary Key
Item Name String Not Null
Item Cat ID String Foreign Key
Item Image String Not Null
Item Price Long Not Null
Item Discount Long Not Null
Item Status String Not Null
Item Unit Long Not Null
2.13 Assumptions and Dependencies:
The details related to the Item, Customer, payment and order details provided manually.
Administrator is created in the system already.
Roles and tasks are predefined.
