Online Sale System
June 1, 2016 | Author: Ankit Patel | Category: N/A
Short Description
Download Online Sale System...
Description
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
INDEX 1. INRODUCTION…………………………………………………………………………………………………..3 1.1 PURPOSE………………………………………………………………………………………………………..3 1.2PROJECT SCOPE…………………………………………………………………………………………….… 3 1.3FEASIBILITY STUDY……………………………………………………………………………………….…3 1.4 OBJECTIVE………………………………………………………………………………………………..……4
2. MODULES………………………………………………………………………………………………..………5 2.1PRODUCTION MODULE……………………………………………………………………………..……….5 2.2 REGISTRATION MODULE…………………………………………………………………………………..6 2.3 SALES MODULE………………………………………………………………….…………………………..7
3. OPERATING ENVIRONMENT………………………………………………………………………………….8 3.1 HARDWARE REQUIREMENT……………………………………………………………………………….8 3.2SOFTWARE REQUIREMENT…………………………………………………………………………………8
4. CONSTRAINS…………………………………………………………………………………………………….9 4.1 REGULATORY POLICIES…………………………………………………………………..………………..9 4.2 HARDWARE LIMITATIONS…………………………………………………………………………………9 4.3 INTERFACES TO OTHER APPS……………………………………………………………………………..9 4.4 PARALLEL OPERATIONS……………………………………………………………….…………………..9 4.5 HIGHER ORDER LANGUAGE REQUIREMENT…………………………………………………………...9 4.6 REALIABILITY REQUIREMENT…………………………………………………………………………..10 4.7CRITICALITY OF THE APPS………………………………………………………………………………..10 4.8 SAFETY AND SECURITY CONSIDERATION……………………………………………….……………10
5. DFD………………………………………………………………………..……………………………………..10 5.1 CONTEXT LEVEL DFD……………………………………………………………………………………..11 5.2 0-LEVEL DFD………………………………………………………………………….…………………….12 5.3 1-LEVEL DFD………………………………………………………………………………………………..13 5.4 2-LEVEL DFD………………………………………………………………………………………………..16
6 DIAGRAMS………………………………………………………………………………………...……………18 6.1 USE CASE DIAGRAM……………………………………………………………………………………….18 6.1.1 USE CASE FOR VISITOR………………………………………………………….………….19 6.1.2 USE CASE FOR ADMIN…………………………………………………..…………………..20 6.1.3 USE CASE FOR CUSTOMER…………………………………………….……………………21 6.2 CLASS DIAGRAM……………………………………………………………………….…………………..22 6.3 STATE DIAGRAM…………………………………………………………………...………………………23 6.3.1 STATE DIAGRAM FOR LOGIN STATE……………………………………………………..23
GEC, MODASA
Page 1
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.3.2 STATE DIAGRAM FOR REGESTRATION STATE…………………………..……………24 6.3.3 STATE DIAGRAM FOR USER PROCESS STATE…………………………...…………….25 6.4 SEQUENCE DIAGRAM……………………………………………………………………..……………..26 6.4.1 SEQUENCE DIAGRAM FOR REGISTER A USER…………………….…………………..26 6.4.2 SEQUENCE DIAGRAM FOR LOGIN CUSTOMER……………………….……………….27 6.4.3 SEQUENCE DIAGRAM FOR SUBMIT A CART……………………………………..……28 6.4.4 SEQUENCE DIAGRAM FOR ADD PRODUCT……………………………………………29 6.5 E-R DIAGRAM……………………………………………………………………………………………..30 6.5.1 ER DIAGRAM……………………………………………………………………..…………31
GEC, MODASA
Page 2
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
1. INTRODUCTION Today in age of computer communication, it has become easy to to perform sale online, it is time + cost effective, so we came across idea of having Online Sale System. Online sale will make it easy to acknowledge loved one across globe. We have strived hard to make it consumer friendly , so they can interact hassle free.
1.1 PURPOSE The purpose of this document is to present a detailed description of the Web Publishing System. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the stakeholders and the developers of the system and will be proposed to the Regional Historical Society for its approval.
1.2 PROJECT SCOPE 1. This is an Online System so, we can handle it any where and any time 2. As we are making the generalized system, so this system can be used for handling any of the Customers of the particular Company. 3. This System will help bridge between Customer and Company. 4. File Formats: Customers are sending their inquiry and other information in formats like Word or they can fill up all their information in form available on website. 5. Security: Site is accessible via internet, Customers needs their login to purchase a product. 6. Search: Search feature is provided to view all information of every product by according to their requirements of customer. 7. Accessibility: Site is accessible using all the standard web browsers via internet. 8. Availability: Available 24 hours online, all the Customers are access this website anytime. 9. News: Contains a news section, where current product information is available. 10. Links: Site contains links to sites of sage pay company and useful sites.
1.3 FEASIIBILITY STUDY Feasibility is the determination of whether or not a project is worth doing. The process followed in making this determination is called a feasibility study. In the conduct of the feasibility study, many types of feasibility study are used. Amongst those, we have confined ourselves in the following types:
GEC, MODASA
Page 3
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
1.3.1 Time Feasibility Online sales system will give the opportunities for getting the detail of the all product with their properties to the customer. 1.3.2 Operational Feasibility We studied and analyzed the recruitment process of different organizations and makes a decision for our projects 1.3.3 Technical feasibility This is concerned with specifying equipment and software that will successfully satisfy the user requirement. It includes:
The facility to produce outputs in a given time. Ability to process a certain volume of transaction at a particular speed. Facility to communicate data to distant location.
1.3.4 Economic Feasibility Economic feasibility has been done in advanced for estimating the cost of the proposed system. The cost of hardware and software for the class of application being considered the cost if nothing changes.
1.4 OBJECTIVE To develop a website that allows user to buy gift articles online. 1.4.1 What Website can do?
i.
Allow Site Visitor to give some Suggestion or Feedback to Admin.
ii.
Site Visitor can purchase Products using cash on delivery.
iii.
Allow Site Visitor to give some Suggestion or Feedback to Admin.
iv.
Allow Site Visitor to do custom Search for Products.
v.
Providing review to product.
vi.
Getting News related to Products by subscribing newsletter.
1.4.2. What Website cannot do? i. ii. iii.
GEC, MODASA
User can not customize product according to his/her requirement. No other payment method is provided except cash on delivery. Comparing features of two products etc…
Page 4
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
2. MODULES On line sales system contain main three modules with detail description of product, customer registration and selling of product with great feasibility. Main three modules are I. II. III.
Production Registration Sales
Production module contain the information about the product category and sub module product category can divide into two parts Collect product informationAdd and update products. Registration responsible for the registration information of the customer and it can sub module into three parts: Collect User Information Verify Username & Password Login. Sales module contains the main four processes: Place Order Receive Product Check Product Price.
ON LINE SALES SYSTEM
PRODUCTION
REGISTRATION
SALES
2.1 Production Module: Production module content the relationship with the administrator and it is maintained by administrator. For example if any product is not in stock then the quantity of the specific product can be maintained by the admin. Change in the price of the product can also changeable by the admin with the feasible path,
GEC, MODASA
Page 5
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
Key feature:
Admin can check the product and get the product information through the product master database. Maintain product category is sub module of the production which is collect product information and add and update the product. Collect product information is responsible to delivery of check product report when admin apply for the detail. Collect product information give the product report to the admin with reference of the product master database. Add and update sub module update the stock of product into the database and then collect the product information.
PRODUCTION
MAINTAIN PRODUCT CATEGORY
COLLECT PRODUCT INFORMATION
ADD & UPDATES PRODUCT
2.2 Registration Module: Production module content the relationship with the administrator and it is maintained by administrator. For example if any product is not in stock then the quantity of the specific product can be maintained by the admin. Change in the price of the product can also changeable by the admin with the feasible path, Key feature:
Admin can check the product and get the product information through the product master database. Maintain product category is sub module of the production which is collect product information and add and update the product. Collect product information is responsible to delivery of check product report when admin apply for the detail. Collect product information give the product report to the admin with reference of the product master database.
GEC, MODASA
Page 6
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
Add and update sub module update the stock of product into the database and then collect the product information.
PRODUCTION
MAINTAIN PRODUCT CATEGORY
COLLECT PRODUCT INFORMATION
ADD & UPDATES PRODUCT
2.3 Sale Module: Sales module content the relationship with the administrator and customer and it is maintained by the administrator. For example if any product is not in stock then the quantity of the specific product can be maintained by the admin. Change in the price of the product can also changeable by the admin with the feasible path. Customers who want to purchase the product must have to place order and then it is verified with reference to the product master database. If the suitable stock is available then process get proceed otherwise it display the incomplete purchase message. Key feature:
Customer can collect the product information and then place the order as it requirement When customer place the order , it is received by admin and then it is checked with the various parameter such as a onetime purchase limit, stock of the product ordered by the customer, order date and delivery date etc. After verification of the product, customer get the detail of the quantity and price of product then customer sends order and it is received by the admin. Customer pay the bill with the check and then it will get the delivery within seven day. The detail of sales module is given below in graphical format.
GEC, MODASA
Page 7
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
3. OPERATING ENVIROMENT 3.1 HARDWARE REQUIREMENTS:
Pentium iv processor
Intel 810GL motherboard
1 GB SDRAM
80 GB HDD
52x CD Drive
Keyboard
Mouse
15th SVGA Colour monitor
3.2 SOFTWARE REQUIREMENTS:
For Development Purpose I used following software specification
Operating System :Windows 7 Ultimate
Development Tool: Dream weaver, notepad
Web Server :Apache server
GEC, MODASA
Page 8
SRS
ONLINE SALE SYSTEM
Database: MySQL 1.3.2.27
Internet Explorer :IE 8,Firefox 3.0+, Chorme, Opera
Documentation: Microsoft Office
EN. No-080160116035
4. CONSTRAINS There are some constraints to use this web application i. ii.
As the java script is used the web browser should be JavaScript enabled. Also the internet facility should be in order to get the correct and accurate results as Expected.
4.1 Regulatory Policies To buy any Product user must create account. The user account can be generated only after sign up process. User must have credit card or PayPal account to buy Product from Product store.
4.2
Hardware Limitations The user of the system is free to use any modules, which satisfies above minimum software requirements. The system requires: RAM cannot be less than 512 MB but ideal would be 1 GB and the processor cannot be less than Pentium 4.
4.3
Interfaces to Other Applications The System must have the Internet Explorer or Fire Fox or any other web browser though which each user can interact with the system. It specifies: i.
The website is made in PHP and it run on the Web Browser.
ii. The System will interact with the user through GUI. So, User can easily operate with the System.
4.4
Parallel Operations It won’t create any problem.
4.5
Higher Order Language Requirements This website needs PHP as a higher order language and some use of Jquery to make website more attractive.
GEC, MODASA
Page 9
SRS
ONLINE SALE SYSTEM
4.6
EN. No-080160116035
Reliability Requirements The system should be reliable enough that no other user should be able to login as other customer by using other customer’s username & password else same named user can login from 2 or more systems. The system should be reliable enough to get the back up of data if at all the data crashes due to catastrophic event or some other event.
4.7
Criticality of the Application If any problem will occur during any Operation of modules entire transaction will be cancelled and it will be rolled back.
4.8
Safety and Security Consideration The system uses PHP functions to make website more secure and safe.
5. DATA FLOW DIAGRAM The DFD is a simple graphical formalism that can be used to represent a system in terms of the input data to the system, various processing carried out on these data, and the output data generated by the system. The DFD model uses a very limited number of primitive symbols to represent the functions performed by a system and the data flow among these functions. Starting with a set of high-level functions that a system performs, a DFD model hierarchically represents various sub-functions.
Table 5.1 Notations of DFD Notation Description External The external entities are essentially those physical entities Entity external to the software system which interact with the system by inputting data to the system or by consuming the data produced by the system. Process
Symbol
Process or function performed when it is initiated by external entity or by other means.
GEC, MODASA
Page 10
SRS
ONLINE SALE SYSTEM
Data Flow
A data flow represents the data flow occurring between two processes, or between an external entity and a process, in the direction of the data flow arrow.
Output
It is used when a hard copy is produced and the user of the copies cannot be clearly specified or there are several uses of the output.
Data Store
A data store represents a logical file. A logical file can represent either a data store symbol which can represent either a data structure or a physical file on disk.
EN. No-080160116035
5.1 Context level DFD
GEC, MODASA
Page 11
SRS
ONLINE SALE SYSTEM
Login
ADMIN Check User Info & Riceive Order
Online sales
EN. No-080160116035
Check Place Order
Customer Payment
5.2 0-level DFD
GEC, MODASA
Page 12
SRS
ONLINE SALE SYSTEM
Check Product Detail
Product Info
ADMIN
EN. No-080160116035
Production 1.0
PRODUCT _MST
User Registration Create registration Admin Login
Registration 2.0 Check Cust_Detail
REGI_MAST CUSTOMER_ MST
Registered User Login
COSTOMER
check order-master Send order
Sales 3.0
Send order ORDER_ MST Place order
Receive Product & Payment
5.3 1-level DFD
FIRST LEVEL DFD FOR PRODUCTION
GEC, MODASA
Page 13
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
Check Products
ADMIN
Production 1.1
Product_Mstr Product Info
Collect Product Info
Maintain Product Category Collect Product Info
Maintain Product Category 1.2
Update Stock Collect Product Info
FIRST LEVEL DFD FOR REGISTRATION
GEC, MODASA
Page 14
SRS
ONLINE SALE SYSTEM
Customer
EN. No-080160116035
Registration
Registration
Choose Username & Password
Registration Table
1.2.1
Verification Username & Password
Access Username & Password
Verify Username &Password 1.2.2
Verification Process
Verified User Login
Login 1.2.3
Access Data
Cost_Mst
FIRST LEVEL DFD FOR SALES
GEC, MODASA
Page 15
SRS
ONLINE SALE SYSTEM
Check Products
ADMIN
Place Order 1.1
Collect Product Info
EN. No-080160116035
COSTOMER
Send Order Collect Product Info
Receive Order 1.2 Check Product Damaged
Check Product 1.2 Receive Product Send Order
Receive Order
Price 1.2
Payment
Costumer_Mstr
5.4 2-level DFD
SECOND LEVEL DFD FOR MAINTAIN CATAGORY
GEC, MODASA
Page 16
SRS
ONLINE SALE SYSTEM
Check Products
ADMIN Collect Product Info
Maintain Product Category Collect Product Info
Collect Product Info 2.1
Add & Update Products 2.2
EN. No-080160116035
Product_Mstr Product Info
Update Stock Collect Product Info
Fig. 5.1 0-level DFD
GEC, MODASA
Page 17
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6. DIAGRAMS
6.1. USE CASE DIAGRAM To introduce use case diagrams
Actors Use cases Dependency relationships between use cases
An actor is anyone or anything that must interact with the system. Actors are NOT part of the system In the UML, an actor is represented as a stickman.
A use case must deliver something of value to an actor. The collection of use cases for a system constitute all the defined ways the system may be used. In the UML, a use case is represented as an oval.
A use case diagram is a diagram that shows a set of use cases and actors and their relationships. Actors may be connected to use cases only by association. An association between an actor and a use case indicates that the actor and the use case communicate with one another, each one possibly sending and receiving messages. Use case diagrams are used to … GEC, MODASA
Page 18
SRS
ONLINE SALE SYSTEM
Model the context of a system.
Model the requirements of a system
EN. No-080160116035
Dependency Relationships between Use Cases
6.1.1
GEC, MODASA
extend : Specifies that the target use case extends the behavior of the source use case. Include: Specifies that the source use case explicitly incorporates the behavior of another use case at a location specifies by the source.
Use Case Diagram For Visitor
Page 19
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
Fig. 6.1 Use Case Diagram for Visitor 6.1.2
Use Case Diagram For Admin
Fig. 6.2 Use Case Diagram for Admin Operation
GEC, MODASA
Page 20
SRS
ONLINE SALE SYSTEM
6.1.3
EN. No-080160116035
Use Case Diagram For Customer
Fig. 6.3 Use Case Diagram for Customer Operation
GEC, MODASA
Page 21
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.2 CLASS DIAGRAM
Fig. 6.4 Class Diagram for E-commerce Portal
GEC, MODASA
Page 22
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.3 STATE DIAGRAM 6.3.1
State Diagram – Login State
Login Do: Enter Username And Password
Checked/Reject
Checked/accept
Role Create Account Full Authority
User
Admin
Log Out
Fig . 6.5 Login State
GEC, MODASA
Page 23
SRS
ONLINE SALE SYSTEM
6.3.2
EN. No-080160116035
State Diagram – Registration
[User] / Create Account
[admin] / Create Account
Registration
Registration
Do: Enter details
Do: Enter details
Invalid
Invalid
Save
Save
Do: Validation Check
Do: Validation Check
Log Out
Fig 6.6 Registration State
GEC, MODASA
Page 24
SRS
ONLINE SALE SYSTEM
6.3.3
EN. No-080160116035
Sate Diagram - User
Login Do: Enter Details Invalid
Save Do: Check Validation Valid Entry
Home Do: View Category Select Category
Product Select Product
Delete (cart_id)/delete Item
Do: View Product Infomation
Log Out
Cart
Cart Do: View Cart Details Checkout
Checkout Do: Enter Details
Fig 6.7 User Process State
GEC, MODASA
Page 25
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.4 SEQUENCE DIAGRAM 6.4.1 Sequence Diagram : Register a User
Fig. 6.8 Sequence Diagram: Register a user
GEC, MODASA
Page 26
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.4.2 Sequence Diagram : Login Customer
Fig. 6.9 Sequence Diagram: Login a customer
GEC, MODASA
Page 27
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.4.3 Sequence Diagram :Submit a Cart
Fig. 6.10 Sequence Diagram: Submit a cart
GEC, MODASA
Page 28
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.4.4 Sequence Diagram : Add Product
Fig. 6.11 Sequence Diagram: Add a new product GEC, MODASA
Page 29
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.5 E-R DIAGRAM ERD stands for Entity / Relationship diagram. It defines the relationship between different entities of a system. It enables a software engineer to fully specify the data objects that are input and output from a system, the attributes that define the properties of these objects, and their relationships.
Table 6.1 Notations of ER Diagram Notation
Description
Symbol
It is a distinguishable real world object that is to be represented in the database. Entity
It is the characteristics of an entity, which give more / detail information about entities. Attribute
Connectors between different symbols. Link
Association between the entities. Relationship
GEC, MODASA
Page 30
SRS
ONLINE SALE SYSTEM
EN. No-080160116035
6.5.1 E-R DIAGRAM FOR E-COMMERCE PORTAL:
NAME
ADDRESS
ID_NO
ID_NO
NAME Place Order
1
ADMIN
M 1
Receive Order
Customer
1 M
M
Payment ADDRESS
GEC, MODASA
Page 31
View more...
Comments
