SRS Online Shopping Mall

  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 Mr. Husen Mahammad Momin Mr. Trushen Doshi

  

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

  2.12. Entity Relationship Diagram……………………..21

  2.13. Data Dictionary………………………..……………….22 2.14.

  Assumptions and Dependencies……………….23

  Introduction:

  

1.1. Purpose: Online Shopping Mall is an online shopping site

  to manage the items in the shop and also help customers purchase 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.
• Secured mechanism for checking out from the Shop (Credit card verification mechanism).

• 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.
• DB2: DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications.
• WAS: Web sphere application server is an application server that runs business applications and supports the J2EE and web services standards.

• 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. 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.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  AJAX: Asynchronous JavaScript and XML 

2. Overall Description: Describe the general factors that affect the product and its requirements.

2.1. Product Perspective:

• The web pages (XHTML/JSP) are present to provide the user interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS protocols.
• 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) Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML), DB2, OS (Windows), Web Server.

  Hardware Interface: 2.3.

  Client Side Processor RAM Disc Space Internet Explorer Pentium II at

64 MB

  1 GB 6.0 500

  MHz Server Side

  Web sphere Pentium III at 1 GHz 512

  2 GB application server

  MB

  V5.0 DB2 V8.1 Pentium III at 1 512 MB

  1GB (Excluding GHz 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,

• information related to Category like Apparel, Kitchen accessories, Bath accessories, and Food items and related category Item Information maintained.

  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.
• There is no maintainability of back up so availability will get affected.

  2.8. Use Case Modal Survey:

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):

  Administrators (Managers and Shop Owners) are responsible for Add New Shop Employee in the Website.

• 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.

2. Shop Employee: Responsible for View Order Update Order

• View Order: Shop Employees are responsible for view order of customer and verify credit card system automatically called

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 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.

• Add Item to Cart: Customers ones Sign Up in to E-Mall then customers Pick cart and add Particular Item into Cart.
• View All Item From Cart: 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.

• 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. 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.
• Mail Product Details to Admin: If Customer wants some product into shop then customer can mail list of product to admin.

2.9 Sequence Diagram:

2.10 Class Diagram:

  1

  1

  1

  1

  1

  1

  1

  1

2.11 Architecture Diagram:

  Admin Shop Emp Log In Orders

  Item Cat-Item Bill Admin/Shop Emp

  Log - In Order Item Category-Item

  Bill Admin/Shop Emp_UI Log In_UI Order_UI

  Item_UI Category Item_UI Bill_UI Business Layer Application Layer

  Data Layer Customers Customer Customer_UI

2.11. Entity Relationship Diagram:

  M ¹ _{1 has} Bill Customer _{has 1 1 1 has M has} Order _{1 has} ¹ _{1 M} Payment _allow Suggestion _{M has} new Item _{M M Category M has 1 1 M 1 handle has 1} Item _{M M has 1} Discount _{Define has 1 Delivery} Manager Structure _{1 M 1 handle M 1 1 M 1 has} Employee _{M has} Item Rate _{M Define 1 has} Structure

  Shop owner ₁ Department

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

  Master

  2. Customer Address

  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 Master

  3. Log in

  Fields Data Type Constraints Email ID String(Eg.trushen.doshi@gmail.com) Primary Key Password String Not Null User Cat ID String Foreign Key

  4. User Category Master

  Fields Data Type Constraints User Cat ID String(E.G. CU, SE, Ad) Primary Key User Cat Name String(E.g. Customer, Shop Employee) Not Null User Cat Status String(E.g. Enable/Disable) Not Null

  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

9. Item Category Master

  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