0% found this document useful (0 votes)
222 views

Business Directory

This document provides an overview and requirements for a business directory application. It describes the purpose as providing business information categorized by location, activity, or size. The objectives are to include details like business name, address, phone numbers, services, employees, and reviews. The proposed system would computerize the manual record keeping process currently used to improve efficiency and reduce costs. It outlines functional requirements for admin and user features, as well as performance, security and design constraints.

Uploaded by

Kumar Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
222 views

Business Directory

This document provides an overview and requirements for a business directory application. It describes the purpose as providing business information categorized by location, activity, or size. The objectives are to include details like business name, address, phone numbers, services, employees, and reviews. The proposed system would computerize the manual record keeping process currently used to improve efficiency and reduce costs. It outlines functional requirements for admin and user features, as well as performance, security and design constraints.

Uploaded by

Kumar Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 31

BUSINESS DIRECTORY

1. INTRODUCTION

1.1 PURPOSE:
The project “Business Directory” is to provide the information about business. A
business directory is a website or printed listing of information which lists businesses can be
categories. Businesses can be categorized by location, activity, or size. Business may be
compiled either manually or through an automated online search software. Online yellow
pages are a type of business directory, as is the traditional phone book.

1.2 OBJECTIVES:
In this project Business Directory, the details provided in a business in a business
directory may vary. They may include the business name, address, telephone numbers,
location, contact information and type of service or products the business provides, the
number of employees, the served region and any professional associations. Some directories
include a section for user reviews, comments, and feedback. Business directories in the past
would take a printed format but have recently been upgraded to websites due to advent of the
internet.

1.3 SCOPE:
Then the project ‘Business directory’ has been explained and executed in detail.
Through this application, future extensions can be incorporated in it. Many business
directories offer complimentary listings in addition to the premium options. There are many
business directories and some of these have moved over to the Internet and away from
printed format. Whilst not being search engines, business directories often have a search
function, enabling users to search businesses by Zip Code, country, state, area or city.

1.4 DEFINITIONS, ACRONYMS & ABBREVATIONS:

GUI : Graphical User Interface


HTML : Hypertext Markup language. is the predominant mark-up language for web pages.
C# .NET: C# (pronounced "C-sharp") is an object-oriented programming language from Microsoft
that aims to combine the computing power of C++ with the programming ease of Visual Basic. C# is
based on C++ and contains features similar to those of Java.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

2. LITERATURE SURVEY

Literature survey involves a detailed study of existing system and limitations. To


overcome the limitations the requirements is reanalyzed and a new system is proposed. The
new proposed system should provide more facilities than existing system by residing in same
constraints.

2.1 EXISTING SYSTEM:


In the existing system details are done through manual records. These records are
entered in manual process. This process takes lot of time, separate workers need to
maintaining the databases. All the business details are stored via separate databases. It will
take long time due to this process time waste, money waste.

2.2 PROPOSED SYSTEM:


The proposed system provides a user friendly interface. This system computerizes all
the details of business details. Large volumes of data can be stored with case. Maintenance of
file is flexible. Records stored are updated now and then. Stored data and procedures can be
easily edited. Reports can be generated with case. Accurate calculations are made. Less
manpower require.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

3. SYSTEM REQUIREMENT SPECIFICATION

System specification forms the foundation on which the architecture, design, and
implementation of a software is built. Documents containing system specifications are critical
because major expenses come along with having to fix the implementation of incorrect
requirements as a result of not having a specification document on hand. System specification
documents can thus be defined as the requirements documentation that formally specifies the
system-level requirements of a software application. System specification documents most
predominantly contain information on basic website requirements which include:

 performance levels
 reliability
 quality
 interfaces
 security and privacy
 constraints and limitations
 functional capabilities

3.1 FUNCTIONAL REQUIREMENTS:

Functional requirements are statements of the services that the system must provide or
are descriptions of how some computations must be carried out. The plan for implementing
functional requirements is detailed in the system design.

 Admin is provided with Username and Password to avoid unauthorized access.


 Basic and advance admin facilities like add/update/delete business details are provided.
 View the details of users.
 Users are able to register themselves and login using their name and mobile number.
 Users can search the business based on the city, type of business, and name-wise

3.2 NON-FUNCTIONAL REQUIREMENTS:

A non-functional requirement is a requirement that specifies criteria that can be used


to judge the operation of a system, rather than specific behaviors. This should be contrasted
with functional requirements that define specific behavior or functions.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

 The system should provide user-friendly interfaces.


 The system should provide consistent performance with easy tracking of records an
updating of records.
 Only authorized users must be able to access the system, view & modify the data.

3.3 DESIGN CONSTRAINTS:


In case of any errors Error Handling mechanisms have been provided
 Without proper authorization the data in the database can’t be modified.
 Complete validation has been done so that no mandatory fields are empty by chance if
any field is left empty then appropriate alert message will be displayed.
 In case of any errors Error Handling mechanisms have been provided\

3.4 FEASIBILITY STUDY:


Preliminary investigations examine project feasibility; the likelihood of how the system is
will be useful to the organization. Three tests of feasibility-all equally important are studied.

Three tests of feasibility-all equally important are studied.


3.4.1 Economic feasibility:
Although an investment has been made on hardware and software aspect, proposed aims at
processing or transaction efficient thus saving time and money and system are sufficient
enough for a project to be undertaken.

3.4.2 Technical feasibility:


Since the necessary hardware and software is made available to the organization along with
the system, the development of the system is technically feasible

3.4.3 Operational feasibility:


The proposed system offers greater levels of user friendliness combined with faster
processing of transaction and faster response to queries given to the system. Therefore the
personally using the system welcome its development and implementation. Since the

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

management is also convicted of the benefits resulting from the implementation and
development of the system, the project is operationally feasible.

4. HARDWARE & SOFTWARE REQUIREMENTS

4.1 HARDWARE SPECIFICATION:

Sl. No. Hardware Description

1 PROCESSOR Celeron or higher

2 RAM 1GB or more

3 HARD DISK 128 GB

4.2 SOFTWARE SPECIFICATION:

OPERATING SYSTEM Window 8 & above

Visual studio 2010,


HTML,
TOOLS & TECHNOLOGIIES C#,
SQL server management
studio .2008.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

5. OBJECT-ORIENTED ANALYSIS DESIGN

Object-oriented analysis and design (OOAD) is a software engineering approach that


models a system as a group of interacting objects. Each object represents some entity of
interest in the system being modelled, and is characterized by its class, its state (data
elements), and its behavior. Various models can be created to show the static structure,
dynamic behavior, and run-time deployment of these collaborating objects. There are a
number of different notations for representing these models, such as the Unified Modelling
Language (UML).

Object-oriented analysis (OOA) applies object-modelling techniques to analyze the


functional requirements for a system. Object-oriented design (OOD) elaborates the analysis
models to produce implementation specifications. OOA focuses on what the system does,
OOD on how the system does it.

5.1 DESIGN OF THE SYSTEM:

5.2.1 Introduction:

The purpose of the design phase is to plain a solution of the problem specified by the
requirements document. This phase is the first step moving the problem domain to the
solution domain. It involves the process, in which conceiving, planning and the carrying out
the plain by generating the necessary report and inputs, in other words, the design phase act
as a bridge between SRS and implementation phase. The design of the system is perhaps the
most critical factor affecting the quality of the software, and has a major impact on the later
phase, particularly the testing and maintenance.

5.2.2 Design System:


System design is concerned with how the system functionality is to be provided by the
different components of the system Design is the key phase of any project. It is the first step
in moving from problem domain to the solution domain. It may be defined as “The process of
applying various techniques and principles for the purpose of defining a device, a process, or
a system insufficient detail to permit its physical realization”. The input to design phase is the
specifications of the system to be designed. The output of the top level design is the

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

architectural design, or the system design for the software system to be built. A design should
be very clear, verifiable, complete, traceable, efficient & simple.
Admin Login:

Businness id

business name

business nature

Welcome
Address
Admin

Business Details add/edit/delete contact person


Username &
Admin Login Manage
Password
Users contact no

Logout city

state

country

User Login:

Welcome User

Profile

Directory city
wise
User Login Username &
Explore
/Register Password
Directory
business nature
wise

Directory
Business name
wise
Dept. of BCA, Veerashaiva Degree College, Ballari.
Logout
BUSINESS DIRECTORY

5.2.3 Architecture of .Net:

The initial design process of identifying the sub-system and establishing a frame work
for sub-system control and communication is called architectural design and the output of this
design process is a description of the software architecture. The user interface, functional
process logic, product data storage and data access are developed and maintained. This
diagram is very important to understand the overall concept of system.

5.2.4 Design Principles:

Basic design principles that enable the software engineer to navigate the design
process are:
 The design process should not suffer from “Tunnel vision”.
 The design should be traceable to analysis model.
 The design should not reinvent the wheel.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

 The design should minimize the intellectual distance between the software and the
problem, as it exists in the real world.
 The design should exhibit uniformity and integrity.
 The design should be structured to accommodate changes.
 The design not coding, the coding is not a design.
 The design should be assessed for the quality, as it is being created, not after the fast.
 The design should be reviewed to minimize the conceptual errors.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

6. SOFTWARE DESCRIPTION

6.1 WHY YOU NEED .NET?

.NET security is not an island of technology, but a slice of a larger entity


called the .NET Framework. Basic understanding of the .NET Framework is required before
attempting .NET security programming. This chapter presents the basic concepts of the .NET
Framework architecture and programming. This is an overview and is not intended to replace
the independent study required for a mastery of this subject. (For a comprehensive discussion
on the .NET Framework from a developer's perspective, I recommend .NET Framework
Essentials by Thun L. Thai and Hoang Q. Lam, O'Reilly & Associates, February 2002.)
Microsoft .NET is not just a different spin on the Win32 operating model. Furthermore,
despite reports to the contrary, it is not Java in wolf's clothing. You will never understand or
adequately explain .NET simply by comparing it to existing products. .NET is new. As
such, .NET introduces a fresh operating modality and perspective on computing software and
devices.

Are there similarities to Java? Are there similarities to Win32? Yes, but there are many more
differences. Successfully programming in .NET requires embracing this new technology as
new and fully understanding the many things that make .NET unique. When object-oriented
languages were introduced, developers faced a similar challenge and, unfortunately, mindset.
Many programmers quickly learned the syntax and ported their C application to C++ or
SmallTalk. However, without the requisite understanding of object-oriented programming,
these new applications were procedural programs draped in the syntax of an object-oriented
language. Some developers invested the time to learn object-oriented programming—not just
the syntax, but the philosophy and intent. Their resulting applications were true object-
oriented programs that provided all the benefits envisioned for the new programming
modality. Similarly, understanding the philosophy and architecture of .NET is essential for
creating applications that offer new solutions. Some industry analysts assert that Microsoft
has gambled the company on .NET. I would not agree. .NET does represent a massive
investment. However, Microsoft is a diversified and multibillion dollar company with many
products and a sizable market share in many segments of the software industry. In addition,
Microsoft is no longer simply a software company, having expanded into many markets
outside their traditional stronghold.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

But recognizing that Microsoft is not teetering on a precipice named .NET does not diminish
the importance of .NET. .NET does represent a new philosophy in product development.
From .NET will emerge an entirely new family of products that will drive Microsoft sales
into the stratosphere over the next 5 to 10 years. If the .NET initiative fails, or more likely is
adopted slowly, Microsoft will recover and continue, although maybe with a little less lustre.
Importantly, .NET allows Microsoft to escape the Windows conundrum. Although Windows
has been enormously successful, it is still a box. .NET helps Microsoft emerge from that box
and develop applications for a universal audience. This new opportunity will fuel growth not
just for Microsoft, but for software developers everywhere.

I attended the formal launch of Microsoft .NET at the Professional Developers Conference in
Orland, Florida several years ago. William Gates III (aka Bill) was the keynote speaker. Part
of his speech included an entertaining video. The video portrayed .NET as a new standard
that will allow software to run anywhere, at any time, on any platform, and on devices large
and small.

6.2 INTRODUCTION TO C#

C# is a general-purpose, modern, and object-oriented programming language pronounced as


“C Sharp”. It was developed by Microsoft led by Anders Hejlsberg and his team within the .Net
initiative and was approved by the European Computer Manufacturers Association (ECMA) and
International Standards Organization (ISO). C# is among the languages for Common Language
Infrastructure. C# is a lot similar to Java syntactically and is easy for users who have knowledge of C,
C++, and OR Java. C# is designed to work with Microsoft’s .Net platform, which is a runtime support
environment. Microsoft aim is to facilitate the exchange of information and services over the web, and
to enable developers to build highly portable applications. C# simplifies programming language
through its use of Extensible Mark-up Language (XML) and Simple Object Access Protocol (SOAP)
without requiring programmer to write additional code.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

6.3 SQL SERVER MANAGEMENT STUDIO:

SQL Server Management Studio (SSMS) is a software application first launched with
Microsoft SQL Server 2005 that is used for configuring, managing, and administrating all
components within Microsoft SQL Server. It’s the successor to the Enterprise Manager in
SQL 2000 or before. The tool includes both script editors and graphical tools which work
with objects and features of the server.

A central feature of SSMS is the Object Explorer, which allows the user to browse,
select, and act upon any of the objects within the server. It also shipped a separate Express
edition that could be freely downloaded, however recent versions of SSMS are fully capable
of connecting to and manage any SQL Server Express instance.

6.4 MICROSOFT VISUAL STUDIO

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

Microsoft Visual Studio is an integrated development environment (IDE) from


Microsoft. It is used to develop computer programs, as well as websites, web apps, web
services and mobile applications. Visual Studio uses Microsoft software development
platforms such as windows API, windows forms, windows presentation foundation, windows,
and Microsoft Silver light. It can produce both native code and managed code. Visual Studio
includes a code editor supporting Intelligence (the code completion component) as well as
code refactoring. The integrated debugger works both as a source-level debugger and a
machine level debugger.

Other built-in tools include a code profiler, designer for building GUI applications,
web designers, class designers, and database schema designer. It accepts plug-ins that
enhance the functionality at most every level-including adding support for source control
systems (like Subversion and Git) and adding new toolsets like editors and visual designers
for domain specific languages or toolsets for other aspects of the software development
lifecycle (like the Azure DevOps client: Team Explorer).

Visual Studio supporter 36 different programming languages and allows the code
editor and debugger to support (to varying degrees) nearly any programming language,
provided a language -specific service exists. Built-in languages include C, C++, C++/CLI,
Visual Basic.Net, C#, F#, JavaScript, Typescript, XML, XSLT, HTML, and CSS. Support for
other languages such as Python, Ruby, Node.js among others is available via plugins. Java
(and J#) was supported in the past. The most basic edition of Visual Studio, the Community
edition, is available free of charge. The slogan for Visual Studio Community edition is “Free
and fully featured IDE” for students, open-source and individual developers.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

7. TABLES

BUSINESS DETAILS:

USER REG:

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

TABLE RECORD:

LOGIN TABLE:

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

8. CODING

BUSINESS DETAILS FORM:

<%@ Page MasterPageFile="~/adminmaster.master" Language="C#" AutoEventWireup="true"


CodeFile="Business_det_form.aspx.cs" Inherits="Business_det_form" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">


<form id="form1" runat="server">
<div>

<table class="style1" style="font-size: x-large">


<tr>
<td colspan="3">
<strong>Business Details:</strong></td>
</tr>
<tr>
<td>
Business Name:</td>
<td>
<asp:TextBox ID="tbname" runat="server"></asp:TextBox>

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="tbname" ErrorMessage="You missed this Field."
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Address:</td>
<td>
<asp:TextBox ID="tbadd" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server"
ControlToValidate="tbadd" ErrorMessage="You missed this Field." ForeColor="Red"
ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Contact Person:</td>
<td>
<asp:TextBox ID="tbcperson" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server"
ControlToValidate="tbcperson" ErrorMessage="You missed this Field."
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Contact Number:</td>
<td>
<asp:TextBox ID="tbcno" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server"
ControlToValidate="tbcno" ErrorMessage="You missed this Field." ForeColor="Red"
ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Business Nature:</td>
<td>
<asp:TextBox ID="tbbnature" runat="server"></asp:TextBox>

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator5" runat="server"
ControlToValidate="tbbnature" ErrorMessage="You missed this Field."
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
City:</td>
<td>
<asp:TextBox ID="tbcity" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator6" runat="server"
ControlToValidate="tbcity" ErrorMessage="You missed this Field."
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
State:</td>
<td>
<asp:TextBox ID="tbstate" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator7" runat="server"
ControlToValidate="tbstate" ErrorMessage="You missed this Field."
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Country:</td>
<td>
<asp:TextBox ID="tbcountry" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator8" runat="server"
ControlToValidate="tbcountry" ErrorMessage="You missed this Field."
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
&nbsp;</td>
<td>
<asp:Button ID="Button1" runat="server" onclick="Button1_Click" Text="Submit"

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

ValidationGroup="g1" style="font-size: medium" />


&nbsp;
<asp:Label ID="Label1" runat="server"></asp:Label>
</td>
<td>
<asp:ValidationSummary ID="ValidationSummary1" runat="server" ForeColor="Red"
ValidationGroup="g1" />
</td>
</tr>
</table>

</div>
</form>
</asp:content>

USER_REG_FORM:

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="user_reg_form.aspx.cs"


Inherits="user_reg_form" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"


"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
<style type="text/css">
.style1
{
height: 343px;
width: 410px;
}
.style2
{
height: 48px;
}
</style>
</head>
<body background="images/img01.jpg"
style="height: 852px; margin-left: 0px; margin-right: 0px; margin-bottom: 0px">
<form id="form1" runat="server">
<div style="height: 891px; margin-left: 0px; margin-top: 190px; background-color: #E2E0E2; font-
size: large;">

<table class="style1" align="center">


<tr>

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

<td colspan="3"
style="font-family: Arial, Helvetica, sans-serif; font-size: medium; font-weight: bold;">
Registeration Details:</td>
</tr>
<tr>
<td>
Name:</td>
<td>
<asp:TextBox ID="tbname" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="tbname" ErrorMessage="You missed this Field*"
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Gender</td>
<td>
<asp:RadioButtonList ID="RadioButtonList1" runat="server">
<asp:ListItem>male</asp:ListItem>
<asp:ListItem>female</asp:ListItem>
</asp:RadioButtonList>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server"
ControlToValidate="RadioButtonList1" ErrorMessage="You missed this Field*"
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Contact No:</td>
<td>
<asp:TextBox ID="tbcontact" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server"
ControlToValidate="tbcontact" ErrorMessage="You missed this Field*"
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Email:</td>
<td>
<asp:TextBox ID="tbmail" runat="server"></asp:TextBox>

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server"
ControlToValidate="tbmail" ErrorMessage="You missed this Field*"
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
Address:</td>
<td>
<asp:TextBox ID="tbadd" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator5" runat="server"
ControlToValidate="tbadd" ErrorMessage="You missed this Field*" ForeColor="Red"
ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td>
DOB:</td>
<td>
<asp:TextBox ID="tbcity" runat="server"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator6" runat="server"
ControlToValidate="tbcity" ErrorMessage="You missed this Field*"
ForeColor="Red" ValidationGroup="g1">*</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td align="center" class="style2">
</td>
<td align="center" class="style2">
<asp:Button ID="Button1" runat="server" onclick="Button1_Click" Text="Submit"
ValidationGroup="g1" />
&nbsp;<asp:Label ID="Label1" runat="server"></asp:Label>
</td>
<td align="center" class="style2">
<asp:ValidationSummary ID="ValidationSummary1" runat="server" ForeColor="Red"
ValidationGroup="g1" />
</td>
</tr>
</table>

</div>

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

</form>
</body>
</html>

USER LOGIN:

<%@ Page Title="" Language="C#" MasterPageFile="~/mainmaster.master"


AutoEventWireup="true" CodeFile="userlogin.aspx.cs" Inherits="userlogin" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">


<form id="form1" runat="server">
<table style="width: 100%; font-size: x-large;">
<tr>
<td colspan="3" style="font-size: medium">
<strong>Login:</strong></td>
</tr>
<tr>
<td style="width: 139px">
User Name:</td>
<td style="width: 200px">
<asp:TextBox ID="tbuname" runat="server" Width="180px"
style="font-size: medium"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="tbuname" ErrorMessage="Please enter user
name."></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td style="width: 139px">
Password:</td>
<td style="width: 200px">
<asp:TextBox ID="tbpwd" runat="server" TextMode="Password" Width="180px"
style="font-size: medium"></asp:TextBox>
</td>
<td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server"
ControlToValidate="tbpwd" ErrorMessage="Please enter
password."></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td style="width: 139px">
&nbsp;</td>
<td style="width: 200px">

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

<asp:Button ID="btnlogin" runat="server" onclick="btnlogin_Click"


Text="Login" Height="26px" Width="54px" />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<asp:Button ID="btncancel" runat="server" onclick="btncancel_Click"
Text="Cancel" Height="26px" Width="69px" />
</td>
<td>
<asp:Label ID="Label1" runat="server"></asp:Label>
&nbsp;<asp:HyperLink ID="HyperLink1" runat="server"
NavigateUrl="~/user_reg_form.aspx">Register</asp:HyperLink>
</td>
</tr>
</table>
</form>
</asp:Content>

9. TESTING

Software testing methods are traditionally divided into black box testing and white
box testing. These two approaches are used to describe the point of view that a test engineer
takes when designing test cases.

1. Black box testing :


Black box testing treats the software as a "black box," without any knowledge
of internal implementation. Black box testing methods include: equivalence
partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based
testing, traceability matrix, exploratory testing and specification-based testing.

2. White box testing:


White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that implement
these).White box testing methods can also be used to evaluate the completeness of a
test suite that was created with black box testing methods. This allows the software
team to examine parts of a system that are rarely tested and ensures that the most
important function points have been tested.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

3. Grey Box Testing:


Grey box testing involves having access to internal data structures and
algorithms for purposes of designing the test cases, but testing at the user, or black-
box level. Manipulating input data and formatting output do not qualify as "grey box,"
because the input and output are clearly outside of the "black-box" that we are calling
the system under test. This distinction is particularly important when conducting
integration testing between two modules of code written by two different developers,
where only the interfaces are exposed for test. Grey box testing may also include
reverse engineering to determine, for instance, boundary values or error messages.

4. Acceptance testing :
Acceptance testing can mean one of two things:
A smoke test is used as an acceptance test prior to introducing a build to the main
testing process.
Acceptance testing performed by the customer is known as user acceptance testing

5. Regression Testing:
Regression testing is any type of software testing that seeks to uncover
software regressions. Such regression occurs whenever software functionality that
was previously working correctly stops working as intended. Typically regressions
occur as an unintended consequence of program changes. Common methods of
regression testing include re-running previously run tests and checking whether
previously fixed faults have re-emerged.

6. Non Functional Software Testing:

Special methods exist to test non-functional aspects of software.

 Performance testing checks to see if the software can handle large quantities of data or
users. This is generally referred to as software scalability. This activity of Non
Functional Software Testing is often times referred to as Load Testing.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

 Stability testing checks to see if the software can continuously function well in or
above an acceptable period. This activity of Non Functional Software Testing is often
times referred to as indurations test.
 Usability testing is needed to check if the user interface is easy to use and understand.
 Security testing is essential for software which processes confidential data and to
prevent system intrusion by hackers.
 Internationalization and localization is needed to test these aspects of software, for
which a pseudo localization method can be used.

10. SCREENSHOTS
HOME:

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

ADMIN LOGIN:

USER LOGIN:

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

ABOUT:

CONTACT:

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

11. FUTURE ENHANCEMENTS

The following enhancements can be done in the future:

 Allow the business to add their details themselves


 Allowing the business to promote themselves
 Allowing the users to apply for any opening positions in the business
 Better mapping of the business using maps.

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

12. CONCLUSION
The intention with which the project was started i.e. the providing the all information of
business. Moreover the display of business details to the users dynamically as and when the
admin is implemented. Thus our project provides a user-friendly environment to carry out the
business processes at last the basic purpose with the project was initiated is server. Still there
are some shortcomings, as the time was insufficient. But the basic operations required are
provided by our project.

REFERENCES/ BIBLIOGRAPHY
References:

www.1000project.com
www.c#miniproject.com
www.wikipedia.org
www.projectabstracts.com

Books:

Dept. of BCA, Veerashaiva Degree College, Ballari.


BUSINESS DIRECTORY

1. Andrew Troelsen: Pro C# with .NET 3.0, 4th Edition, Wiley India, 2009.
2. E. Balagurusamy: Programming in C#, 2nd Edition, Tata McGraw Hill, 2008. .
3. Tom Archer: Inside C#, WP Publishers, 2001.
4. Herbert Schildt: C# The Complete Reference, Tata McGraw Hill, 2004.

Dept. of BCA, Veerashaiva Degree College, Ballari.

You might also like