E-Trading Website: Project Supervisor

E-TRADING WEBSITE
Project Supervisor
Ms. Ansif Arooj
Submitted By
PID-BSIT-F14-23
Shoaib Iqbal BSIT-F14-E25

Hafiz Ali Raza BSIT-F14-F24
Hamza Shafique BSIT-F14-E09
Zeeshan Ali BSIT-F14-E44
Qasim Yar BSIT-F14-E16
Division of Science & Technology, University of

Education, Lahore
CERTIFICATE
This is to certify that Shoaib Iqbal (BSIT-F14-E25), Hafiz Ali Raza(BSIT-F14-E24), Hamza
Shafique(BSIT-F14-E09), Zeeshan Ali (BSIT-F14-E44), Qasim Yar (BSIT-F14-E16) have
worked on and completed their Software Project at Division of Science & Technology,
University of Education, Lahore in partial fulfillment of the requirement for the degree of
BSIT under my guidance and supervision.
In our opinion, it is satisfactory and up to the mark and therefore fulfills the requirements
of BS in Information Technology.
Supervisor / Internal Examiner
Miss Ansif Arooj

Supervisor,
Division of Science & Technology
University of Education, Lahore
___________________
(Signature)
TABLE OF CONTENTS
CHAPTER NO. 1
GATHERING & ANALYZING INFO
1.1 INTRODUCTION…………………………………………………………………………02
1.2 PROJECT OVERVIEW STATEMENT…………………………………………………….02
1.3 PROJECT GOALS & OBJECTIVES……………………………………………………..04
1.4 HIGH LEVEL SYSTEM COMPONENTS………………………………………………….04
1.5 LIST OF FUNCTIONAL OPTIONAL UNITS………………………………………………04
1.6 EXCLUSION……………………………………………………………………………..05
1.7 APPLICATION ARCHITECTURE………………………………………………………....05
1.8 GANTT CHART………………………………………………………………………….06
1.9 HARDWARE & SOFTWARE SPECIFICATION……………………………………………07
1.10 TOOLS & TECHNOLOGIES USED WITH REASONING……………………………….07
CHAPTER NO. 2
SOFTWARE REQUIREMENT SPECIFICATION
2.1 FUNCTIONAL REQUIREMENTS………………………………………………………….10
2.1.1 CREATE USER ACCOUNT……………………………………………………….10
2.1.2 THEMES………………………………………………………………………….10
2.1.3 UPLOAD ITEM……………………………………………………………………10
2.1.4 SEARCH FOR PRODUCT/ COMPANY/ FREELANCER/INDIVIDUAL USER……10
2.1.5 COMPARING ITEMS……………………………………………………………..11
iii
2.1.6 SELECTING ITEMS…………………………………………………………….11
2.1.7 CHECK OUT/BUY AN ITEM…………………………………………………..11
2.1.8 SUBMIT PAYMENT…………………………………………………………….11
2.1.9 MANAGE PAYMENT…………………………………………………………...11
2.2 NON-FUNCTIONAL REQUIREMENTS……………………………………………….13
2.2.1 SECURITY……………………………………………………………………..13
2.2.2 USER INTERFACE…………………………………………………………….13
2.2. 3 SCALABILITY…………………………………………………………………13
2.2.4 RECOVERABILITY…………………………………………………………….13
2.2.5 AVAILABILITY…………………………………………………………………13
2.2.6 RELIABILITY…………………………………………………………………..13
2.2.7 PERFORMANCE……………………………………………………………….13
2.2.8 SUPPORTABILITY……………………………………………………………..13
2.2.9 SYSTEM REQUIREMENT……………………………………………………..14
2.3 DOMAIN REQUIREMENTS……………………………………………………………14
CHAPTER NO. 3
USE CASE DIAGRAMS
3.1 USE CASE OVERVIEW……………………………………………………………….16

3.1.1 ADMIN…………………………………………………………………………16
3.1.2 BUYER…………………………………………………………………………24
3.1.3 SELLER………………………………………………………………………..33
iv
CHAPTER NO. 4
PLANNING THE PROJECT
4.1 INTRODUCTION……………………………………………………………………………….43
4.2 METHODOLOGY……………………………………………………………………………43
4.3 AVAILABLE METHODOLOGIES……………………………………………………………44
4.4 CHOSEN METHODOLOGY…………………………………………………………………45
4.5 REASONS FOR CHOSEN METHODOLOGY………………………………………………..45
4.6 WORK PLAN………………………………………………………………………………..46
4.7 PROJECT STRUCTURE…………………………………………………………………….47
4.7.1 Team Structure…………………………………………………………………………47
4.7.2 Project Schedule (Submission Calendar)……………………………………………48
CHAPTER NO. 5
DESIGNING THE PROJECT
5.1 INTRODUCTION…………………………………………………………………………….50
5.2 PURPOSE……………………………………………………………………………………50
5.3 SCOPE………………………………………………………………………………………51
5.4 ARCHITECTURAL REPRESENTATION (ARCHITECTURE DIAGRAM)…………………….52
5.5 DYNAMIC MODEL: SEQUENCE DIAGRAMS……………………………………………..53
5.5.1 SEQUENCE DIAGRAM OF LOGIN PROCESS………………………………………53
5.5.2 SEQUENCE DIAGRAM OF REGISTRATION PROCESS……………………………54
5.5.3 SEQUENCE DIAGRAM OF BUYING PROCESS……………………………………55
5.5.4 SEQUENCE DIAGRAM UPLOAD ITEM…………………………………………….56
5.5.5 SEQUENCE DIAGRAM SEARCHING ITEM…………………………………………57
v
5.5.6 SEQUENCE DIAGRAM COMPARING ITEM………………………………………...58
5.6 OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM………………………………….59
5.7 DEPLOYMENT MODEL (DEPLOYMENT DIAGRAM)………………………………………..60
5.8 DATABASE MODEL …………………………………………………………………………61
5.8.1 ER DIAGRAM…………………………………………………………………………61
5.8.2 DATABASE SCHEMA…………………………………………………………………62
5.9 GRAPHICAL USER INTERFACES…………………………………………………………….68
5.9.1 WEBSITE INDEX PAGE………………………………………………………………68
5.9.2 USER PROFILE……………………………………………………………………….69
5.9.3 UPLOAD ITEM………………………………………………………………………..70
5.9.4 SEARCHING RESULT………………………………………………………………..71
5.9.5 ITEM PROFILE……………………………………………………………………....72
CHAPTER NO. 6
DEVELOPMENT
6.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)………………………………………...74
CHAPTER NO.7
TESTING
7.1 INTRODUCTION………………………………………………………………………………..76
7.2 PURPOSE………………………………………………………………………………………76
7.3 TEST CASES…………………………………………………………………………………..77
7.3.1 TEST CASE LOGIN PAGE………………………………………………………………77
vi
7.3.2 TEST CASE REGISTRATION PAGE……………………………………………………78
7.3.3 TEST CASE UPLOAD PROFILE PICTURE…………………………………………….79
7.3.4 TEST CASE UPLOAD NEW ITEM……………………………………………………..80
7.3.5 TEST CASE COMMENTING ON ITEM…………………………………………………81
7.3.6 TEST CASE ORDERING AN ITEM……………………………………………………..82
7.3.7 TEST CASE COMPARING TWO ITEMS………………………………………………...83
CHAPTER NO. 8
CONCLUSION AND FUTURE WORK
8.1 DISCUSSION……………………………………………………………………………………...85
8.2 FUTURE WORK…………………………………………………………………………………..85
8.3 CONCLUSION……………………………………………………………………………………..85
CHAPTER NO.9
DEPLOYMENT
9.1 DEPLOYMENT DIAGRAM…………………………………………………………………………87
vii
CHAPTER 1
Gathering & Analyzing Info
1.1 Introduction
This document provides a clear description of this Project “E-Trading Website”. It explains
the key concepts, functional requirements, and major terminologies. In this document a
reader will find whole overview about this project.
The product of this project will have huge scope, but till it has a scope within this city.
Means the customers of this website will belong to Lahore, because in beginning level it is
difficult to manage and control such type of huge system all over the country or world. The
main reason behind this scope is its three important active stakeholders (i.e. Buyer, Seller
and optional one Courier), these stakeholders are major and important stakeholders of this
website and in beginning it is much important thing that these all stakeholders should be
belonged from same city. Again I will repeat these important words, at beginning level. At
this level it will easy to get test the system and go for best solutions for problems then this
product and system will move to next levels and it scope can be expanded.
Project Title
The title is much clear. Here the category of project is mentioned. It is an “E-Trading
Website”.
1.2 Project Overview Statement

This project is an E-Trading website. The product of this project is a platform for a user to
buy or sell an object. In this a user can buy 2nd hand things as well as brand new things
directly from companies and vice versa. Two things of same category can also be compared
that which one is better and by machine learning a user can take help from machine by
asking its decision about which product is better.
Stakeholders can also communicate with each other on website by messenger while each
user has its account.
2
Project Overview
Project Title: E-Trading Website
Group Leader: Shoaib Iqbal (BSIT-F14-E25)
Project Members:
Sr. Name Roll No.
1 Shoaib Iqbal BSIT-F14-E25
2 Muhammad Zeeshan BSIT-F14-E44
3 Hafiz Ali Raza BSIT-F14-E24
4 Hamza Shafique BSIT-F14-E09
5 Qasim Yar BSIT-F14-E16
Project Goal: To achieve a highly easier, comfortable and reliable way to buy and sell any
type of thing at any level and make trading easiest.
Objectives:
Sr.#
1 To ease in buying and selling.
2 To compare two or more things of same type.
3 Make able website to give decision of best thing to buy in first hand category.
4 To give a portable platform for communication among users.
5 To allot user accounts
6 To analyze all trending items for users by analysts.
7 Can Rate and comment a product.
Project Success Criteria: This project will be highly successful in all type of transaction
that can be made at any level of E-Trading.
Assumptions, Risks and Obstacles: None
Organizational Address: None
Type of Project: Development
Target End Users:
 Buyers
 Sellers
 Analysts
 Companies
Development Technology: Object Oriented
Platform: Web based
Suggested Project Supervisor: Ms. Ansif Arooj
Approved By: Ms. Ansif Arooj
Date: November 20th , 2017
3
1.3 Project Goals & Objectives
The objectives of this project are already mentioned above, in this project we will manage
all the users with respect to their user accounts. Each user account can act Buyer, Seller
and Analyst and make transactions in accordance to its act. This provide the base for each
user to buy and sell anything. We have to make it easy for user to do any transaction. A
user can communicate easily with another user with the help of messenger. On it, identity
of a user is its user account and not only on messenger, at anywhere on website the user is
identified by its user account. So, a user can rate and comment any product.
The main goal of this project is to launch a product that will be web based and will make
to achieve a highly easier, comfortable and reliable way to buy and sell any type of thing
at any level and make trading easiest.
1.4 High-level system components

In every product, there is a set of components which cooperate with each other to get the
results, a system cannot work without anyone if missing. These components are known as
High-level system components. In our system, a list of High-level system components are
mentioned below:
 Data Base is one of the most important component because it holds all the data of
user accounts.
 Server is another important component of our system, it will hold all the system in
it.
 Node is required to access the website because an end user must require a device to
access it.
1.5 List of optional functional units

List of optional functional units are these:
 User accounts have customized option.
 A user can comment on any product.
 A user can rate another user or his/her product.
 Color themes of home page can be customized.
 Feedback will also be taken from users.
 A complain box will collect complain (if any).
4
1.6 Exclusion
We think that there is no such thing or activity that we include in Exclusion. Because all
the functional units and functional requirement that we mentioned above are dependent on
skills and ideas, no physical constraint can disturb these units.
1.7 Application Architecture

Let us discuss about the whole architecture about the project. This project working on three
layers:
1. Presentation Layer
2. Business Layer
3. Data Layer
First layer is Presentation layer, which consists of User Interface. This Layer represent an
interface, which ease a user to understand and use the website by different graphical items
e.g. input fields, buttons, menu bars, images etc.
Second layer is the Business layer, it is also known as Data access Layer. This layer will
work as intermediate between Presentation layer and Data Layer. It consist of code that
communicate user and data base means communicate presentation and data layer. At this
layer processing will work.
Third and the last layer is Data layer, it consists of data base. Here the all data will be stored
and the business layer after processing show output from this layer.
So all the above discussion shows that this is 3-tier Architecture.
5
1.8 Gantt chart
6
1.9 Hardware and Software Specification:
Software and Hardware Specification for building this project is given below:
Hardware Requirement
XAMPP is required to work on this project. It requires following hardware specifications.
 Minimum 350MB Hard Disk space for installation.
 4GB HD space required for a typical live system with 1000-2000 events.
 Recommended minimum CPU-Pentium 4.3.2 GHz.
 Recommended 1GB RAM for a central server with 3 nodes.
 Network Card.
Software Specification
Software requirements are given below.
 Operating System.
 Apache Server
 MySQL
 PHP
 Perl
1.10 Tools and technologies used with reasoning

In this project, as mentioned above that we are working on Web based system. So, the tools
and technologies are accordingly. Here we will use different known tools and technologies
like programming languages, development tools, technologies etc.
 This project will develop under the theme of Waterfall method. Step will be
followed during the project development i.e. requirement, design, implementation,
verification, maintenance.
 Host work as a service provider which works 24 hours.
 For the development of front end, mean presentation layer for user interface we
work on HTML, CSS, JavaScript, JQuery, AngularJS, and Bootstrap.
 There is no existing tool on which we are working from beginning, because this is
a new project on which no work has done still. However OS is the most first
requirement to work.
 For Business layer, a programming language is required to develop it and we are
working on PHP.
 Besides PHP some other cooperative platforms are also required which are
working with PHP like server, SQL Database and some other. There are some
software packages which are freely available to work on them. They consist of
PHP, local server, SQL e.g. xampp, wampp etc. and we will work on xampp.
 For professional and well organized work we will use Laravel framework of PHP.
 Text editor that we have decided to work on it is Sublime text editor.
7
 It is a low cost project, because it requires personal skills much more rather than
pcostly budget.
 If we estimate the time duration of our project it will take maximum 4 months for
completion, but inconsistence in meaning of academic works will increase its
duration up to 7 to 8 months.
8
CHAPTER 2
Software Requirement Specification
2 Specific Requirements
2.1 Functional Requirements
No. Requirement Description

FR1 Create user account Any user that will visit can create user account easily. User
account will convenient for user because without user
account a user can only READ posts on website and buy
items from individual sellers by private communication. So
for getting all rights user will Create user account by Signing
Up on website. It requires:
 Username
 Account Type (individual user, company, Free
lancers)
 Phone number
 Email
 Birthday
 Password
FR2 Themes Every user can change his account theme. By default,
website will provide a theme but theme will also be
customized able. A user will able to change these things in
theme of his/her account:
Profile picture
Cover picture
Color of his local chatrooms
FR3 Upload Item A registered user can upload any item that he wants. But in
case of different user types, the definition of uploaded item
is different i.e. If the company type account upload the item
its means it will be a firsthand product that may be bought
by an individual buyer as single piece or in stock. And if the
item is uploaded by the individual user or a freelancer then
it can also be bought by any buyer.
FR4 Search for Product/ There will be selection box from which a user can select the
Company/ option that will be searched. Options will be:
Freelancer/Individual  Product
User  Company
 Free lancer
 Individual User
10
After selecting one of them, user will find the search box
where she/he will search the thing which she/he will be
trying to search.
FR5 Comparing items When user will be searching the items she/he can insert the
items (more than one) into Comparison table and when
selection process will complete user can watch the
comparison table.
FR6 Selecting Item User who search some item can also have requirement to
select the item or add to cart. For this purpose, each item
profile has a button which help user to add that item in cart
or list of items that user will be going to buy.
FR7 Check Out/ Buy an To buy an item user will pass the process, after selecting the
Item item the buyer can check the price per item and price of
stock or offers if available. In case of any query or meeting,
users can converse ate with each other and can deal and
arrange meet ups. Messenger will also be a convenient mean
to deal among them. After donning the deal the user can pay
the seller by mean of E-Banking or in cash on receiving
item. User will use shopping cart for this purpose.
FR8 Submit Payment After selecting items, user will use Submit Payment option.
User will facilitate with two options.
 Pay online by e-banking
 Pay on receiving order
Paying online by e-banking is a convenient way especially
for seller because it is safer method. In case of trading deal
it will compulsory for buyer to pay online by e-banking,
when seller is a company. But in case of individual or
freelancer seller, buyer can paid accordingly.
On receiving order payment, the dealing is mostly of
minimum items, where the seller and buyer can chat and
meet each other than trade occur. So in this case both
methods of payment are convenient.
FR9 Manage Payment Payment management will working under the

administration of website. In case of any type of mistake
occur in Submit Payment can be updated. E.g. the user will
have submit more money by mistake then application will
send to seller for return this money and it will an easy and
simple method but the thing is that such type of mistakes are
rare.
The other thing is to manage money, actually this website
will be cutting its percentage directly from each deal, and so
11
the money from one party will directly transfer to the other
party means buyer to seller so there is no use to create
process for managing money. But their records that who
paid for what and how much, it will be recorded and
managed.
12
2.2 Non-Functional Requirement
No Requirement Description
NFR1 Security Admin panel of Website will be limited up to Administration.

Login system will only permit the Authenticated users of website.
It means person who have correct username and password can
only access relevant account.
Any type of SQL injection and attack will not possible because
of covered queries i.e. n-tier architecture.
Signup system will be much intelligent to secure account for
future confidentiality attacks.
NFR2 User Interface Browsers will provide the user interface to clients as well as the
administrators because of its web based nature.
NFR3 Scalability Website will be able to grow in future in accordance to scope

requirements.
NFR4 Recoverability Data can be easily recoverable in case of any disaster or temporary
blockage. In this project the servers are integrated in such way that
they will create backup automatically.
NFR5 Availability Website will available 24x7 a day.
NFR6 Reliability This website will develop much more reliable for use. As its
availability is 24x7 a day, in such case reliability is a challenge
with maintaining efficiency as well. But all these aspects will
preserve with maintenance, So this website will reliable.
NFR7 Performance At a time, many users will access the websites. But each user will
access website by his/her own system e.g. Computer, Laptop, Tab,
Mobile etc. which consume their own RAM, it will not affect
servers and so it will not disturb servers’ performance. Therefore,
Servers will independent from users’ devices and it will maintain
performance all the time.
NFR8 Supportability Website will support by any new version browser on Computers,
Laptops, Tabs, Mobiles etc.
NFR9 System Software and Hardware Specification for building this project is
Requirement given below:
13
Hardware Requirement
XAMPP is required to work on this project. It requires following
hardware specifications.
 Minimum 350MB Hard Disk space for installation.
 4GB HD space required for a typical live system with
1000-2000 events.
 Recommended minimum CPU-Pentium 4.3.2 GHz.
 Recommended 1GB RAM for a central server with 3
nodes.
 Network Card.
Software Specification
Software requirements are given below.
 Operating System.
 Apache Server
 MySQL
 PHP
 Perl
3 Domain Requirements
Domain of this Website is Business (Trade). So, to meet the characteristics of Business
domain it require some specific requirements:
 To maintain the security of the user, the System should have a secure
authentication and verification criteria.
 It provides the strong communication among users to shorten the distance
among users and providing a trustworthy environment among them.
 In order to use the e-banking facility for transaction. It will ensure the validity
of bank account of user.
14
CHAPTER 3
USECASE DIAGRAMS
3.1 Use Case Overview
3.1.1 Admin
16
UC Number: 1.1
UC Name: Login
Actors/Stakeholders: Admin
Goals: To get admin authenticate and logged in Website for using functions of Website.
Relative Use Case: None
Preconditions: None
Summary: Admin will be prompted to login with his/her account information before they can use
the system.
Steps:
1. User will connect with internet.
2. Open Browser
3. Browse the Website.
4. User will enter username and password.
5. System will authenticate the user information from Database.
6. If information is correct the user will log in otherwise terminate the process or start again
from beginning.
Post conditions:
1. The admin will log in to the system
2. The admin has access to the functions of the system
Alternative Scenario: If in the Basic Flow the actor enters an invalid name and/or password, the
system displays an error message. The actor can choose to either return to the beginning of
the Basic Flow or cancel the login, at which point the use case ends.
Includes: None
Frequency of Use: Every time the admin wants to access the system.
17
UC Number: 1.2
UC Name: Change Theme
Goals: To customize the Default Theme of the Admin Account by Admin himself/herself. I.e.
Changing Profile picture, Cover photo and change chat color.
Related Use Case: None
Preconditions:
1. Admin should on Website.

2. Admin should login.
Summary: Admin will able to change the theme i.e. profile picture, cover photo and chat color
according to him/her. So website provide customizable theme.
Steps:
1. Admin will click on option for change profile picture, cover photo or chat color.
2. Browse Computer to select picture for profile or cover, but in case of chat color, it will
browse the color picker to pick the color.
3. Select the picture or color from color picker.
4. Set save change.
Post Conditions:
1. Admin will get the message of “Changes Saved”.

2. Admin will see the Changed theme.
Alternative Scenario: If in the basic flow the Admin will have any problem in accordance to
internet connectivity, uploading photo or browsing computer/color picker. The Admin can choose
to either return to the beginning of the Basic Flow or terminate this process.
Include: None
Frequency of Use: Any time Admin can customize the theme.
18
UC Number: 1.3
UC Name: Manage Orders
Goal: To Manage the orders of Customers and maintain the record of orders.
Related Use Cases: None
Preconditions:

2. Admin should log in.
Summary: Admin will manage and maintain all the orders given by Customers i.e. Buyer and also
manage all the deliveries given by Sellers i.e. Companies, Freelancers.
Steps:
1. When any order is given a notification is prompt on Admin’s account.

2. Order will then store in Database.
3. Admin can check this order.
Post Conditions:
1. Admin can cancel this order.

2. Admin can read this order.
Alternative Scenario: This will be the only and most effective and efficient way to manage order,
so no alternative scenario is existed.
Include: None
Frequency of Use: Every time Admin will facilitated with this function to facilitate the Users.
19
UC Number: 1.4
UC Name: Manage Payment
Goal: To manage and maintain the payment record after payment of order by Buyer.
Preconditions:
1. Admin should connected to internet.

Summary: Admin will manage and maintain all the payment records that will have obtained after
buying any item by a buyer from a seller.
Steps:
1. When any transaction occur a notification about payment record is obtained at Admin
account.
2. This record will store in Database then.
3. Admin can check this record.
Post Conditions:
1. Admin can read this record.

2. Admin can cancel this record.
Alternative Scenario: This will be the only and most effective and efficient way to manage order,
Include: None
20
UC Number: 1.5
UC Name: Manage Shipment
Goal: To manage and maintain the Shipment and Shipment record after placement of order by
Buyer.
Preconditions:
1. Admin should connect to internet.

Summary: Admin will manage and maintain all the Shipment and Shipment records that will have
obtained after buying any item by a buyer from a seller.
Steps:
1. Order notification is obtained at admin account.

2. Then Seller will receive the same order notification.
3. After shipment of order Seller will send the Shipment notification to admin.
4. This notification is then stored in Database.
Post Conditions:
1. Admin can read this record.
Alternative Scenario: This will be the only and most effective and efficient way to manage
Shipment and Shipment order, so no alternative scenario is existed.
Include: None
21
UC Number: 1.6
UC Name: Manager User Accounts
Goal: To manage and maintain the User accounts e.g. individual buyers and sellers accounts,
company accounts, freelancers accounts.
Preconditions:
1. Admin should connect with internet.

Summary: Admin will able to allow users to create accounts. These accounts will be then
managed and maintained by admin. Admin can block any user.
Steps:
1. User will register himself/herself on Signup page.

2. This account is verified by admin.
3. Then user will login his/her account.
4. User after login fill some forms for information.
5. User and account information is then stored in Database.
Post Condition:
1. Admin then can block, delete and read his/her account.
Alternative Scenario: This will be the only and most effective and efficient way to manage User
accounts and accounts information, so no alternative scenario is existed.
Include: None
22
UC Number: 1.7
UC Name: Manage advertisement
Goal: To manage and maintain the Advertisements and Advertisement record after placement of
order by Adviser.
Preconditions:
1. Admin should connect with internet.

2. Admin should on website.
Summary: Admin will manage and maintain all the Advertisement and Advertisement records
that will have placed by advertiser.
Steps:
1. Advertiser will place an order for advertisement on website contact i.e. on Admin account.
2. Admin receive order and verify it.
3. Admin will send verification message to advertiser and ask for advertising content and
online payment.
4. Advertiser will pay online and send payment record to Admin.
5. Admin after receiving payment record set advertisement on Website.
6. Admin will send Advertise successfully message to advertiser.
Post Conditions:
1. Advertiser can watch advertisement on website.

2. Admin can maintain and delete this advertisement within contracted time and must delete
after due time.
Alternative Scenario: This will be the only and most effective and efficient way to manage
Advertisement and advertisement record, so no alternative scenario is existed.
Include: None
23
3.1.2 Buyer
24
UC Number: 2.1
UC Name: Login
Actors/Stakeholders: Buyer
Goals: To get Buyer authenticate and logged in Website for using functions of Website.
Preconditions:
1. Buyer should connect with internet.

2. Buyer should on website.
Summary: Buyer will be prompted to login with his/her account information before they can use
the system.
Steps:
1. Buyer will connect with internet.
2. Open Browser
4. Buyer will enter username and password.
6. Buyer will log in his/her account.
Post conditions:
1. The Buyer will log in to the system
2. The Buyer has access to the functions of the system
Includes: None
Frequency of Use: Every time the Buyer wants to access the system.
25
UC Number: 2.2
UC Name: Search and View Item
Goal: To search item which you want to view and then view the profile of that item.
Preconditions:

3. Buyer might be logged in if he will be buying item from Freelancer or Companies but log
in is not necessary when Buyer will be buying an item from a local User.
Summary: When Buyer will want to buy an item. He /She will search for this item and view all
the searched items and can view profile of that Item.
Steps:
1. Buyer will write the item name on search bar and click on search button.
2. All searched items will prompt on page.
3. Buyer can view all items that will have searched.
4. Buyer can view the profile of required or selected Item.
Post Conditions:
1. Buyer can view profile of any Item.
Alternative Scenario: This will be the only and most effective and efficient way to search item,
so no alternative scenario is existed but Buyer can view trending items on going to item category.
Include: None
Frequency of Use: Buyer can search and view Item any time whenever he/she want to buy an
item.
26
UC Number: 2.3
UC Name: Order Item
Goal: To order Item that buyer will have wanted to buy.
Related Use Cases: Search and View Item.
Preconditions:

3. Buyer should log in.
Summary: Buyer will search the item that he will want to buy and then order this item by adding
it in Cart.
Steps:
1. Buyer will search the items.

2. Select the Item.
3. Add this Item to Cart.
4. Then order this Item or set of Items.
Post Conditions:
1. Order notification will send to Seller.

2. Buyer will ask for payment.
Alternative Scenario: This will be the only and most effective and efficient way to order Item, so
no alternative scenario is existed.
Include: None
Frequency of Use: Any time Buyer can order one or more items according to his/her requirements.
27
UC Number: 2.4
UC Name: Payment
Goal: To pay the Items, that will have ordered. In case of online payment Buyer will use e-banking
method, otherwise he/she will pay on cash.
Related Use Cases: Order Item
Preconditions:

3. Buyer should login in case of online payment. (On Cash login is not required)
Summary: When Buyer will order item he/she will have to pay for Item. In case of online payment
Buyer will login and pay by e-banking, while in case of on Cash he/she will pay it on meeting.
Steps:
1. Buyer will choose the method for payment.

2. In case of online payment, he/she will pay by e-banking. Buyer will enter will account
information.
3. But in case of on cash payment. He/she contact Seller and meet up and then cash in hands.
Post Conditions:
1. Buyer will receive successfully paid message.

2. Buyer will be delivered by his Item.
Alternative Scenarios: These will be the only and most effective and efficient ways to order Item,
Include: None.
Frequency of Use: Whenever the Buyer will order for any Item, Buyer will pay for these items.
28
UC Number: 2.5
UC Name: Cancel Order
Goal: To cancel order, that will have set already.
Related Use Cases: Order Item
Preconditions:

2. Buyer should on Website.
4. Buyer will have must place order.
Summary: Buyer will have placed order, due to any reason Buyer will want to cancel that order,
so he/she will cancel order by this function.
Steps:
1. Buyer will go on his/her account.

2. Open his/her Ordered Items.
3. Click on Order that he/she will want to delete.
4. Finally Buyer will click on cancel order option.
Post Conditions:
1. Order will cancel.

2. Buyer will not see that order in order list.
Alternative Scenario: This will be the only and most effective and efficient ways to order Item,
Include: None
Frequency of Use: When Buyer will place any order, he/she will cancel order in limited time.
Every time when he/she will place order, he/she will get this function.
29
UC Number: 2.6
UC Name: Chat
Goal: To communicate with sellers.
Preconditions:

Summary: When a Buyer will view profile of an Item and let suppose he/she will have any query
about item or he/she will be wanting to hold a meetup or wanting to deal with seller, he/she will
communicate with seller by messenger.
Steps:
1. Buyer will search for seller.

2. Go on his/her profile.
3. Click on Message Button.
4. Write message.
5. Send it.
6. Buyer then receive reply and he/she can read it, vice versa.
Post Conditions:
1. Buyer will communicate with seller.
Alternative Scenario: These will be the only and most effective and efficient ways to chat, so no
alternative scenario is existed.
Include: None
Frequency of Use: Any time Buyer can chat with Seller when he/she will require communication.
30
UC Number: 2.7
Goals: To customize the Default Theme of the Buyer Account by Buyer himself/herself. I.e.
Preconditions:

4. Buyer should login.
Summary: Buyer will able to change the theme i.e. profile picture, cover photo and chat color
Steps:
5. Buyer will click on option for change profile picture, cover photo or chat color.
8. Set save change.
Post Conditions:
3. Buyer will get the message of “Changes Saved”.

4. Buyer will see the Changed theme.
Alternative Scenario: If in the basic flow the Buyer will have any problem in accordance to
internet connectivity, uploading photo or browsing computer/color picker. The Buyer can choose
Include: None
Frequency of Use: Any time Buyer can customize the theme.
31
UC Number: 2.8
UC Name: Compare Items
Goal: To compare two or more items to choose best one.
Preconditions:

4. Buyer should already selected Items, those he/she will want to compare.
Summary: When user will want to compare two or more items, he/she will first select these items
and choose Compare items options and he/she will show all the information of items in form of
table and Buyer can easily differentiate and choose the best one. If Buyer will not judge best one,
he/she can also ask from website that which one is best.
Steps:
1. Buyer will choose the first item which he/she want to compare.
2. Buy will choose the second item which he/she want to compare.
3. Click on Compare Items option.
Post Conditions:
1. Buyer will watch the comparison table.

2. Buyer will ask for best one by machine learning.
Alternative Scenario: These will be the only and most effective and efficient ways, so no
Include: None
Frequency of Use: Buyer can any time use this function whenever he/she will need.
32
3.1.3 Seller
33
UC Number: 3.1
UC Name: Login
Actors/Stakeholders: Seller
Goals: To get Seller authenticate and logged in Website for using functions of Website.
Preconditions:
3. Seller should connect with internet.

4. Seller should on website.
Summary: Seller will be prompted to login with his/her account information before they can use
the system.
Steps:
7. Seller will connect with internet.
8. Open Browser
10. Seller will enter username and password.
12. Seller will log in his/her account.
Post conditions:
1. The Seller will log in to the system
2. The Seller has access to the functions of the system
Includes: None
Frequency of Use: Every time the Seller wants to access the system.
34
UC Number: 3.2
Goals: To customize the Default Theme of the Seller Account by Seller himself/herself. I.e.
Preconditions:
5. Seller should on Website.

6. Seller should login.
Summary: Seller will able to change the theme i.e. profile picture, cover photo and chat color
Steps:
9. Seller will click on option for change profile picture, cover photo or chat color.
12. Set save change.
Post Conditions:
5. Seller will get the message of “Changes Saved”.

6. Seller will see the Changed theme.
Alternative Scenario: If in the basic flow the Seller will have any problem in accordance to
internet connectivity, uploading photo or browsing computer/color picker. The Buyer can choose
Include: None
Frequency of Use: Any time Seller can customize the theme.
35
UC Number: 3.3
UC Name: Upload Item
Goal: To upload new item on Website for Selling purpose.
Preconditions:

3. Seller should log in.
Summary: When Seller will want to sell any item or he/she will have a new product to sell (in
case of Company or Freelancer) then he will upload this item on website.
Steps:
1. Seller will click on Upload Item option.

2. Enter details of Item.
3. Browse photos from Computer.
4. Click on Upload option.
Post Conditions:
1. Seller will get message “Uploaded Successfully”.

2. Seller can watch uploaded Item.
Alternative Scenarios: These will be the only and most effective and efficient ways to upload
item, so no alternative scenario is existed.
Include: None
Frequency of Use: Seller can upload any new item any time.
36
UC Number: 3.4
UC Name: Search and View Item
Goal: To search item which you want to view and then view the profile of that item.
Preconditions:

3. Seller might be logged in if he will be buying item from Freelancer or Companies but log
in is not necessary when Buyer will be buying an item from a local User.
Summary: When Seller will want to buy an item. He /She will search for this item and view all
the searched items and can view profile of that Item.
Steps:
1. Seller will write the item name on search bar and click on search button.
2. All searched items will prompt on page.
3. Seller can view all items that will have searched.
4. Seller can view the profile of required or selected Item.
Post Conditions:
1. Seller can view profile of any Item.
Alternative Scenario: This will be the only and most effective and efficient way to search item,
so no alternative scenario is existed but Seller can view trending items on going to item category.
Include: None
Frequency of Use: Seller can search and view Item any time whenever he/she want to buy an
item.
37
UC Number: 3.5
UC Name: Delete Item
Goal: To delete any Item that will have uploaded by Seller
Preconditions:

Summary: When Seller will want to delete his uploaded item, then he will use this function to
delete it.
Steps:
1. Seller will go to profile of that item which he will be wanting to delete.

2. Seller will click on Delete item button.
Post Conditions:
1. Seller will asked that will he really want to delete item.

2. If he click on yes button then he will not see that item again.
Alternative Scenarios: These will be the only and most effective and efficient ways to delete
item, so no alternative scenario is existed.
Include: None
Frequency of Use: Any time seller can delete his uploaded item.
38
UC Number: 3.6
UC Name: Chat
Goal: To communicate with buyer.
Preconditions:

Summary: When a Seller will view profile of an Item and let suppose he/she will have any query
about item or he/she will be wanting to hold a meetup or wanting to deal with seller, he/she will
communicate with buyer by messenger.
Steps:
7. Seller will search for seller.

8. Go on his/her profile.
9. Click on Message Button.
10. Write message.
11. Send it.
12. Seller then receive reply and he/she can read it, vice versa.
Post Conditions:
2. Seller will communicate with seller.
Alternative Scenario: These will be the only and most effective and efficient ways to chat, so no
Include: None
Frequency of Use: Any time Seller can chat with buyer when he/she will require communication.
39
UC Number: 3.7
UC Name: Confirm Order
Goal: To confirm the order that will have placed by Buyer.
Preconditions:

4. Seller will receive order notification.
Summary: When Buyer will place order, Seller receive order notification and confirm this order
for further processing.
Steps:
1. Seller will respond Confirm order by clicking on Confirm order option.
Post Conditions:
1. Order notification will be checked.

2. Website will guide for further processing.
Alternative Scenarios: These will be the only and most effective and efficient ways to confirm
order, so no alternative scenario is existed.
Include: None
Frequency of Use: When seller receive order notification only then seller will confirm order.
40
UC Number: 3.8
UC Name: Cancel Order
Goal: To cancel the order that will have placed by Buyer.
Preconditions:

8. Seller will receive order notification.
Summary: When Buyer will place order, Seller receive order notification and cancel this order
for further processing.
Steps:
2. Seller will respond Cancel order by clicking on Cancel order option.
Post Conditions:
3. Order notification will be checked.

4. Website will remove this order.
Alternative Scenarios: These will be the only and most effective and efficient ways to cancel
order, so no alternative scenario is existed.
Include: None
Frequency of Use: When seller receive order notification only then seller will cancel order.
41
CHAPTER 4
Planning the Project
4.1 Introduction
4.2 Methodology
Customers build up a sense of loyalty to those e-commerce websites that offer them a
good user experience, and that transmit to confidence and reliability. There are various
factors that influence this: how easy it is to find the product they are looking for, how
easy/difficult it is to make the payment, how fast the order was executed. All of these
factors determine whether the customer will shop at that website again or not. In general,
potential buyers are more and more impatient, which means they do not have much time
to find what they are looking for, or to receive a positive first impression. Our e-trading
module, takes these needs into consideration and as well as others.
Attracting and retaining customers

Gaining high visibility on search engines is key to attracting new customers. This is why
our e-commerce projects make the Google indexation easy, as well as that of the other
main search engines. With regards customer retention, our Content Management System
includes some online Marketing and customer services, such as forums, e-magazines,
surveys, etc., and also recognizes returning customers in order to facilitate the payment
process, and thus help with customer retention.
Searching in an easier way

Our approach is customer-focused and geared towards natural web browsing, which
combined with a customizable search helps new and returning customers to find the
products and services they need, quickly and easily. This methodology improve the e-
commerce’s profitability.
43
Potential customers will not wait
When new customers go onto a website that is slow to load, they are quick to get impatient
and leave the site. Our e-trading website projects guarantee quick loading, as we use
stylesheets (CSS) and files which have been size-optimized. Our servers also allow for
boosting hosting capacity on days with high traffic, such as the first day of the sales.
Peace of mind for customers

Many users are careful when shopping online, particularly given the even coverage of
online cons on the news. As a result, the web design, usability and content of an e-trading
business needs to offer customers complete peace of mind and convince them of the
website’s reputation and integrity. We can write or advise you on what to say about
customer security on the site. If done well, this will help you increase Work methodology
for E-trading conversions and the site’s overall profitability.
Security and reliability

Our e-trading module is a trustworthy, secure and user-friendly system that is able to
handle high levels of traffic to your website. The payments are made in a very secure way.
Our specific e-trading development is user-friendly and can be integrated into any
administration system, even with those used by the logistics companies you work with,
thus reducing costs and maximizing profits.
4.3 Available Methodologies

A website based software development methodology or system development
methodology in software engineering is a framework that is used to structure, plan, and
control the process of development of an information system.
There are following methodologies:
 Agile method
 Crystal Methods
 Dynamic Systems Development Model
 Extreme programming
 Feature Driven Development
 Joint Application Development
 Learn Development
 Rapid Application Development
 Rational Unified Process
 Scrum
44
 Spiral
 System Development Life Cycle
 Waterfall
4.4 Chosen Methodology

This e-trading website is following the “Agile methodology” to be built. It is a conceptual
framework for undertaking software engineering projects. Agile method attempt to
minimize risk by developing software in short time boxes. These time boxes may typically
last one to four weeks. Each iteration is like a mini software project of its own, and
includes all the tasks necessary to release the mini-increment of new functionality:
planning, requirements analysis, design, coding, testing, and documentation. While
iteration may not add enough functionality to warrant releasing the product, an agile
software project intends to be capable of releasing new software at the end of every
iteration. At the end of each iteration, the team reevaluates project priorities.
Agile methods emphasize real time communication, preferably face to face, over written
documents. At minimum, this includes programmers and the people who define the
product such as product managers, business analysts or actual customers. It also includes
tester, interface designers, technical writers and management.
Agile methods also emphasize working software as the primary measure of progress.
Combined with the preference for face to face communication, agile method s produce
very little written documentation relative to other methods.
4.5 Reasons for Chosen Methodology

Project methodology is chosen on the bases of project level. As this project is Final year
project for Graduation level program. It has no primary client who told project team that
which functions are required in this e-trading website. But team had to evaluate their
project to supervisor that they done timely. So the requirements also changed somehow
in meetings. For this scenario Agile Software development method is best for team to
keep this in work. Agile Software development method keep track of all the ways for
alternative situations. This methodology is also best for risk management so that team
chose this methodology for development of e-trading website.
45
4.6 Work Plan
Work
Breakdown
structure
Front End Back End

Documentation Deployment
Development Development
Gathering and Creating

Choosing the Avail Web
analyzing Database
color schema Services
requirements schema
Software Choosing the

Writing Server Configuring web
requirement appropriate
side code storage
Specification theme
Development of Connecting the

Planing the Configuring web
Designed Front software
project database
End databasee
Testing the Testing the

Designing the Migrating data
developed front website Back
project and databases
end end
Deploying front
Development
end interfacce
Testing the
Testing deployed
system
Deployement
46
4.7 Project Structure
4.7.1 Team Structure

Team consist of five members. The above work plan is divided so all the members of
team participate in work plan of project. Team has been following structure hierarchy:
Group leader
Group leader is the person who will be monitoring the whole project and working as
the project manager. He helps team members to circulate the whole working of project
plan.
Analyst
He will be the person who gather the requirements and analyze these requirements.
Analyst analyze all the facts and figures get for project.
Designer
Designer will design the user interface for the website. Azure is used for designing
purpose and he has good command on azure as well as all the languages that help him
to design the interface for the e-trading website.
Developer
Developer will develop the Business layer as well as Data layer for the website.
Developer who is developing this website has good command on php and its framework
Laravel. These are the languages that are used in development this e-trading website.
Tester
Tester will perform the main step of testing. He will test the system at individual units
and also integration of unit testing.
47
4.7.2 Project Schedule
48
CHAPTER 5
Designing the Project
5.1 Introduction
5.2 Purpose
World is moving toward modern age. In which all the technology is moving on web
platform. That’s why, Project team chose web platform to build this software. This will
provide 24x7 service anywhere from the world. This is the basic purpose to choose the web
based platform. E-Trading websites are already working in World Wide Web all over the
world and many people use this platform to buy and sell products. But here a question rise
that, what is the purpose of this website while many e-trading websites are already working
in market? Answer of this question is the two unique feature of this website. This website
like all other e-commerce and e-trading website provide platform to buy and sell the
products. They connect people and act as the market place for them, this e-trading website
also provide the same feature. But the two unique features that make this e-trading website
different from other e-commerce and e-trading website is that a user can select two items
of same category and can compare both items in the form of table, and the other unique
feature of this e-trading website is that, user after comparing two items in the form of table
can also take decision from website that will after watching statistics from data tell the high
rated item as a better item than other.
50
5.3 Scope
51
5.4 Architecture Diagram
52
5.5 Dynamic Model: Sequence Diagram
5.5.1 Sequence Diagram of Login Process
53
5.5.2 Sequence Diagram of Registration process
54
5.5.3 Sequence Diagram of Buying Process
55
5.5.4 Sequence Diagram of Upload Item Process
56
5.5.5 Sequence Diagram of Searching Item
57
5.5.6 Sequence Diagram of Comparing item
58
5.6 Object Model: Class Diagram
59
5.7 Deployment Model
60
5.8 Database Model
5.8.1 ER Diagram
61
5.8.2 Database Schema
5.8.2.1 Table Name: Users
62
5.8.2.2 Table Name: Roles
63
5.8.2.3 Table Name: Orders
64
5.8.2.4 Table Name: Messages
65
5.8.2.5 Table Name: Items
66
5.8.2.6 Table Name: Comments
67
5.9 Graphical User Interface
5.9.1 Website Index page
68
5.9.2 User Profile
69
5.9.3 Upload Item
70
5.9.4 Searching Results
71
5.9.5 Item Profile
72
CHAPTER 6
Development & Implementation
6.1 Architecture Diagram
6.2 Development Plan

As this e-trading project is web based system, so for this the web based server platform is
choose. And language that is used for development is also totally web based. E-Trading
Website is actually an ecommerce website and now a days, they have a huge scope in
market. Many of the people build such type of ecommerce website and launch them into
the market. But all these website doesn’t work many more. The simple reason is that all
these people don’t working in the latest technologies that may cause the failure of these
websites.
Project team research for many new methods and frameworks that are going to use is
website. For all the development purpose team uses xampp as a localhost. It helps us to
check the progress of work by running it on localhost. This website is planned to develop
in php and its framework Laravel. In development process, first of all the mockups that
are designed in above chapter are implemented in code and front end is developed. This
front is then integrated in Laravel framework project. After integration, team started
working on migrations of database. After completion of migrations, Models, controllers
and views are formed and then all back end is complete.
74
CHAPTER 7
Testing
7.1 Introduction
Software testing is a task intended to detect defects in software by contrasting a computer
program's expected results with its actual results for a given set of inputs. By contrast, QA (quality
assurance) is the implementation of policies and procedures intended to prevent defects from
occurring in the first place.
7.2 Purpose
In addition, testing validates that the system being developed is what the user needs. While finding
defects / bugs is one of the purposes of software testing, it is not the sole purpose. It is important
for software testing to verify and validate that the product meets the stated requirements /
specifications.
76
7.3 Test Cases
7.3.1 Test Case Login page
ID: 001
Title: Login Page – Authenticate successfully on our website.
Description: A registered user should be able to successfully login at our website.
Preconditions:
1. The user should have a valid account.

2. The user has permission to make session.
3. The user is not already logged in to the system.
Test Steps:
User logs in to the system and can check all available data with his account information and
manages overall operation of the system.
Expected Result:
1. The user is logged in to the system.
2. The user has access to the functions of the system.
77
7.3.2 Test Case for user Registration
ID: 002
Title: Register User on website (Creating User Account).
Description: A user who want to take any transaction and use all the features of this website will
register himself on website.
Test Steps:
User has to enter all required information to registration form so that he can use all the
feature of the website.
Expected Result:
The User has successfully created the new user account.
78
7.3.3 Test Case Upload Profile Picture
ID: 003
Title: Upload profile picture.
Description: A registered user should be able to successfully upload his profile picture on his user
account.
Preconditions:
1. The user is logged in to his account.
Test Steps:
User has the facility to upload Profile picture. He/ she may browse through his/ her
computer to select a picture and upload it to the system.
Expected Result:
The user has successfully uploaded the profile picture on the system.
79
7.3.4 Test Case upload new Item
ID: 004
Title: Upload new item on the website.
Description: A registered user should be able to successfully upload the new item on website.
Preconditions:
1. The user is logged inn to the system.
Test Steps:
User has the facility to create/ upload new item on website. He/ she should fil the upload
new item form also upload its image by browsing it from computer and successfully upload the
item.
Expected Result:
The user has successfully uploaded new item on the website.
80
7.3.5 Test Case Commenting on item
ID: 005
Title: Comment on an item.
Description: A registered user should be able to comment an item of any user.
Preconditions:
Test Steps:
User has the facility to comment on an item on website. And his comment is visible to all
other users.
Expected Result:
The user has successfully commented on an item on the website.
81
7.3.6 Test Case ordering an item
ID: 006
Title: Order an item from the website.
Description: A registered user will be able to order any item or stock of items from the company
type user of website.
Preconditions:
Test Steps:
User has the facility to order an item or stock of item from the company type user of
website. When user is logged in he can view all items and can also order item any of them.
Expected Result:
The user has successfully order the item.
82
7.3.7 Test Case comparing two items
ID: 007
Title: compare two items that user selected.
Description: A registered user should be able to compare two items of same category.
Preconditions:
1. The user is logged inn to the system.
Test Steps:
User has the facility to compare two items of same category. User first selects the items
and then executes their comparison and he sees the comparison of these items in the form of table.
Expected Result:
The user has successfully saw the comparison table of two items.
83
CHAPTER 8
Conclusion & Future Work
8.1 Discussion
Finally, we wish to consider the best way to navigate the proposed document hierarchy.
This hierarchy could also be used to fine-tune responses to user queries. While we may not
want to prohibit user access to certain levels of detail, it could prove useful to allow a user
to limit the areas browsed and the scope of query responses to exclude levels which are too
general or too detailed for their purposes.
8.2 Future Work

After the acceptance of project, the future plan of team is that, this website will be hosted
on the server for people. Team will provide a strong theme to advertise the website all over
the scope. Some things might be there which provide changes and alternation, so team will
perform surveys and feedbacks to improve the quality and performance of website. This
will tend to improve team skills as well as the website functionality in marketplace. In early
future advertisement is an important thing to launch it in marketplace. This could be done
on social media as well as by the mean of posters. Team hopes that this project will achieve
all the levels of success and there motto is to improve this website with the requirement of
time and update the feature which will enhance the better working of website.
8.3 Conclusion
This software documentation explain the whole processes and phases for development of
Website. Requirements are not told by primary client. It is a final year project for
graduation level, so requirements are gathered by supervisor and on the basis of team
members’ ideas. These requirements are categorized in functional and non-functional
requirements. Then these requirements and aspects related to these requirements are
represented in graphical and pictorial manners. As it is an E-Trading website so it is
important to create its front end in relevant manner. Team use azure software for designing
front end designs. Designing phase also included DB designs and process designs. After
designing, team move toward new phase of development and coding. It was the most time
consuming phase. Team required great skills and experience in this phase, they use php
and its framework Laravel for development of this web based software. This phase covered
the development of front end, DB migrations and Back end. Design phase already give the
code for front end with the help of Microsoft azure. In development stage the only thing
about front end is that the team have to integrate this front end code in laravel project. Then
over to MVC. Front end consists of DB portion means Data Layer and Business Layer.
Migration are created with the help of MySQL. Models, Controllers, Views are coded with
a software Sublime text. After the development of website, another important thing testing
is also done by team. They done both unit testing and system testing. Now software is in
working state.
85
CHAPTER 9
Deployment
9.1 Deployment Diagram
87
REFERENCES
1. https://www.google.com/
2. https://www.wikipedia.org/
3. https://www.youtube.com/
4. https://github.com/daveozoalor/pmanager
5. https://www.webopedia.com/
6. https://laravel.com/
7. https://www.techopedia.com/
89
APPENDIX

E-Trading Website: Project Supervisor

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E-Trading Website: Project Supervisor

Uploaded by

Copyright:

Available Formats

E-TRADING WEBSITE

Shoaib Iqbal BSIT-F14-E25

Division of Science & Technology, University of

Supervisor / Internal Examiner

Miss Ansif Arooj

1.2 PROJECT OVERVIEW STATEMENT…………………………………………………….02

1.3 PROJECT GOALS & OBJECTIVES……………………………………………………..04

1.4 HIGH LEVEL SYSTEM COMPONENTS………………………………………………….04

1.5 LIST OF FUNCTIONAL OPTIONAL UNITS………………………………………………04

1.7 APPLICATION ARCHITECTURE………………………………………………………....05

1.8 GANTT CHART………………………………………………………………………….06

1.9 HARDWARE & SOFTWARE SPECIFICATION……………………………………………07

1.10 TOOLS & TECHNOLOGIES USED WITH REASONING……………………………….07

2.1.1 CREATE USER ACCOUNT……………………………………………………….10

2.1.3 UPLOAD ITEM……………………………………………………………………10

2.1.4 SEARCH FOR PRODUCT/ COMPANY/ FREELANCER/INDIVIDUAL USER……10

2.1.5 COMPARING ITEMS……………………………………………………………..11

2.1.7 CHECK OUT/BUY AN ITEM…………………………………………………..11

2.1.8 SUBMIT PAYMENT…………………………………………………………….11

2.1.9 MANAGE PAYMENT…………………………………………………………...11

2.2 NON-FUNCTIONAL REQUIREMENTS……………………………………………….13

2.2.2 USER INTERFACE…………………………………………………………….13

2.2.9 SYSTEM REQUIREMENT……………………………………………………..14

2.3 DOMAIN REQUIREMENTS……………………………………………………………14

3.1 USE CASE OVERVIEW……………………………………………………………….16

4.3 AVAILABLE METHODOLOGIES……………………………………………………………44

4.4 CHOSEN METHODOLOGY…………………………………………………………………45

4.5 REASONS FOR CHOSEN METHODOLOGY………………………………………………..45

4.6 WORK PLAN………………………………………………………………………………..46

4.7 PROJECT STRUCTURE…………………………………………………………………….47

4.7.1 Team Structure…………………………………………………………………………47

4.7.2 Project Schedule (Submission Calendar)……………………………………………48

5.4 ARCHITECTURAL REPRESENTATION (ARCHITECTURE DIAGRAM)…………………….52

5.5 DYNAMIC MODEL: SEQUENCE DIAGRAMS……………………………………………..53

5.5.1 SEQUENCE DIAGRAM OF LOGIN PROCESS………………………………………53

5.5.2 SEQUENCE DIAGRAM OF REGISTRATION PROCESS……………………………54

5.5.3 SEQUENCE DIAGRAM OF BUYING PROCESS……………………………………55

5.5.4 SEQUENCE DIAGRAM UPLOAD ITEM…………………………………………….56

5.5.5 SEQUENCE DIAGRAM SEARCHING ITEM…………………………………………57

5.6 OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM………………………………….59

5.7 DEPLOYMENT MODEL (DEPLOYMENT DIAGRAM)………………………………………..60

5.8 DATABASE MODEL …………………………………………………………………………61

5.8.2 DATABASE SCHEMA…………………………………………………………………62

5.9 GRAPHICAL USER INTERFACES…………………………………………………………….68

5.9.1 WEBSITE INDEX PAGE………………………………………………………………68

5.9.2 USER PROFILE……………………………………………………………………….69

5.9.3 UPLOAD ITEM………………………………………………………………………..70

5.9.4 SEARCHING RESULT………………………………………………………………..71

5.9.5 ITEM PROFILE……………………………………………………………………....72

6.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)………………………………………...74

7.3 TEST CASES…………………………………………………………………………………..77

7.3.1 TEST CASE LOGIN PAGE………………………………………………………………77

7.3.3 TEST CASE UPLOAD PROFILE PICTURE…………………………………………….79

7.3.4 TEST CASE UPLOAD NEW ITEM……………………………………………………..80

7.3.5 TEST CASE COMMENTING ON ITEM…………………………………………………81

7.3.6 TEST CASE ORDERING AN ITEM……………………………………………………..82

7.3.7 TEST CASE COMPARING TWO ITEMS………………………………………………...83

8.2 FUTURE WORK…………………………………………………………………………………..85

9.1 DEPLOYMENT DIAGRAM…………………………………………………………………………87

1.2 Project Overview Statement

1.4 High-level system components

1.5 List of optional functional units