Web Based Uni Platform Application For Maintaining Shopping Malls

Web Based Uni Platform Application
For maintaining Shopping Malls
By
Bijjar Sayed
(BSCS/S14/0116)
M. Usman Khan
(BSCS/S14/0108)
M. Hassam Shakeel
(BSCS/S14/0101)
2018
Faculty of Engineering Sciences and Technology

Hamdard Institute of Engineering and Technology
Hamdard University, Karachi, Pakistan
For maintaining Shopping Malls
By
Bijjar Sayed
(BSCS/S14/0116)
M. Usman Khan
(BSCS/S14/0108)
M. Hassam Shakeel
(BSCS/S14/0101)
Under the Supervision of

Mr. Afzal Hussain
2018

For Maintaining Shopping Malls
By
Bijjar Sayed
(BSCS/S14/0116)
M. Usman Khan
(BSCS/S14/0108)
M. Hassam Shakeel
(BSCS/S14/0101)
A Project Presented to the

In partial fulfillment of the requirements for the degree
Bachelors of Science
In
Computer Science

CERTIFICATE
This project “Web Based Uni Platform Application for Maintaining Shopping Malls” is
presented by Bijjar Sayed, M. Hassam Shakeel and M. Usman Khan under the supervision
of their project advisor and approved by the project examination committee, and acknowledged
by the Hamdard Institute of Engineering and Technology, in the fulfillment of the requirements
for the Bachelor degree of Computer Science.
_____________________ _______________________
In-charge FYP-Committee Mr. Afzal Hussain
(Project Supervisor)
______________________ _______________________
Prof. Dr. Aqeel-ur-Rehman Muhammad Fahad
Chairman (Project Co-Supervisor)
(Department of Computing)
_______________________
Prof. Dr. Vali Uddin
(Dean, FEST)
Acknowledgement
All praises to Al Mighty” ALLAH”, the most merciful, the most gracious, the source of
knowledge and wisdom end owed to mankind. All respects for Holy Prophet “Hazrat
MUHAMMAD ‫ﷺ‬, whose personality will always be source of guidance for humanity.
Acknowledgement is due to Hamdard Institute of Engineering and Technology for support of

this Project, a highly appreciated achievement for us in the undergraduate level.
We wish to express our appreciation to our Supervisor, Mr Afzal Hussain who served as our
major advisor. We would like to express our heartiest gratitude for their keen guidance, sincere
help and friendly manner which inspires us to do well in the project and makes it a reality.
Many people, especially our classmates and team members itself, have made valuable comment
suggestions on this proposal which gave us an inspiration to improve our project. We thank all
the people for their help directly and indirectly to complete our project.
I
Abstract
E-commerce is not a new thing but has been a great source of online business for many years. In
the modern world internet has made business much easier through online transaction and virtual
stoppings, banks have moved to internet banking which has given benefits to e-commerce.
It’s very common these days to order anything from online and get the product at your gate, all
you need to do is go to that particular shop website and order and even pay the bill online.
This process is quite easy for large business vendor’s to obtain a website and maintain it for their
customers, their budget is well enough to permit large vendor’s to obtain a website and maintain
for business purposes. As earlier discussed E-commerce is growing rapidly, business owner
focuses on coming online to facilitate their customers, at the same time small business owner
require their own website for the business too.
The project focuses on small vendors to help them get their business online. The project
addresses that to obtain a single platform and allow multiple shops to business online. The
purposed project targets a shopping mall where different business owners are running their
businesses having multiple website, which is quite difficult for customer to remember each
website name too. The project will have a single name to let the customer to browse through that
one single name and virtually visit each shop present at the shopping mall be a small are large
vendor. The project will also resolve the budget problem for small business owner as having a
stand-alone website will require them a greater budget than the budget is require to obtain a
portion of proposed project.
Keywords: E-commerce, content management system (CMS), single platform, virtual visit.
II
Table of Contents
Acknowledgement ..........................................................................................................................I
Abstract ......................................................................................................................................... II
Table of Contents ......................................................................................................................... III
List of Figures .............................................................................. Error! Bookmark not defined.
List of Tables ............................................................................................................................. VII
List of Abbreviations ................................................................................................................ VIII
CHAPTER 1 ................................................................................................................................. 1
INTRODUCTION TO THE PROJECT ........................................................................................ 1
1.1 Introduction ......................................................................................................................... 1
1.2 Purpose................................................................................................................................ 1
1.3 Motivation ........................................................................................................................... 1
1.4 Problem Statement .............................................................................................................. 2
1.5 Background ......................................................................................................................... 2
1.6 Solution Scope .................................................................................................................... 2
CHAPTER 2 ................................................................................................................................. 3
DETAILED REQUIREMENTS SPECIFICATION ..................................................................... 3
2.1 Functional Requirements System Features ......................................................................... 3
i. Admin .................................................................................................................................. 3
ii. Shop panel ........................................................................................................................... 4
User Purchase ..................................................................................................................... 5
2.2 Non-Functional Requirements ............................................................................................ 7
i. Performance ........................................................................................................................ 7
ii. Security ............................................................................................................................... 7
iii. Usability .............................................................................................................................. 7
iv. Portability ........................................................................................................................... 7
2.3 Software Quality Attributes ................................................................................................ 7
i. Availability .......................................................................................................................... 7
2.4 Assumptions and Constraints .............................................................................................. 7
i. Constraints .......................................................................................................................... 7
ii. Assumptions ........................................................................................................................ 8
CHAPTER 3 ................................................................................................................................. 9
III
How It Works................................................................................................................................. 9
3.1 Admin Login ..................................................................................................................... 10
3.2 Admin Dashboard ............................................................................................................. 11
3.3 Malls Listed ...................................................................................................................... 12
3.4 Shop Creation.................................................................................................................... 13
3.5 Vendor Panel (Shop Insertion).......................................................................................... 14
3.6 Edit and Update product ................................................................................................... 15
3.7 Implementation ................................................................................................................. 16
3.8 Home Page ........................................................................................................................ 17
CHAPTER 4 ............................................................................................................................... 19
Software Development Model ..................................................................................................... 19
4.1 Methodology ..................................................................................................................... 19
4.2 Requirement Phase............................................................................................................ 19
4.3 Development Phase ........................................................................................................... 20
4.4 Testing Phase .................................................................................................................... 21
Black Box Testing .......................................................................................................... 22
System Testing ............................................................................................................... 22
Unit Testing ................................................................................................................... 23
Integration testing ......................................................................................................... 23
Functional testing.......................................................................................................... 23
User Acceptance Testing ............................................................................................... 23
Finalized testing ............................................................................................................ 24
4.5 Test Cases ......................................................................................................................... 24
4.5.1 Test Case # 1 ................................................................................................................. 24
4.5.2 Test Case # 2 ................................................................................................................. 25
4.5.3 Test Case # 3 ................................................................................................................. 25
4.5.4 Test Case # 4 ................................................................................................................. 26
4.5.5 Test Case # 5 ................................................................................................................. 26
4.5.6 Test Case # 6 ................................................................................................................. 27
4.5.7 Test Case # 7 ................................................................................................................. 27
4.5.8 Test Case # 8 ................................................................................................................. 28
CHAPTER 5 ............................................................................................................................... 29
Project Planning ........................................................................................................................... 29
IV
5.1 Project Timeline ................................................................................................................ 29
5.2 Designing Phase ................................................................................................................ 30
System Diagram ........................................................................................................................... 30
CHAPTER 6 ............................................................................................................................... 34
TOOLS AND TECHNIQUES ..................................................................................................... 34
6.1 Project Techniques ............................................................................................................ 34
CSS (Cascading Style Sheet) ......................................................................................... 34
Smart Draw ................................................................................................................... 34
Java Script ..................................................................................................................... 34
HTML ............................................................................................................................ 34
6.2 Project Tools ..................................................................................................................... 35
Web-Browser ................................................................................................................. 35
Visual Studio ................................................................................................................. 35
Sublime 3 ....................................................................................................................... 36
Notepad++ .................................................................................................................... 36
MS-Project .................................................................................................................... 36
MS-Word ....................................................................................................................... 36
MS-PowerPoint ............................................................................................................. 36
CHAPTER 7 ............................................................................................................................... 37
CONCLUSION AND FUTURE WORK .................................................................................... 37
7.1 Limitation .......................................................................................................................... 37
7.2 Conclusion ........................................................................................................................ 37
7.3 Future Work ...................................................................................................................... 37
REFERENCES ........................................................................................................................... 38
APPENDICES ............................................................................................................................ 39
Appendix A: Admin login ........................................................................................................... 39
Appendix B: Customer CMS Creation ....................................................................................... 40
Appendix C: Dashboard ............................................................................................................... 43
Appendix D: Mall Creation ......................................................................................................... 46
Appendix E: Customer Management Dashboard ........................................................................ 47
Appendix F: Customer Product Edits .......................................................................................... 50
Appendix G: Customer Order List ............................................................................................... 52
Appendix H: Purchasing User Login ........................................................................................... 55
V
List of Figures
Figure No Descriptions Page No.
Figure 1.1 : Solution Scope ............................................................................................................ 2

Figure 2.1 : Admin Panel ............................................................................................................... 4
Figure 2.2 : Customer Panel........................................................................................................... 5
Figure 2.3 : User CMS ................................................................................................................... 6
Figure 3.1 : Login Pages ................................................................................................................ 9
Figure 3.2 : Admin Authentication .............................................................................................. 10
Figure 3.3 : Authorization Policy................................................................................................. 10
Figure 3.4 : Admin Dashboard..................................................................................................... 11
Figure 3.5 : List of Malls ............................................................................................................. 12
Figure 3.6 : Shop CMS Creation.................................................................................................. 13
Figure 3.7 : Shops inside Mall ..................................................................................................... 14
Figure 3.8 : Product Insertion Panel ............................................................................................ 14
Figure 3.9 : Product Edits ............................................................................................................ 15
Figure 3.10 : Product Updates ..................................................................................................... 16
Figure 3.11 : Customer Login ...................................................................................................... 16
Figure 3.12 : Users Login (Purchase) .......................................................................................... 17
Figure 3.13 : Initial UI ................................................................................................................. 18
Figure 4.1 : Methodology ........................................................................................................... 19
Figure 4.2 : Coding Sample (1).................................................................................................... 20
Figure 4.3 : Coding Sample (2).................................................................................................... 21
Figure 5.1 : System Diagram ....................................................................................................... 30
Figure 5.2 : Activity Diagram ...................................................................................................... 31
Figure 5.3 : Use Case ................................................................................................................... 33
VI
List of Tables
Table No. Descriptions Page No.
Table 4.1 : Testing the Create Account. .................................................................................... 24

Table 4.2 : Testing the Main Page access. ................................................................................. 25
Table 4.3 : Data addition to database through UI. ..................................................................... 25
Table 4.4 : Testing the viewing the products by user. ............................................................... 26
Table 4.5 : Testing the registration request by user. .................................................................. 26
Table 4.6 : Admin can view the request of user. ....................................................................... 27
Table 4.7 : Testing users should be able to register. .................................................................. 27
Table 4.8 : Testing that users adding products to cart. .............................................................. 28
Table 5.1 : Phases of Project ...................................................................................................... 29
VII
List of Abbreviations
CMS: Content Management System
DB: Database
CSS: Cascading Style Sheet
HTML: Hypertext Markup language
HTTP: Hypertext Transfer Protocol
UAT: User Acceptance Testing
UML: Unified Modeling language
PC: Personal Computer
MS: Microsoft
E-Commerce: Electronic Commerce
VIII
CHAPTER 1
INTRODUCTION TO THE PROJECT
1.1 Introduction
The project web based uni platform application for maintaining shopping malls in unique itself
by providing facility to small business owners in a huge shopping mall to use E-commerce
feature in a mutual website containing one entire shopping mall.
Actually the idea is to combine a whole shopping mall in a signal website in which multiple
(may be 100) shops running in the particular mall. For each shop a separate content management
system (CMS) is created so they can place and view their products and orders.
The web based uni platform application for maintaining shopping malls and is a Web based
platform for the digital aspects that allows small business owner to share the entire web app for
their customer facilitation.
Taking an example of ABC shopping mall which has 100 shops in it and when a client intends
to buy some product to that particular ABC mall, he/she simply brows the ABC.com and
virtually visits each shop be a small or a large outlet. He /she has nothing to do with the
remembering each shop name and their web site name so to shop.
It integrates an entire shopping mall supporting multiple functions. It also incorporates all the
following tools within one single software environment.
1.2 Purpose
The purpose of the project is to make E-commerce easier than ever buy the integration of
multiple CMS. Further the purpose extends to make the E-commerce operations easier such as
product placement, order views and monthly report card.
1.3 Motivation
It has said every problem drives to some solution, similarly in this project the problem was to
find a single web site that contains many shops and their CMSs for online shopping. While
having our literature review we could not find such a website so we took that challenge to
develop that solution by our self that can facilitate shopping malls for better use of E-commerce.
1
1.4 Problem Statement
Observing that people are often confused where to shop online similarly small business owner
facing same problem how to acquire a website and how to advertise it so people should know.
Having stand-alone website cost them quite much and its social media advertisement and
marketing is another cost, this fear often leaves them in dark rooms.
1.5 Background
The basic purpose for reviewing is to relate to ongoing research to develop that knowledge. The
literature review may resolve the argument and provides better exposure to the current research.
Literature review is significant factor that allows the researcher to look back on the work done on
similar project and learn from their findings. The tenacity of literature review is to examine the
work done by older students and compare this system with other system. Most importantly a
review helps to find the right direction by critically analyzing the published paper/article.
1.6 Solution Scope

The basic purpose for reviewing is to relate to ongoing research to develop that knowledge. The
literature review may resolve the argument and provides better exposure to the current research.
Literature review is significant factor that allows the researcher to look back on the work done on
similar project and learn from their findings. The tenacity of literature review is to examine the
work done by older students and compare this system with other system. Most importantly a
review helps to find the right direction by critically analyzing the published paper/article. [1]
Figure 1.1 : Solution Scope
2
CHAPTER 2
DETAILED REQUIREMENTS SPECIFICATION
2.1 Functional Requirements System Features
The project basically consists of three major panels one is admin panel, second is client panel
(shops) and third one is customer panel (buyer panel). But the main panels are admin and
customer. Further defined below.
i.Admin
Admin can creates/delete accounts for clients and gives rights to client for managing their CMS.
We have facilitated our system by authentication, which lets management from admin panel.
Here happens the management of application with multiple options. [2] Product attributes
management, sales reports, prices charts and mall creations are key functions to be access from
dashboard. Somehow dashboard can be thought of a managerial room.
To access the Admin Panel, clink on admin link given on the bottom of web page, enter your
administrator account email address and password, and click log in [3]. All modern browsers
support. Transport Layer Security is a certificate for secure log in’s.
When navigating the dashboard of admin remain aware of that we round big quantities for the
dashboard view, but if you need to know you can click any of the numbers to see an exact count.
The information shown first on the dashboard provides a quick overview of users with bypass or
locked out status, inactive users who haven't logged in recently, your total end user count. Click
on any of these items to view a filtered list of users.
3
Description: The below figure describes about the admin panel. The Admin can manage their
dashboard to create accounts for shop owners, delete accounts and edit their data, as well
generate sales report.
Figure 2.1 : Admin Panel
ii.Shop panel
Shop owners can view their CMSs created by admin, they can manage their CMSs by adding
products their details [4].
Description: The below figure shows shop owners right’s to maintain their CMS. Once their
account is created further it’s up to them how they manage their CMS via login to their
dashboard. They can add products with their details, view orders and generate sales reports.
4
Figure 2.2 : Customer Panel
User Purchase
While the browsing or purchasing user has a separate CMS through which he/she adds products
to their cart and check out. For buying any product from any shops user has to register their selves
first so that their address could be collected for delivery as the web app currently offer cash on
delivery (COD) [5].
5
Figure 2.3 : User CMS
Descriptions: The above flow diagram shows the flow of user activity in the web. Initially user
selects the product then its added to cart, further if he continues shopping, again the said process
is conducted if not the exit for exit customer has to login if already registered if not then as to
register and insert address. [6]
6
2.2 Non-Functional Requirements
i. Performance
It is a web based application.
It allows multiple CMS creation
It can handle multiple users at the same time.
It is efficient.
ii.Security
Only the authorized users use the portal.
Its admin that creates client accounts.
Users have to fill their details to login
iii.Usability
Web app admin and client can create accounts first and can access it easily. It is user
friendly.
iv.Portability
The portal is made using HTML5, CSS3, C#, SQL server, bootstrap, which are platform
independent and can be transported to other services with minimum efforts.
2.3 Software Quality Attributes
i.Availability
If the internet services gets disrupted while sending information to the server. The
information can be sent again.
2.4 Assumptions and Constraints
i.Constraints
The project User interface only supports English language.
7
Admin and User have to login using their registered user name and passwords i.e.
Limited to HTTP.
ii.Assumptions
User Interface is only in English i.e. no other language option is available

Admin, Teacher and Students can login only with his/her assigned Username and
Password i.e. limited to HTTP.
8
CHAPTER 3
How It Works
This developed system is intended to work not like other typical E-commerce website in which
their product are list and any buyer/ user register to add their post addresses. In the proposed
system we have taken the owners involvement in our priority to let the shop owners to be
involved in add products, receiving orders, approving order and delivering orders [7]. This
process will help owners to run their web independently.
In first phase admin has to register who is the main admin of whole website.
Figure 3.1 : Login Pages
The above figures show the registration and admin login pages for main admin, where the main
admin register himself/herself to further create malls. Until there is no admin there cannot be
any malls created. While the register option is shown in user interface (UI) through which admin,
customer and the purchasing user can login. But for the admin perspective the process is different
as using registration option anybody can make an admin account and create malls. The process
is further discussed in next figure.
9
3.1 Admin Login
When the admin is registered via the web registration form then admin has to make yourself as
admin from the server. Until the admin make changes for admin and authorizes himself/herself
as admin from server side he/she cannot access the web as admin and create malls. The below
snap is of server where the admin has made changes from server [8].
Figure 3.2 : Admin Authentication
As the admin as the developer and has the access to server. The above figure show the two
column named “Adduser” and “Auth” these two column determine the rest of the work for
admin. The admin has to write admin and Y for yes to authorization the he she can login as
admin.
Figure 3.3 : Authorization Policy
While the second figure show those same “Adduser” and “Auth” column filled with N, this
means these are simple customer or purchasing user who do not have privileges to create malls
10
and access to dashboard.
3.2 Admin Dashboard

Once the admin is logged in will be presented with the dashboard of creating malls, reports and
management. Dashboard of a website presents the best of website functions that are used as
management functionalities. Dashboard is the admin panel somehow can be thought of setting
panel. It is the setting panel for the entire website. Here's an example:
Figure 3.4 : Admin Dashboard
When the admin is in, further will be presented with these facilities listed above. Mall creation
and management. The admin is also well aware of total orders, suppose one time there are 10
malls created and each mall consist of 10 shops and each shop containing thousands of product
the mall management can track how many products are available currently in the mall, similarly
can track how many orders have be placed with the total cost. Moreover the Mall management/
11
admin can select any of mall to check how many orders and products are available to that
particular mall. This makes the work of management to be aware of any fraud is being done by
the shop employees [9].
We design our Website Dashboard UI in a way that users can easily understand and ease to
learn. In fact, if you use email sites or if you navigated or used any e-commerce site we know
that you are not going to face any problem using it. No code or password is needed to use our
website’s dashboard or to edit any website’s content. And, if you face any difficulties, problems
or unable to understand any function and the built-in documentation does not help you, user can
simply get in touch with us for free support.
3.3 Malls Listed

Whatever mall is created is shown on main page, where users can visit to any particular mall of
their interest. Malls are further extended with shops for the virtual visits and shopping. Malls
may very buy the number of shops. Once the mall is selected will redirect to shops where each
shops contains specific products.
Figure 3.5 : List of Malls
Suppose luck one mall is brows it will take to its shops where may be 10, 12, or 15 shops
12
available. Shop owners to which mall they create their Shop CMS and start adding their product.
But the best way of creating CMS is to create it where the actual shop is presented so it will
become easier for user for physical visit.
3.4 Shop Creation

The shop creation depends upon admin, until admin creates a mall shop connot be created.
So to create a shop admin mast create at least one mall. Now that mall is create shop owners
register through registration form above mentioned and will be redirected to Interface shown
below.
Figure 3.6 : Shop CMS Creation
The figure shows when the shop owner is registered will be presented with this page where shop
owner creates a shop and list a mall from list view according to their shop presence.
Such as Hassam has created a shop named as Electro word in lucky one mall.
13
Figure 3.7 : Shops inside Mall
3.5 Vendor Panel (Shop Insertion)

Vendor panel is the insertion page for shop owners to add product and categories. This page lets
the shop owners to add product and entire detailing of products. Shown below.
Figure 3.8 : Product Insertion Panel
Using the above option shop owner will be able to fully determine product details, whether it’s
14
pricing, discount, categorizes and product updates such as deletion of product and price updates
when you have to decrease the price anyway. Creating different categories. These all functions
are listed here for shop owner.
3.6 Edit and Update product

Description: Suppose a product has to be deleted or made changes to its pricing or detailing
will be performed accessing this page.
Figure 3.9 : Product Edits
Description: while edit product panel shows all the product of entire shop to access the particular
product you must click to that and enter to edit product.
15
Figure 3.10 : Product Updates
3.7 Implementation
Description: This is the Sign Up page of our project. By Sign Up by this page admin and user
can registered their ids. [10]
Figure 3.11 : Customer Login
16
Description: This is the login page of both customer panel and user panel.
Figure 3.12 : Users Login (Purchase)
3.8 Home Page

That first view of a website is its homepage. Visitor often use any of search engine out there for
website, it also serves a lot as a landing page to attract visitors the more attractive the home page
is the more users like it to use attractive in a sense that website UI/UX is designed in a way that
users find it easy to use and it looks also attractive. The home page is used to linked to other pages
on the site by providing links to all pages, products, and it also contains a search box which saves
time of the user by typing the desired product the search bar will navigate to the desired product
that users wants to buy. It also contains a banner that shows the latest products that have been
added recently by the website’s shopkeeper’s which makes it easier to know that which products
are recently edit. It also contains ADMIN LOG IN, Shopkeeper LOG IN and User LOG IN links.
It also contains create shop button (registered shopkeeper’s can create their shops) [11], Login
button (For registered users and shopkeeper’s), Register Button (For new users that needs to be
17
registered to shop) on the bottom of the home page admin button (For admins to log in), my shop
button (For shopkeeper’s to view their shops), Manage shop button (For shopkeepers to manage
their shops adding products or do other things) and other information links.
Description: This is the initial IU when users brows to the UHB web. The will be presented with
this interface.
Figure 3.13 : Initial UI
18
CHAPTER 4
Software Development Model
4.1 Methodology
We have used Evolutionary development methodology for development of our project.
Evolutionary Methodology.
 Evolutionary Models are iterative type models.
 Evolutionary Model allow to develop more complete version of the software.
 Evolutionary prototyping is the most integral form of prototyping.
Figure 4.1 : Methodology
4.2 Requirement Phase

In requirement phase we have gathered all the requirements that are required in our project.
 Our FYP is based on web based application in which admin and client make
accounts and can access easily.
 Admin can update information, create/delete accounts.
 Customer can view the information, pictures and shops virtually. They can only
view data and can edit cart.
19
4.3 Development Phase
Coding samples
Description: This is the coding sample of admin and this is the code admin dashboard.
Figure 4.2 : Coding Sample (1)
20
Description: This is the coding sample of user panel and this is the code user dashboard.
Figure 4.3 : Coding Sample (2)
4.4 Testing Phase

Before Deployment of project we had test each operations of Application by using SQL server
connectivity with visual studio.
 We Fix Errors and Bugs Such as
 File Validation
 File Handling
 Session Handling
21
 Database connectivity and Retrieval data.
Black Box Testing

Black-box testing, is a software testing technique to test functionalities of any system developed,
without having looked into its internal or workings. The method black box testing can almost be
implement to every stage of development: unit, integration and acceptance. It’s not the best or
the high level test but mostly preferred over unit test as unit test is just bound to only one
function. The method tends to obtain errors from these below mentioned categories:
 Inappropriate/ functions missed
 Interface bugs
 Bugs in structure/ data retrieval from database
 Performance bugs
 Admin and User should have login portal by using username and password
 Only registered admin and user can access the portal
 Behavior and performance errors
 Initialization and termination errors
System Testing
System testing, is a process that involves system testing. While in this phase users are given
different sort of trainings to use system. In system testing, it’s on users how the use system
according to their working and changes are made accordingly. Some précised set of data are
arranged to test. Meanwhile, test is carried out bugs are observed and noted to be fixed. The staff
that is going to operate the system are given trainings. This is the stage where the major goal is
to make sure that the system is working properly as well efficiently. Testing is a very crucial
task for the successful running of system.
Major types of system testing are:

 Unit Testing
 Integration Testing
 User acceptance Testing
 Functional Testing
22
Unit Testing
Unit testing is a method of software testing in which systems are broken into smallest parts to
test. Such as a sign up page is tested alone where it work properly. This testing type is also called
module or single function test. The modules are tested separately in unit testing. This type of
tests are also taken meanwhile development, as after every function developed and tested.
Integration testing
Meanwhile unit test is carried out on small and sample units of software, whereas Integration
testing is carried when multiple of units are together and test. It is supposed system as a whole
tested. Integration testing is done after unit test and before validation is tested. The integration
testing has the facility to take the results of unit testing and test the system in a larger scope.
Basically, in integration testing developer integrates two or more units as combine to test, such
as sign up and login, these both are tested together to check whether after signup system allows
to sign in with those username and password used in sign up. In this way we can clearly see the
output of one unit is impacting the second one. The ultimate motive of any testing method is to
uncover the errors related to functionalities or development.
Functional testing
Like other testing technique functional testing is a method of software testing used in software
development where software is tested to conform to all requirements. Functional testing is a
method of testing software to determine that the software has its all functionalities. This
technique is a sort of black box which considers test cases of similar software tested earlier. To
check/test Functions, system is given input and the outputs are observed whether or according
to specification or not. Functional testing often determines what system does
User Acceptance Testing

User acceptance testing (UAT), is said to be ultimate stage of testing. The ultimate task of the
system is to satisfy the user by performing certain task that the user require. During UAT, the
user (for whom the software is developed) of system has to be satisfied by the performance
required, according to specifications. User acceptance testing (UAT) of a system is the major
factor of system that determines the successful working of developed of system. The
23
application/system that is being tested should be engaged with user constantly so that user should
be putting load to check the efficiency and accuracy.
Finalized testing
We encounter and fix errors, bugs before the portal is accepted for operational use. The portal has
been tested by uploading, viewing information, reserved request, searching location date and accept
reserved request.
4.5 Test Cases

When a system is developed, different types of test cases are carried out from this. Of course the
motive behind is to verify/ validate the specification and requirement. Generally test cases are
derived from similar projects developed earlier with the same parameter.
4.5.1 Test Case # 1

Test Case Title: Testing the Create Account mechanism of “Web Based uni Platform
application for maintaining shopping malls”
Table 4.1 : Testing the Create Account.
Procedures Description
Preconditions Make a member in the system by create account
Action Click submit button after adding information of new user
Expected Result System would add new user into the database
Tested By Bjjar Sayed, M. Hassam and M. Usman Khan
Result Pass
24
4.5.2 Test Case # 2
Test Case Title: Testing the Main Page access of “Web Based uni Platform application for
maintaining shopping malls”
Table 4.2 : Testing the Main Page access.
Preconditions
Users must login in the system
Actions Click on login button in login panel after providing

username and password
Expected Results System should identify the user request to get into its panel
of the system according to his role.
Result Pass
4.5.3 Test Case # 3

Test Case Title: Testing the uploading material by Web Based uni Platform application for
maintaining shopping malls
Table 4.3 : Data addition to database through UI.
Preconditions Customer may insert the data
Action Customer adding data
Expected Result Data should be uploaded on portal by Customer
Tested by Bjjar Sayed, M. Hassam and M. Usman Khan
Result Pass
25
4.5.4 Test Case # 4
Test Case Title: Testing the data addition by customer and can be viewed and by user in Web
Based uni Platform application for maintaining shopping malls.
Table 4.4 : Testing the viewing the products by user.
Preconditions User may view the product by the customer
Actions User can view the products
Expected Result Material should be viewed by the user
Result Pass
4.5.5 Test Case # 5

Test Case Title: Testing account creation for customer by admin in “Web Based uni Platform
application for maintaining shopping malls”.
Table 4.5 : Testing the registration request by user.
Preconditions Customer account creation
Actions Admin creates account for customer
Expected Result Account should be created
Result Pass
26
4.5.6 Test Case # 6
Test Case Title: Testing that customer should login using given ID passwords by admin on web
app.
Table 4.6 : Admin can view the request of user.
Preconditions Customer login
Actions Customer to login via ID password given
Expected Result ID password should be authentic
Result Pass
4.5.7 Test Case # 7

Test Case Title: User can register to web app.
Table 4.7 : Testing users should be able to register.
Preconditions Users are able to register
Actions Users creating accounts
Expected Result Users should be able to create account
Result Pass
27
4.5.8 Test Case # 8
Test Case Title: Users should be able to add products to cart.
Table 4.8 : Testing that users adding products to cart.
Preconditions Users adding products to cart
Actions Inserting products to cart by users
Expected Result Products should be shown in cart
Result Pass
28
CHAPTER 5
Project Planning
5.1 Project Timeline
Description: Below table contains the information of various phases of project.
Table 5.1 : Phases of Project
Responsible
No. Phase Duration Action Performed
Person
Non-Functional
Bijjar Sayed
Requirement &
1 50 Days Hassam Shakeel
Gathering Functional
Usman Khan
Requirements
Functional Bijjar Sayed
Requirement
2 30 Days & Hassam Shakeel
Analysis
System Analysis Usman Khan
Bijjar Sayed
User Interface and
3 Designing 45 Days Hassam Shakeel
System Flow
Usman Khan
Front-End Bijjar Sayed
4 Development 62 Days & Hassam Shakeel
Backend Development Usman Khan
Black-Box Bijjar Sayed
5 Testing 25 Days & Hassam Shakeel
White-Box Testing Usman Khan
Bijjar Sayed
6 Documentation 30 Days FYP Report Hassam Shakeel
Usman Khan
Overall Project 245 Days
29
5.2 Designing Phase
System Diagram
System context diagrams show a system, as a whole and its inputs and outputs from/to external
factors.
System Context Diagrams represent all external entities that may interact with a system. Such a
diagram pictures the system at the center, with no details of its interior structure, surrounded by
all its interacting systems, environments and activities. The objective of the system context
diagram is to focus attention on external factors and events that should be considered in
developing a complete set of systems requirements and constraints.
System context diagrams are used early in a project to get agreement on the scope under
investigation. Context diagrams are typically included in a requirements document. These
diagrams must be read by all project stakeholders and thus should be written in plain language,
so the stakeholders can understand items within the document.
Description: This System Diagram shows how the Customer and Admin can access the
Application, this diagram also show that how task has been performed systematically.
Figure 5.1 : System Diagram
30
5.3 Activity Diagram
Description: This is the activity diagram of our project. This activity diagram shows the
working and activities done by admin, Customer and user.
Figure 5.2 : Activity Diagram
Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system. Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.
31
The control flow is drawn from one operation to another. This flow can be sequential, branched,
or concurrent. Activity diagrams deal with all type of flow control by using different elements
such as fork, join.
The basic purposes of activity diagrams is similar to other four diagrams. It captures the dynamic
behavior of the system. Other four diagrams are used to show the message flow from one object
to another but activity diagram is used to show message flow from one activity to another.
5.4 Use Case Diagram
This is the Use case diagram of our app in which admin and customer are the actors. Showing
information is edited and set by admin and customer updates the data.
A use case diagram is a graphic depiction of the interactions among the elements of a
system. A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. In this context, the term "system" refers to something being developed or
operated, such as a mail-order product sales and service Web site. Use case diagrams are
employed in UML (Unified Modeling Language), a standard notation for the modeling of real-
world objects and systems. System objectives can include planning overall requirements,
validating a hardware design, testing and debugging a software product under development,
creating an online help reference, or performing a consumer-service-oriented task. For example,
use cases in a product sales environment would include item ordering, catalog updating, payment
processing, and customer relations. A use case diagram contains four components.
32
Figure 5.3 : Use Case
33
CHAPTER 6
TOOLS AND TECHNIQUES
6.1 Project Techniques

For the Development of “Web Based uni Platform application for maintaining shopping
malls” we used these tools and techniques which are as follows:
CSS (Cascading Style Sheet)

We have used CSS3 for Design and it is used to create attractive pages of Web Based uni
Platform application for maintaining shopping malls. We have used CSS3 in Signup Page,
Login, Front-end Page, back-end Page. Cascading Style Sheets (CSS), is a presentation language
of document. CSS defines the webpages with the support of HTML and JavaScript, it is used
for visualization of webpages for better looks and feels that is user interface.
Smart Draw
Every project that are developed require some visualization and working flow. Flow charts are
important in a software development that shows how the system is going to work. Smart Draw
is tool to create flow charts for software project. We can also draw ERD diagram for project
after which we go for database creation.
Java Script
We have used Java Script for create ON Click function, alert function, delete data function, show
and hide function. JavaScript is a high-level, interpreted programming language. It is a language
characterized as dynamic, weakly typed, prototype based and multi-paradigm. It is used to make
WebPages interactive and provide online programs.
HTML
We have used HTML to create Structure of Class Management System such as Division, Header,
Footer, and Navigation bar Side Bar Tables. Hypertext Markup Language (HTML) is a standard
34
markup language for creating web pages and web applications. With Cascading Style Sheets
(CSS) and JavaScript, it forms a triad of cornerstone technologies for World Wide Web. HTML
describes the structure of a web pages semantically and originally included cues for the
appearance of the document.
6.2 Project Tools

The following hardware and software so far we have used in Web Based uni Platform
application for maintaining shopping malls is discussed below.
 Web-Browser
 Visual Studio
 Sublime
 Notepad++
 MS-Project
 MS-Word
 MS-PowerPoint
Web-Browser
We have used web browser like GOOGLE CHROME and Edge for viewing.
Visual Studio
To develop any kind of software project we require coding edition. By using which we create
our code and test for errors. Coding editors are also called compiler. Any programming language
supports some dedicated editors, we have developed our project using C# we support visual
studio. It’s a Microsoft coding editor supports multiple operating systems: Windows, Linux and
MacOs. It’s a free and open source editor that is very efficient and user friendly for development.
It’s also support many other languages like C++ and allows database connection and application
35
like desktop and web app both can be developed using visual studio.
Sublime 3
We have used Sublime3 for Html Coding. Sublime is sample and allow adding extension to
change the format for coding. Sublime has the facility to support many languages using changed
the extension according to the language.
Notepad++
Notepad++ code editor has been used to develop some parts of the project
MS-Project
We have used MS-Project to create FYP Timeline.
MS-Word
We have used MS Word to Create FYP Reports like Proposal, First evaluation, and final
evaluation.
MS-PowerPoint
We have used MS PowerPoint to create Presentations like Proposal, First evaluation, and Final
evaluation.
36
CHAPTER 7
CONCLUSION AND FUTURE WORK

7.1 Limitation
System will be designed on the defined.
Project will be delivered after final evaluation.
Customer (Shop owner) can’t become a part of system unless admins approval.
7.2 Conclusion
The project is an easy way for E-commerce. It has the vision of making easy way out for small
to large business owners to get their business online within the same domain of shopping mall.
It will not only help business owners to become online but also benefits to operate within the
same domain. Separate content management systems are the huge beneficiary factors for the
small businesses to maintain it easily. Every shop owner has to be registered via main admin
who creates them account which would become their CMS. Once their accounts are created
owners are presented with a dashboard where the start maintain and updating their CMS.
Meanwhile, by user perspective it’s also very helpful and user friendly as users’ needs to just
brows to only one site to visit multiple shops, their offerings and sales.
7.3 Future Work

i.Extend to multiple Malls
ii.Online payment method
iii.SMS Notifications
In future we add these features in our project to make our project more effective. Through Push
notification we can engage users more than a normal usage. The engaging of users is also be
done thorough SMS and E-mail notifications.
37
REFERENCES
[1] R. a. M. R. Kalakota, ""e-Business. Roadmap for Success,"," Addison Wesley, 1999.
[2] B. J. a. M. R. Jansen, ""An examination of searcher's perceptions of nonsponsored and

sponsored links during ecommerce Web searching."," Journal of the American Society for
information Science and Technology ,," no. 2006, p. p. 57.14, 1949-1961...
[3] H.-b. T. T. K. a. S. W. S. Kim, ""Modeling roles of subjective norms and eturst in customer
acceptance of airline B2C Ecommerce websites",," Turism Management,, (2009.
[4] R. M. Ballenger, ""An eCommerce Development Case: Your Company's eCommerce Web
Site..," Journal of Information Systems Education,, Vols. vol. 18.4,, p. p . 409, 2012.
[5] D. K. V. J. L. a. J. I. Duyne, ""The design of sites: patterns, principles, and processes for
crafting a customer-centered Web experience," 2002..," Addison-Wesley Longman
Publishing Co., Inc., vol. vol. 0.3, p. p . 289, 2002.
[6] L. M. F. a. L. G. Mich, ""Evaluating and designing web site quality."," IEEE MultiMedia,
vol. vol. 10.1, no. 2010, pp. pp. 34-43, 2005.
[7] H. J. H.-G. C. a. H.-G. H. Wen, ""E-commerce Web site design: strategies and models.,"
Information management & computer security,, vol. vol. 9.1, no. 2001, pp. pp. 5-12.
[8] L. F. G. a. P. P. Baresi, ""From web sites to web applications: New issues for conceptual
modeling.," 2000., 2012.
[9] ". F. a. R. K. F. a. R. K. Ricker, ""Order fulfillment: the hidden key to e-commerce success.,"
Supply chain management review, vol. vol. 11.3, no. 2005, pp. pp. 60-70, 1999.
[10] ". J. a. F. Z. J. a. F. Z. Song, ""Web design in e-commerce: a theory and empirical

analysis."," ICIS 2001 Proceedings (2001), Vols. ICIS Proceedings, vol. II, no. 2013., p. p.
24.
[11] R. a. M. R. Kalakota, " "e-Business. Roadmap for Success"," Addison Wesley, Chicago,
2014.
38
APPENDICES
Appendix A: Admin login

using System;
using System.Collections.Generic;
using System.Data;
using System.Data.SqlClient;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
namespace EcomProj2.Pages.General
{
public partial class Login : System.Web.UI.Page
{
MainBLL DL = new MainBLL();

protected void Page_Load(object sender, EventArgs e)
{
if (Session["UserName"] == null)
{
}
else
{
Response.Redirect(@"~\Pages\General\Malls.aspx");
}
}
protected void btnRegister_Click(object sender, EventArgs e)

{
Response.Redirect(@"~\Pages\General\Register.aspx");
}
protected void btnHome_Click(object sender, EventArgs e)

{
}
protected void btnLogin_Click(object sender, EventArgs e)

{
39
SqlParameter[] param = {
new SqlParameter("@UserName",SqlDbType.VarChar,50 ),//0
new SqlParameter("@Password",SqlDbType.VarChar,50),//1
new SqlParameter("@Auth",SqlDbType.VarChar,50)//1
};
param[0].Value = txtUsername.Text;
param[1].Value = txtPassword.Text;
param[2].Value = 'N';
DataSet ds = DL.FillDataSet("sp_Login", param);

if (ds.Tables[0].Rows.Count > 0)
{
string strIsShop = "";
string strCustomerCode = "";
string strUserName = "";
string strShopCode = "";
for (int i = 0; i < ds.Tables[0].Rows.Count; i++)
{
strIsShop = Convert.ToString(ds.Tables[0].Rows[0][0]);
strCustomerCode = Convert.ToString(ds.Tables[0].Rows[0][1]);
strUserName = Convert.ToString(ds.Tables[0].Rows[0][2]);
strShopCode = Convert.ToString(ds.Tables[0].Rows[0][3]);
}
if (strIsShop == "Y" || strIsShop == "N")

{
Session["IsShop"] = strIsShop;
Session["CustomerCode"] = strCustomerCode;
Session["UserName"] = strUserName;
Session["ShopCode"] = "SH000"+strShopCode;
Session["Auth"] = 'N';
}
else
{
lblError.Visible = true;
}
}
}
Appendix B: Customer CMS Creation

using System;
using System.Linq;
using System.Data;
40
using System.Web;
using System.Collections;
{
public partial class CreateShop : System.Web.UI.Page
{
DataSet DS_Cat_Code;
DataSet DS_CatName;
{
if (Session["UserName"] != null)
{
}
else
{
Response.Redirect(@"~\Pages\General\Login.aspx");
}
protected void btnSave_Click(object sender, EventArgs e)

{
new SqlParameter("@ShopCode",SqlDbType.VarChar,20), //0

new SqlParameter("@ShopName",SqlDbType.VarChar,150), //1
new SqlParameter("@ShopAddress",SqlDbType.VarChar,20), //1
new SqlParameter("@MallCode",SqlDbType.VarChar,20), //2
new SqlParameter("@ShopStartTime",SqlDbType.VarChar,50),
//3
new SqlParameter("@ShopCloseTime",SqlDbType.VarChar,50),
//4
new SqlParameter("@isActive",SqlDbType.VarChar,50),
//4
new SqlParameter("@IsFlag",SqlDbType.VarChar,50), //4
new SqlParameter("@AddUser",SqlDbType.VarChar,50) //5
41
};
Random a = new Random();

int code = a.Next(10, 100);
param[0].Value = "SH000" + code;
param[1].Value = ShopName.Text;
param[2].Value = ShopAddress.Text;
param[3].Value = DropDownList1.SelectedValue;
param[4].Value = DateTime.Now;
param[8].Value = Session["UserName"];
Session["IsShop"] = 'Y';
Session["ShopCode"] = "SH000" + code;
bool isSaved = DL.ExecuteSP_NonQuery("sp_Insert_Shop", param);
SqlParameter[] paramss = {
new SqlParameter("@UserName",SqlDbType.VarChar,15),
new SqlParameter("@AddUser",SqlDbType.VarChar,15),
new SqlParameter("@IsShop",SqlDbType.Char,1),
new SqlParameter("@IsActive",SqlDbType.Char,1),
new SqlParameter("@ShopCode",SqlDbType.VarChar,15)
};
{
paramss[0].Value = Session["UserName"];
}
else
{
paramss[0].Value = "Guest";
}
paramss[1].Value = "N";
paramss[2].Value = 'Y';
paramss[3].Value = 'Y';
paramss[4].Value = code;
bool isSave = DL.ExecuteSP_NonQuery("sp_Profile_Manage_Shop",

paramss);
42
}
Appendix C: Dashboard
using System;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
namespace EcomProj2.Pages.admin
{
public partial class Dashboard1 : System.Web.UI.Page
{

{
Label1.Text = "0";
Int32 count = 0;
String connetionString;
SqlConnection cnn;
connetionString = @"Data Source=ITWORLD\ITWORLD;Initial

Catalog=EcomDb ;User ID=sa;Password=itworld";
cnn = new SqlConnection(connetionString);
cnn.Open();
SqlCommand command;
SqlDataReader dataReader;
String sql = "Select ID from Orders ";
command = new SqlCommand(sql, cnn);
dataReader = command.ExecuteReader();
while (dataReader.Read())
{
count = Int32.Parse(dataReader.GetValue(0).ToString());
}
43
if (count >= 50) {
Response.Write("<script>alert('" + count + "');</script>");
}
cnn.Close();
// DropDownList1.SelectedValue =
Request.Params.GetValues(0).GetValue(0).ToString();
Label4.Text = "0";
Orderss();
Customers();
Products();
Price();
protected void Currencies_SelectedIndexChanged(object sender,

EventArgs e)
{
//if (DropDownList1.SelectedIndex.Equals(1)) {
//
Response.Redirect(@"~\Pages\admin\Dashboard.aspx?ShopCode=SH0008
9");
//}else
//{
//
Response.Redirect(@"~\Pages\admin\Dashboard.aspx?ShopCode="+Drop
DownList1.SelectedValue);
//}
}
private void Orderss()

{
//string sql = " select title,content from company";
//string con = "server=...";
System.Data.DataSet ds = new System.Data.DataSet();
// System.Data.SqlClient.SqlDataAdapter da = new
System.Data.SqlClient.SqlCommand(sql, con);
ds = DL.FillDataSet("sp_Orders_View", null);
// da.Fill(ds);
reptater.DataSource = ds;
//Label1.Text = reptater.Pag
44
reptater.DataBind();
private void Customers()

{
ds = DL.FillDataSet("sp_Profile_View_all", null);
// da.Fill(ds);
Repeater1.DataSource = ds;
Repeater1.DataBind();
private void Products()

{
ds = DL.FillDataSet("sp_Price_View", null);
// da.Fill(ds);
private void Price()

{
45
ds = DL.FillDataSet("sp_Price_View", null);
// da.Fill(ds);
Appendix D: Mall Creation
using System;
using System.Data;
using System.Linq;
using System.Web;
namespace EcomProj2.Pages.admin
{
public partial class MallCreate : System.Web.UI.Page
{

{
{
}
else
{
Response.Redirect(@"~\Pages\admin\Login.aspx");
}

{
46
new SqlParameter("@MallCode",SqlDbType.VarChar,20), //0

new SqlParameter("@MallName",SqlDbType.VarChar,150), //1
new SqlParameter("@MallAddress",SqlDbType.VarChar,20), //2
new SqlParameter("@MallOpenTime",SqlDbType.VarChar,50),
//3
new SqlParameter("@MallCloseTime",SqlDbType.VarChar,50),
//4
new SqlParameter("@isActive",SqlDbType.VarChar,50),
//4
new SqlParameter("@IsFlag",SqlDbType.VarChar,50), //4
new SqlParameter("@AddDateTime",SqlDbType.VarChar,50) //5
};

param[0].Value = "ML000"+a.Next(10, 10);
param[1].Value = MallName.Text;
param[2].Value = MallAddress.Text;
param[5].Value = 'Y';
param[6].Value = 'Y';
bool isSave = DL.ExecuteSP_NonQuery("sp_Insert_Mall", param);
Response.Redirect("/Pages/admin/Dashboard.aspx", false);
Appendix E: Customer Management Dashboard
using System;
using System.Data;
47
using System.IO;
using System.Linq;
using System.Text;
using System.Web;
namespace EcomProj2.Pages.Customer
{
public partial class Manageaccount : System.Web.UI.Page
{

{
HTML_ProductList();
if
(Request.Params.GetValues(14).GetValue(0).ToString().Equals("yes
"))
{
Label1.Text =
btnSave_Click();
}
}
private void HTML_ProductList()

{
new SqlParameter("@UserName",SqlDbType.VarChar,50),
};
param[0].Value =
ds = DL.FillDataSet("sp_Profile_View", param);
48
// da.Fill(ds);
}
private void btnSave_Click()

{
new SqlParameter("@UserName",SqlDbType.VarChar,50),//1
new SqlParameter("@Gender",SqlDbType.VarChar,10),//3
new SqlParameter("@FirstName",SqlDbType.VarChar,50),//4
new SqlParameter("@LastName",SqlDbType.VarChar,50),
new SqlParameter("@Email",SqlDbType.VarChar,150),
new SqlParameter("@DOB",SqlDbType.DateTime),
new SqlParameter("@Address1",SqlDbType.VarChar,50),
new SqlParameter("@Remarks",SqlDbType.VarChar,150),
new SqlParameter("@MobilePhone",SqlDbType.VarChar,15),
new SqlParameter("@isVerifiedByEmail",SqlDbType.Char,1),
new SqlParameter("@isVerifiedBySMS",SqlDbType.Char,1),
};
param[0].Value =
param[1].Value =
param[2].Value =
param[3].Value =
param[4].Value =
param[6].Value =
param[7].Value =
param[8].Value =
param[9].Value =
param[10].Value =
param[11].Value =
49
param[12].Value =
param[13].Value =
bool isSaved = DL.ExecuteSP_NonQuery("sp_Profile_Manage",

param);
Response.Redirect(@"~\Pages\admin\UserManagement.aspx");
}
Appendix F: Customer Product Edits
using System;
using System.Data;
using System.IO;
using System.Linq;
using System.Text;
using System.Web;
namespace EcomProj2.Pages.Customer
{
public partial class EditProduct : System.Web.UI.Page
{
{
HTML_ProductList();
if
(Request.Params.GetValues(5).GetValue(0).ToString().Equals("yes"
))
{
Label1.Text =
btnSave_Click();
}
}
50
private void HTML_ProductList()
{
new SqlParameter("@ItemCode",SqlDbType.VarChar,50),
};
param[0].Value =
ds = DL.FillDataSet("sp_Product_Manage_List", param);
// da.Fill(ds);
}
private void btnSave_Click()

{
new SqlParameter("@itemCode",SqlDbType.VarChar,50),
new SqlParameter("@item",SqlDbType.VarChar,50),
new SqlParameter("@desc",SqlDbType.VarChar,50),
new SqlParameter("@price",SqlDbType.Int),
new SqlParameter("@amount",SqlDbType.Int)
};
param[0].Value =
param[1].Value =
param[2].Value =
param[3].Value = Session["UserName"];
param[4].Value =
Int32.Parse(Request.Params.GetValues(3).GetValue(0).ToString());
51
param[5].Value =
Int32.Parse(Request.Params.GetValues(4).GetValue(0).ToString());
bool isSaved = DL.ExecuteSP_NonQuery("sp_Product_Manage",

param);
Response.Redirect(@"~\Pages\Shop\ProductList.aspx");
}
}
Appendix G: Customer Order List
using System;
using System.Text;
using System.Data;
using System.Linq;
using System.Web;
{
public partial class Order : System.Web.UI.MasterPage
{
{
{
Session["cart"] =
(Int32.Parse(Session["cart"].ToString())+(1)).ToString();
List<string> newList = new List<string>();

List<string> st2 = new List<string>();
st2 = (List<string>)Session["checkouts"];
foreach (var item in st2) {

newList.Add(item.ToString());
}
newList.Add(Request.Params.GetValues(0).GetValue(0).ToString());
52
Session["checkouts"] = newList;
String store = null;
List<string> st3 = new List<string>();

st3 = (List<string>)Session["checkouts"];
foreach (var item in st3)

{
store += item.ToString()+",";
}
store = store.TrimEnd(store[store.Length - 1]);
string[] array = store.Split(',').ToArray();
string[] eliminate = array.Distinct().ToArray();

String ab = "";
foreach (String dif in eliminate)
{
ab += dif.ToString()+",";
ab = ab.TrimEnd(ab[ab.Length - 1]);
txtProdId.Text = ab;
}
else
{
Response.Redirect(@"~\Pages\General\Login.aspx");
}
}

{
if (Session["CustomerCode"] != null)
{
SqlParameter[] paramss = {
new SqlParameter("@Shipping_Method", SqlDbType.VarChar,50),

//1
new SqlParameter("@Shipping_Address",SqlDbType.VarChar,50),
//2
new SqlParameter("@Prod_ID",SqlDbType.VarChar,50), //2
new SqlParameter("@Shop_Code",SqlDbType.VarChar,50), //2
new SqlParameter("@Approved",SqlDbType.VarChar,50), //2
53
new SqlParameter("@Customer_Code",SqlDbType.VarChar,50)
};
string[] array = txtProdId.Text.Split(',').ToArray();

String ass = "";
foreach (String dif in array)
{
ass += dif;
paramss[0].Value = txtShipMethod.SelectedValue;
paramss[1].Value = txtShipAddress.Text;
paramss[2].Value = dif.ToString();
paramss[3].Value =
paramss[4].Value = 'N';
paramss[5].Value = Session["CustomerCode"].ToString();
bool isSave = DL.ExecuteSP_NonQuery("sp_Insert_Shipping",

paramss);
new SqlParameter("@OrderID",SqlDbType.Int), //0

new SqlParameter("@CustomerCode",SqlDbType.VarChar,150), //1
new SqlParameter("@OrderDate",SqlDbType.DateTime), //2
new SqlParameter("@IsFlag",SqlDbType.Char,1),
new SqlParameter("@ProductId",SqlDbType.VarChar,50),
new SqlParameter("@ShopCode",SqlDbType.VarChar,50)
};

int code = a.Next(1, 100);
string[] arrays = txtProdId.Text.Split(',').ToArray();

foreach (String dif in arrays)
{
param[0].Value = code;
param[1].Value = Session["CustomerCode"];
54
param[5].Value = dif.ToString();
param[6].Value = Session["ShopCode"];
bool isSaved = DL.ExecuteSP_NonQuery("sp_Insert_Orders", param);
Session["checkouts"] = null;
Session["cart"] = null;
Response.Write("<script>alert('Successfully Send
Order');</script>");
}
else
{
Response.Redirect(@"~\Pages\General\Register.aspx");
Appendix H: Purchasing User Login
using System;
using System.Linq;
55
using System.Data;
using System.Web;
{
public partial class Register : System.Web.UI.Page
{
DataSet DS_Sub_Cat_Code;
DataSet DS_CatName;

{
if (Session["UserName"] == null)
{
}
else
{
}
IList bklist = GenderList();

if (!this.IsPostBack)
{
this.Gender.DataSource = bklist;
this.Gender.DataTextField = "Book";
this.Gender.DataValueField = "Author";
this.DataBind();
}
}
protected IList GenderList()

{
ArrayList allbooks = new ArrayList();
booklist bl;
bl = new booklist(" ", " ");

allbooks.Add(bl);
bl = new booklist("Male", "Male");

allbooks.Add(bl);
56
bl = new booklist("Female", "Female");
allbooks.Add(bl);
return allbooks;
}

{
if (txtPassword.Text.Length >= 5)
{
new SqlParameter("@CustomerCode",SqlDbType.Char,10),//0
new SqlParameter("@UserName",SqlDbType.VarChar,50),//1
new SqlParameter("@Password",SqlDbType.VarChar,150),//2
new SqlParameter("@Gender",SqlDbType.VarChar,10),//3
new SqlParameter("@FirstName",SqlDbType.VarChar,50),//4
new SqlParameter("@LastName",SqlDbType.VarChar,50),
new SqlParameter("@Email",SqlDbType.VarChar,150),
new SqlParameter("@DOB",SqlDbType.DateTime),
new SqlParameter("@CountryCode",SqlDbType.VarChar,10),
new SqlParameter("@ProvinceCode",SqlDbType.VarChar,10),
new SqlParameter("@CityCode",SqlDbType.VarChar,10),
new SqlParameter("@Remarks",SqlDbType.VarChar,150),
new SqlParameter("@HomePhone",SqlDbType.VarChar,15),
new SqlParameter("@MobilePhone",SqlDbType.VarChar,15),
new SqlParameter("@CreateDate",SqlDbType.DateTime),
new SqlParameter("@ShopCode",SqlDbType. VarChar,10 ),
new SqlParameter("@isVerifiedByEmail",SqlDbType.Char,1),
new SqlParameter("@isVerifiedBySMS",SqlDbType.Char,1),
new SqlParameter("@auth",SqlDbType.Char,1),
};

int store = a.Next(10, 100);
param[0].Value = "CC000" + store;
param[1].Value = txtUsername.Text;
param[2].Value = txtPassword.Text;
57
param[3].Value = Gender.Text;
param[4].Value = Name.Text;
param[5].Value = Last.Text;
param[6].Value = Email.Text;
param[8].Value = Address1.Text;
param[9].Value = Address2.Text;
param[10].Value = CountryCode.Text;
param[11].Value = ProvinceCode.Text;
param[12].Value = CityCode.Text;
param[13].Value = Remarks.Text;
param[14].Value = HomePhone.Text;
param[15].Value = MobilePhone.Text;
param[16].Value = "NO";
Session["CustomerCode"] = "CC000" + store;

Session["UserName"] = txtUsername.Text;
Session["Auth"] = 'Y';
bool isSaved = DL.ExecuteSP_NonQuery("sp_CustomerProfile",

param);
Response.Redirect(@"~\Pages\General\WantShop.aspx");
}
else
{
Response.Write("<script>alert('Password should be 5
characters');</script>");
}
}
}
}
58
59

Web Based Uni Platform Application For Maintaining Shopping Malls

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Web Based Uni Platform Application For Maintaining Shopping Malls

Hochgeladen von

Copyright:

Verfügbare Formate

Web Based Uni Platform Application

For maintaining Shopping Malls

Faculty of Engineering Sciences and Technology

Under the Supervision of

Faculty of Engineering Sciences and Technology

A Project Presented to the

In partial fulfillment of the requirements for the degree

Faculty of Engineering Sciences and Technology

Acknowledgement is due to Hamdard Institute of Engineering and Technology for support of

Figure No Descriptions Page No.

Figure 1.1 : Solution Scope ............................................................................................................ 2

Table 4.1 : Testing the Create Account. .................................................................................... 24

CMS: Content Management System

CSS: Cascading Style Sheet

HTML: Hypertext Markup language

HTTP: Hypertext Transfer Protocol

UAT: User Acceptance Testing

UML: Unified Modeling language

PC: Personal Computer

E-Commerce: Electronic Commerce

1.6 Solution Scope

Figure 1.1 : Solution Scope

Figure 2.1 : Admin Panel

2.3 Software Quality Attributes

2.4 Assumptions and Constraints

User Interface is only in English i.e. no other language option is available

Figure 3.1 : Login Pages

Figure 3.2 : Admin Authentication

Figure 3.3 : Authorization Policy

3.2 Admin Dashboard

Figure 3.4 : Admin Dashboard

3.3 Malls Listed

Figure 3.5 : List of Malls

3.4 Shop Creation

Figure 3.6 : Shop CMS Creation

3.5 Vendor Panel (Shop Insertion)

Figure 3.8 : Product Insertion Panel

3.6 Edit and Update product

Figure 3.9 : Product Edits

Figure 3.11 : Customer Login

Figure 3.12 : Users Login (Purchase)

3.8 Home Page

Figure 3.13 : Initial UI

Figure 4.1 : Methodology

4.2 Requirement Phase

Figure 4.2 : Coding Sample (1)

Figure 4.3 : Coding Sample (2)

4.4 Testing Phase

 We Fix Errors and Bugs Such as

Black Box Testing

Major types of system testing are:

User Acceptance Testing

4.5 Test Cases

4.5.1 Test Case # 1

Table 4.1 : Testing the Create Account.

Preconditions Make a member in the system by create account

Action Click submit button after adding information of new user

Tested By Bjjar Sayed, M. Hassam and M. Usman Khan

Table 4.2 : Testing the Main Page access.

Actions Click on login button in login panel after providing

4.5.3 Test Case # 3

Table 4.3 : Data addition to database through UI.

Preconditions Customer may insert the data