Objective of The System

Overview of the system
Lead Management System is a part of Customer Relationship Management (CRM). Lead

generation and Lead management is a very important process for any business firms to keep
their leads, sales tracking quick and accurate. Every sales process is different. Our Lead
Management Tool that is tailored to your needs. This is a Web based Lead Management
Software can be accessed via from anywhere and any devices to manage customers, leads,
allocate leads to sales managers, lead status, remainder, appointment scheduler and fix sales
target etc. This Lead Management has kinds of role such as Admin ,Lead and Sales
Managers.
Objective of the system
Lead management is the process of managing leads, constantly and equally
.Lead management is the process of capturing leads, tracking their activities and behavior,
qualifying them, giving them constant attention to make them sales-ready, and then passing
them on to the sales team.
Lead Management System is a part of Customer Relationship Management (CRM).
Lead generation and Lead management is a very important process for any business firms to
keep their leads, sales tracking quick and accurate. Every sales process is different. Our Lead
Management Tool that is tailored to your needs. This is a Web based Lead Management
Software can be accessed via from anywhere and any devices to manage customers, leads,
allocate leads to sales managers, lead status, remainder, appointment scheduler and fix sales
target etc. This Lead Management has different kind of Modules such as Admin ,Lead and
Sales Managers.
Modules:
 Admin Modules
 Sales manager modules
 Lead manager modules
 Track modules
2. SYSTEM STUDY
Existing System
In the existing system only a view Lead and sales can be reported manually , also it has
more workload for the authorized person, but in the case of Proposed System, the user can track
the sales manager and company revenue from the site and send the sales information report
about company and particular target based on report.
Drawbacks of Existing System

 More man power ,Time consuming.
 Consumes large volume of paper work.
 Needs manual calculations and no direct role for the higher officials.
 To avoid all these limitations and make the working more accurately the system needs to
be computerized in a better way.
Proposed System
The aim of proposed system is to develop a system of improved facilities. The
proposed system can overcome all the limitations of the existing system. The proposed system
tries to eliminate or reduce these difficulties up to some extent. The proposed system will help
the user to reduce the workload and mental conflict can be accessed via from anywhere and any
devices to manage customers, leads, allocate leads to sales managers, lead status, remainder,
appointment scheduler and fix sales target etc.
Advantages of Proposed System:
The system is very simple in design and to implement. The system requires very low system
resources and the system will work in almost all configurations. It has got following features;
 Easily Accessible: Being a web-based application, it can be accessed from
anywhere with internet. It is not necessary to enqiury the sales report manually ,the
can access and track lead through pitch in online for sales and features.
 Secured: The whole system and database is fully password protected. Only the
admin and authorized users can access the data and information in the system.
 Flexibility: The software has been designed in such a way that new features and
modules can be incorporated in the system as per requirement.
 Reliable and Efficient: As this application works through computer and internet, it
has higher working efficiency and reliability.
SOFTWARE REQUIREMENTS
Front end : ASP.Net.
Back end : Ms SQL
Tools : Microsoft Visual Studio 2010, Ms-office
Operating System : Windows 8
Hardware Requirements
Processor : i3 Processor or above
Clock speed : 500 MHZ
System bus : 32 bits
RAM : 4GB of RAM
HDD : 500 GB or higher
Monitor : LCD Monitor
Keyboard : 108 keys
Mouse : 2 button mouse
SOFTWARE DESCRIPTION:
The software requirements document is the specification of the system. It should include both a
definition and a specification of requirements. It is a set of what the system should do rather than
how it should do it. The software requirements provide a basis for creating the software
requirements specification. It is useful in estimating cost, planning team activities, performing
tasks and tracking the teams and tracking the team’s progress throughout the development
activity.
ASP.net Introduction:
ASP.NET is a web development platform, which provides a programming model, a

comprehensive software infrastructure and various services required to build up robust web
applications for PC, as well as mobile devices.
ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and policies to set
a browser-to-server bilateral communication and cooperation.
ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are compiled codes,
written using the extensible and reusable components or objects present in .Net framework.
These codes can use the entire hierarchy of classes in .Net framework.
The ASP.NET application codes can be written in any of the following languages:
 C#
 Visual Basic.Net
 Jscript
 J#
ASP.NET is used to produce interactive, data-driven web applications over the internet. It
consists of a large number of controls such as text boxes, buttons, and labels for assembling,
configuring, and manipulating code to create HTML pages.
ASP.NET Web Forms Model
ASP.NET web forms extend the event-driven model of interaction to the web applications. The
browser submits a web form to the web server and the server returns a full markup page or
HTML page in response.
All client side user activities are forwarded to the server for stateful processing. The server
processes the output of the client actions and triggers the reactions.
Now, HTTP is a stateless protocol. ASP.NET framework helps in storing the information
regarding the state of the application, which consists of:
 Page state
 Session state
The page state is the state of the client, i.e., the content of various input fields in the web form.
The session state is the collective information obtained from various pages the user visited and
worked with, i.e., the overall session state. To clear the concept, let us take an example of a
shopping cart.
User adds items to a shopping cart. Items are selected from a page, say the items page, and the
total collected items and price are shown on a different page, say the cart page. Only HTTP
cannot keep track of all the information coming from various pages. ASP.NET session state and
server side infrastructure keeps track of the information collected globally over a session.
The ASP.NET runtime carries the page state to and from the server across page requests while
generating ASP.NET runtime codes, and incorporates the state of the server side components in
hidden fields.
This way, the server becomes aware of the overall application state and operates in a two-tiered
connected way.
The ASP.NET Component Model
The ASP.NET component model provides various building blocks of ASP.NET pages.
Basically it is an object model, which describes:
 Server side counterparts of almost all HTML elements or tags, such as <form> and
<input>.
 Server controls, which help in developing complex user-interface. For example, the
Calendar control or the Gridview control.
 ASP.NET is a technology, which works on the .Net framework that contains all web-
related functionalities. The .Net framework is made of an object-oriented hierarchy. An
ASP.NET web application is made of pages. When a user requests an ASP.NET page,
the IIS delegates the processing of the page to the ASP.NET runtime system.
The ASP.NET runtime transforms the .aspx page into an instance of a class, which inherits from
the base class page of the .Net framework. Therefore, each ASP.NET page is an object and all
its components i.e., the server-side controls are also objects.
1.14 BACK END:MYSQL

 It is a software, developed by Microsoft, which is implemented from the specification of
RDBMS.
 It is also an ORDBMS.
 It is platform dependent.
 It is both GUI and command based software.
 It supports SQL (SEQUEL) language which is an IBM product, non-procedural,
common database and case insensitive language.
Usage of SQL Server
 To create databases.
 To maintain databases.
 To analyze the data through SQL Server Analysis Services (SSAS).
 To generate reports through SQL Server Reporting Services (SSRS).
 To carry out ETL operations through SQL Server Integration Services (SSIS).
SQL Server works in client-server architecture, hence it supports two types of components − (a)
Workstation and (b) Server.
 Workstation components are installed in every device/SQL Server operator’s machine.
These are just interfaces to interact with Server components. Example: SSMS, SSCM,
Profiler, BIDS, SQLEM etc.
 Server components are installed in centralized server. These are services. Example:
SQL Server, SQL Server Agent, SSIS, SSAS, SSRS, SQL browser, SQL Server full text
search etc.
Instance of SQL Server
 An instance is an installation of SQL Server.
 An instance is an exact copy of the same software.
 If we install 'n' times, then 'n' instances will be created.
 There are two types of instances in SQL Server a) Default b) Named.
 Only one default instance will be supported in one Server.
 Multiple named instances will be supported in one Server.
 Default instance will take the server name as Instance name.
 Default instance service name is MSSQLSERVER.
 16 instances will be supported in 2000 version.
 20 instances will supported in 2005 and later versions.
Advantages of Instances
 To install different versions in one machine.
 To reduce cost.
 To maintain production, development, and test environments separately.
 To reduce temporary database problems.
 To separate security privileges.
 To maintain standby server.

3. SYSTEM DESIGN AND DEVELOPMENT
3.1 Modules Design:
Lead Management has different kind of Modules such as Admin ,Lead and Sales
Managers. They are
Admin Modules:
 Admin can add sales manager and can view the list of added sales manager
 Admin can delete or active the sales manager record from list.
 Admin can create leads and can view the list of created leads.
 Search filter for sales manager leads details i.e. search by selecting name, status,
monthly, weekly, daily, and date range
 Admin can view all current logged in users, leader board for sales manager lead
details and targets completed by sales manager
Sales manager modules:
 Sales manager can view upcoming reminders and all sales on dashboard
 Sales manager can add sales report and can view list of all data
 Search filter for searching customer
 Handle hard and cold calls for sales
 Sales manager can add reminder for further action
 Can edit his profile
 Can view reminder on calendar
Lead manager modules:
 Handle cold calls based on leads report.

 Email pitching a letter or email sent to an editor or agent .which details an idea for
a magazine, newspaper, book or other publication,
 Email marketing campaigns run by Lead Managers.
 Lead manager can add pitch to customer based on requirement costbudget and
convert lead.
 Lead manager can view upcoming reminders and all leads on dashboard
 Lead manager can add lead and can view list of all leads
Track modules:
 Track the employee of sales report of particular location based on city.

 Track the Lead of particular Lead Managers.
 Search filter for searching customer based on Lead.
 Can view reminder on calendar.
Reminder and schedule modules
 Can add reminder for particular lead manager based on month target..
 Add reminder for Sales manager based on daily and monthly target..
 Can view reminder on calendar.
 Schedule the task by admin to both manager .
 View the Task based on schedules dates.
3.2 Data Flow Diagram
Data Flow Diagram (DFD) is a two-dimensional diagram that describes how data is
processed and transmitted in a system. The graphical depiction recognizes each source of data
and how it interacts with other data sources to reach a mutual output. In order to draft a data flow
diagram one must
 Identify external inputs and outputs
 Determine how the inputs and outputs relate to each other
 Explain with graphics how these connections relate and what they result in.
Role of DFD:
 It is a documentation support which is understood by both programmers and non-
programmers. As DFD postulates only what processes are accomplished not how they are
performed.
 A physical DFD postulates where the data flows and who processes the data.
 It permits analyst to isolate areas of interest in the organization and study them by
examining the data that enter the process and viewing how they are altered when they
leave.
Level 0:
Admin login
Request Data Response

Lead
Management
process
Leadand sales
Database
Request Data
Lead/sales Manager
DFD Level 1:
Lead and
sales Lea
information d
Ma
nag
em
ent
Sales Sal
Dat
Manager es
a
information Ma
tabl
nag
e
er
Lead Dat
re
Admin reminder for a
Management Manager min
login process tabl
der
e
for
sal
es
Lead Lea
Manager Dat
da
information Ma
tabl
nag
e
er
Schedules for Dat

Sch
Managers edua
tabl
les
e
and
re
min
der
Dat
a
tabl
e
DFD Level :Lead
View Lead
Information Lea
d
Dat
a
tab
le
View Sales Sal
information es
Dat
a
Lead Lead tab
Managers Management le
process View Sch
Schedules ed
and reminder ule
s
information
an
d
re
mi
nd
View Cus
er
Customer Datto
information me
a
tabr
le
Dat
a
tab
le
DATABASE DESIGN
Data base is designed to manage large bodies of information. The management of data
involves both the definitions of structures for the storage of information. In addition the data base
system must provide for the safety of the information solved, despite system crashes or due to
attempts at unauthorized access. For developing an efficient database we have to fulfil certain
conditions such as controlled redundancy.
● Defining the data
● Inputting the data
● Locating the data
● Accessing the data
● Communicating the data
● Revising the data
Objectives of Data base deign
For designing data base design several objectives have to be met as follows:
● Ease of use
● Control of data integrity
● Control of redundancy
● Data independence (logical & physical)
Login details
Field DataType Constraints

empid Int Primary Key
employeename Varchar(20) Null
username Varchar(20) Null
password Varchar(20) Null
Employee Details

Did Int Primary Key
Designaionname Varchar(20) Null
emploeename Varchar(20) Null
dateofbirth date Null
Age Varchar(20) Null
Relgion Varchar(20) Null
fathername Varchar(20) Null
occupation Varchar(20) Null
Addres Varchar(20) Null
Pincode Varchar(20) Null
Email Varchar(20) Null
Gender Varchar(20) Null
nationality Varchar(20) Null
bloodgroup Varchar(20) Null
mothertongue Varchar(20) Null
customer Details

Customeridno Int Primary Key
Customername Varchar(20) Null
Caddres Varchar(20) Null
Lead table details

id Int Primary Key
Lead name Varchar(20) Null
email Varchar(20) Null
Country Varchar(20) Null
status Varchar(20) Null
Client name Varchar(20) Null
Client type Varchar(20) Null
Lead source Varchar(20) Null
Calendar Details
id Int Primary Key
Leadname Varchar(20) Null
Set Date Varchar(20) Null
Enter title of reminder Varchar(20) Null
Action Varchar(20) Null
Created date Varchar(20) Null
Reminder table details

id Int Primary Key
Set date Varchar(20) Null
Time to reminder Varchar(20) Null
Sales source Varchar(20) Null
FILE DESIGN:
One problem that would overcome is how to deal with the relations and searching to
minimize I/O operations. All fields are variable length apart from the id, year & length. Server
should be able to synchronize the database to all clients with minimal operations. When a client
comes online, all changes part the date sync back to the client. Another way to do this would
have a separate table on the server which lists all the operations that have happened and the date
they happened; and sync in a similar happened.Minimise I/O operations The server will store an
“index” of the tracks database in memory with the id and file name so read operations are kept to
a minimum. The main problem will be fragmentation when a record is deleted. Because of the
variable length fields, a new record cannot be added in that place. So fixed length fields should
not be used either (as the filename could be huge for instance).
3.4.1 INPUT DESIGN

Input design is one of the most important phases of the system design. Input design is the
process where the input received in the system are planned and designed, so as to get necessary
information from the user, eliminating the information that is not required. The goal of the input
design is to make the data entry logical and free from errors. Input data are collected and
organized into a group of similar data. Once identified input media are selected for processing. In
the software, importance is given to develop Graphical User Interface (GUI), which is an
important factor in developing efficient and user- friendly software. For inputting user data,
attractive forms are designed. User can also select desired options from the menu, which
provides all possible facilities.Input is any data or instructions entered into the memory of a
computer. Two types of input are data and instructions. Data is a collection of unorganized items
that can include
Create Lead Input:
Add Reminder Input:

Document Upload:
3.4.2 OUTPUT DESIGN

Computer output is the most important direct source of information to the user. The output
design refers to the result and information that it’s generated by the system forms many end
users. To produce the output which are displayed in a screen, efficient and intelligent output
design improves the system relationship with the users and help indecision making. It is
designed in a user-friendly way to avoid user burden.
Two of the most output media today are printers and screen. Most customers now access
their reports from a hard copy or screen display. Computer’s output is the most important and
direct source of information to the user, efficient, logical, output design should improve the
systems relations with the user and help in decision-making. As the outputs are the most
important source of information to the user, better design should improve the system’s relation
and also should help in decision-making.
View All Lead Data:
View Clientstatus Data:

View Rerminder Data
4.TESTING AND IMPLEMENTATION
4.1 INTRODUCTION:
Testing is the process of detecting errors for which the required open web application
secure employment portal specifications stated. Testing performs a very critical role for quality
assurance and for ensuring the reliability of software. The results of testing are used later on
during the software maintenance. The aim of testing is often used to demonstrate that a program
works by showing that it has no errors. The basic purpose of testing phase is to detect the errors
that may be present in the program. Hence one should not start testing with the intent of showing
that a program works, but the intent should be to show that a program doesn’t work. The main
objective of testing is to uncover an error in systematic way with minimum effort and time.
TESTING OBJECTIVES
The testing objectives are summarized in the following three steps:
 Testing is process of executing a program with the intent of finding an error.
 A good test case is one that has high probability of finding an undiscovered error.
 A successful test is one that uncovers an as yet undiscovered error.
TESTING TYPES
The different types of testing are:
 Unit testing
 Integration testing
 System testing
 Acceptance testing
Unit Testing:
This test focuses on verification effort on the smallest unit of software module. Using the
detailed design and the process specifications testing is done to uncover errors within the
boundary of the module. All the modules must be successful in the unit test before the start of
the integration testing begins. In this project each service is a module like Login, Forms etc.
Each module has to be tested by giving different sets of inputs. The inputs are validated when
accepting from user.
Integration Testing:
After the unit testing the integration of modules has to be done and then integration
testing can be done. The goal here is to see if modules can be integrated properly, the emphasis
being on testing interfaces between different modules.
System Testing:
In the system testing the entire web portal is tested according the software requirement
specifications document.
Acceptance Testing:
The acceptance testing is performed with realistic data of the client, which focus on the
external behaviour of the system; the internal logic of the program is emphasized. Software
testing is a critical element of software quality assurance and represents the ultimate review of
specification, design and coding. Testing is the exposure of the system to trial input to see
whether it produces correct output.
TESTING PHASES:
Software testing phases include the following:
 Test activities are determined and test data selected.
 The test is conducted and test results are compared with the expected results.
TESTING METHODS:
Testing is a process of executing a program to find out errors. If testing is conducted
successfully, it will uncover all the errors in the software.
Any testing can be done basing on two ways:

 White Box Testing
 Black Box Testing
White Box Testing:

It is a test case design method that uses the control structures of the procedural design to
derive test cases.
Using this testing a software Engineer can derive the following test cases:
 Exercise all the logical decisions on either true or false sides.
 Execute all loops at their boundaries and within their operational boundaries.
 Exercise the internal data structures to assure their validity.
Black Box Testing:
It is a test case design method used on the functional requirements of the software. It will help a
software engineer to derive sets of input conditions that will exercise all the functional
requirements of the program.
Black Box testing attempts to find errors in the following categories:
 Incorrect or missing functions
 Interface errors
 Errors in data structures
 Performance errors
 Initialization and termination errors
By black box testing we derive a set of test cases that satisfy the following criteria:
 Test cases that reduce by a count that is greater than one
 The number of additional test cases that must be designed to achieve reasonable testing.
TESTING PLANS:
Testing can be done in two ways:
 Bottom up approach
 Top down approach
SYSTEM IMPLEMENTATION
System implementation is the important stage of project when the theoretical design is tunes
into practical system. The main stages in the implementation are as follows:
● Planning
● Training
● System testing and
● Changeover planning
Planning is the first task in the system implementation. Planning is deciding on the method
and the time scale to be adapted. At the time of implementation of any system people from
different departments and system analysis involve. They are confirmed to practical problem of
controlling various activities of people outside their own data processing departments.
The line manager controlled through an implementation co-ordinate committee. The
committee consists of idea, problems and complaints of user department. It must also be
consider,
● The implementation of system environment.
● Self-selection and allocation for implementation tasks.
● Consultation with unions and resources available.
● Standby facilities and channels of communication.
CONCLUSION & FUTURE ENHANCEMENTS
While developing the system a conscious effort has been made to create and develop a
software package, making use of available tools, techniques and resources - that would generate a
proper system.
While making the system, an eye has been kept on making it as user-friendly, as cost-
effective and as flexible as possible. As such one may hope that the system will be acceptable to
any user and will adequately meet his or her needs.
As in case of any system development processes where there are a number of
shortcomings, there have been some shortcomings in the development of this system also. The
project is still under modification.
BIBLIOGRAPHY
BOOK REFERENCES
 Author-Simone Chiaretta. Front-end Development with ASP.NET Core, Angular, and
Bootstrap.
 Professional Application Lifecycle Management with Visual Studio 2013 and
Professional Visual Studio 2013 Ebook Bundle
Martin Hinshelwood, Mickey Gousset, Brian A. Randell, Brian Keller, Martin
Woodward, Bruce Johnson.
 ,William Penberthy. Richards Fairley, Beginning ASP.NET for Visual Studio 2015
“Software Engineering Concepts”
 Eric A Smith, Valor Whister& Hank Marquis, “Visual Programming Bible”

WEBSITES
 https://www.tutorialspoint.com/ms_sql_server/
 https://www.w3schools.com/sql/sql_intro.asp
 www.sqltutorial.org/
Appendix
Sample Screenshots:
Lead add:
screen 2:
screen3:
screen4:
Screen5:
Scrren6:
Screen7:
Screen 8:
B.Sample Code:
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.SqlClient;
public partial class Admin_LoginPage : System.Web.UI.Page

{
SqlConnection con;
SqlCommand cmd;
protected void Page_Load(object sender, EventArgs e)

{
}
protected void Button1_Click(object sender, EventArgs e)
{
string loc_email = txt_uname.Text;
string loc_password = txt_pwd.Text;
con = new SqlConnection();

con.ConnectionString = @"Data Source=.\SQLEXPRESS;Initial
Catalog=coolcabs;Integrated Security=True";
//con.ConnectionString = @"data source=RAJ-PC\SQLEXPRESS;Initial Catalog=cool
cabs;Integrated Security=true";
con.Open();
string myquery = null;

myquery = "select * from ManagerCreation where EmailID='" + loc_email + "' and
Password='" + loc_password + "'";
SqlDataAdapter adpt = new SqlDataAdapter(myquery, con);
DataTable dt = new DataTable();
adpt.Fill(dt);
if (dt.Rows.Count == 1)
{
Session["EmailId"] = dt.Rows[0]["EmailID"].ToString();
string Designation = dt.Rows[0]["Designation"].ToString();
if (Designation == "finance Manager")

{
Response.Redirect("~/FinancialManager/Home.aspx");
}
if (Designation == "HRManager")
{
Response.Redirect("~/HRManager/home.aspx");
}
if (Designation == "Maintance Manager")
{
Response.Redirect("~/MaintenanceManager/Home.aspx");
}
if (Designation == "Movement Manager")
{
Response.Redirect("~/MovementManager/Home.aspx");
}
if (Designation == "Admin")
{
Response.Redirect("~/Admin/Home.aspx");
}
}
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="LoginPage.aspx.cs"
Inherits="Admin_LoginPage" %>
<!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>Untitled Page</title>
<style type="text/css">
.style1
{
width: 67%;
height: 181px;
}
.style4
{
height: 12px;
}
.style5
{
height: 29px;
}
.style6
{
height: 35px;
}
.style7
{
width: 100%;
}
.style10
{
width: 157px;
height: 169px;
}
.style11
{
width: 585px;
}
.style12
{
height: 12px;
width: 94px;
}
.style13
{
height: 29px;
width: 94px;
}
.style14
{
width: 94px;
}
.style15
{
height: 35px;
width: 94px;
}
.style16
{
width: 700px;
height: 238px;
}
</style>
</head>
<body>
<form id="form1" runat="server">
<div>
<p>
<span lang="en-us">    </span>
<table cellpadding="0" cellspacing="0" class="style7">
<tr>
<td>
<span lang="en-
us">            &nb
sp;            &nbs
p;            &nbsp
;


</span>
<img alt="1" class="style16" src="Admin/Untitled-2%20copy.jpg" /></td>
</tr>
</table>
</p>
<table align="center" cellpadding="0" cellspacing="0" class="style1">

<tr>
<td rowspan="4" class="style11">
<span lang="en-
us">            &nb
sp;        </span>
<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000"
codebase="http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflas
h.cab#version=7,0,0,0"
id="car" align="middle" class="style10">
<param name="allowScriptAccess" value="sameDomain" />
<param name="movie" value="Admin/car.swf" /><param name="quality" value="high"
/><param name="bgcolor" value="#ffffff" />
<embed src="Admin/car.swf" quality="high" bgcolor="#ffffff" width="550"
height="400" name="car" align="middle" allowScriptAccess="sameDomain"
type="application/x-shockwave-flash"
pluginspage="http://www.macromedia.com/go/getflashplayer" />
</object></td>
<td class="style12">
<asp:Label ID="Label1" runat="server" Text="User Name"></asp:Label>
</td>
<td class="style4">
<asp:TextBox ID="txt_uname" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<asp:Label ID="Label2" runat="server" Text="Password"></asp:Label>
</td>
<td class="style5">
<asp:TextBox ID="txt_pwd" runat="server"></asp:TextBox>
<br />
<asp:Label ID="Label3" runat="server"></asp:Label>
</td>
</tr>
<tr>
</td>
<td>
<asp:Button ID="Button1" runat="server" Text="Sign In"
onclick="Button1_Click" />
<br />
<br />
<asp:LinkButton ID="LinkButton1" runat="server"
PostBackUrl="~/Forget Password.aspx">Forget Password</asp:LinkButton>
</td>
</tr>
<tr>
</td>
<td class="style6">
<br />
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
<?xml version="1.0"?>

<configuration>
<appSettings/>
<connectionStrings/>
<system.web>

<compilation debug="true" targetFramework="4.0">
</compilation>

<authentication mode="Windows"/>

<pages controlRenderingCompatibilityVersion="3.5"
clientIDMode="AutoID"/></system.web>

</configuration>
C.Table Design:
Login details

empid Int Primary Key
employeename Varchar(20) Null
password Varchar(20) Null
Employee Details

Did Int Primary Key
Designaionname Varchar(20) Null
emploeename Varchar(20) Null
dateofbirth date Null
Age Varchar(20) Null
Relgion Varchar(20) Null
fathername Varchar(20) Null
occupation Varchar(20) Null
Email Varchar(20) Null
Gender Varchar(20) Null
nationality Varchar(20) Null
bloodgroup Varchar(20) Null
mothertongue Varchar(20) Null
customer Details

Customeridno Int Primary Key
Customername Varchar(20) Null
Caddres Varchar(20) Null
Lead table details

id Int Primary Key
Lead name Varchar(20) Null
Country Varchar(20) Null
status Varchar(20) Null
Lead source Varchar(20) Null
Calendar Details

id Int Primary Key
Leadname Varchar(20) Null
Set Date Varchar(20) Null
Enter title of reminder Varchar(20) Null
Action Varchar(20) Null
Created date Varchar(20) Null
Reminder table details

id Int Primary Key
Set date Varchar(20) Null
Time to reminder Varchar(20) Null
Sales source Varchar(20) Null

Objective of The System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Objective of The System

Uploaded by

Copyright:

Available Formats

Overview of the system

Lead Management System is a part of Customer Relationship Management (CRM). Lead

Drawbacks of Existing System

 Consumes large volume of paper work.

Advantages of Proposed System:

Front end : ASP.Net.

Back end : Ms SQL

Tools : Microsoft Visual Studio 2010, Ms-office

Operating System : Windows 8

Clock speed : 500 MHZ

System bus : 32 bits

RAM : 4GB of RAM

HDD : 500 GB or higher

Monitor : LCD Monitor

Keyboard : 108 keys

Mouse : 2 button mouse

ASP.NET is a web development platform, which provides a programming model, a

ASP.NET Web Forms Model

The ASP.NET Component Model

1.14 BACK END:MYSQL

Usage of SQL Server

Instance of SQL Server

 An instance is an installation of SQL Server.

 An instance is an exact copy of the same software.

 If we install 'n' times, then 'n' instances will be created.

 There are two types of instances in SQL Server a) Default b) Named.

 Only one default instance will be supported in one Server.

 Multiple named instances will be supported in one Server.

 Default instance will take the server name as Instance name.

 Default instance service name is MSSQLSERVER.

 16 instances will be supported in 2000 version.

 20 instances will supported in 2005 and later versions.

 To install different versions in one machine.

 To maintain production, development, and test environments separately.

 To reduce temporary database problems.

 To separate security privileges.

 To maintain standby server.

3.1 Modules Design:

Sales manager modules:

Lead manager modules:

 Handle cold calls based on leads report.

 Track the employee of sales report of particular location based on city.

Reminder and schedule modules

 Determine how the inputs and outputs relate to each other

Request Data Response

Schedules for Dat

Field DataType Constraints

Field DataType Constraints

Field DataType Constraints

Lead table details

Field DataType Constraints

Reminder table details

Field DataType Constraints

3.4.1 INPUT DESIGN

Add Reminder Input:

3.4.2 OUTPUT DESIGN

View All Lead Data:

View Clientstatus Data:

Any testing can be done basing on two ways:

White Box Testing:

CONCLUSION & FUTURE ENHANCEMENTS

 Eric A Smith, Valor Whister& Hank Marquis, “Visual Programming Bible”

public partial class Admin_LoginPage : System.Web.UI.Page