Documentation PDF

DIGITAL SHOP
By
Muhammad Shakeel Abbas
&
Ahsan Jamal
DEGREE
BS Information Technology
Department of Information Technology

Govt. Post Graduate Chakwal
University of Gujrat
Session 2010-14
ACKNOWLEDGEMENTS
We have taken efforts in this project. However, it would not have been possible without
the kind support and help of teachers & friends. We would like to extend our sincere
thanks to all of them.
We are highly indebted to Prof. Muhammad Imran Faizi for their guidance and constant
supervision as well as for providing necessary information regarding the project & for
their support in completing the project.
We cannot forget the help & support of Prof. Farooq Bilal, Prof. Amir Mumtaz , Prof.
Amir Hussain, Prof. Amir Huusain, Prof. Waqas Ud Din & Prof. Fazal Abbas.
Our thanks and appreciations go to our classmates. Above all, we would like to express
our gratitude to Almighty Allah for providing us all these great people & the strength
to complete this project.
Muhammad Shakeel Abbas
______________
Ahsan Jamal
______________
DEDICTION
The project is dedicated to our parents, teachers, and friends.
ii
DECLARATION
We Muhammad Shakeel Abbas S/O Abbas Khan Roll # (10060656-045) & Ahsan
Jamal S/O Manzoor Hussain Roll # (10060656-037) students of Bachelor of Science
(Computer Science Or It), Department Of Computing & Information Technology,
University Of Gujrat, Pakistan, hereby solemnly declare that the data quoted in this
project titled Digital Shop is based on my original work, and has not yet been
submitted or published elsewhere.
Muhammad Shakeel Abbas _________________
Ahsan Jamal
__________________
We certify that Muhammad Shakeel Abbas S/O Abbas Khan, ROLL # 10060656-045,
& Ahsan Jamal S/O Manzoor Hussain Roll # 10060656-037 students of Bachelor of
Science (Computer Science or Information Technology), Department of Computing &
Information Technology, University of Gujrat, Pakistan, worked under my
supervision and the above stated declaration is true to the best of my knowledge.
MUHAMMAD IMRAN FAIZI (Supervisor) ___________________

Govt. Post Graduate College, Chakwal, Punjab, Pakistan.
Email: imranfaizi@yahoo.com
Dated: ________________________________
iii
PROJECT COMPLETION CERTIFICATE

It is to verify that this project titled DIGITAL SHOP by MUHAMMAD SHAKEEL
ABBAS S/O ABBAS KHAN, ROLL # 100606560-45, & AHSAN JAMAL S/O
MANZOOR HUSSAIN Roll # 10060656-037 students of Bachelor of Science
(Computer Science or Information Technology), Department of Computing &
Information Technology, University of Gujrat, Pakistan, contains sufficient material
required for the award of above said degree.
MUHAMMAD IMRAN FAIZI (Supervisor)

Email: imranfaizi@yahoo.com
_________________
Head Department of Information Technology,

__________________
Dated: ------------------------------------------
iv
TABLE OF CONTENTS
CONTENTS
PAGE
LIST OF TABLES, FIGURES AND APPENDIXES ----------------------------- VIII

ABSTRACT --------------------------------------------------------------------------- 1
CRAPTER 01: INTRODUCTION --------------------------------------------------
1.1 Introduction -------------------------------------------------------------------
1.2 Background and Existing System ------------------------------------------
1.2.1 Problem in Existing System ------------------------------------------
1.3 Proposed System--------------------------------------------------------------
1.3.1 Main Modules ----------------------------------------------------------
1.3.1.1 Admin Modules -----------------------------------------------
1.3.1.2 Client Modules ------------------------------------------------
1.3.1.3 Search Modules -----------------------------------------------
1.4 Expected Outcomes ----------------------------------------------------------
1.5 Tools & Technologies -------------------------------------------------------
1.6 Activity Index ----------------------------------------------------------------
CHAPTER 02: REQUIREMENT ANALYSIS ------------------------------------
2.1 Requirement Analysis ----------------------------------------------------------
2.1.1 Functional Requirement-------------------------------------------------
2.1.1.1 User-----------------------------------------------------------------
2.1.1.2 Admin---------------------------------------------------------------
2.1.2 Non-Functional Requirement ------------------------------------------
2.2 Use Case Diagrams ------------------------------------------------------------
10
2.3 Use Cases ----------------------------------------------------------------------
11
2.3.1 Admin Login----------------------------------------------------------
11
2.3.2 Administrator Manage Stock---------------------------------------- 12

2.3.3 Admin Manage Client -----------------------------------------------
13
2.3.4 Admin Manage Order -----------------------------------------------
14
2.3.5 Admin Manage Report ----------------------------------------------
15
2.3.6 Admin Manage Blog --------------------------------------------------- 16

2.3.7 Client Login ------------------------------------------------------------
17
2.3.8 Add Product To Cart --------------------------------------------------- 18

2.3.9 Admin Proceed Order ------------------------------------------------- 19
2.3.10 Services ----------------------------------------------------------------
20
2.3.11 Email Alerts -----------------------------------------------------------
21
2.3.12 Delivery Status -------------------------------------------------------- 22

2.3.13 Generate Invoices ----------------------------------------------------
23
2.3.14 Logout -----------------------------------------------------------------
24
CHAPTER 03: DESIGN & UML --------------------------------------------------- 25

3.1 UML Diagram ------------------------------------------------------------------------- 26
3.1.1 Functional Requirement View ----------------------------------------------- 26
3.1.2 Static Structural View --------------------------------------------------------
26
3.1.3 Dynamic Behavior View -----------------------------------------------------
26
3.2 Class Diagram ------------------------------------------------------------------------- 27

3.3 Sequence Diagram ------------------------------------------------------------
28
3.3.1 Admin Login Sequence -----------------------------------------------
28
3.3.2 Admin Client Management Sequence ------------------------------- 29

3.3.3 Stock Management Sequence ----------------------------------------
29
3.3.4 Blog Management Sequence -----------------------------------------
30
3.3.5 Services Management Sequence -------------------------------------
30
3.3.6 Report Management Sequence ---------------------------------------
31
3.3.7 Client Registration Sequence ----------------------------------------
31
3.3.8 Client Login Sequence ------------------------------------------------ 32

3.3.9 Client Order Sequence ------------------------------------------------
32
3.3.10 Client Cart Product Sequence ---------------------------------------
33
3.3.11 Cart Management Sequence -----------------------------------------
33
3.3.12 Client Invoice Sequence ---------------------------------------------
34
3.4 Domain Model-------------------------------------------------------------------------
35
CHAPTER 04: TESTING ----------------------------------------------------------
36
4.1 Testing ------------------------------------------------------------------------------
37
4.1.1 Check Login Page ----------------------------------------------------------
37
4.1.2 Client Login ------------------------------------------------------------------
38
vi
4.1.3 Testing Home Page ----------------------------------------------------------
38
4.1.4 Delivery Status ---------------------------------------------------------------- 39

4.1.5 Email Alerts -------------------------------------------------------------------
39
4.1.6 Automated Invoice -----------------------------------------------------------
40
CHAPTER 05: CONCLUSION & FUTURE WORK
41
5.1 Conclusion and Future Work ----------------------------------------------------
42
USER MANUAL -------------------------------------------------------------- -------
51
REFERENCES ------------------------------------------------------------------------ 52
APPENDIXES ------------------------------------------------------------------------
53
Responsive Design -------------------------------------------------------------------
53
Restrictions ---------------------------------------------------------------------------
54
Security on different levels ---------------------------------------------------------
54
Performance ------------------------------------------------------------------ --------
54
Accuracy ------------------------------------------------------------------ ------------
55
Usability ------------------------------------------------------------------------------
55
vii
LIST OF TABLES, FIGURES AND APPENDIXES

CONTENTS
TABLE 1.1: Activity Index --------------------------------------------------------------------------
PAGE
6
TABLE 2.1: Admin Login ----------------------------------------------------------------------------
11
TABLE 2.2: Admin Manage Stock ----------------------------------------------------------
12
TABLE 2.3: Admin Manage Client ---------------------------------------------------------
13
TABLE 2.4: Admin Orders -------------------------------------------------------------------- 14

TABLE 2.5: Admin Generate Reports -----------------------------------------------------
15
TABLE 2.6: Admin Manage Blog -----------------------------------------------------------
16
TABLE 2.7: Client Login ----------------------------------------------------------------------
17
TABLE 2.8: Product Management ---------------------------------------------------------
18
TABLE 2.9: Admin Proceed Order ---------------------------------------------------------
19
TABLE 2.10: Services -------------------------------------------------------------------------- 20

TABLE 2.11: Email Alerts --------------------------------------------------------------------- 21
TABLE 2.12: Deliver Status ------------------------------------------------------------------
22
TABLE 2.13: Automated Invoices ---------------------------------------------------------- 23

TABLE 2.14: Log out --------------------------------------------------------------------------
24
TABLE 4.1 Check Login Page ---------------------------------------------------------------------
37
TABLE 4.2 Client Login ---------------------------------------------------------------------
38
TABLE 4.3 Testing Home Page ----------------------------------------------------------
38
TABLE 4.4 Delivery Status ----------------------------------------------------------------
39
TABLE 4.5 Email Alert ----------------------------------------------------------------------
39
TABLE 4.6 Automated Invoice-----------------------------------------------------------
40
Figures
FIGURE-2.1: Use Case Diagram ------------------------------------------------------------------
10
FIGURE-3.1: Class Diagram ------------------------------------------------------------------------ 27

FIGURE-3.2 Admin Login Sequence ---------------------------------------------------
28
FIGURE-3.3 Admin Client Management Sequence ---------------------------
29
FIGURE-3.4 Stock Management Sequence ----------------------------------------- 29

FIGURE-3.5 Blog Management Sequence ------------------------------------------
30
viii
FIGURE-3.6 Services Management Sequence -------------------------------------- 30

FIGURE-3.7 Report Management Sequence ---------------------------------------- 31
FIGURE-3.8 Client Registration Sequence ------------------------------------------ 31
FIGURE-3.9 Client Login Sequence ---------------------------------------------------
32
FIGURE-3.10 Client Order Sequence ------------------------------------------------
32
FIGURE-3.11 Client Product Management Sequence --------------------------
33
FIGURE-3.12 Cart Management Sequence ------------------------------------------ 33

FIGURE-3.13 Client Invoice Sequence ------------------------------------------------
34
FIGURE-3.14 Domain Model ---------------------------------------------------------------
35
SCREEN SHOTS
FIGURE-5.1: Front Page ----------------------------------------------------------------------------
44
FIGURE-5.2: Product Info Page ------------------------------------------------------------ 44

FIGURE-5.3: User Login ---------------------------------------------------------------------
45
FIGURE-5.4: User Registration ------------------------------------------------------------
45
FIGURE-5.5: Services Page ----------------------------------------------------------------- 46

FIGURE-5.6: Blog Page ----------------------------------------------------------------------
46
FIGURE-5.7: Admin Login ------------------------------------------------------------------
47
FIGURE-5.8: New Product Page ----------------------------------------------------------
47
FIGURE-5.9: Order Page --------------------------------------------------------------------
48
FIGURE-5.10: Add Services Page ---------------------------------------------------------- 48

FIGURE-5.11: Account Registration Email ----------------------------------------------
49
FIGURE-5.12: Order Successfully Placed Alert ----------------------------------------
49
FIGURE-5.13: New Order Email Alert to Admin --------------------------------------- 50

FIGURE-5.14: Order Successfully Update ----------------------------------------------- 50
APPENDIX
Appendix (A) ----------------------------------------------------------------------------------
53
ix
ABSTRACT
Electronic Commerce is process of doing business through computer networks. A
person can access the facilities of buying or selling products online.
Unlike traditional commerce, e-commerce has made easier for human to reduce
physical work, time, effort and energy.
We will develop a web base system with similar working mechanism with enhanced
security and will offer better services to the customers. All the transactions will be
done securely with the trust of banks and some like Omni and Easy Paisa etc. Orders
will be delivered through the trusted carriers.
Digital Shop
Govt. Post Graduate College Chakwal
Page 1 of 55
CHAPTER 1
INTRODUCTION
CHAPTER-1
INTRODUCTION
1.1 Introduction
The major problem we are trying to remove in our project is to replace manual
system by an automated system, which removes the flaws in manual system. Today,
we see many businesses large and small using websites as a platform to sell a
product or provide a service.
The business organization has its offices in few cities/states and normally use
courier facility to deliver the product .if possible home delivery also provided. The
business organization mainly has two sectors first one is sale which sale the
products to the customer and second is service which provide services to the
customer.
Here we have solution to a worldwide business problem, which not only increase
profit margin but also attract customers attraction.
1.2 Background and Existing System
As we see today, many websites are available to provide online shopping system. It
is helpful for both parties, Clients & Businessmen. Businesspersons wants to extend
their business into many cities. Through advancement in E-Commerce, they are
able to do this, which require a platform such as a Website where they can show
their products to public.
Our product has similar working mechanism with enhanced security and better
services for customers.
1.2.1
Problems in Existing System

Our existing system is manual system. Needs to convert into an
automated system. Existing system have following problems,
Less Security.
Less Users - Friendly.
Accuracy not guaranteed.
Risk of mismanagement of data.
Retrieval of data takes lot of time.
A lot of manpower is required.
Digital Shop
Page 3 of 55
Not in reach of distant users.
1.3 Proposed System

We are going to develop a web based, Digital Shop, intended to provide
automated solution and services to customers. Consider a Business organization,
which has his business through INTERNET.
Organization, using our product can increase their productivity as well as enhance
their business countrywide. People can avail their services anywhere.
1.3.1 Main Modules

1.3.1.1 Module 1: Manage Admin Module
Admin Module
Sub-Modules are,
Admin Login
Stock Management (Add, Delete, Modify)
Users Management (View, Delete)
Orders Management (View, Delete, Proceed)
Reports Generation (Stock In, Stock Out)
Blog Management (Add, Delete, Modify)
1.3.1.2 Module 2: Client Module
Client Module
Sub-Modules are,
Client Registration
Client Login
Products Information
Add Product to cart
Delete Product from cart

Proceed order
Automated Invoice
Email Alerts
Delivery Status
Services
1.3.1.3 Module 3: Search Module
Search by Name, Search by Price Range & Search by Category.
Digital Shop
Page 4 of 55
1.4 Expected Outcome
Enhanced Productivity
Enhanced Publicity
Enhanced Reliability
Nationwide Business
More Profit
More Performance
More Clients
1.5 Tools & Technology
Apache Server 2.5
PHP 5.5 (Coding Language)
HTML5 , CSS3 , jQuery, Ajax (for Design / template)
BootStrap 3 (FrameWork Library For Interactive Web Design)
MySQL Server (for Database)
MySQL workbench (for Database Design)
phpMyAdmin (for Maintaining database )
Adobe Dreamweaver CC (for Arrangements of Contents)
Digital Shop
Page 5 of 55
1.6 Activity Index:

No.
Activity
Duration
Proposal
1W
Database Creation
2W
Design
3W
Coding
5W
Testing
1W
Implementation
1W
Deliverables
yes
yes
(Table 1.1)
Digital Shop
Page 6 of 55
CHAPTER 2
REQUIREMENT ANALYSIS
CHAPTER-2
REQUIREMENT ANALYSIS
2.1 Requirement Analysis
2.1.1 Functional Requirements

2.1.1.1 User:
Registration (User Can Register)
Email Verification (Email Verification After Registration)
Login (Registered User Can Login)
Search Products (Any One Can Search Products)
Cart Features (Add, Update, Remove)
Place Order (User Can Place Order)
Order List (User Can View His/her Orders List)
Email Alerts (User Will Receive Alerts)
Order Status (Will Get Order Status Via Email & Through
Login)
Invoice (Will Be Able to Generate Invoice & Print It)
2.1.1.2 Admin:
Manage Stock (Add, View)
Manage Categories/Brands ( Add, View, Modify)
Manage Products (Add, View, Modify, Delete)
Manage Clients (View)
Manage Orders (View, Update/Proceed)
Manage Payment Methods (Add, View, Modify, Delete)
Manage Blog (Add, View, Modify, Delete)
Manage Services (Add, View, Modify , Delete)
Generate Reports (View, Generate, Print)
Digital Shop
Page 8 of 55
2.1.2 Non- Functional Requirements (See Appendix (A))
Responsive Design
Restrictions
Security on different levels
Performance
Accuracy
Usability
Digital Shop
Page 9 of 55
2.2 Use Case Diagram
(Fig 2.1)
Digital Shop
Page 10 of 55
2.3 Use Cases

2.3.1 Admin Login:
Admin Login
Description
Specifications
Priority
UC-01
Log in required for Admin.

Title:
Log in.
Actors
Administrator
Intent:
Describe Administrator interacts with the system and logged in.
Preconditions
Administrator log in to the system
Post-Conditions
Administrator performs several tasks
Main Scenario
Administration open login page
1. Types password
2. Email Address
Alternate Scenario
1.Incorrect password
2.Login fail
3. System displays a message that (invalid User id, User id
already exist)
Uses/Extends
N/A
Frequency
Frequent
Issues
N/A
High
(Table 2.1)
Digital Shop
Page 11 of 55
2.3.2 Administrator Manage Stock:

Administrator manage stock
Description
Specifications
UC-02
Administrator must be able to manage products.

Title:
Stock management.
Actors
Administrator
Intent:
Describe Administrator interacts with the system during add data
relating stock.
Preconditions
Administrator login to the system
Post-Conditions
Administrator interacts with system to manage stock
Main Scenario
Admin manage stock by
1. Add stock
2. Administrator press save button
3. Data is saved
Alternate Scenario
1- Wrong User id entered (duplicate User id)
2- System displays a message that (invalid User id, User id
already exist)
Uses/Extends
N/A
Frequency
Frequent
Issues
N/A
Priority
High
(Table 2.2)
Digital Shop
Page 12 of 55
2.3.3 Administrator Manage Clients:

Administrator manage clients
Description
Specifications
UC-03
Administrator must be able to manage clients.
Title:
Administrator manages clients.
Actors
Administrator
Intent:
Administrator interacts with the system for client management.
Preconditions
Administrator login.
Post-Conditions
Administrator interacts with system to manage clients
Main Scenario
1- Administrator view clients.
2- Deletes clients.
Alternate Scenario1
1- No clients will show
Uses/Extends
N/A
Frequency
Frequent
Issues
N/A
Priority
High
(Table 2.3)
Digital Shop
Page 13 of 55
2.3.4
Administrator Manage Orders:

Administrator manage orders
Description
Specifications
UC-04
Administrator must be able to manage orders

Title:
Administrator mange orders.
Actors:
Administrator
Intent:
Describe Administrator interacts with the system during order
management.
Preconditions
Administrator login.
Orders already recorded.
Post-Conditions
Administrator manages orders placed by clients after login
Main Scenario
Administrator login to Manage orders.
Administrator view orders
Deletes orders.
Alternate Scenario1
1- The first time the Administrator logged in to the system and no
orders exists.
2- The system displays a message welcome the Administrator and
tells him that no data is recorded in the system yet.
Frequency
Frequent
Priority
High
(Table 2.4)
Digital Shop
Page 14 of 55
2.3.5 Administrator Manage Reports:

Report generation
Description
Specifications
UC-05
Administrator must be able mange report generation.

Title:
Report management.
Actors
Administrator
Intent:
Describe Administrator interacts with the system to manage automated
reports generation.
Preconditions
Post-Conditions
Administrator interacts with system and manage reports
Main Scenario
1- Stock in
2- Stock out
3- Administrator press save button
4- Data is saved.
Alternate Scenario
1.Incorrect information
Uses/Extends
N/A
Frequency
Frequent
Priority
High
(Table 2.5)
Digital Shop
Page 15 of 55
2.3.6 Administrator Manage Blog:

Blog management
UC-06
Description
Administrator must be able to manage blog.
Specifications
Title
Blog management.
Actors
Administrator
Intent:
Describe Administrator interacts with the system during blog
management
Preconditions
Post-Conditions
Administrator interacts with system and manages blog
Main Scenario
Admin can:
1. Add blog
2. View blog
3. Modify blog
4. Delete blog
Alternate Scenario
1.Incorrect information
2.Error message
Uses/Extends
N/A
Frequency
Frequent
Priority
High
(Table 2.6)
Digital Shop
Page 16 of 55
2.3.7 Client Login:

Client login
Description
Specifications
UC-07
Administrator must be able to log in.

Title:
Client log in.
Actors:
Client
Intent:
Describe Administrator interacts with the system for logging in.
Preconditions
Clients opens the login page.
Post-Conditions
Client login
Main Scenario
1. Clients enter email and password to log in.
2. Log in successful.
Alternate Scenario1
Error message shows.
Frequency
Frequent
Priority
High
(Table 2.7)
Digital Shop
Page 17 of 55
2.3.8 Add Product To Cart:

Product management
UC-08
Description
Client visits the page and selects the product to purchase.
Specifications
Title:
Client manage products to be purchase.
Actors
client
Intent:
Describe Client interacts with the system during product purchasing.
Preconditions
client login to the system
Post-Conditions
Client mange products to be purchased
Main Scenario
1. Client opens the product page
2. View the product
3. Add products to the cart
4. Delete products from cart.
Alternate Scenario
1.Login fails
2.Error message
Uses/Extends
N/A
Frequency
Frequent
Priority
High
(Table 2.8)
Digital Shop
Page 18 of 55
2.3.9
Admin Proceed Order:

Admin proceed order
UC-9
Description
Admin should be able to proceed order.
Specifications
Title:
Administrator proceeds order.
Actors
Admin
Intent:
Describe Administrator interacts with the system to proceed order.
Preconditions
Admin login to the system
Post-Conditions
Admin after login ,proceeds orders
Main Scenario
1. Admin opens the order page
2. View the order
3. Proceed order
Alternate Scenario
1.Incorrect information provided
2.Do not proceed orders
Uses/Extends
N/A
Frequency
Frequent
Priority
High
(Table 2.9)
Digital Shop
Page 19 of 55
2.3.10 Services :
UC-10
Services
Description
Specifications
Clients will be able to avail services.

Title:
Services
Actors:
client
Intent:
Describe client interacts with the system to avail services.
Preconditions
Client opens the page and logs in.
Post-Conditions
Avail services
Main Scenario
1. Client can avail any service related to product
2. Description
3. Warranty claim
4. Pictures
5. Shipment
Frequency
Frequent
Priority
High
(Table 2.10)
Digital Shop
Page 20 of 55
2.3.11 Email Alerts:

Email Alerts
Description
Specifications
Priority
UC-11
Clients get email alerts for their registration and product shipment.
Title:
Email alerts
Actors
client
Intent:
Describe clients interacts with the system to get email alerts.
Preconditions
Client should be registered
Clients opens emails.
Post-Conditions
Clients gets email alerts
Main Scenario
1- Client log in to mail.
2- Checks the mail
Alternate Scenario1
1. No mail found related to product shipment and registration
Uses/Extends
N/A
Frequency
Frequent
Issues
N/A
High
(Table 2.11)
Digital Shop
Page 21 of 55
2.3.12 Delivery Status:
Delivery status
UC-12
Description
Clients can check delivery status of their ordered product.
Specifications
Title:
Delivery status
Actors
Client
Intent:
Describe client interacts with the system to check delivery status.
Preconditions
Client log in to system.
Post-Conditions
Clients can check delivery status of their ordered products
Main Scenario
1- Client logs to system
2- Checks the delivery status of desired product.
Alternate Scenario
1-No product ordered
2-No status
Uses/Extends
N/A
Frequency
Frequent
Issues
N/A
Priority
High
(Table 2.12)
Digital Shop
Page 22 of 55
2.3.13 Invoice:
UC-13
Invoice
Description
Specifications
Priority
System generate automated invoices for client feasibility.

Title:
Automated invoice.
Actors
Client
Intent:
Client interacts with the system to generate automated invoice and to
print it.
Preconditions
Client login.
Post-Conditions
Clients gets invoice
Main Scenario
1- Client log in
2- Client purchase product
3- Generate automated invoice
4- Print invoice
Alternate Scenario
1- No information provided
2- No invoice
Uses/Extends
N/A
Frequency
Frequent
Issues
N/A
High
(Table 2.13)
Digital Shop
Page 23 of 55
2.3.14 Logout:
Logout
Description
UC-14
Logout
Title:
Logout.
Specifications
Priority
Actors:
Administrator/client
Intent:
Describe Administrator /client interacts with the system during Logout
Preconditions
User login.
Post-Conditions
User logs out
Main Scenario
User Press Logout.
User logout successfully from system
Alternate Scenario1
User Press Logout
Unsuccessful Logout Error message displayed
Uses/Extends
N/A
Frequency
Frequent
High
(Table 2.14)
Digital Shop
Page 24 of 55
CHAPTER 3
DESIGN
CHAPTER-3
DESIGN
3.1 UML Diagrams
In the field of software engineering, the Unified Modeling Language (UML) is the
standardized visual specification language for object modeling. UML is a generalpurpose modeling language that includes a graphical notation used to create an abstract
model of a system, referred to as a UML model.
UML is not a method by itself; however, it was design to be compatible with the leading
object-oriented software development methods to its time. Since UML has evolved,
some of these methods have recast to take advantage of the new notation, and new
methods have created based on UML. The best known is Rational Unified Process
(RUP). There are many other UML-based methods like abstraction method, dynamic
systems development method and others designed to provide most specific solutions or
achieve different objectives.
It is very important to distinguish between the UML model and the set of diagrams of
a system. A diagram is a partial graphical representation of a systems model.
UML diagrams represent three different views of a system model:
3.1.1 Functional Requirements View
Emphasizes the functional requirements of the system from the users point of view e.g.
use case diagrams.
3.1.2 Static Structural View
Emphasizes the static structure of the system using objects, attributes, operations and
relationships e.g. class diagrams.
3.1.3 Dynamic Behavior View
Emphasizes the dynamic behavior of the system by showing collaborations among
objects and changes to the internal states of objects e.g. sequence diagrams, activity
diagrams and state diagrams.
Digital Shop
Page 26 of 55
3.2 Class Diagram

A class diagram is a type of static structure diagram that describes the structure of a
system by showing the systems classes, their attributes and the relationships between
the classes.
(Fig 3.1)
Digital Shop
Page 27 of 55
3.3 Sequence Diagram
3.3.1 Admin Login :
Digital Shop
Page 28 of 55
3.3.2 Admin Client Management:
3.3.3 Stock Management:
Digital Shop
Page 29 of 55
3.3.4 Blog Management:
3.3.5 Services Management:
Digital Shop
Page 30 of 55
3.3.6 Report Management:
3.3.7 Client Registration:
Digital Shop
Page 31 of 55
3.3.8 Client Login:
3.3.9 Client Order:
Digital Shop
Page 32 of 55
3.3.10 Client Products:
3.3.11 Cart Management:
Digital Shop
Page 33 of 55
3.3.12 Client Invoice:
Digital Shop
Page 34 of 55
3.4 Domain Model
Digital Shop
Page 35 of 55
CHAPTER 4
TESTING
CHAPTER-4
TESTING
4.1 Testing
In this section we will test
1.
2.
3.
4.
5.
6.
4.1.1
Admin Login
Client login
Check home page
Delivery status
Automated invoice
Email Alerts
Check Login Page:

Test Engineer: Muhammad Shakeel Abbas
Test Case ID: TC-1

Related UC/FR/NFR UC-01
Date: 09-08-2014
Purpose: Checking Login Page.
Pre-Req: User data already recorded.
Test Data: Email: paki.monda@gmail..com
Password: admin
Steps:
1.
2.
3.
4.
5.
visit Login Page

enter email
enter password
click login
Redirected to home page.
Status: Pass
(Table 4.1)
Digital Shop
Page 37 of 55
4.1.2
Client Login:
Test Case ID: TC-2
Date: 09-08-2014
Purpose: Client login.
Pre-Req: Open login page.
Test Data: Email: paki.monda@yahoo.com
Password: admin
Steps:
1.
2.
3.
4.
visit Login Page

enter email
enter password
click login
Status: Pass
(Table 4.2)
4.1.3 Testing Home Page:
Test Case ID: TC1
Related UC/FR/NFR UC
Date: 07-08-2014
Purpose: Testing Home page
Pre-Req: Browse web page
Test Data: Checked menu bars, navigation buttons, icons,
pictures
Steps: Steps to carry out the test. See step formatting
rules below.
1. Checked menu bar
2. Navigation bar
3. Buttons
Status: Pass
(Table 4.3)
Digital Shop
Page 38 of 55
4.1.4 Delivery Status Page:

Test Case ID: TC-4
Date: 09-08-2014
Purpose: Check delivery status page.
Pre-Req: Client must be login.
Test Data: login
Steps:
1. Login.
2. Visit status page.
3. Check status
Status: Pass
(Table 4.4)
4.1.5 Email Alerts:
Test Case ID: TC-6
Date: 09-08-2014
Purpose: Email alerts
Pre-Req: Client must be registered
Test Data: Log in to the mail
Steps:
1. Visit the mail

2. Mail in the inbox from shipping company
to show the delivery status.
Status: Pass
(Table 4.5)
Digital Shop
Page 39 of 55
4.1.6 Automated Invoice:

Test Case ID: TC-7
Date: 09-08-2014
Purpose: Automated invoice
Pre-Req: Client must be login
Test Data: login
Steps:
1. Login
2. Browse page
3. Print invoice
Status: Pass
(Table 4.6)
Digital Shop
Page 40 of 55
CHAPTER 5
CONCLUSION &
FUTURE WORK
CHAPTER-5
CONCLUSION & FUTURE WORK
E-commerce is progressing rapidly and to compete with the current situations/time we
need such things like Websites to provide services with easiness while sitting at home.
We have tried our best to fulfill our project by keeping in mind both the parties
(Businessman & Customers). We are hopeful our work will be in favor of both parties.
Currently we have some limitation of sending and receiving payments via Internet, In
future when these services will be available, we will upgrade our project to provide
these facilities too.
Digital Shop
Page 42 of 55
USER MANUAL
USER MANUAL
User Manual
a. Screen Shot I
Front Page (Fig 5.1)
b. Screen Shot II
Product Info Page (Fig 5.2)
Digital Shop
Page 44 of 55
c. Screen Shot III

User Login (Fig 5.3)
d. Screen Shot IV
User Registration (Fig 5.4)
Digital Shop
Page 45 of 55
e. Screen Shot V
Services Page (Fig 5.5)
f. Screen Shot VI
Blog Page (Fig 5.6)
Digital Shop
Page 46 of 55
g. Screen Shot VII

Admin Login (Fig 5.7)
h. Screen Shot VIII

New Product Page (Fig 5.8)
Digital Shop
Page 47 of 55
i. Screen Shot IX
Order Page (Fig 5.9)
j. Screen Shot X
Add Services (Fig 5.10)
Digital Shop
Page 48 of 55
k. Screen Shot XI
Account Registration Email (Fig 5.11)
l. Screen Shot XII

Order Successfully Placed Email Alert (Fig 5.12)
Digital Shop
Page 49 of 55
m. Screen Shot XIII

New Order Email Alert to Admin (Fig 5.13)
n. Screen Shot XIV

Order Successfully Update (Fig 5.14)
Digital Shop
Page 50 of 55
REFERENCES
REFERENCES
W3School. PHP 5 Tutorial: http://www.w3schools.com/php/, [Mar. 4, 2014].
W3School. SQL Tutorial: http://www.w3schools.com/sql/, [Mar. 4, 2014].
Kevin
Skoglund.
PHP
with
MySQL
Essential
Training:
http://www.lynda.com/MySQL-tutorials/PHP-MySQL-Essential-Training/1190032.html, [Aug. 11, 2013].
Jon Peck. Object-Oriented Programming with PHP: http://www.lynda.com/PHPtutorials/Object-Oriented-Programming-PHP/107953-2.htm, Apr 10, 2013[Jul. 8,
2013].
Shophive. Online Shopping in Pakistan: http://www.shophive.com/, [Nov. 16, 2013].
Digital Shop
Page 52 of 55
APPENDICES
Appendix (A)
Responsive Design
Our Web Design is responsive it can easily adjust itself according to the device
on which website will be open. E.g. Windows Browsers, Mobile Browsers and
Tablets Browsers etc.
Digital Shop
Page 53 of 55
Restrictions
Clients are not allow to access admin panel; also, unfilled form will not
submitted.
Security on Different Levels

Users login credentials are encrypted and their information is secured through
their credentials. In addition, our website will use SSL and will load using
HTTPS Hyper Text Transfer Protocol Secure.
Performance
Our website will be loading fast, all the Images/Graphics will be processed
on server than it will took less time to load on client browsers.
Digital Shop
Page 54 of 55
Accuracy
All bills calculations are automated by the system. Reports will be accurate than
manual system, admin can get report anytime.
Usability
As our project is not limited only on PC, so clients have facility to access it
while traveling through their mobiles or tablets etc.
Digital Shop
Page 55 of 55

Documentation PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Documentation PDF

Încărcat de

Drepturi de autor:

Formate disponibile

DIGITAL SHOP

Department of Information Technology

Muhammad Shakeel Abbas

Muhammad Shakeel Abbas _________________

MUHAMMAD IMRAN FAIZI (Supervisor) ___________________

PROJECT COMPLETION CERTIFICATE

MUHAMMAD IMRAN FAIZI (Supervisor)

Head Department of Information Technology,

LIST OF TABLES, FIGURES AND APPENDIXES ----------------------------- VIII

1.1 Introduction -------------------------------------------------------------------

1.2 Background and Existing System ------------------------------------------

1.2.1 Problem in Existing System ------------------------------------------

1.3 Proposed System--------------------------------------------------------------

1.3.1 Main Modules ----------------------------------------------------------

1.3.1.1 Admin Modules -----------------------------------------------

1.3.1.2 Client Modules ------------------------------------------------

1.3.1.3 Search Modules -----------------------------------------------

1.4 Expected Outcomes ----------------------------------------------------------

1.5 Tools & Technologies -------------------------------------------------------

1.6 Activity Index ----------------------------------------------------------------

CHAPTER 02: REQUIREMENT ANALYSIS ------------------------------------

2.1 Requirement Analysis ----------------------------------------------------------

2.1.1 Functional Requirement-------------------------------------------------

2.1.2 Non-Functional Requirement ------------------------------------------

2.2 Use Case Diagrams ------------------------------------------------------------

2.3 Use Cases ----------------------------------------------------------------------

2.3.1 Admin Login----------------------------------------------------------

2.3.2 Administrator Manage Stock---------------------------------------- 12

2.3.4 Admin Manage Order -----------------------------------------------

2.3.5 Admin Manage Report ----------------------------------------------

2.3.6 Admin Manage Blog --------------------------------------------------- 16

2.3.8 Add Product To Cart --------------------------------------------------- 18

2.3.11 Email Alerts -----------------------------------------------------------

2.3.12 Delivery Status -------------------------------------------------------- 22

2.3.14 Logout -----------------------------------------------------------------

CHAPTER 03: DESIGN & UML --------------------------------------------------- 25

3.1.3 Dynamic Behavior View -----------------------------------------------------

3.2 Class Diagram ------------------------------------------------------------------------- 27

3.3.1 Admin Login Sequence -----------------------------------------------

3.3.2 Admin Client Management Sequence ------------------------------- 29

3.3.4 Blog Management Sequence -----------------------------------------

3.3.5 Services Management Sequence -------------------------------------

3.3.6 Report Management Sequence ---------------------------------------

3.3.7 Client Registration Sequence ----------------------------------------

3.3.8 Client Login Sequence ------------------------------------------------ 32

3.3.10 Client Cart Product Sequence ---------------------------------------

3.3.11 Cart Management Sequence -----------------------------------------

3.3.12 Client Invoice Sequence ---------------------------------------------

3.4 Domain Model-------------------------------------------------------------------------

CHAPTER 04: TESTING ----------------------------------------------------------

4.1 Testing ------------------------------------------------------------------------------

4.1.1 Check Login Page ----------------------------------------------------------

4.1.2 Client Login ------------------------------------------------------------------

4.1.3 Testing Home Page ----------------------------------------------------------

4.1.4 Delivery Status ---------------------------------------------------------------- 39

4.1.6 Automated Invoice -----------------------------------------------------------

CHAPTER 05: CONCLUSION & FUTURE WORK

5.1 Conclusion and Future Work ----------------------------------------------------

USER MANUAL -------------------------------------------------------------- -------

Responsive Design -------------------------------------------------------------------

Security on different levels ---------------------------------------------------------

Performance ------------------------------------------------------------------ --------