Enquiry Management Systerm- Project Report

Institute Of Engineering & Technology (D.A.V.V.) , Indore Page 1

Table of Contents

1. Introduction 3

1.1 Overview and issue involved 3

1.2 Problem Definition 3

1.3 Proposed Solution 3

2. Litrature Survey 4

2.1 Methedology 4

2.2 Technology and Tools 6

3. Requirement Gathering 7

3.1 Software requirements 7

3.1.1 Microsoft Visual Studio 2010 7

3.1.2 Microsoft SQL Server 2005 7

3.1.3 Web Browser 7

3.1.4 Operating System 8

3.2 Hardware requirements 8

3.2.1 Processor 8

3.2.2 Monitor 8

3.2.3 Mouse 9

3.2.4 Keyboard 9

3.2.5 RAM 9

3.2.6 Harddisk 9

3.2.7 GUI 9

3.3 Use Case Model 10

3.4 Use Case Description 11

4. Analysis 12

4.1 Sequence Diagram and Activity Diagram 12

4.1.1 Login Activity Diagram 13

4.1.2 Login Sequence Diagram 14

4.2 Class Diagram 14

4.2.1 Class Diagram of application 15

5. Design 16

5.1 Technology 16

5.2 Subsystem and their dependencies 16

5.2.1 Registration Form 17

5.2.2 Login Form 17

5.2.3 Customer Form 18

5.2.4 Enquiry Form 18

5.2.5 Product Form of Enquiry 19

5.2.6 Follow up Form 19

5.3 Class diagram description 20

5.4 Database design with E-R Diagram 20

5.4.1 Database table of Registration 20

5.4.2 Database table of Login 21


5.4.3 Database table of Customer 21

5.4.4 Database table of Enquiry 22

5.4.5 Database table of Product Detail 22

5.4.6 Database table of Follow-up 23

5.4.7 Database table of Products 23

5.4.8 Database table of Employee 24

5.4.9 E-R Diagram 24

6. Testing 25

6.1 Testing objective 25

6.2 Testing Principle 25

6.3 Testing method used 26

6.4 Testing issue 27

6.5 Sample test cases and Resuls 28

6.5.1 Case-1 28

6.5.2 Case-2 29

7. Conclusion 30

7.1 Limitation 30

6.2 Advantages 30

6.3 Short Description 30


Chapter 1

Introduction

1.1) Overview and issue involved

Enquiry Management System is a web application designed to manage the

Customers, Employee and Products database with a special feature of Follow-up

(Reminder for the Employee to follow the customer).

The main issue is that many companies and business organizations faces is

in the enquiry registration and the follow-up process that gets missed or not responded

due to lack of a good Enquiry Management System. This software works the same

way as a Lead Management System.

1.2) Problem Definition

As the competition is increasing in today’s environment the business

organization has to work hard to attain the maximum profit from the market and to do

this the company has to provide the maximum input to achieve the desired goal.

Due to lack of technology in an organization reflects in a low profit or certain losses

like improper communications, no consumer satisfactions and the reputation of the

company.

1.3) Proposed solution

This project enables the desired solution for the above problem. This project

evolves the complete package of enquiry and its management when a user log

in through the Log in form he/she enters the home page. Now the user has

several options to add or view the products, add or view the customer’s

database, and his or her interest in the project. The user can view or update

any of this information’s.

This project has a unique feature of follow up which reduces the work load of

employee by getting the reminder as per the interest of a customer.


Chapter 2

Literature Survey

2.1) Methodology

Web Applications:

A web application is an application utilizing web and [web] browser

technologies to accomplish one or more tasks over a network, typically through a web

browser. A web application is also an application that is accessed over a network such

as the Internet or an intranet. The term may also mean a computer software

application that is coded in a browser-supported language (such as JavaScript,

combined with a browser-rendered markup like HTML) and reliant on a common web

browser to render the application executable.

Database Management System:

A database management system (DBMS) is a software package

with computer programs that control the creation, maintenance, and use of a database.

It allows organizations to conveniently develop databases for various applications

by database administrators (DBAs) and other specialists. A database is an integrated

collection of data records, files, and other objects. A DBMS allows different user

application programs to concurrently access the same database. DBMSs may use a

variety of database models, such as the relational model or object model, to

conveniently describe and support applications. It typically supports query languages,

which are in fact high-level programming languages, dedicated database languages

that considerably simplify writing database application programs. Database languages

also simplify the database organization as well as retrieving and presenting

information from it. A DBMS provides facilities for controlling data access,

enforcing data integrity, managing concurrency, and recovering the database after

failures and restoring it from backup files, as well as maintaining database security.


Microsoft SQL Server:

Microsoft SQL Server is a relational database server, developed

by Microsoft: it is a software product whose primary function is to store and retrieve

data as requested by other software applications, be it those on the same computer or

those running on another computer across a network (including the Internet). There

are at least a dozen different editions of Microsoft SQL Server aimed at different

audiences and for different workloads (ranging from small applications that store and

retrieve data on the same computer, to millions of users and computers that access

huge amounts of data from the Internet at the same time).

ASP.NET:

ASP.NET is a Web application framework developed and marketed

by Microsoft to allow programmers to build dynamic Web sites, Web

applications and Web services. It was first released in January 2002 with version 1.0

of the .NET Framework, and is the successor to Microsoft's Active Server

Pages (ASP) technology. ASP.NET is built on the Common Language

Runtime (CLR), allowing programmers to write ASP.NET code using any

supported .NET language.

Web Browsers:

A web browser is a software application for retrieving, presenting, and

traversing information resources on the World Wide Web. An information resource is

identified by a Uniform Resource Identifier (URI) and may be a web page, image,

video, or other piece of content. Hyperlinks present in resources enable users easily to

navigate their browsers to related resources. A web browser can also be defined as

an application software or program designed to enable users to access, retrieve and

view documents and other resources on the Internet. Protocol, so an IP address is an

Internet Protocol address. That mean An Internet Protocol is a set of rules that govern

Internet activity and facilitate completion of a variety of actions on the World Wide

Web.


2.2) Technologies and Tools

Technology:

In this project we are using Microsoft Visual Studio 2010 as Front end and

Microsoft SQL Server 2005 as back end.

Microsoft Visual Studio 2010- Microsoft Visual Studio is a powerful IDE that ensures

quality code throughout the entire application lifecycle, from design to deployment.

Whether you’re developing applications for SharePoint, the web, Windows, Windows

Phone, and beyond.

Microsoft SQL Server 2005- SQL Server 2005 released in October 2005, is the

successor to SQL Server 2000. It included native support for managing XML data, in

addition to relational data. For this purpose, it defined an xml data type that could be

used either as a data type in database columns or as literals in queries.

Tools:

In this project we are using .NET Framework 4.0 and SQL Server 2005

Management Studio as the powerful tools.

.NET Framework 4.0- The .NET Framework's Base Class Library provides user

interface, data access, database connectivity, cryptography, web

application development, numeric algorithms, and network communications.

Programmers produce software by combining their own source code with the .NET

Framework and other libraries.

SQL Server 2005 Management Studio- SQL Server Management Studio is a software

application first launched with the Microsoft SQL Server 2005 that is used for

configuring, managing, and administering all components within Microsoft SQL

Server. The tool includes both script editors and graphical tools which work with

objects and features of the server.


Chapter: 3

Requirement Gathering

In software (project) development we have the particular requirements

that called specific requirements. In this project development have the following

requirements:-

3.1) Software Requirement:-

In this project have following software requirements:-

3.1.1) Microsoft Visual Studio 2010:

Microsoft Visual Studio is a powerful IDE that ensures quality code

throughout the entire application lifecycle, from design to deployment. Whether you

are developing applications for SharePoint, the web, Windows, Windows Phone, and

beyond.

3.1.2) Microsoft SQL Server 2005:

SQL Server 2005 released in October 2005, is the successor to SQL

Server 2000. It included native support for managing XML data, in addition

to relational data. For this purpose, it defined an xml data type that could be used

either as a data type in database columns or as literals in queries.

3.1.3) Web Browser:

A web browser is a software application for retrieving, presenting, and

traversing information resources on the World Wide Web. An information resource is

identified by a Uniform Resource Identifier (URI) and may be a web page, image,

video, or other piece of content. Hyperlinks present in resources enable users easily to

navigate their browsers to related resources. A web browser can also be defined as

an application software or program designed to enable users to access, retrieve and


view documents and other resources on the Internet. Protocol, so an IP address is an

Internet Protocol address. That mean An Internet Protocol is a set of rules that govern

Internet activity and facilitate completion of a variety of actions on the World Wide

Web.

Although browsers are primarily intended to access the World Wide Web, they can

also be used to access information provided by web servers in private networks or

files in file systems. The major web browsers are Firefox, Google Chrome, Internet

Explorer, Opera, and Safari.

3.1.4) Operating system:

An operating system (OS) is a set of programs that manage computer

hardware resources and provide common services for application software. The

operating system is a vital component of the system software in a computer system.

Application programs require an operating system which are usually separate

programs, but can be combined in simple systems. For this project we require

Windows XP service pack 3 and above version of Windows operating system.

3.2) Hardware requirement

In this project have following Hardware requirements:

3.2.1) Processor:

In this project we require Intel Pentium processor minimum speed of 1

GHz or above.

3.2.2) Monitor:

The monitor displays the video and graphics information generated by the

computer through the video card. Monitors are very similar to televisions but usually

display information at a much higher resolution. Recommended resolution for this

project is 1024X768 or above.

The monitor is also known as: Screen, Display, Video display, Video screen


3.2.3) Mouse:

A mouse is a pointing device that functions by detecting two-

dimensional motion relative to its supporting surface. Physically, a mouse consists of

an object held under one of the user's hands, with one or more buttons. It sometimes

features other elements, such as "wheels", which allow the user to perform various

system dependent operations, or extra buttons or features that can add more control or

dimensional input. The mouse's motion typically translates into the motion of a

pointer on a display, which allows for fine control of a graphical user interface.

3.2.4) Keyboard:

A keyboard typically has characters engraved or printed on the keys and

each press of a key typically corresponds to a single written symbol. However, to

produce some symbols requires pressing and holding several keys simultaneously or

in sequence. While most keyboard keys produce letters, numbers or signs (characters),

other keys or simultaneous key presses can produce actions or computer commands.

3.2.5) RAM:-

Random access memory (RAM) is a form of computer data storage.

Today, it takes the form of integrated circuits that allow stored data to be accessed in

any order with a worst case performance of constant time.

In this project we need of minimum 512 Mb RAM .

3.2.6) Hard disk:-

A hard disk drive (HDD) also hard drive, hard disk, or disk drive is a

device for storing and retrieving digital information, primarily computer data.

In this project we need of minimum 40 GB HDD.

3.2.7) GUI:

The term GUI (Graphical User Interface) is restricted to the scope of two-

dimensional display screens with display resolutions able to describe generic

information, in the tradition of the computer science & information technology


3.3) Use Case Model

A Use Case Diagram is a type of behavioral diagram defined by and created

from a Use-case analysis. It is used to identify the primary elements and processes

that form the system. The primary elements are termed as "actors" and the processes

are called "use cases." The Use case diagram shows which actors interact with each

use case. The main purpose of a use case diagram is to show what system functions

are performed for which actors.

The elements used for this representation are

• Actors

• Use Cases

• System Boundary

Fig 3.3.1 Use case diagram of Login


Fig 3.3.2 Use case diagram of Application

3.4) Use Case Description

Fig 3.3.1 shows Login use case that is also used by user and administrator.

Fig 3.3.2 shows application use case in its use case shows client, server and database

also use users but database is not use (look) by users. But all three fields are used by

administrator.


Chapter 4

Analysis

4.1) Sequence diagram and Activity diagram

Sequence Diagram:

The Sequence Diagram is used primarily to show the interactions between

objects in the sequential order that those interactions occur.

One of the primary uses of sequence diagrams is in the transition from

requirements expressed as use cases to the next and more formal level of refinement.

Use cases are often refined into one or more sequence diagrams. In addition to their

use in designing new systems, sequence diagrams can be used to document how

objects in an existing (call it "legacy") system currently interact. This documentation

is very useful when transitioning a system to another person or organization.

Activity Diagram:

Activity diagrams are diagram technique showing workflows of stepwise

activities and actions, with support for choice, iteration and concurrency. In the

Unified Modeling Language, activity diagrams can be used to describe the business

and operational step-by-step workflows of components in a system. An activity

diagram shows the overall flow of control. Activity diagrams are constructed with a

limited set of building blocks, consisting of: (a) Nodes: like the initial node and

activity final node, and. (b) Activity building blocks.

Sometimes activity diagrams also contain building block for decision

making, but it is questionable if these diagrams should be called activity diagram. The

starting point of the diagram is the initial node, which is mostly located on top or on

the left. And the ending of the diagram with an activity final node is on the bottom or

on the right. In between there can be zero, one or more activity building blocks, which

can be represented by rounded.


Fig 4.1.1 - Login Activity Diagram


Fig 4.1.2 Login Sequence Diagram

4.2) Class Diagrams

A class diagram is a type of static structure diagram that describes the structure of a

system by showing the system's classes, their attributes, and the relationships between

the classes.

Class diagrams are widely used to describe the types of objects in a system and their

relationships. Class diagrams model class structure and contents using design

elements such as classes, packages and objects. Class diagrams describe three

different perspectives when designing a system, conceptual, specification, and

implementation. These perspectives become evident as the diagram is created and

help solidify the design.


Fig 4.2 Class Diagram of Applications


Chapter :5

Design 5.1) Technology

In this project Application development we are using .NET Technology

because we have interest in this technology, this technology is easy to

understand and learn this technology provides better performance is provided

by using the just-in-time compilation, early binding, caching services and

native optimization. Web pages created with the .NET technology perform

common tasks such as form submission and client authorization much easier.

5.2) Subsystem and Their Dependencies

In this project there are four Subsystems available:

1) Registration Form

2) Login Form

3) Applications Forms

In this project User need to register by using Registration Form, after completing

the registration process user have to log in. After log in, user can fill up the

Customer’s Details and his Enquiry with product details, User can also fill the Follow

up form if the Enquiry is not completed yet.

There are some extra features to Administrator to Add/Update new Products and

Employee detail.


Fig 5.2.1 - Registration Form

Fig 5.2.2 - Login Form


Fig 5.2.3- Customer Form

Fig 5.2.4- Enquiry Form


Fig 5.2.5- Product detail Form of Respected Enquiry

Fig 5.2.6- Follow Up Form


Fig 5.2.1- Registration form is used to create a new account; for log in, User

can create a unique User- id and password through this form.

Fig 5.2.2- Log in form in used to log in for accessing all features of

Application.

Fig 5.2.3- By using Customer form user can fill up the Customer detail.

Fig 5.2.4- By using Enquiry form user fill up the Enquiry detail.

Fig 5.2.5- By using Product detail form user can fill up the product detail of

respected enquiry.

Fig 5.2.6- By using Follow up form Employee can fill up the multiple Follow

up detail of a customer.

5.3) Class Diagram Description

In chapter 4 fig 4.2 shows the class diagrams of a application. This class

diagram shows that a customer can add multiple enquiries and in every enquiry he can

select multiple products. If there is an delay in enquiry then we can add follow up

with the product enquiry. A product can have multiple follow up.

5.4) Data Base Design with ER Diagram

In this project we are using various database fields/tables for maintaining the

Database.

Fig 5.4.1 - Data Base table of Registration.


Fig 5.4.2- Database table for Login details.

Fig 5.4.3- Database table for Customer details.


Fig 5.4.4- Database table for Enquiry details.

Fig 5.4.5- Database table for Product detail of respected Enquiry.


Fig 5.4.6- Database table for Follow up.

Fig 5.4.7- Database table for Products.


Fig 5.5.8- Database table for Employee.

ER (Entity Relationship) Diagram

Fig 5.5.9- E-R Diagram for Enquiry Management System.


Chapter :6

Testing

Testing is a method to uncover and correct as many errors as possible before

delivery t the customer. In this our goal is to design the series if test cases that can

find errors, this is done through various techniques developed for testing. At early

stage the developer of the system does testing. But as the testing progresses, testing

specialist may become involved. Testing for any software is done from two different

perspectives; internal program logic is exercised using "White Box Testing" and

software requirement are exercised using "Black Box Testing".

6.1) Testing Objectives

Following are well known testing objectives:

• Testing is a process of executing a program with the intent of finding an error.

• A good test is one that has high probability of finding an as-of-yet undiscovered

error.

• A successful test is one that uncovers an as-of-yet undiscovered error.

6.2) Testing Principles

Before applying methods to design effective test case, we must understand the

basic principles that guide software testing, following are some principles that must

be followed.

• All tests should be traceable to customer requirements.

As we have seen, the objective of software testing is to uncover errors. It follows

that the most severe defects are those that cause the program to tail to meet its

requirement.

• Tests should be planned long before testing begins.

Testing planning begins as soon as the requirement model is complete. Detail

definition of the test case should begin as soon as the design model is solidified.

• The Pareto principle applies to the software testing.

It implies that 80 percent of all errors uncovered during the testing will likely be

traceable to 20 percent of all programs, components of the software. The problem

is to identify these 20 percent components and test them thoroughly.


• Testing should begin "in small" and progress towards testing "in large"

Initial tests planned and executed, generally focus on individual components. As

testing progresses, focus shifts in an attempt to find errors in the integrated clusters

of components and ultimately in the entire system.

• Exhaustive testing is not possible.

The number of path permutations for even a moderately sized program is

exceptionally large. For this reason it is impossible to execute every combination

of paths during the testing phase

6.3) Testing Methods Used

The following testing methods have been used in this project:

Black Box Testing

Black Box testing also called behavioral testing focuses on the functional

requirements of the software. That is, black box testing enables the software engineer

to derive sets of input conditions that will fully exercise all functional requirements

tor a program. It attempts to find error in the following categories:

• Incorrect or missing functions.

• Interface errors

• Error in data structures or external database access

• Initialization and terminal errors.

This testing strategy is applied during later stages of testing. Because black box

testing purposely disregards control structure, attention is focused on the information

domain. Tests are designed to answer the following questions.

• How is functional validity tested?

• How is system behavior and performance tested?

• What classes of input will make a good test case?

• Is the system particularly sensitive to certain input values?

• What effect will specific combination of data have on system operation?

The various types of black box testing are:

• Graph-Based testing

• Equivalence partitioning

• Boundary value analysis

• Comparison testing

• Orthogonal array testing


6.4) Testing Issues

How was functional validity tested?

The functional validity of the project was tested by giving series of input and

noting the output and then matching the output obtained with the expected

output. All modules were tested individually in different environment and

were found to be functionally valid.

How is system behavior and performance tested?

The system behavior and performance was tested on the basis of the inter-

functioning of the modules of the project. The project was stable and the

performance of this exceeding well.

What classes of input will make a good test case?

The project has been tested for all classes of input. The best class of input that

will make a good test case would be the input which matches the username

and password along with the phone No., and login mode, so that a person can

log in and place his call.

Is the system particularly sensitive to certain input values?

No. The project is not sensitive to any certain input values.

What effects will the wrong Username or password on system operation?

If the username and password or phone No does not match, then a particular

error message is displayed to user and he/she cannot connect to the Server.

Login and Registration modules are being tested on many systems of

different configuration.


6.5) Sample Test Cases & Results

Case 1 Wrong Registration details (e. g. wrong Password )

Input:

o User ID: abhi

o Password: abhi123

Desired output: Password not match!!.

Obtained output: as Desired.

Fig 6.5.1

Case 2 Cannot put Blank values in Log in.

a) User cannot provide blank values in the Log in fields.

b) Error generates at the submission of the information.

Input:

Username:

Password:

Desired output: Please type Used ID

Please type Password!

Obtained output: Please type Used ID

Please type Password!


Fig 6.5.2


Chapter :7

Conclusion 7.1) Limitation

• This Application is used only to maintain Database.

• There are no facility available send any information to our Mobile no. or

Email ID.

7.2) Advantage

Proper maintenance of Enquiries received.

History of enquiries for future reference.

Maintain Enquiries of Customers, Employees and Products.

Follow-up feature which Reminds for the Employee to follow the customer.

7.3) Short Description

Enquiry Management System is a web application designed to manage the

Customers, Employee and Products database with a special feature of Follow-up

(Reminder for the Employee to follow the customer).

Enquiry Management Systerm- Project Report

Documents

ensures quality

uniform resource

world wide

microsoft

activity final

included native

black box

entire application