Final Project Report

On
Online Business Directory
(A web application)

Prepared By

Muhammad Ayoub (MCS-18-19)

Supervised By
Miss. Tahira Malik

Computer Sciences Department

University of Sahiwal, Sahiwal Campus

II
 DEDICATION

Our Parents and Teachers all who’ve given us their support during the development of
this project and for giving good ideas to prove ourselves as intellectuals in front of our
Respected Teachers.
 ACKNOWLEDGEMENT

Praise to Allah Almighty, Lord of the worlds, the Merciful and the Beneficent,
who gave us strength, thoughts and co-operative people to enable us to accomplish
this goal and fulfill the required functionalities.
This was all not possible without the guidance, continuous appreciation and moral
support by “Miss. Tahira Malik”. She was always there whenever we need her
help and ideas. We are really thankful to her who made our concepts clearer.
At last, we would like to acknowledge all of the assistance and contributions of
UNIVERSITY OF SAHIWAL for supporting us with all that is needed starting
from the books, and ending with the full care that it is providing us with, to help us
to be professionals in the field of Information Technology.

2
 DECLARATION

We hereby declare that we have developed this application and accompanied report
entirely on the basis of our personal efforts. Not any of the portions of the
application work presented has been submitted of any application for any other
qualification or degree of this or any other university or institute of learning.

Students Name & Signature

Muhammad Ayoub

_______________

3
 CERTIFICATE OF APPROVAL

It is to certify that the final year project of BS(CS) “Online Business Directory”
(A web application) was developed by Muhammad Ayoub under the supervision
of “Miss. Tahira Malik” and that in her opinion, it is in scope, fully adequacy and
quality of the degree of Bachelors of Science in Computer Sciences.

Supervisor External Examiner

Ms. Tahira Malik Name:

Lecturer Designation:

Department of Computer Science Organization:

University of Sahiwal

Signature:__________ Signature:_________

______________________________ ____________________________

Head of Department

Dr. Shafiq Hussain

Department of Computer Science

University of Sahiwal

Signature:____________

4
__________________________________________

Abstract
Business Directory Listing is a unique and specialized website with a Dynamic home page,
search bar and top listings. Customers can browse category wise directory listings. It has a
unique feature weekly opening & closing hours schedule. First customers will need to get
registered before creating a listing. If they are successful registered users and have a valid
package, then they are ready to create listings and get published. People around the country are
able to search business directory, filter them and can purchase directory price packages. Admin
is able to generate revenue selling packages.

5
 Table of Contents
1 INTRODUCTION.............................................................................................2

1.1 Introduction & History..................................................................................2

1.2 Statement of the Problem..............................................................................3
1.3 Objectives.....................................................................................................3
1.4 Proposed Solution.........................................................................................3
1.5 Motivation.....................................................................................................4
1.6 Scope of Proposed Solution..........................................................................4
1.7 Tools & Techniques......................................................................................5
1.7.1 Hardware Details.......................................................................................................5
1.7.2 Software Details.........................................................................................................5
1.8 Existing Applications:...................................................................................5
1.8.1 Eduvision:..................................................................................................................5
1.8.2 Ilm Ki Dunia:.............................................................................................................5
1.9 Drawbacks of Existing Applications............................................................6
1.10 The Necessity................................................................................................6
1.10.1 Education Assistant Confidentiality..........................................................................6
1.10.2 Accurate Records.......................................................................................................6
1.10.3 Minimum Latency.....................................................................................................6
1.10.4 Better Communication...............................................................................................6
2 REQUIREMENT ANALYSIS.........................................................................8

Requirements Gathering Techniques.....................................................................8

2.1 Requirement Analysis...................................................................................8
2.1.1 Functional Requirements...........................................................................................8
2.1.2 Non-Functional Requirements...................................................................................9
2.2 Application Quality Attribute.......................................................................9
2.2.1 Availability................................................................................................................9
2.2.2 Maintainability.........................................................................................................10
2.2.3 Consistency..............................................................................................................10
2.2.4 Portability................................................................................................................10

6
 2.2.5 Database Requirements...........................................................................................10
2.3 Use Cases....................................................................................................10
2.3.1 UC1: Login..............................................................................................................10
2.3.2 UC2: Register Member............................................................................................12
2.3.3 UC3: Manage Members...........................................................................................13
2.3.4 UC4: Change Password...........................................................................................14
2.3.5 UC6: Logout............................................................................................................15
2.4 Use case......................................................................................................16
2.5 The Necessity..............................................................................................17
2.5.1 High Speed Internet Connection..............................................................................17
2.5.2 Signup......................................................................................................................17
3 METHODOLOGY & WORKPLAN............................................................19

3.1 Adopted Methodology................................................................................19

3.2 Roles & Responsibilities.............................................................................20
4 SYSTEM ANALYSIS & DESIGN................................................................22

4.1 Activity Diagram........................................................................................22

4.1.1 Log in (user)............................................................................................................22
4.2 Sequence Diagrams.....................................................................................23
4.2.1 Sequence diagram (search data)..............................................................................23
4.2.2 Sequence diagram (fields recommendation)...........................................................24
4.3 Data flow diagram.......................................................................................25
4.3.1 Flow diagram (user panel).......................................................................................25
4.4 Class Diagram.............................................................................................26
4.5 Planning & Scheduling...............................................................................27
4.5.1 Gantt chart...............................................................................................................27
5 SYSTEM IMPLEMENTATION...................................................................29

5.1 Introduction.................................................................................................29
5.2 Screenshots.................................................................................................29
6 SYSTEM TESTING........................................................................................38

7
 6.1 Introduction.................................................................................................38
6.2 Testing Plan................................................................................................38
6.2.1 Unit Testing.............................................................................................................38
6.2.2 System Testing.........................................................................................................39
6.2.3 Integration Testing...................................................................................................39
6.2.4 User Acceptance Testing.........................................................................................39
6.3 Test Cases...................................................................................................39
6.4 Testing Results............................................................................................41
7 CONCLUSION & FUTURE WORK............................................................44

7.1 Conclusion..................................................................................................44
7.2 Future Work................................................................................................44
REFERENCES:.....................................................................................................45

8
 Table of Figures
Figure 1.1: About career counselling...............................................................................................4
Figure 2.1: Login (use case)..........................................................................................................11
Figure 2.2: Register Member (use case)........................................................................................12
Figure 2.3: Manage Members (Use Case).....................................................................................13
Figure 2.4: Change Password (Use Case)......................................................................................14
Figure 2.5: Logout (Use Case).......................................................................................................15
Figure 2.6: Use Case......................................................................................................................16
Figure 3.1: Adopted Methodology................................................................................................20
Figure 4.1: Activity diagram (login)..............................................................................................22
Figure 4.2: Sequence Diagram (search data).................................................................................23
Figure 4.3: Sequence Diagram (field recommendation)................................................................24
Figure 4.4: Flow diagram (user panel)..........................................................................................25
Figure 4.5: Class diagram (choose your career wisely).................................................................26
Figure 5.1: Sign Up (Screenshot)..................................................................................................29
Figure 5.2: Log In (Screenshot).....................................................................................................30
Figure 5.3: Admin Log In (Screenshot).........................................................................................30
Figure 5.4: Home Page (Screenshot).............................................................................................31
Figure 5.5: Latest Admission (Screenshot)...................................................................................31
Figure 5.6: Comment Box (Screenshot)........................................................................................32
Figure 5.7: Institutes detail (Screenshot).......................................................................................32
Figure 5.8: Admin detail (Screenshot)...........................................................................................33
Figure 5.9: Users detail (Screenshot).............................................................................................33
Figure 5.10: Send email to user (Screenshot)................................................................................34
Figure 5.11: Institute detail (Screenshot).......................................................................................34
Figure 5.12: Latest Admission (Screenshot).................................................................................35
Figure 5.13: Form for recommendation (Screenshot) Fields Recommendation...........................35
Figure 5.14: Fields Recommendation (Screenshot).......................................................................36

9
 List of Tables
Table 4-1: Project Plan & Key Milestones....................................................................................27
Table 6-1: Testing Cases...............................................................................................................39
Table 6-2: Testing Result..............................................................................................................41

CHAPTER # 1
INTRODUCTION

10
1 INTRODUCTION
In this section, we will introduce this application, software tools, problem statement, goals, the
scope of this application, the proposed application, the motivation of this proposed solution, and
its relevance to the lessons and tools and techniques used to implement this application.

1.1 Introduction & History

Whenever we move to a new region, region, State or country, our first goal is to address a
particular region, its people, its culture, where the various places it is very famous for, the
marketplace and the workplaces, etc. It is to be familiar. The only thing we are thinking about to
get all this information is the Trade Directory. Today, very difficult time students have no
guidelines regarding their field. The student has a certain knowledge about his fields. They don't
know the best area for their interests and studies.

The business directory is considered an important search tool for customers, both personally and
commercially. It meets your specific needs to find a specific area or locations in the smoothest
way. The business directory is the most reliable tool for anyone when they need it.

A business directory is a great way to search for places with great ease and convenience. It has
everything for everyone! Shopping in the marketplace, looking for partners for cinemas or
dining, contracting for home remodeling, plumber, electrician or carpenter for housework, or for
a well-known company, etc.

Business directory provides useful information about your various Searches in the friendliest
way. These days, you can have these job directories online or printable according to your needs.
Statement of the Problem

The business directory application is developed for users who wish to access, edit, search or
modify the business details of the companies by knowing only the names of it. India is a fast-

11
growing market, and growing disposable incomes mean more and more people entering the
target group for the services market. Also, the advent of newer enablers like mobile phones has
made life much easier for the customer, and as such there is tremendous scope for a referral
system like business directory.

1.2 Objectives

The main objectives of our project are following

 Provide facility of finding your Business.
 Provide all information about your Business listens.
 All information about top Business listing of Pakistan.
 Recommendation based on aria wise
 Customer can create new listing , and publish as well
 Recommendations will be sending to their account.

1.3 Scope of Proposed Solution

According to our survey which we have done to check the feasibility of this project, the modules
that are selected to be implemented in this web application (Online Business Directory) are the
modules that are found as a prior need of every customer. This application can fulfill the
requirements of every type of customer.

The online business directory publishes details of manufacturing, construction, wholesale and
business service companies.

The scope of this application cannot be considered too wide or too narrow the factor defining its
scope is its volume of data storage and as the way to use this application is very easy and
understandable therefore anyone can use it without any problem.

1.4 Tools & Techniques

Online Business Directory is Web based Project consists of software and hardware tools.

12
1.4.1 Hardware Details

 No Hardware Require except laptop/tablet/phones.

 Normal Internet Connection

1.4.2 Software Details

 Visual Studio Code Editor

 My SQL
 Xampp server
 PHP
 HTML5
 CSS3
 JAVASCRIPT

13
 CHAPTER # 2
REQUIREMENT ANALYSIS
2 REQUIREMENT ANALYSIS

In this section, needs analysis is discussed. The biggest challenge for developing any project is
requirement gathering. It is simpler to ask questions from customers than to gather requirements.
We will also focus on functional and non-functional requirements.

The procedure for gathering requirements has its own defined procedure according to the
complexity of the application. Different models and techniques were also focused in this section
to describe the project program and processing. Requirements Gathering Techniques

A requirement can be defined as a condition or capability that must be processed by a product or

an application. Techniques that can be used for collecting requirements are as follows:

 With questionnaire and survey

 With interview
 With observations
 Using software tools
 Using techniques for decision making
 Focus on facilitated groups and workshops
 Use of prototype

The techniques we have used to collect requirements are observations and interviews.

2.1 Requirement Analysis

Requirements analysis is the process of planning, predicting and reviewing the previous general
needs of application requirements. Requirements analysis is further divided into two parts:

1. Functional Requirements
2. Non-Functional Requirements

2.1.1 Functional Requirements

Functional requirements are requirements that must be met by an application. It is defined as a

service statement. Functional requirements tell how an application should behave in different

19
situations and how it will react to a particular input. The functional requirements of the Online
Business Directory are as follows: The main functions of our project are as follows:

 Users search businesses and category wise listing.

 Users signup, create listings, get publish listings.
 Users add favorite directories to Wish list & browse later/
 Users give rating and reviews
 User can also delete and update their profile record
 Recommendation based on Customer Search
 Admin of the system maintain the record of the website.
 Admin create & manage Listing category & subcategory listings.
 Admin manage Listing cities & Listing ratings

2.1.2 Non-Functional Requirements

Non-functional requirements are the constraints or checks on the services and functions
provided by an application such as constraints on the development standards/process and
constraints of time etc.

 Non-Functional requirements of OBD are as follows:

 Access
This application needs access to the network to store and retrieve record from central database
 Performance
Application provides the functions more efficiently, consistently, effectively without
any hurdle.

 User interface
The application provides an excellent user interface through user can easily able to
access the system
 Portability
The application can be easily accessible on every system which have proper internet
connection.
 Security
The application can be easily accessible on every system which have proper internet

20
2.2 Application Quality Attribute

2.2.1 Availability

 Application must be responsive and available at every time.

 Availability of high-speed internet connection is the major requirement of the application.

2.2.2 Maintainability

Making changes or upgradeability in the site will not be that much difficult. By having some
knowledge of programming, some features of the application might be converted to a new
version.

2.2.3 Consistency

When an administrator is updating information consistency must hold there.

2.2.4 Portability

OBD is web application that is why there is no problem in portability process.

2.2.5 Database Requirements

In this section, the database requirements for this application are mentioned:

We used MY SQL Server for database purpose.

2.3 Use Cases

An important part of the analysis phase is to drawing the diagrams of Use cases. They are used
through the phase of analysis of a project to find and divide functionality of the application.
Application is separated into actors and use cases.

Actors play the role that is played by the application users. Use cases define the application
behavior when one of the actors sends any particular motivation. This type of behavior can be
described by text. It describes the motivation nature that activates use case, the inputs and
outputs to some other actors and the behavior of conversion of inputs to the outputs. Usually the
use case describes everything that can go wrong during the detailed behavior and what will be
helpful action taken by the application.

21
Some of the use cases are as follows:

Some of the use cases are as follows:

2.3.1 UC1: Login

Actor: User
Search business
listing

Browse Directory
listings

Login

Create listing

Rating & feedback

1.1 Manage
1.3 Cust
Account
ome
1.4 Si
r
g

Figure 2.1: Login (use case)

Pre-Condition:

1. For the member, he/she must have registered already in application

2. User must enter correct Email address and password for login.

22
Post-Condition:

User can access to application’s main features.

Basic Path:

1. Enter Email-Address and password for login.

2. The application verifies the correct format and valid email address and Password.
3. If provided inputs are correct, the application displays the all other user’s content of the
application and session of particular user started.

Constraints:

1. If provided email address and password are incorrect or invalid, application redirect to main page.

Non-Functional Requirements:

1. Short Response Time

2. Better performance
3. Availability
4. Robustness

23
2.3.2 UC2: Register Member

Actor: Administrator

Manage users

Create listing &

Manage Listing

Admin
Dashboard Website
settings

1.7
1.5 Full
Adm
Websi
in
te
Figure 2.2: Register Member (use case)

Basic Path:

1. The administrator should be logged in to admin panel application to perform this activity.
2. The application verifies the valid entered inputs.
3. After verifying provided information; the application will generate the member account.
4. Admin check customer directories, he creates business listing.
5. Admin manage all listings and website content.

24
Alternative Path:

1. On wrong entries of mandatory fields, the application displays particular message for invalid
entry or required fields.

Non-Functional Requirements:

1. Better response
2. Robustness
3. Reliable

2.3.3 UC3: Manage Members

Actor: Administrator

Figure 2.3: Manage Members (Use Case)

Pre-Condition:

1. UC1 & UC2

2. The member’s detail is required.

Post-Condition:

1. The member information should be edited and deleted.

Basic Path:

1. The administrator views the customer’s detail (Business listings) and then select a particular
member to perform these activities.

25
 2. Update information of specific member by entering updated information and click on update
button.
3. The application verifies the valid entered inputs and updated.
4. For deleting information of specific member, applications display the message of confirmation.
5. Administrator clicks on delete button for deleting that member.
6. The application commits changes to the database.

Non-Functional Requirements:

1. Better response
2. Easy to use
3. Secure
4. Availability
5. Short response time.

2.3.4 UC4: Change Password

Actor: User

Figure 2.4: Change Password (Use Case)

Pre-Condition:

3. UC1

Post-Condition:

1. Password must be updated into the database.

2. User can view new password in a text field.

Basic Path:

26
 1. User select change password menu from sidebar menu list.
2. User enters new password to update old password.
3. The application verifies and updated into database.
4. Click on Logout to check whether the password has changed or not.

CONSTRAINTS:
1. User must enter valid inputs for password.

NON-FUNCTIONAL REQUIREMENTS:

1. Short response time.

2. Efficient
3. Availability
4. Secure

2.3.5 UC6: Logout

Actor: User

Figure 2.5: Logout (Use Case)

Pre-Condition:

1. UC1

Post-Condition:

1. Main page displayed to the user.

27
Basic Path:

1. The member can perform activities with or without login.

2. Click the logout for logging out.
3. Clicks on logout to close the connection with the application and application move the user
towards main page of the application for login again if he/she wants to.

NON-FUNCTIONAL REQUIREMENTS:

1. Secure
2. Reliable
3. Better performance
4. Short Response Time

2.4 The Necessity

There are some necessities for this online application portal to run properly are as follows:

2.4.1 High Speed Internet Connection

Online application portal requires high speed internet connection to run properly.

2.4.2 Signup
The admin must be signup with application before using application portal.

28
 CHAPTER # 3
METHODODLOY AND
WORKPLAN

29
3 METHODOLOGY & WORKPLAN

In this chapter, we will examine that what are the current approaches and which one we have
decided for execution of this task in a compelling way, likewise we will talk about points of
interest of embraced procedure.

The issues which are happened in the current applications are defeated in proposed application.
In this application we are actualized the greater part of the usefulness by utilizing any gadget
with web access for association to taking care of the correspondence between the Admin and
User.

3.1 Existing Approaches and techniques

There are the following existing Approaches ‘Adopted Methodology

3.2 Water fall Approach

In the product improvement process, the plain first model that is distributed from other building
forms that is fell starting with one stage then onto the next is known as Waterfall display. This
model is otherwise called direct consecutive model. In the cascade show, right off the bat the
majority of the prerequisites accumulated.

Subsequent to social occasion the majority of the prerequisites and examination of the
considerable number of necessities additionally move to next stage that is making the outline of a
venture and afterward usage, testing and upkeep stages. As the greater part of the following
periods of this model is subject to past stage. Every one of the stages functioned as a cascade
after each other.

It is a documentation driven model. In this model, criticism of the customer is gotten toward the
finish of the venture and when the item is conveyed to the client. Henceforth, botch in the item
prerequisite particular is found after conveyed to the client. This is time and cost devouring
system, that is the reason we have not utilized this philosophy in building up this undertaking.

30
 Figure 3.6: Waterfall Approach

3.3 Incremental Approach

To conquer the disadvantages of the cascade show, incremental model is utilized. In incremental
model, the item is created in increases and apportioned into little pieces.

These littler pieces, at that point fabricated and conveyed to customer in increases. Speedy
reaction from customers. Every module is littler than contrast with entire module.

Figure 3.2: Incremental Approach

31
3.4 Agile Method

Agile model is valuable when there is no expectation for changings in item after sending. It is a
specific way to deal with venture administration that is used in programming improvement. This
technique helps groups in reacting to the unusualness of building programming.

It utilizes incremental, iterative work successions that are regularly known as dashes. The
capacity to make and react to change keeping in mind the end goal to prevail in an unverifiable
and turbulent condition.

This method assists teams in responding to the unpredictability of constructing software. It uses
incremental, iterative work sequences that are commonly known as sprints.

The ability to create and respond to change in order to succeed in an uncertain and turbulent
environment.

Figure 3.3: Agile Approach

32
3.5 Extreme Programming (XP) Methodology

XP is a methodology for creating software within a very unstable environment. It allows

flexibility within the modelling process.

The main goal of XP is to lower the cost of change in software requirements. With traditional
system development methodologies, like the Waterfall Methodology, the requirements for the
system are determined and often “frozen” at the beginning of the development project. This
means that the cost of changing the requirements at a later stage in the project - something that is
very common in the real-world can be very high.

Figure 3.4: XP Approach

3.6 Adopted Approach

Incremental model is utilized to build up this task, in which we separated our work in various
modules. Every one of these modules are additionally separated into all the more effectively
oversaw modules which made up the genuine usage of the necessity.

33
Figure 3.5: Received Approaches

34
 CHAPTER#4
SYSTEM ANALYSIS &
DESIGN
4 SYSTEM ANALYSIS & DESIGN
In this chapter requirements analysis, feasibility study, planning, forecasting, modeling,
scheduling and design of the project is discussed. For developing any project, the major problem
is requirement gathering. Asking questions from clients is straightforward than collecting
requirements. We will also focus on functional and non-functional requirements.

The procedure for gathering requirements has its own defined procedure according to the
complexity of the application. To define project schedule and processing, different models and
techniques also focused on this chapter.

4.1 Compatibility of the product

The product is design I such a way that It can run on every type of system in other word the
product is fully compatible to every system but if the internet connection is available

4.2 Data structure of product

A data structure is a specialized format for organizing and storing data. General data structure
types include the diagrams, the file, the table and so on.

4.3 Data structure of product

A sequence diagram shows object interactions arranged in time sequence. It depicts the objects
and classes involved in the scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario. Sequence diagrams are typically
associated with use case realizations in the Logical View of the system under development.
Sequence diagrams are sometimes called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them.

29
4.4 Sequence Diagram of system (Admin)

Figure 4.7: sequence Diagram of System (Admin)

30
4.5 Sequence Diagram of product (user)

Figure 4.2: sequence Diagram of System (User)

31
4.6 Activity diagram for Admin (Login/Menu)

Figure 4.3: Activity Diagram of product Admin

32
4.7 Activity Diagram of product Admin

Figure 4.4: Activity Diagram of user

33
 CHAPTER#5

SYSTEM
IMPLEMENTATION

34
5 SYSTEM IMPLEMENTATION
In this chapter, we’ll focus on an implementation of “Choose your Career Wisely” application.
Where administrator and user can perform many activities on android application and as well as
on web application.

5.1 Introduction

The most important goal of this phase is to develop the application. The work in this phase
should be much more straightforward as a result of the work done in the planning and design
phases. This phase involves changing design specifications into executable programs.  When the
design is there, developers can have an idea on looks of application. All that is needed by
developers is to put them at one place to understand about the intended project.

5.2 Screenshots

Sign Up (Screenshot)

35
Log In (Screenshot)

36
Homepage (Screenshot)

37
FAQ Page (Screenshot)

38
Privacy Policy (Screenshot)

39
Terms and Conditions (Screenshot)

40
About Us Page (Screenshot)

41
Popular Categories (Screenshot)

42
Listing Page (Screenshot)

43
Admin Panel – Update City (Screenshot)

44
Admin Panel Home (Screenshot)

45
Admin Panel - Users List (Screenshot)

46
Admin Panel - Category List Page (Screenshot)

47
Admin new category page (Screenshot)

48
Admin Panel - Business Listing (Screenshot)

49
Admin Panel –Add New Listing (Screenshot)

50
Admin Panel – Update City (Screenshot)

51
User Panel - Homepage (Screenshot)

52
Admin Panel – Add New Category (Screenshot)

53
Admin Panel – Cities List (Screenshot)

54
Admin Panel - Listings (Screenshot)

55
Log In (Screenshot)

Admin Panel – Users List (Screenshot)

56
Admin Panel – Manage Profile (Screenshot)

57
 CHAPTER#6
SYSTEM TESTING
6 SYSTEM TESTING
In this chapter, we will discuss the testing phase of developed application “Online Business
Directory” in different manner to know that how much efficient and effective application is?

6.1 Introduction

A process of performing as application or program with the intention of finding errors and
whether the application is fulfilling user needs. It can also be defined as the ability of a program
in meeting the required or desired results.

In many methodologies of software engineering, a separate phase is called phase of testing which
is performed after the completion of the implementation. There is a benefit in using this approach
that it is hard to see one's own mistakes, and a fresh eye can find observable errors much faster
than the person who has read the material many times.

6.2 Testing Phase Planning

A process of performing as application or program with the intention of finding errors and
whether the application is fulfilling user needs.

6.2.1 Unit Testing

The software units in an application are modules and routines that are assembled and
integrated to perform a specific function. Unit testing focuses first on modules, independently of
one another, to locate errors. This enables, to detect errors in coding and logic that are contained
within each module. This testing includes entering data and ascertaining if the value matches to
the type and size supported by php. The various controls are tested to ensure that each performs
its action as required.

Commonly used method is White-Box Testing method. Every time a component of the program
is changed, it can be run for testing that is the biggest and famous benefit of this testing phase.
Issues that are arise during this phase, allowing to be resolved as quickly as possible. Unit testing
is familiar by software developers. It allows them to test their application units before move them
to testers for formal testing.

38
6.2.2 System Testing

To test the total application all in all, framework testing has been utilized. It is advantageous to
check whether the application meets its necessities and satisfy Quality Standards.

6.2.3 Integration Testing

Coordination testing enables the product engineers to incorporate the greater part of the
segments/units of the application inside a program and after that test them in a gathering.
Essentially, this testing level is utilized to get the imperfections in the UI between the
capacities/modules. It is valuable to decide how legitimately and proficiently every one of the
units/segments are running together.

Here the gushing module and encoding module alternatives are coordinated and tried. This
testing gives the affirmation that the application is all around incorporated practical unit with
smooth change of information

User acceptance of an application is the key factor for the success of any application. The
application under consideration is tested for user acceptance by constantly keeping in touch with
the application users at time of developing and making changes whenever required.

6.2.4 Client Acceptance Testing Phase

Client acknowledgment of an application is the key factor for the accomplishment of any
application. The application under thought is tried for client acknowledgment by continually
staying in contact with the application clients at time of creating and rolling out improvements at
whatever point required.

6.2.5 Client Acceptance Testing Phase

Here is following consequence of test eliminate conveyed amid the test stage the experiment
comes about depicted that the item is working precisely and the client won't confront any sort of
issue while connecting to the framework

6.2.6 Test Results

These are the Following test which was carried out while performing test phase on the system.

39
These are following result which is calculated during the testing phase of product and in which
most of the result shows that the product is working successfully and will work according to the
needs of the user.

6.2.7 Test Standards and acceptance Results

User acceptance of an application is the key factor for the success of any application. The
application under consideration is tested for user acceptance by constantly keeping in touch with
the application users at time of developing and making changes whenever required.

Standards Results Acceptance

7 The web-based 8 Successfully 9 Yes

system must
start accurately

10 The Android
11 Successfully 12 Yes
based system must
start accurately

13 The GUI must be 14 Successfully 15 Yes

user friendly

16 User login 17 Successfully 18 Yes

19 Admin Login 20 Successfully 21 Yes

performed

40
22 User Registration 23 Successfully 24 Yes

25 Admin Actions 26 Successfully 27 Yes

performed

41
 CHAPTER # 7
CONCLUSION & FUTURE WORK

28 CONCLUSION & FUTURE WORK

In this chapter, we will discuss the results and discussions of this framework “Online Business
Directory” with conclude remarks and will also discuss related future work of this application.

28.1 Conclusion

“Online Business Directory” (Website) has been developed for users who want to access, edit,
search for, or edit corporate business details by knowing only their names. India is a fast-
growing market, and increasing disposable income means more and more people are entering the
target group in the services market. The emergence of newer enablers such as cell phones has
also made life much easier for the customer, thus there is ample room for a referral system like a
business directory.

Online Business Directory publishes details on manufacturing, construction, wholesale and

business service companies.

REFERENCES:
1. W3Schoos.com

44
 https://www.w3schools.com

2. Tutor points
https://www.tutorialspoint.com

3. Udemy
https://www.udemy.com/

4. Eduvision.edu.pk. (2018). About EduVision: Pakistan's Largest Career

Counselling and Educational Guidance Organization. [online] Available at:
http://www.eduvision.edu.pk/about-us/ [Accessed 7 May 2018].

5. Ilmkidunya.com. (2018). Pakistan Education News Colleges Scholarship

Result Admission Jobs | ilmkidunya. [online] Available at:
https://www.ilmkidunya.com [Accessed 7 May 2018].

6. UML Revision Task Force. OMG Unified Modelling Language

Specification, Version 1.4 (final draft). February 2001

5. Robert L. Harris. Information Graphics: A Comprehensive Illustrated

Reference. 2000. p. 153-155

45