Final Year Project Report ON OPEN E- MARKET BS-COMPUTER SCIENCE Submitted by 1

Final Year Project Report
ON
OPEN E- MARKET
BS-COMPUTER SCIENCE

Submitted by
1. Deepak Raj (24505)
2. Faraz Hussain (24581)
3. Jannat Qazi (27090)

Project Advisor
Dr. Aarij Mahmood Hussaan

March, 2018

Faculty of Engineering, Sciences and Technology
IQRA University, Karachi

ACKNOWLEDGMENT

First of all thanks to Almighty Allah, He enabled us to complete this project; we would like to appreciate the guidance provided to us by our project coordinator Sir Mansoor Ibrahim and project supervisor Dr. Aarij Mahmood Hussaan, and they provided us all technical assistance which made it possible to complete this project.

INTRODUCTION TO GROUP MEMBERS

1. Jannat Qazi (27090)
(Designer & Data Base Developer)
Immediate Contact: 0333-1367257
[email protected]
2. Faraz Husain (24581)
(Programmer)
Immediate Contact: 0334-3093463
[email protected]
3. Deepak Raj(24505)
(Tester AND Developer)
Immediate Contact: 03323928000
[email protected]

Abstract
Open e Market (OEM) is free open source platform for online stores. It is providing reliable foundation for build online store. It is allowing to set a advanced user privileges and separate access for users and customers. Open e Market is efficiently working project where user can add multiple stores and products accordance with categories already given by the admin in dashboard. This project manages the multiple stores of one user; each user has a separate profile store where he can add banner and logo, changes the theme colour. Open e Market project allows admin to change the order status. The main abject of this project is to help the users to make good online business. OEM project is the flexible and easy to use and understandable for doing shopping and online business, customer can see the all stores of multiple users and products at the same time.

SUMMRY
Open e Market (OEM) is proposed to make easy online shopping and business. Currently there are many online shopping web stores, but this projects allows you to make your own web store and add products accordance with given categories by admin in dashboard. This project can be used widely by many users at same time. Open e Market allows user to create multiple stores and multiple products there. Customers can see all products of store; customer can see the all stores sorted with respect to categories. It supports the customers for buying products and sellers for creating stores for business purpose. Admin can manually see the status of order and change it. After buying the product the customers can give the ratings and feedback on product, which can be seen to user of that store. User can add banner, logo of store and change the theme colour, then user can add image, brand name and description of product in store, user can set the price for product and discount on it. The main aim of this project is to make easy home shopping and business. Admin can check the order and see the selling of all sellers. Where can order the product by giving his information of mobile number, name, email and address.

LIST OF ACRONYMS

1. OEM (open e market)
2. OOP(object oriented programming)
3. SDLC ( software development life cycle )
4. PHP (personal home page )
5. XAMPP ( cross platform apache my SQL PHP and Perl)
6. CSS (cascading style sheet)
7. HTML (hyper text markup language)
8. i.e. (that is)
9. e.t.c
10. SD ( software development)
11. SDM ( software development model)
12. FR (functional requirement )
13. NFR (non function requirement)
14. DB (data base )
15. SE (software engineering)

OVER ALL STRUCTURE OF REPORT
Chapter 1:
In this chapter the introduction part of the complete report where we can introduce our project we can define the object of open e market as well as the scope of the project what types of problem we face in the project and this solution as well. We can also define the relevance domain which we use in our project which is database or software engineering part.
Chapter 2:
Chapter 2 recover the professional consideration for the project here is cover complete public interest of then online shopping and create easy online store. Also cover the ethical concentrations for the project manager.
Chapter 3:
In this chapter we cover the requirement analysis of the project we can cover here user requirement function requirement, performance constrain interface requirement in the interface requirement we also cover the area of user interface hardware interface or software interface.
Chapter 4:
chapter 4 cover the project plan here we can cover all the phases of project which we can phase also mention the Gantt chart for complete project ,also cover the area of project expectation where we can define the expectation of the project there are two different expectation of the project 1 is primary objective and the other is secondary objective .
Chapter 5:
in chapter 5 we cover the all design and development of the project we can cover the initial design part which is initial data flow diagram and layer architecture also cover the branding which is color schema and icons one the development phase we can cover the development tool which tool we use here and so on also cover the model diagram and problem which we phase and their relevant solution
Chapter 6:
Chapter 6 cover the all non functional requirement of the project some of the non function requirement is given blow:
? Accuracy Requirements
? Auditing and Reporting Requirements
? Backup and Recovery Requirements
? Capacity Requirements
? Compatibility Requirements
? Concurrency Requirements
? Configurability Requirements
? Error-Handling Requirements
? Legal and Regulatory Requirements
? Licensing Requirements
? Localizability Requirements
? Maintainability Requirements
? Performance Requirements
? Precision Requirements
Chapter 7:
Chapter 7 covers all the structure of the project simulation that how the open e market can work also completes the database design description.
Chapter 8 :
Chapter 8 cover the complete interface design which is similar as chapter 7 also cover the application testing which have logical testing system testing and function testing.
Chapter 9:
In chapter 9 we can cover all the testing which we can perfume in our project which is load testing and unit testing in unit testing we also cover the client side testing and server side testing.
Chapter 10:
In chapter 10 cover all the evolution and conclusion of the project as well as cover the future. In work. in evolution we can cover with the help of diagram and the conclusion cover for open e market is that it is very convenient user privilege and relatively cheap. You are able to create multiple stores as well as you can visit the stores and buy which you want from the comfort of your home; which means that you do not have to worry about time money stress or any restrictions .you can place your order and get the products which you really want . Future work cover like as all projects which are software based or online web based, in our project there are many certain parts are having scope for further development. A list of future enhancements and updates are maybe endless. Project maybe enhanced with more themes and user privileges. More enhanced selling report to admin. More secure payment transaction system.
Estimation of the project
We can also cover the estimation of the project with the help of table.
Content of figure:
Figures show all the description which I mention in our reports
References:
At the end we give the reference of where we can collect the data which is help full for our report and project

CONTENTS:
ACKNOWLEDGEMENTS…………………………………………………………………………………………2INTRODUCTIONS TO GROUP MEMBERS……………………………………………………………….3
ABSTRACT……………………………………………………………………………………………………….4
SUMMARY ……………………………………………………………………………………………………………..5
LIST OF ACRONYM…………………………………………………….6
STRUCTURE OF REPORT…………………………………………………….….9
TABLE OF CONTENTS…………………………………………………………………………………………….12
CHAPTER ONE:
1 -INTRODUCTION…………………………………………………………………………………….13
1.1- OBJECTIVE………………………………………………………………………………13
1.2- SCOPE OF THE PROJECT …………………………………………………………………13
1 .3 PROBLEM STATEMENTS AND SOLUTION …………………………………13
STATEMENT …………………………………………………………………………………….13
SOLUTION………………………………………………………………………………………13
1.4- RELIVANCE DOMIN ……………………………………13
1.4.1 DATABASE…………………………………………………………………14
1.4.2 SOFTWARE ENGINERING / DEVLOPMENT ……………………………14
CHAPTER TWO:
2 -PROFFESSIONAL CONSIDRATION ………………………………………….15
2.1- PUBLIC INTREST …………………………………………………15
2.2 – ETHICAL CONSIDERATIONS…………………………………………………………………..15
CHAPTER THREE:
3-REQUIREMENTS ANALYSIS…………………………………16
3.1 USER REQUIREMENTS/ USE CASES ……………………………………………………….16
3.2 FUNCTIONAL REQUIREMENTS …………………………………………………………………17
3.3 PERFORMANCE CONSTRAINTS………………………………………………………………..20
3.4 QUALITY REQUIREMENTS…………………………………………………………………….20

3.5 INTERFACE REQUIREMENTS ………………………………………………………………….20
3.5.1 USER INTERFACE………………………………………………………………………………………… 21
3.5.2 HARDWARE INTERFACE …………………………………………………………………………………….21
3.5.3 SOFTWARE INTERFACE……………………………………………………………………………………….. 21
CHAPTER FOUR:
4-PROJECT PLAN…………………………………………………………………………………22
4.1-PHASES……………………………………………………………………………………………………………..22
4.2 – GANTT CHART…………………………………………………………………………………………….23
4.3- PROJECT EXPECTATIONS………………………………………………………………………….24
4.3.1 – PRIMARY OBJECTIVE ……………………………………………………………………………..24
4.3.2 – SECONDRY OBJECTIVE………………………………………………………………………………………24
CHAPTER FIVE :
5- DESIGN AND DEVLOPMENT……………………………………………………………25
5.1- INITIAL DESIGN………………………………………………………………………25

5.1.1- INITIAL DATA FLOW DIAGRAM………………………………………………….25

5.1.2 Layer ARCHITECTURE …………………………………………………………….26
5.2 – DEVLOPMENT……………………………………………………………………27
5.2.1 php my admin /SQL server: ………………………………………………………………27
5.3- DESIGN…………………………………………………………………………………27
53.1 BRANDING………………………………………………………………………………………..27
? COLOR SCHEME
? ICONS
5.4-MODEL DIAGRAM…………………………………………………………..28
5.5 -DEVELOPMENT TOOLS: ……………………………………………………………………………… 28
5.6-PROBLEM, ISSUE FACED AND OPTIMISSION.29

CHAPTER SIX:
6- NON-FUNCTIONAL REQUIREMENTS……………………………………………….30
CHAPTER SEVEN:
7- PROJECT STRUCTURE ……………………………………………………32
7.1 -PRJECT SIMMULATION…………………………………………………32
7.2- DATA BASE DESIGN………………………………………………………………44
CHAPTER EIGHT:
8 -USER INTERFACE ……………………………………………………………………………………….51

8.1. SYSTEM INTERFACE OVERVIEW: ………………………………………………………………… 51
8.2. APPLICATION TESTING: …………………………………………………..…….51
CHAPTER NINE:

9 -TESTING ……………………………………………………………………………………..53
9.1 – LOAD TESTING……………………………………………………………………………………….53
9.2 – UNIT TESTING ……………………………………………………………………………………..54
9.2.1 – Client-Side ……………………………………………………………………………………………………………….54
9.2.2 – Server-Side ……………………………………………………………………………………………54
CHAPTER TEN:
10 -EVALUATION AND CONCLUSION…………………………………………….55
10.1 – EVALUATION………………………………………………………………………………………55
10.2 – CONCLUSION …………………………………………………………………………………………56
10.3– FUTURE WORK…………………………………………………………………………….56
• ESTIMATED TIME FRAME REQUIRED FOR VERIOUS STAGE OF PROJECT IMPLIMENTATION……………………………………………….57
TABLES OF FIGURES ……………………………………………………………………………………………58-60
CHAPTER ONE
1. INTRODUCTION
1.1 Objective
The main object of the project is to help the user making success business online.
This will be flexible, easy and understandable to users for doing shopping and online business
Separate access to all. This will allow to set advanced user privileges.
1.2 scope
Our project scope is to provide the facility to people’s who love to shopping different type of website. We design oem application to provide to make easy online shopping and business and create your own store.
1.3 problem Statement and Solution
STATEMENT
We create this application because we don’t need to go outside for shopping and waste much time for this and also we can create our own store here and most people cannot go outside like office timing, meetings family restrictions also for women’s that cannot go outside they can order online from home and easily can get which they actually want.

SOLUTION
Therefore, in order to overcome this problem we decided to build an application that can enable us to make online shopping and business from home and we try to get all stores in one place any type of product they can get from our application which is OEM.

1.4. RELEVANCE OF DOMAINS
1.4. 1-DATABASE
I will try to convince you that using SQL Server Data Tools (SSDT) Database Projects is a really good idea. Recently during a project I have been advocating that it indeed is worth the effort. It certainly applies to any type of database.
1.4.2- SOFTWARE ENGINEERING / DEVLOPMENT
Many different software engineering methods are available but we choose SDLC because software development life cycle is best for software development applications and our application can design better by this method.

CHAPTER TWO
2. PROFESSIONAL CONSIDERATIONS
2.1 PUBLIC INTREST
Why the public interest for online shopping?
Some of the numerous advantages and benefits, more and more people say they prefer online shopping over conventional shopping these days. It’s important to understand the psyche of the online shopper.
8 -Reason public like to shop online
? Convenience
? Better price
? Variety
? Fewer experience
? Comparison of price
? Crowds
? Compulsive shopping
? Discreet purchases
Ref: 1
2.2 ETHICAL CONSIDERATIONS
There are ethical considerations when doing any long form project like this one, which I will be working on over the next couple of months, but this project is unique in the sense that there is the added worry that the people I’m using as my case studies will actually forget that they have given me consent.
? Informed Consent
? Security
? Equipment / tools

CHAPTER THREE:
3.REQUIREMENTS ANALYSIS
3.1 USER REQUIREMENTS/ USE CASES

Admin/user

Use-Case Name: Home page
Use-Case Description: This use case lets the user/administrator view the home page which has different categories when they first run the application.
Primary Actor: Admin/User
Precondition: Run the application.
Post-condition: The user successfully runs the application and is able to view the home page with the different categories.
Basic Flow:
? Run the application
? View the home page
? Browse the categories

Customer/seller

Use-case name: Select category
Use-case description: This use case details the category for selecting a process where the user can browse through the different categories and select one category to view items.
Primary actor: customer/seller
Precondition: The customer/seller successfully runs the application to view the home page and browse different categories.
Post-condition: The user successfully selects a category to view items in a particular category.
Admin/seller

Use-case name: add banner
Use-case description: This use case details the admin can add banner ..
Primary actor: admin
Precondition: admin can add or delete banner for the system
Post-condition: nil.

Admin/seller/customer

Use-case name: login
Use-case description: User will Sign in to their id by giving id password
Primary actor: customer/seller/admin

Admin/seller/customer

Use-case name: logout
Use-case description: all actor will Sign out to their id by giving id password
Primary actor: customer/seller/admin
Precondition: Actors should have sign up their account.
Customer

Use-case name: order product
Use-case description: customer can order the product
Seller
Use-case name: add store
Use-case description: actor will add store
Primary actor: seller
Precondition: Actors should have sign up their account.
Admin

Use-case name: add / removed category
Use-case description: actor will add / removed category
Primary actor: admin
Precondition: Actors should have sign up their account.
3.2 FUNCTIONAL REQUIREMENTS
? System enable the user to view store as well as products, can create their account, login to the system to add their stores.
? System enable the customer to view store as well as products, can create their account, login to the system and place there order.
? System displays the stores with their products that are in cart, the individual item, prices and the total payment amount.
? Admin can view, create, edit and delete the stores.
? User can update information (description, photo, banner, products etc) of store.
? Admin can update the categories
? Admin can approve the request of new user
? System enable the customer to add cart, can create their account, login to the system to add their stores.
? System enable the e customer to view feedback as well as give feedback of the product can create their account, or login to the system to add their stores.
? System enables the user to give rating for the product with the help of login or register their account.
3.3 PERFORMANCE CONSTRAINTS
Performance of this application is a major concern to us while in development phase we mostly focus on the performance of the application to perform well according to the customer’s expectations and fulfil the requirements for which it has been developed.
3.4 QUALITY REQUIREMENTS
The application is very simple and really fast and better. We will ensure that no hangs will be tolerated in the working of the application.

3.5 INTERFACE REQUIREMENTS
3.5.1 USER INTERFACE
The interface of application is very easy to use it has been designed according to a common user or a beginner to the pc/mobile phone user.

3.5.2 HARDWARE INTERFACE
Windows PC.
3.5.3 SOFTWARE INTERFACE
? WINDOWSOS (7/ 8/10).
? PHP MY ADMIN
? BOOTSTRAPE
? XAMMP
? SQL server.

CHAPTER FOUR :
4-PROJECT PLAN
4.1PHASES.
Our project lifecycle starts from the initiation phase in which we gather the information or data regarding to our project after that we plan to how to complete each phase of our project in order to complete the project before the deadline of the project. After that we execute those plans and move to the closure phase.

Figure 1

4.2 – GANTT CHART

Figure 2

4.3- PROJECT EXPECTATIONS
4.3.1 – PRIMARY OBJECTIVE
? System enable the user to view store as well as products, can create their account, login to the system to add their store.
? System enable the customer to add cart, can create their account, login to the system to add their stores.
? System enable the e customer to view feedback as well as give feedback of the product can create their account, or login to the system to add their stores.
? System enables the user to give rating for the product with the help of login or register their account.

4.3.2 – SECONDRY OBJECTIVE

? All data of the application should be stored in SQL database therefore SQL management system must be install in host computer.

? System should have maintainability easy to maintain so in future we can easy make new changes.

? System performance and response time should be fast.

? System should have usability easy to use for new users.

? System should have expandability in future if need to upgrade the system.

CHAPTER FIVE :
5- DESIGN AND DEVLOPMENT
.5.1- INITIAL DESIGN

5.1.1- INITIAL DATA FLOW DIAGRAM

Figure 3
5.1.2 -LAYER ARCHITECTURE:
We use here three layer architecture. Because our application work as in web server, application server and database server.

Figure 4
5.2 – DEVLOPMENT
5.2.1 PHP My admin /SQL server:
We use PHP my admin in this application we use OOP concept we chose PHP language in development of project we use JQUERRY and bootstrap for navigations html and CSS to style application interface. And also use SQL server management system for database.
5.3 -DEVELOPMENT TOOLS:
PHP My admin
Bootstrap
XAMMP
Text sublime
JQUERRY.
HTML
CSS.
Sublime Text:
Sublime Text is a proprietary cross-platform source code editor with a Python application programming interface (API). It natively supports many programming languages and mark-up languages, and functions can be added by users with plugging, typically community-built and maintained under free-software licenses.
Bootstrap:
Bootstrap is a popular web development framework used for creating websites. It was developed by a team at Twitter and has been an open source project since 2011. The Bootstrap framework includes CSS styles, JavaScript libraries, and HTML files. Bootstrap provides a way for developers to easily build responsive websites rather than designing them from scratch
5.4- DESIGN
53.1 BRANDING
? COLOR SCHEME
We chose different color theme in our project but the basic and top level we chose color blue and white
Figure 5
? ICONS
We choose different icon which we can show in CSS folder or also put a detail of icon in this folder

5.5-MODEL DIAGRAM

Figure 6
5.6-PROBLEM, ISSUE FACED AND OPTIMISSION
First we wanted to add categories by user. Then we observed it may be the failure of project, then decided all categories must be added already by Admin in dashboard, because we tried to add categories by user. We have so many incorrect, misunderstood categories were there, i.e. clothes, Clothes, Cloths, Clouhts, and may more like that. Then we have decided to make it clear and add all possible categories by admin. And the record of orders is also maintaining, admin can also check orders and change status.

CHAPTER SIX:
6- NON-FUNCTIONAL REQUIREMENTS
All data of the application should be stored in SQL database therefore SQL management system must be install in host computer.

System should have maintainability easy to maintain so in future we can easy make new changes.

System performance and response time should be fast.

System should have usability easy to use for new users.

System should have expandability in future if need to upgrade the system.
LIST OF SOME NON FUNCTIONAL REQUIRMENT

? Accessibility Requirements
? Accuracy Requirements
? Auditing and Reporting Requirements
? Backup and Recovery Requirements
? Capacity Requirements
? Compatibility Requirements
? Concurrency Requirements
? Configurability Requirements
? Error-Handling Requirements
? Legal and Regulatory Requirements
? Licensing Requirements
? Localizability Requirements
? Maintainability Requirements
? Performance Requirements
? Precision Requirements
? Redundancy Requirements
? Reliability Requirements
? Scalability Requirements
? Security Requirements
? Stress Requirements
? Supportability Requirements
? Throughput Requirements
? Etc, etc, etc

CHAPTER SEVEN:
7- PROJECT STRUCTURE
7.1 -PROJECT SIMMULATION
Main page and login page
This is the main page of the Website.

Figure 7
Login section on main page user can login their account and also new user can register them and admin manager also can login.

Admin Account

Figure 8
This is the admin account where the admin check all the information about users ,they also check total buyers total income of the users .

Figure 9
Admin also add or delete the categories.

Figure 10
Admin also check the orders and their status which is pending complete reject and conform.

Users account
User can manage their account .They create multiple stores.
Figure 11
User add multiple stores with logo, banner, categories and different color themes.

Figure 12
Website view
Here is a website view where customer can see multiple stores at same time they can see the multiple product as well. They can also brows a category which they want. If they want to be a part of our website means they want to create store as well so they can . with the help of add store button.

Figure 13

This is a store page where customer can see the products with there complete description as well as they can give the feedback of the product ..Customer also can rate the product which they want.

Figure 14

But for rating or feedback customer should need to login or register for the next step

Figure 15

If you want to buy any product then add to cart and fill the form for booking

Figure 16
In this page you can fill the information for the booking conformation

Figure 17
In this page customer should logout for the given red button

Figure 18

7.2 DATABASE DESIGN
This show the complete database design which we put on our project

Figure 19

User Table
In this table we provide every information about user their name id password email each and every thing.

Figure 20

Store Table
In this table we provide every information about store their name id logo banner each and every thing.

Figure 21

Rating Table
In this table we clarify all attributes about rating that which customer can rate on which product.

Figure 22
Product Table
In this table we provide information about products their name description brand price also provide that which store`s product i.e. store id.

Figure 23

Feedback Table
In this table we provide some attribute of feedback from the customers which is customer id . They can give a message related to the product which is product id.

Figure 24

Customer Table
In this table we provide attributes related to customer information like cus-id name email address

Figure 25
Category Table
In this table we provide the category name and id.

Figure 26

Booking Table
In this table we provide the attribute related to booking. We provide customer id product name that which product customer want product id, store that the selected product is in which store, also provide price of the product and date and time attribute that customer add cart in which time? Also provide status that the status of the booking is what pending conform complete reject. And booking number.

CHAPTER EIGHT

8 -USER INTERFACE

8.1. SYSTEM INTERFACE OVERVIEW
In chapter 7 giving complete detail of system interface that the system can work. Each figure shows the working of that page. In our project system must do login either its user customer or admin each member can login there system for the next step. When then login successfully on that application then they create multiple stores add multiple products mange their account but if they unsuccessful for login due to any error then they register them self. Admin can manage the website admin can add delete user or customers .admin can also add or removed category . Customer visits the website and check the multiple stores at the same time free any restriction. they can visit the store check products check rating or feedback of the product if they want to buy the product then they login or create a account after that they can buy any product which they want so add chrt and fill the booking information after placing an order customer log out the account . now user can see the booking and give the status received pending reject or etc.

8.2. APPLICATION TESTING
LOGICAL LIST:

Logical testing was conducted to check each function of each feature and query also it was implemented using valid and extreme data.

FUNCTIONAL TESTING:

Every aspect of product item was tested to ensure that at implementation no function had been missed.

SYSTEM TESTING:

The whole range of test were conducted and checked that no errors had been found in system. Also checked the performance and standards of the system, In system testing also checked the integration of the various modules.

CHAPTER NINE
9 -TESTING
9.1 – LOAD TESTING
In a load testing we measure a performance and volume of our application we can measure in our website so at the same time when 10to 15 user connect in our web page then there is no effect on the performance but still if 20to 30 user connect at the same time then the level of the performance little bit slow and when the 30 to 50 users connect at the same time then the volume and the performs is much slow

Figure 28
9.2 – UNIT TESTING
9.2.1 – Client-Side
In a client site we can perform unite testing for check the performance of code wither the code is correct or note client side we also test the product acceptance testing here
9.2.2 – Server-Side
In a server site we also perfume a unit testing to check the data base weather the data is we put is correct or not . Server side unit testing also on a web page we also major the unit testing in our project.

CHAPTER TEN:
10 -EVALUATION AND CONCLUSION
10.1 – EVALUATION
Here we evaluate our complete project in to three series we can evaluate our project with giving rank out of 5 on different categories like customer ,user, feedback ,rating booking store and products in series 1 we can see the user can be evaluate 4.5 out of 5 and customer evaluate 2.5 out of 5 ,feedback 5 out of 5 , rating 3.5 out of 5 also feedback same rank ,booking 3.5 out of 5 store evaluate 3.5 out of 5 and product 5 out of 5 and so on in other series.

Figure 29

10.2 – CONCLUSION
The conclusion for open e market is that it is very convenient user privilege and relatively cheap. You are able to create multiple stores as well as you can visit the stores and buy which you want from the comfort of your home; which means that you do not have to worry about time money stress or any restrictions .you can place your order and get the products which you really want.
10.3– FUTURE WORK
As like all projects which are software based or online web based, in our project there are many certain parts are having scope for further development. A list of future enhancements and updates are maybe endless. Project maybe enhanced with more themes and user privileges. More enhanced selling report to admin. More secure payment transaction system.

ESTIMATED TIME FRAME REQUIRED FOR VERIOUS STAGE OF PROJECT IMPLIMENTATION

S .no
Phases
Time Duration
1. Planning. 3 weeks
2. Software Requirement Specification. 8 weeks
3. System Design. 9weeks
4. Coding. 12 weeks
5. Implementation. 8 weeks
Figure 30
Content of figure ;
Figure 1:
Project life cycle…………………………………………………………………….22
Figure 2:
Gantt chart………………………………………………………………………..23
Figure 3:
Data flow diagram……………………………………………………………………25
Figure 04:
Layer architecture diagram…………………………………………………………….26
Figure 05 :
Design colour schema…………………………………………………………………..27
Figure 06:
Model diagram………………………………………………………………………….28
Figure 07:
Main page …………………………………………………………………………..32
Figure 08 :
Admin page ……………………………………………………………………………33
Figure 09:
Add category page………………………………………………………………………34
Figure 10:
Add order page………………………………………………………………………….35
Figure 11;
User page……………………………………………………………………………36
Figure 12:
Create store page…………………………………………………………………………37
Figure 13:
Website view page ……………………………………………………………………38
Figure 14:
Product page………………………………………………………………….39
Figure 15:
Feedback rating login page…………………………………………………………….40
Figure 16:
Add cart page……………………………………………………………………………41
Figure 18:
Booking conformation page………………………………………………………………..42
Figure 19:
Logout page…………………………………………………………………………………43
Figure 20:
Data base design: ……………………………………………………………………..44
Figure 21:
User table……………………………………………………………………………..45
Figure 22:
Store table ………………………………………………………………….46
Figure2 3:
Rating table……………………………………………………………………..47
Figure 24:
Feedback table………………………………………………………………..48
Figure 25:
Product table:…………………………………………………………………..48
Figure 26:
Customer table……………………………………………………………………..49
Figure 27:
Category table……………………………………………………………….50
Figure 28:
Booking table………………………………………………………………51
Figure 29:
Load testing……………………………………………………………..53
Figure 30:
ESTIMATTING TIME FOR PROJECT………………………………………………….. 57

Reference :
1 http://upstreamcommerce.com/blog/2012/02/14/8-reasons-consumer-likes-shop-online

2 OpenCart by Christopher G. Mann for Walnut Creek CDROM and later The FreeBSD Mall in May 11, 1999.

3 Shopify by Tobias Lutke, Daniel Weinand, and Scott Lake in june 2006.