SUPERIOR UNIVERSITY LAHORE

Faculty of Computer Science & IT

E-commerce SYSTEM

Student Name Roll no /Student ID Program/ Phone Number Email Address

Degree
Muhammad Talha MCSE-F20-020 MCS 0309-4231697 mcse-f20-020@superior.edu.pk
Abdulrehman Majid MCSE-F20-002

Maryam zaheer MCSE-F19-191

Team

Supervisor
Mr. Muhammad Ahmed Kahloon
 Project Report: E-commerce System

Project Report
E-commerce System

Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0

APPROVAL

Faculty of CS&IT, Superior University Lahore, Pakistan ii

PROJECT SUPERVISOR
Comments:

Name:
Date: Signature:

PROJECT MANAGER
Comments:

Date: Signature:

HEAD OF THE DEPARTMENT

Comments:

Date: Signature:
 1 Dedication

We dedicated our dissertation to our beloved parents, who taught us that even
the largest task can be accomplished if it is done with sincerity and devotion
and given us all of their resources for our study. We want to dedicate this to our
teachers also who enlightened us with knowledge.
 2 Acknowledgements

First of all, we are very grateful to Almighty ALLAH who gave us strength and guidance to carry
out our research project. We take great pleasure/honour in thanking Assistant Professor Sir
Ahmed Kahloon, our project supervisor (The Superior University Lahore) for permitted us to
carry out this project work.
We would really like to express our honour to our liked parents for their blessings. Our
friends for his or her help and wishes for a success final completion of this project.
 3 Executive Summary

The project is about E-commerce Management. It's all about to solve the current problems of
E-commerce management. Through this you can check the schedule of your order from
departure to arrival time from which order is taken and send. You can reserve product online,
check the availability of product. Through this we can improve our system and our file system.
File system will be completed and the launch system and system go online on internet. By using
database, we can arrange data properly according to our requirements.
4 Table of Contents
1 Dedication................................................................................................................................iv
2 Acknowledgements..................................................................................................................v
3 Executive Summary.................................................................................................................vi
5 List of Tables............................................................................................................................ix
6 List of Figures...........................................................................................................................xi
Chapter 1.......................................................................................................................................12
Introduction...................................................................................................................................12
1.1. Background.....................................................................................................................14
1.2. Goals and Objectives.......................................................................................................14
1.3. Literature Review/Existing Solutions..............................................................................15
1.4. Proposed Solution...........................................................................................................15
1.5. Project Plan.....................................................................................................................16
1.5.1. Work Breakdown Structure.........................................................................................16
1.5.2 Gant Chart.........................................................................................................................17
Figure 1.5.2................................................................................................................................17
1.5.3 Roles & Responsibility Matrix...........................................................................................18
Table 1.5.3.................................................................................................................................18
1.6. Report Outline.................................................................................................................18
Chapter 2.......................................................................................................................................20
Software Requirement...................................................................................................................20
Specifications.................................................................................................................................20
2.1. Introduction....................................................................................................................21
2.1.1. Purpose........................................................................................................................21
2.1.2. Document Conventions...............................................................................................21
2.1.3. Intended Audience and Reading Suggestions.............................................................21
2.1.4. Product Scope..............................................................................................................21
2.1.5. References...................................................................................................................22
2.2Overall Description...............................................................................................................22
2.1.1 Product Perspective..........................................................................................................22
2.1.2Product Functions..............................................................................................................23
2.2 Operating Environment.......................................................................................................24
2.2.1 Design and Implementation Constraints..........................................................................24
2.2.2 User Documentation.........................................................................................................24
2.2.3 Assumptions and Dependencies.......................................................................................25
2.2.4 User Classes and Characteristics......................................................................................25
2.3 External Interface Requirements.........................................................................................26
2.3.1 User Interfaces...................................................................................................................26
2.3.1 Hardware Interfaces....................................................................................................26
2.3.2 Software Interfaces.....................................................................................................27
2.3.3 Communications Interfaces.........................................................................................27
2.4 System Features..............................................................................................................28
2.4.1 System Feature................................................................................................................28
 2.4.1.2.1 Functional requirement 1..............................................................................................28
2.4.1.2.3 Functional requirement 3...................................................................................................29
2.6 Functional Requirements....................................................................................................42
2.7 Other Nonfunctional Requirements...................................................................................42
2.7.1 Performance Requirements..............................................................................................42
2.7.2 Safety Requirements........................................................................................................43
2.7.3 Security Requirements.....................................................................................................43
2.7.4 Software Quality Attributes..............................................................................................43
2.8 Availability...........................................................................................................................43
2.9 Reliability............................................................................................................................44
2.10 Web Page..........................................................................................................................44
2.11 Quality Record..................................................................................................................44
2.11.1......................................................................................................................Business Rules 44
2.12 Other Requirements..........................................................................................................45
2.13 DFD Of website..................................................................................................................46
Chapter 3.......................................................................................................................................51
Use Case Analysis...........................................................................................................................51
3.1. Use Case Model...............................................................................................................52
3.2. Fully Dressed Use Cases..................................................................................................67
Figure 3.2.1................................................................................................................................68
Chapter 4.......................................................................................................................................69
System Design................................................................................................................................69
4.1 Entity Relationship Diagram with data dictionary...............................................................70
4.2 Sequence / Collaboration Diagram 1..................................................................................71
4.3 Sequence / Collaboration Diagram......................................................................................71
4.4 Data Flow diagram...............................................................................................................72
4.5.................................................................................................................Development diagram: 76
4.6 component diagram:...............................................................................................................77
CHAPTER 5.....................................................................................................................................78
IMPLEMENTATION.........................................................................................................................78
5.1. Tools and Techniques......................................................................................................79
REFRENCES.....................................................................................................................................80
AND................................................................................................................................................80
BIBLIOGRAPHY...............................................................................................................................80
Appendix........................................................................................................................................82
Appendix A: To Be Determined List...........................................................................................83
 5 List of Tables
6.1 Table no 3.1.1.....................................................................................................................52
6.2 Table no 3.1.2.....................................................................................................................53
6.3 Table no 3.1.3.....................................................................................................................54
6.4 Table no 3.1.4.....................................................................................................................54
6.5 Table no 3.1.5.....................................................................................................................55
6.6 Table no 3.1.6.....................................................................................................................56
6.7 Table no 3.1.7.....................................................................................................................56
6.8 Table no 3.1.8.....................................................................................................................57
6.9 Table no 3.1.9.....................................................................................................................57
6.10 Table no 3.1.10..................................................................................................................58
6.11 Table no 3.1.11..................................................................................................................59
6.12 Table no 3.1.12..................................................................................................................59
6.13 Table no 3.1.13..................................................................................................................60
6.14 Table no 3.1.14..................................................................................................................60
6.15 Table no 3.1.15..................................................................................................................61
6.16 Table no 3.1.16..................................................................................................................62
6.17 Table no 3.1.17..................................................................................................................62
6.18 Table no 3.1.18..................................................................................................................63
6.19 Table no 3.1.19..................................................................................................................64
6.20 Table no 3.1.20..................................................................................................................64
6.21 Table no 3.1.21..................................................................................................................65
6.22 Table no 3.1.22..................................................................................................................66
6.23 Table no 3.1.23..................................................................................................................66
6.24 Table no 3.1.24..................................................................................................................67
 6 List of Figures

1.5.1. Work Breakdown Structure.........................................................................................16

1.5.2 Gant Chart.........................................................................................................................17
2.4.1 Login.........................................................................................................................................46
Diagram 1:.................................................................................................................................46
2.4.2 product and order info..............................................................................................................47
Diagram:2..................................................................................................................................47
2.4.3 order schedule..........................................................................................................................47
Diagram 3:.................................................................................................................................47
2.4.4 E-commerce system diagram....................................................................................................48
Diagram 4:.................................................................................................................................48
2.4.5 Drop a product/order ...............................................................................................................48
Diagram:5..................................................................................................................................49
2.4.6 Make a order............................................................................................................................49
Diagram:6..................................................................................................................................49
2.4.7 Report diagram.........................................................................................................................49
Diagram:7..................................................................................................................................50
2.4.8 Payment of order......................................................................................................................50
Daigram:8..................................................................................................................................50
4.1 Entity Relationship Diagram with data dictionary...............................................................70
Figure 4.1...................................................................................................................................70
4.2 Sequence / Collaboration Diagram 1..................................................................................71
Figure 4.2...................................................................................................................................71
4.3 Sequence / Collaboration Diagram......................................................................................71
Figure 4.3...................................................................................................................................72
 Project Report: E-commerce Management System

4.4 Data Flow diagram..............................................................................................................72

Figure 4.4.1................................................................................................................................73
Figure 4.4.2................................................................................................................................74
Figure 4.4...................................................................................................................................75
4.5Development diagram:.............................................................................................................76
Figure 4.5...................................................................................................................................76
4.6 component diagram:...............................................................................................................77
Figure 4.6...................................................................................................................................77

Faculty of CS&IT, Superior University Lahore, Pakistan 12

 Project Report: E-commerce Management System

Chapter 1
Introduction

Faculty of CS&IT, Superior University Lahore, Pakistan 13

Chapter 1: Introduction
This document is all about the requirements for the E-commerce system. This project is will be
very helpful in getting things fast and reliable. It makes less man power and work load and once
it is launched it will save a lot of company/government assets and made our country
progressive. Thing which is going to be done in hours happens in minutes or seconds with the
help of this E-commerce system.

Through this way we can easily find the products, we can also check our order by online system.
In this project we use DBMS (database system management) for organising data.
1.1. Background
E-commerce useful for the business and trade purpose. The first primitive electronic data
transactions is in the 1960s and the first online retail transaction in 1994 all the way up to the
present-day.

1.2. Goals and Objectives

Our main objectives and goals of this project of E-commerce management system are to make
the E-commerce system more efficient, easier, comfortable and reliable. This project is only for
the use of administrators. In this project we will come to know how technology system can solve
our problems. The main goals of this project are to managed the arrivals and departures of
products on time, to check the orders, buy pre-booked products.
The objectives of this development efforts are:
 it provides new and latest environment to buy product.
 To provide an avenue for customers to get their orders in a more
convenient way.
 To enforce a prototype of a scaled down model of the very last gadget to
check the solution and further broaden necessities.
 To collect statistics in a more efficient manner for future E-commerce
development.
 To increase efficiency of E-commerce.
1.3. Literature Review/Existing Solutions
The literature overview of the E-commerce management system is to computerized the primer
system through the help of software program and database management system. So, the
information can be saved inside the database for long period of time.
E-commerce management system provide us user friendly, reliable, dependent.

1.4. Proposed Solution

As this project is only for the use of administrators, E-commerce managers and E-commerce
customers to manage the overall approval of a plan or statements for E-commerce system. This
system is user friendly so the E-commerce customers can easily customize and update the
database.
The E-commerce management system gives us proper security and overcome the written and
primer work.
 Increase the security of Data/record
 Enhance the efficiency
 provide the better services
 user friendly and correlative or dependent
 Should be interchangeable
 certify the data validity
 overcome the manual entries of data
 take the less time
1.5. Project Plan
The system will be providing us electronic media content (it may be in the form of
printed output) of the Pakistan E-commerce system. The system will have a user
friendly. This software designed to help the precise/calculated planning. It will be
more cost effective compared to the current non electronic media to buy product.

1.5.1. Work Breakdown Structure

 Schedule structure: it manages the timetable of arrival and departure of the product order
 Login system: it used to handle the login/access details
 customer system: it manages the information and details of customers
 user system: it uses to manage the user details and information
 order and pre-order: they manage the information about order and pre-order system
 1.5.2 Gant Chart
Project
August August 2021 August
Schedule August August August August August Summery
2021 2021
2021 2021 2021 2021 2021
TASKS Hours Percent
Requirements 12 12 12 9 45 22.20%
Design 5 7 12 8 32 14.90%
Code and 3 7 4 2 4 5 6 8 2 6 47 13.20&
Unit Test

Test and 3 6 9 12 15 15 12 9 6 3 90 6.60%

integrate

User Manual 16 12 8 4 38 21.10%

Write

Report 2 4 6 8 10 12 14 16 72 1.90%
Writing

Demonstrate 8 8 20.20%
Hours 12 12 10 9 10 12 14 18 10 12 20 10 8 20 21 12 332 100.00%

Figure 1.5.2
1.5.3 Roles & Responsibility Matrix

M.Talha Ayesha Ahoor Bakhtawar Liaquat

Documentation and Documentation and Documentation and

Coding Coding Coding

Responsibility Responsibility Introduction

Use case Marketing Material System Design
Use case model Visiting card Use analysis
Introductions Standee DFD
Software Posters System Architecture
Requirement s Banners CODING
specifications Designing

Table 1.5.3
1. User Roles:
 Can reserve the product according to their will.
 Can buy different product
 Can do order tracking
 Can complains about the system.
1.6. Report Outline
 All the system inputs are validated and don't accept the invalid values.
 It produces or create the report of customers, users.
 It generates the pure and clear report of products and order.
 It also generates tracking ID of the order.
 Chapter 2
Software Requirement
Specifications
Chapter 2: Software Requirement Specifications

2.1. Introduction
2.1.1. Purpose
This document is all about the requirements for the E-commerce system. This project is will
be very helpful in making the things fast and reliable. It decreases the work load and man power
and once it is online it will save a lot of customer assets, time and made our country progressive
and make E-commerce system more efficient and evolve. Thing done in hours happens in
minutes or even seconds with the help of this system.

2.1.2. Document Conventions

E-commerce Electronic Commerce System

POSS Product order System Server

DB Data Base
PST Pakistan Standard Time
RS Rupees
PKR Pakistani Rupees

2.1.3. Intended Audience and Reading Suggestions

This document is simply just for client not for public. The document is made for,
project managers, developers, marketing staff, users, testers and documentation
writers
2.1.4. Product Scope
The system will be providing us electronic media content (it may be in the form of
printed output) of the E-commerce system in Pakistan. The system will have a user
friendly. This software designed to assist the calculated planning. It will be more cost
effective compared to the present non electronic media content of the product
ordering system.
 The objectives of this development efforts are:
 comfortable registration and profile control facilities for customers
 Adequate searching mechanisms for smooth and short get right of entry to unique services and
products creating a shopping cart so that clients can store ‘n’ no. of items and checkout eventually
with the complete shopping carts.
 clients can add or delete objects inside the cart.
 Male updates regularly to registered customers of the OFS (offer for sale) about new arrivals.
 Uploading ‘Most Purchased’ Items in each category of products in the Shop.
 Strategic data and graphs for Administrators and Shop owners about the items that are popular in
each category and age group
 Maintaining database of daily for the 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, add rating option of individual products to get information about product by relevant
customers
 Adequate payment mechanism and gateway for all popular credit cards, cheques and other relevant
payment options, as available from time to time

2.1.5. References
3. [1] SOFTWARE ENGINEERING Tenth Edition Ian Sommerville
2.2 Overall Description
2.1.1 Product Perspective
Existing system has these features
 Data is stored in papers, isn't secured thanks to natural calamities
 As the data is on paper so it is difficult to update, delete, add or view data
 Existing system is more time consuming
 Existing system consumes more men power
 In existing system there is a large volume of data to deal with
 Existing system has to deal with numerous calculations
 Existing system is manual which involves a lot of paper work

This product proposed the following

 it provides new environment to buy product from anywhere.
 To give an avenue for customers to get their order in a more efficient way to
regain control of the E-commerce System.
 To install a prototype of a scaled down version of the final system is to test the
solution and further develop requirements.
 To collect statistics in a more efficient manner for future E-commerce development
and construction.
 To increase efficiency of E-commerce System.

2.1.2 Product Functions

Functionalities of this project are
 It will provide searching facility
 It manages the customer details, online order details, order pre-booking details and product
details
 It gives all the information about product/order arrival day
 It shows the description of product
 It also monitors the transactions of payment
 Editing, adding and updating of records
 Editing, adding and updating of payment
 Integrity of all records of booking
 Simple status and resolutions
  Individual access to any information
 Order Reports are well designed
 It will provide multi-level priorities
 Updating is more easy
 work speed is increased
 getting product information is easy and fast
 to maintain the security user/admin accounts are being protected

2.2 Operating Environment

Software:
 Language: C++
 Database: SQL server
 Browsers: All the browsers

Hardware:
 Ram
 Hark disk
 Processor
 Monitor
 Keyboard
 Mouse

2.2.1 Design and Implementation Constraints

 The software program layout (maintainability) will now not be obligation of developer or organization.
 it is going to be the responsibility of the admin
 In case of any mishap within the software the developer or employer will now not be responsible for
that lose
 Developer or organization gives a first trail of the software program and after that they will not
entertain their quires.
 After delivering the project any changes in the software will be charged by per hour
2.2.2 User Documentation
 User can pre-order their products
 User can cancel their order
 User can see the whole description to get the desire product
 User can pay online
 User can track order
 User can buy product online
 User can choose payment method
 User/admin will get their personal log in account

2.2.3 Assumptions and Dependencies

Assumptions
 It is assumed that the requirements are complete.
 It is assumed that user can use internet browser
 It is assumed that user know how to use mouse and keyboard
 It is assumed that user has an internet connection
Dependencies
 user’s stages are previously determined for all the users
 Access to the system is restricted to the user’s name
 restrictions and boundaries of all of the degrees are known by means of the high-level customers
 Security employees have got access to any user’s account

2.2.4 User Classes and Characteristics

 It will provide searching facility
 It manages the customer details user
 It shows the description of product and order
 It also monitors the transactions
 Editing, adding and updating of records
 Editing, adding and updating of order
 Integrity of all records of booking Simple status and resolutions
 reduce the person burden involved in existing manual system
 Individual access to any information
 Reports are well designed
  It will provide multi-level priorities
 Better storage capacity
 Updating is more easy
 work speed is increased
 getting of information is easy and fast
 To maintain the safety user accounts are being secured

2.3 External Interface Requirements

2.3.0 User Interfaces

 Admin can View, Edit and Delete everything on the merchandise.

 User can view the entire information.
 It will maintain high contrasts
 It will have high visibility to urge best results
 It will have dark coloured background
 It will have light coloured font o increase the visibility
 Icons are going to be of bright colour
 Layout are going to be consistent with the display and scope of the device on which software is
getting used
 User interface for the appliance is going to be within the sort of forms, that it'll easy to read
Hardware Interfaces
 Ram
 Hark disk
 Processor
 Monitor
 Keyboard
 Mouse
 2.3.1 Software Interfaces
Software requirements are the requirements which are needed for the building of the project. At
which software the project is made up
Language: C++
Database: SQL
server
Browsers: All the browsers

2.3.2 Communications Interfaces

Communication interfaces are the interfaces through which user and merchandise stakeholders
are connected. Developers use many ways for the communication purposes such as

 Telephone
 Mobile phone
 Email
 FAQs
 Live calls
 Live Chats

2.4 System Features

2.4.1 System Feature

2.4.1.1 Description and Priority

These are the features of the system that are really important to write down there in such order if
developer start its work from first requirement to the last it will not face any problem of like this
requirement should in first now, I have to change all the code to fulfil that requirement such
problems will cause a great time lose
 2.4.1.2 Functional Requirements
Functional requirements are the requirements which is important for completion of the small print given by the
client. In this some requirements are putted by programmer which is important for correct functionality
For example
 Minimum steps to make a purchase.
 Mobile-friendliness.
 Unique, recognizable design.
 Relevant, useful content.
 Email tools.
 Live chat

1 Functional requirement 1:

Description:

It should store information about entry of order

Input:

enter the time when the user orders product

Output:
Stores order entry time with order ID Number in database

2 Functional requirement 2:

Description:

Should keep the record of store

Input:

Enter all the store product

Output:

Will be displayed in inventory

3 Functional requirement 3:

Description:

It should update the records on instructions

Input:

Update the record when needed

 Output:

Show that updating on the user interface

4 Functional requirement 4:
Description:

It should delete the records on instruction

Input:

Delete the record when needed

Output:
Will no longer display that record from user interface
5 Functional requirement 5:
Description:
It should have userx personal login account

Input:

Should enter an email and a password

Output:

Login to the account

6 Functional requirement 6:

Description:

It should have an admin’s login account

Input:

Should enter admins id and password

Output:

Logged in to the admin’s account

7 Functional requirement 7:

Description:

It should have a guest’s login account

Input:

Need no id and password

Output:

Enables to see availability product

8 Functional requirement 8:

Description:

It should have a pre-order system

Input:

User can add one or more than one order in the cart

Output:
A message will appear on the screen “Mr Talha order the product number 1,2,3 or name form
DHA to JOHAR Town at 21:00 PST. Do you want to buy product now”
 9 Functional requirement 9:

Description:

It should have visuality of full detail of product so that passengers can select desired product

Input:

Should select the product

Output:

Display a message “Do You want to confirm your order?”

10 Functional requirement 10:

Description:

It should have a order tracking system

Input:

Should enter order number and destination of order

Output:

Will get the position of order on user’s screen

11 Functional requirement 11:

Description:

It should have an online payment option

Input:

enter user bank account number and password

Output:

Transfer amount/money from user’s account to the management’s account

12 Functional requirement 12:

Description:

User should get the notifications from product

Input:

user allow notification

Output:

User get the alert from the product on their devices

13 Functional requirement 13:

Description:

User should get the notifications from product

Input:

Automated to their accounts and given numbers and emails

Output:

User get alerts of new offers, new timings, delays of order and other discount offers
from the product to their respective devices

14 Functional requirement 14:

Description:

For new users, it should have a guide book “how to use this software”
Input:
Click to that link for help
Output:

Open ups the help page or guide book and explain it briefly
15 Functional requirement 15:

Description:

It should have a language option

Input:

User can change Language of the product

Output:

It should display a message “you want to change language” and switch to that desired
language

16 Functional requirement 16:

Description:

For the new customers/users it should have a video guide/tutorial

Input:

Click to the links to get video tutorial help for the users
Output:

video will open and guide the user and its voice and print is as clear as it should be
listening to every one easily
17 Functional requirement 17:

Description:

It should have a search engine to search their desire product

Input:

Write there what user wants to search

Output:

Searched results are showing in a dropdown list

18 Functional requirement 18:

Description:

It should have an option of cancellation

Input:

Cancel the order in fixed amount of time according to the needs of the user’s
Output:

Cancel the order and display a message “your order has been cancelled”

19 Functional requirement 20:

Description:

It should have a concession type

Input:

If user buy product more than 50,000

Output:
 Will get the 50 % off on all types of products

2.6 Functional Requirements

These are the features of the system that are really important to write there in such a way that
if developer start its work from first requirement to the last it will not face any problem of like
this requirement should in first now, I have to change all the code to fulfil that requirement
such problems will cause a great time lose

In this document the requirements are written first as of first priority and last of that least
priority
Functional Requirements

Functional requirements are the requirements which is needed for completion of the project
and details given by the client. In this some requirements are putted by S.E(Software
Engineer) or programmer which is necessary/needed for proper functionality of the
software.

2.7 Other Non-functional Requirements

2.7.1 Performance Requirements
 Its performance should be accurate
 It should be accessible all the time to users/admin
 Its server’s link should never be break
 down
 To get best/better performance or speed, should need best internets to servers
 It should bear the load of as many users at a time, can login to site system shouldn't be
crashed
 System shouldn't be slow on having load on site.
2.7.2 Safety Requirements
 Servers should be placed in low temperature or in cold place
 System should have a backup server for data backup
 System should have a backup database in case of any server damage or loss of data
 Systems should be well updated

2.7.3 Security Requirements

 Security should be of fool proof
 It should have logins
 It should have a case sensitive password
 It should have pin option
 It should have face id.
 It should have a finger print detector
 Account should be integrated
 Personal information of a client should not be leaked out
 Password should not be shown on the URL
 2.7.4 Software Quality Attributes
Quality Service Requirements are the Requirements which are needed to maintain your product
quality for your reputation’s sake.
Quality service requirements are as follow
 There may be many admin’s creating/making the project, all of them will have the right to create changes to the
system but other than admin like members or other users cannot make changes.
 The project should be open source.
 The quality of the database is maintained in such a way so that other users database can understand is easily.
 The user can easily download and install the system in the operating system.

2.8 Availability
System should be available all the 24/7 so that it could not be have any difficulty in
getting any order form the customer or updating its database

2.9 Reliability
System should be reliable so that client can give their personal opinion/review about the
product easily and trust them that their information is not leaked out for any purpose

2.10 Web Page

System should have a web page for its software with the layout and features of web page so that system is
connected to the internet and has the best updating and editing on all the systems at once. It reduces the
probabilities of confusions which make it less complex

2.11 Quality Record

System should have quality record of their data so that whenever record is needed it is easy
to read and understand for that record should be managed
Record can be managed in different ways, like by years, by alphabets and many other ways
 2.11.1Business Rules
 The software design (maintainability) will not be responsibility of developer
or company.

 Admin should take the responsibility of the maintainability of software.

 In case of any accident, issue or mishap in the software the programer or

company will not take responsibility for that lose

 Programmer, software engineer or company gives a first trail test of the software
and after that they will not take any quires from the customer.

 After delivering the project any increment in the software will be charged by per hour.

2.12 Other Requirements

2.12.1 Architectural Requirement:
Architectural requirements are the requirements which are needed for the developing of a product.
Architectural requirements is one of the projects for completion of the project. These requirements are the
clients concerns.
There are some architectural requirements for project

 Clarify and recognize the project Request

 Size of a project should be determined
 Cost must be calculated
 Needed to recognize about the technical and operational feasibility of
alternative approaches
2.12.2 User Requirements:
User Requirements are the requirements which are to be fulfilled by programmer. In this Clients gave
programmer some details of what he wants in his project
There are some User requirements
 User should know what the requirements.
 Screen should be formatted.
 Messages, instructions and information should display on the screen as long as it could be
readable
 Without removing errors, users cannot proceed
 User should never get the programming errors
 Should know about authenticated details
 For concession, concession requirements and percentages will be given for the execution of the
programming logics
 2.13 DFD Of website

2.13.1 Login

Diagram 1:
2.13.2 Admin DFD
Diagram:2
2.13.3 delete product
2.13.4 Dispatch order
User dfd
 Chapter 3
Use Case Analysis
 Chapter 3: System Analysis
Use-case model
• Customers and end users have goals/needs, and want computer systems to help meet them,
• There are several ways to capture these goals and system requirements;
• the better ones are simple and familiar because this makes it easier especially for customers and end users to
contribute to their definition or evaluation.
• Use cases are a mechanism to help keep it simple and understandable for all stakeholders.
• Informally, they are stories of using a system to meet goals.
• use case is a list of steps, defining interactions between a role an "actor" and a system, to achieve a goal.
• Use cases are text documents, not diagrams, and use case modeling is primarily an act of writing, not
drawing. The UML defines a use case diagram to illustrate the names of use cases and actors, and their
relationships.

The beauty of use case:

• it aims at describing a system from external usage viewpoint, rather than from developer's
perspective.
• writing use case can be the deciding factor for building a system that meets users' needs.

Use case modelling for E-Commerce

• Use case modeling identifies the use cases of the system, each representing a different capability that the
system provides to its clients. Some of them are given below.
• “View Inventory”
• “Add product to cart”
• “Delete product from cart”
• “Update product in inventory”
• “Buy product”
• Each use case describes a typical scenario for which the user uses the system.
3.1. Use Case Model

Number: UC-1
Use Case Name: entry of order
Priority 5
Trigger
enter the time when the user/customer orders
product
Precondition Product order is decided
Basic Path 1-POSS send the data to the DB of POSS and
stores the data
2-DB resend the data to the POSS
Alternate Path N/A
Post Condition
Stores order entry time with order ID Number
in database
Exception Path If there is any connection failure POSS returns
to the wait state
Other
 Table no 3.1.1

Table Post Condition

Number: Updated
UC-2 product will be displayed
no
Use Case Name: Store record
3.1.2
Exception
Priority Path If
5 there is any connection failure ECMS returns
Trigger
Number: to the wait
admin
UC-3 loginstate
to updates the record
Table Other
Precondition 1-Admin account is logged in.
no Use Case Name: Update record
3.1.3 Priority 2-Admin
5 clicks on the update button
Basic Path
Trigger 1-ECMS
admin send the data to the DB of ECMS and
Table Number: UC-4 login to store the record
no Precondition updates the
3-Admin data is logged in.
account
Use Case Name: Delete record
3.1.4 2-DB resend theondata
Priority 4-Admin
5 clicks the to thebutton
store ECMS
Alternate
Basic PathPath N/A
3-ECMS sendtothe datathe
to the DB of ECMS and
Trigger admin login delete record
Post Condition It shows
store that update is made on the user
the account
data
Precondition 1-Admin
Interface is logged in.
Exception Path 4-DB resend
If there
2-Admin theon
isclicks
any data
the to
connection thefailure
delete ECMS
buttonECMS returns
Alternate to the wait state
Basic PathPath N/A
1-ECMS send the data to the DB of ECMS and
Other
updates the data
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition
Product will no longer displayed the record in
inventory
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Number: UC-5
Use Case Name: User login account
Priority 5
Trigger When enter a correct email and password
Precondition User device is connected to internet
Basic Path 1-ECMS send the data to the DB of ECMS and
matches with the data
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition User login to account
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.5

Number: UC-6
Use Case Name: Admin’s login account
Priority 5
Trigger When enters correct Admin’s or Staff id and
Password
Precondition Admin’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS
and matches the data
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition Loged into admin’s account and go to the
admin’s panel
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.6

Number: UC-7
Use Case Name: Guest’s login account
Priority 3
Trigger When clicks on the guests account icon
Precondition User’s device should connect to internet
Basic Path 1-ECMS send the data to the DB of ECMS
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition It shows that update is made on the user
Interface
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.7
Number: UC-8
Use Case Name: Pre-order System
Priority 5
Trigger When u s e r enters the Product I D / N a m e
and number of Pre-order product user want to
pre-order
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS and
reserves the seats
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition generates a message on user’s interface/screen
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.8
Number: UC-9
Use Case Name: Visuality of Product
Priority 4
Trigger When enters the Product ID and number of
Product you want to Pre-order
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
3-user clicks on the desired product
Basic Path 1-ECMSS send the data to the DB of ECMS and
reserves the seats
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition generates a message on user’s interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.9
Number: UC-10
Use Case Name: Order tracking system
Priority 4
Trigger When enters the product id and destination of
order

Precondition 1-User account is logged in.

2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS and
reserves the seats
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition Will get the position of order on user’s
Interface
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.10
Number: UC-11
Use Case Name: Online payment System
Priority 5
Trigger When user enters its bank account number
and password
Precondition 1-User account is logged in.
2-User’s device is connected to the
internet 3-User has bank account
Basic Path 1-ECMS send the data to the DB of ECMS and
connect to the Bank
2-DB resend the data to the ECMS and add
money to ECMS account
Alternate Path N/A
Post Condition Transfer money from user’s account to the
management’s account
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.11
Number: UC-12
Use Case Name: Notification
Priority 4
Trigger When user order any product get notification

Precondition 1-User account is logged in.

2-User’s device is connected to the internet
3-User should have network on their device
Basic Path 1-ECMS send the data to the DB of ECMS and
reserves the seats
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition generates a notification on their respective
devices
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.12

Number: UC-13
Use Case Name: ALERT
Priority 5
Trigger user get notification on new offers

Precondition 4-User account is logged in.

5-User’s device is connected to the internet
6-User should have network on their device
Basic Path 3-ECMS send the data to the DB of ECMS and
reserves the seats
4-DB resend the data to the ECMS
Alternate Path N/A
Post Condition generates a notification on their respective
devices
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.13

Number: UC-14
Use Case Name: Guide Book
Priority 3
Trigger When Clicks to that link where guide book is
Placed
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS and
refer to that link
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition Open ups the guide book on user’s interface
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.14
Number: UC-15
Use Case Name: Language option
Priority 3
Trigger When clicks to the language option change
Link
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition generates a message on user’s interface and
switch to that desired language
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.15

Number: UC-16
Use Case Name: Video tutorials
Priority 3
Trigger When Click to the link where videos are places
for the users
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition Video is start playing on user’s interface
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.16

Number: UC-17
Use Case Name: Search area
Priority 5
Trigger Write there what user want to search
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS and
search from the complete forum
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition Searched results are displayed in a dropdown
list on user’s interface
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.17

Number: UC-18
Use Case Name: Cancellation System
Priority 5
Trigger When cancel the order/pre-order
Precondition 1-User’s account is logged in.
2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS
and cancel the order/pre-order
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition generates a message on user’s interface
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.18

Number: UC-19
Use Case Name: Concession option
Priority 5
Trigger When click on the concession option
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-ECMS send the data to the DB of ECMS
2-DB resend the data to the ECMS
Alternate Path N/A
Post Condition Open up the concession form on user’s
Interface
Exception Path If there is any connection failure ECMS returns
to the wait state
Other
Table no 3.1.19