Essay: Integrated Application for Caller-Identification System

ABSTRACT
This is an Integrated Application for Caller-Identification System (Caller-ID System). It is the service where the CLI (Caller Line Identity) is sent to the admin. CNAM (Caller Name) is the character text field used in caller name service. Caller-ID System typically consists of the caller’s contact number with contact information. The information made available to the called party may be displayed on a separately attached device.
It is a windows based application which is hardware integrated system. It is build by using windows technology ASP.NET with C#.NET and Microsoft SQL Server 2008R2.The basic aim of this application is to display customer’s information based on their contact number. It can facilitate the work of those who need to handle huge amount of phone calls by serving customer data for the right person, to the right interface in the appropriate time.
If there is an unknown number for admin then admin asks all details to customer and save it in database. If existing number is appeared then all details of customer will be displayed on the hardware device (Caller-ID device). It is important to handle as many requests as possible on the first contact, and handle them as efficiently as possible. This helps minimize costs while keeping customer satisfied. To help admin to handle requests quickly.
It is common to have a window form with customer’s information, It’s called as CPN (Calling Party Number). This form holds the customer’s screen while entering the contact number. This window is usually called as screen population (screen POP) because that screen is populated with customer’s information.
Contents:
1. ASP.NET with C#.NET Development.
i. Configuration of Visual Studio-2010
ii. Creating a WPF (Windows Presentation Foundation) also called as Windows form application.
iii. Implementing WPF.
2. Microsoft SQL Server 2008 R2.
i. Configuration of SQL Management Studio.
ii. Creating a database and tables.
iii. Implementing it by query firing using WPF.
 
Company Profile
Samyak Infotech Private Limited is an IT company based in Ahmedabad, India specializing in providing Customized Integrated Software Solutions. Imagined, fashioned and accomplished by a group of self-motivated IT professionals with ability to innovate and a strong desire to excel, Samyak Infotech Pvt Ltd is a rapidly growing IT company with extensive experience in designing and developing cutting edge IT solutions for clients representing a broad cross-section of businesses.
Samyak has developed generalized solutions as well as based on specific customer requirements, using some of the latest, creative and revolutionary tools available.
Samyak is an integrated IT resources center that began its corporate journey in 1998 as a 100% export-oriented unit. With a corporate mission focused on providing software development support and solutions to a quality-conscious clientele around the world, Samyak began operations in various fields like Information Technology, Embedded, Electronics, Instrumentation and Industrial Automation.
As a technology company, it is the people that defines the company, and hence Samyak ensures that the technical skills of its team is constantly kept up-to-date with the demands and opportunities of the times.
Infrastructure:
 Samyak is a team of highly qualified professionals.
 Samyak houses latest IT Infrastructure.
 Samyak uses Licensed software tools, to keep abreast of the latest technology and updates.
 Samyak owns development capacity for open source and license software.
 Samyak provides reliable 24×7 support to their clients with online customer care service, as it has clientele all over the world.
Technical Presentation:
 AGR Presentation.
 J2EE
 .NET
 Samyak Presentation.
 Corporate Presentation.
Address:
Samyak Infotech Pvt. Ltd.
905-908,Abhijeet,
Mithakhali Six Roads,
Ellisbridge,Ahmedabad-380006.
Gujarat, India.
List of Figures:
Sr No
Name Page No
1.5.1 Microsoft.net 2
1.5.2 Visual studio-2010 2
1.5.3 SQL Server-2008 3
1.5.4 Caller-ID Device 3
1.5.5 RS-232 Cable 3
1.5.6 Ethernet Cable 4
2.1.1 Waterfall Model 6
2.2.1 Gantt Chart 7
2.4.1.1 Activity Canvas 8
2.4.1.2 Environment Canvas 8
2.4.1.3 Interaction Canvas 9
2.4.1.4 Objects Canvas 9
2.4.1.5 Users Canvas 10
2.4.2 Empathy Canvas 11
2.4.3 Ideation Canvas 12
2.4.4 Product Development Canvas 13
4.5.1 Class Diagram 19
4.5.2 Activity Diagram 20
4.5.3 Use Case Diagram 21
4.5.4.1 Sequence Diagram (Login) 22
4.5.4.2 Sequence Diagram (Whole System) 23
4.5.5 Collaboration diagram 24
5.2.1 Registration Page 29
5.2.2 Login Page 30
5.2.3 Customer Form 31
5.2.4 Customer Registration 32
5.2.5 Admin Registration 33
5.2.6 Admin Login 34
5.2.7 Displaying Information 35
5.2.8 Admin deleted record 36
 
List Of Tables:
Sr No
Name Page No
5.1.1 Registration 25
5.1.2 Login 25
5.1.3 Admin 26
5.1.4 Contact Number 26
5.1.5 Customer 27
5.1.6 Call History 28
5.1.7 Department 28
5.3.1 Coding Standards 30
5.3.2 Basic Validations 30
6.2.1 Test Cases for Admin 46
6.2.2 Test Cases for Customer 47
 
Abbreviations
 My Project definition is “Integrated Application for Caller-Identification System.” An Abbreviations of this application are as follows:
 Caller-ID: Caller-Identification.
 CPN: Caller Party Number.
 CLI: Calling Line Identity.
 CNAM: Caller Name.
 Screen-POP: Screen Population.
 Communication Module: The module that allows communication between clients (Customers) and server (admin).
 Developers: The team responsible for developing software system.
Notations
 For Class Diagram:
Symbol Name
Class
Generalization
Composition
Dependency
 
 For Activity Diagram:
Symbol Name
Action State
Initial State
Final State.
Decision
Object Flow
Control Flow
 For Use Case Diagram:
Symbol Name
Use Case
Actor
Extends
Uses
System Boundry
 For Sequence Diagram:
Symbol Name
Activation
Message
Message Return
Object Lifeline
 For Collaboration Diagram:
Symbol Name
Classifier Role
Association Role
Note
1. INTRODUCTION
1.1 Project Summary
Sometimes it becomes very tedious job and everything has to be handled in a very haphazard manner if one keeps all the manual records. This application is very significant asset to any business which can relieve a person from lot of mundane, repetitive work and help to resolve mistake if any.
This is an Integrated Application for Caller-Identification System (Caller-ID System). It is the service where the CLI (Caller Line Identity) is sent to the admin. CNAM (Caller Name) is the character text field used in caller name service. Caller-ID System typically consists of the caller’s contact number with contact information. The information made available to the called party may be displayed on a separately attached device.
If there is an unknown number for admin then admin asks all details to customer and save it in database. If existing number is appeared then all details of customer will be displayed on the hardware device (Caller-ID device). It is important to handle as many requests as possible on the first contact, and handle them as efficiently as possible. This helps minimize costs while keeping customer satisfied. To help admin to handle requests quickly.
1.2 Project Purpose
The goal of this windows application is to get customer’s information regarding their contact number and display all the information. This application can facilitate the work of those who can handle huge amount of data, as manual track of records is a tedious task, this may reduce lot of unnecessary work.
1.3 Project Scope
The work that needs to be accomplished to deliver the customer for better results with specified features and functions in the project. This windows application is limited to specific organizations. There is no need of internet connection. This is an intranet scope for organizations.
1.4 Project Objective
Caller-ID System typically consists of the caller’s contact number with contact information. The information made available to the called party may be displayed on a separately attached device. It is common to have a window form with customer’s information; It’s called as CPN (Calling Party Number). This form holds the customer’s screen while entering the contact number. This window is usually called as screen population (screen POP) because that screen is populated with customer’s information.
1.5 Technology Review
 Front End:
This is a windows based application, developed using technology ASP.NET with C#.NET in the front end.
Fig: 1.5.1 Microsoft.net
A Windows Form Application is an event-driven supported by Microsoft’s .NET framework. Windows forms provide access to native Windows user interface common controls by wrapping the extant Windows API in Managed code.
 Platform:
Microsoft Visual Studio-2010
Fig: 1.5.2: Visual studio-2010
Microsoft Visual Studio 2010 is an integrated development environment from Microsoft which is used to develop computer programs, websites, web applications and web services. It uses Microsoft software development platforms such as Windows API, Windows Forms, Windows Presentation Foundation, Windows Store and Microsoft Silverlight. It can produce both native node and managed code.
 
 Back End:
Microsoft SQL Server-2008
Fig:1.5.3:SQL Server-2008
Microsoft SQL Server is relational database management system developed by Microsoft. As a database it is a software product whose primary function is to store and retrieve data as requested by other software applications.
 Extra Hardware Device:
Caller-ID Device
Fig: 1.5.4: caller-id device
In this Caller-ID System, it is used as Caller-Identification Device (Caller-ID Device). This device is attached separately to the Personal Computer (PC) through cables. The information is display on this device’s screen regarding to customer contact number.
 This device is connected through two types of cables:
1) RS-232 cable:
Fig: 1.5.5 RS-232 cable
The RS-232 standard is commonly used in computer serial ports. An RS-232 serial port was once a standard feature of a personal computer, used for connections to modems, printers, mice, data storage, and other peripheral devices.
 
2) Ethernet Cable:
Fig: 1.5.6: Ethernet cable
Ethernet cable is a family of computer networking technologies for Local Area Networks (LAN) and Metropolitan Area Networks (MAN).
RJ45 connectors are used for Ethernet computer network cables referred as RJ45 connectors.
1.6 Literature Review
 Study Of Current Existing System:
1 Call Center Management System:
Call center is a centralized system used for receiving phone calls, emails, fax from customers and Call center employees takes calls from customers can provide solution for problem they are facing. In order to provide quality of service customer support team should have good communication system inside office for communicating with other employees. Call center management system project is designed in asp.net programming language. Main aim of this software is to provide computerized solution for call centers for managing employees data, customers data, establish communication between employees inside office.
2 Customer Information Management System:
The Customer Information was collected manually. This information consisted, for example, of names, age, city , address etc information. During this project, it was decided that a customer information system will to be created from scratch. The system was developed with PHP programming language and MySQL database management system using Waterfall development model.
3 VOIP Based Predictive Dialer:
A VoIP (Voice Over Internet Protocol) predictive dialer is a software product capable of predictive dialing using VOIP service directly. A predictive dialer is an automatic dialing system that can dial many telephone numbers at a time to improve productivity.
 
 Limitations Of Existing System:
 Lot of mundane and repetitive work.
 Inefficiency and estimation of cost.
 Maintenance of records for future references.
 Separate hardware device was not introduced in computer caller-id system.
 Usability Of Project:
 To create simple, easy to use, accessible from anywhere software.
 To provide accuracy and precision with reduced human intervention.
 This system allows the call logs on computer for specific organization.
 Discard unwanted calls.
 To identify who wants to communicate.
 Unlimited access to the organization’s largest collection of names and numbers.
 Innovative Ideas Of Project:
 This Caller-ID Computer system has a separate particular caller-id device, which is integrated with this application.
 Update Contacts: Add numbers with contact list with customer information such as name, age, address etc.
 Backup Contacts: It provides backup features that never lose a contact list with information.
 Reputation Check: Arrange the repeated calls are arrived at system by date and time, numeric or alphabetical ascending order.
 
2. Project Management
2.1 Project Planning:
2.1.1 Project Development Approach And Justification:
Procedural approach has been adapted for development of the project. Most of the programmers use a procedural approach by default, since web pages themselves operates in a very procedural way.
 Waterfall Model:
Waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing downwards like waterfall through the phases of Conception, Initiation, Analysis, Design, Construction Testing, Implementation of Maintenance. It is also known as classic life cycle model.
 
2.1.2 Project Plan:
We are planning our project completing in given time duration. We are also gathering customer’s requirement and satisfying all that needs. We are using best functionality to developing this website. Required Database was designed and normalized as required. Code was written in such a way that maximum functionality was coded with minimum possible lines of code.
2.2 Project Scheduling:
Gantt Chart:
Fig: 2.2.1 Gantt chart
2.3 Risk Management:
2.3.1 Risk Identification:
All projects have risks. If a potential risk of the project is not identified early, then the project will be at high risk to complete as per schedule.
Hence, it is the most important process in risk management planning.
2.3.2 Risk Analysis:
It is the second step of risk management. Impact is the effect of the risk in case it happens. There are some technical and business factors while assigning impact.
 Customer loss.
 Loss of business, Financial loss.
 Hardware integration problems.
2.4 Canvas Designing
2.4.1 AEIOU Summary:
2.4.1.1 Activity:-
Fig: 2.4.1.1: Activity Canvas
2.4.1.2 Environment:-
Fig: 2.4.1.2: Environment Canvas
2.4.1.3 Interaction:-
Fig: 2.4.1.3: Interaction Canvas
2.4.1.4 Objects:-
Fig: 2.4.1.4: Objects Canvas
2.4.1.5 User:-
Fig: 2.4.1.5 User Canvas
 
2.4.2 Empathy summary:
Fig: 2.4.2: Empathy Canvas
 
2.4.3 Ideation:
Fig:2.4.3: Ideation Canvas
 
2.4.4 Product Development :
Fig: 2.4.4 Product Development Canvas
 
3. System Requirement Study
3.1 User Characteristics:
 Customer:
Customer as an actor demands for particular product along with specification of all the requirements. Customer can:
 Create a new product request.
 Specify all requirements
 Optionally attach design specifications
 View all past request and its details.
 Admin:
The main job of an administrator is to manage the tasks performed by the user. Admin performs the following tasks:
 Creating whole systems.
 Configure all the parameters for displaying information.
 Configure role of the user be it the employee or the customer.
3.2 Hardware And Software Requirements:
 Hardware Requirements:
 Microsoft Windows XP/7/8
 Dual Core Processor
 RAM- 2GB and above
 Hard Disk-100GB and above
 Software Requirements:
 Platform: Microsoft .NET
 Technology: ASP.NET
 Language: C# (C Sharp)
 For Development: Microsoft Visual Studio-2010
 Back End: Microsoft SQL Server-2008
 
3.3 Specific Requirements:
3.3.1 Functionality:
 All requirements are very well known, clear and fixed.
 Whole technology should be understood.
 Code simplicity is one the best feature to understand the coding phase.
 Login, Registration will be done efficiently.
 The important key is contact number, verified the number or register the number.
 Displaying and getting information also history of the number will be displayed on the screen.
 Logout.
3.3.2 Usability:
 The whole system takes an hour to understand all requirements, specifications and functionality for a normal user.
 It will take minimum 6 months for learning this application.
 Integration with hardware device to software takes much time for learner (normal user).
 Developers need to be up-skilling and expected to bring great code to an organization.
 Developers must follow the specific standards, which the technology is used.
3.3.3 Reliability:
 Maintainability: If any requirement occurs, then it should be easily incorporated in the system.
 Portability: The application should be portable on any windows based system.
3.3.4 Performance:
 Response time for transaction: This term represents the time for a database transaction. This application will take one to two seconds (average) for database transaction.
 Capacity: The system can accommodate around the 40-50 customers’ capacity in this application.
 Resource Utilization: This application contain resources like,
 Personal Computer configured with Windows-7, Pentium dual core processor.
 RAM is around 256MB to 1GB.
 Communication is done through Ethernet cable or RS232 cable between hardware device and software.
 Cost Sensitivity: Under all circumstances, the maximum cost payable as submitted by the user will be the maximum cost charged to the user.
3.3.5 Supportability:
This section includes following supportability requirements:
 Naming Conventions: All code will be written as specified by the Pascal Naming Convention (for Class name and Methods name), Camel Casing Convention (Method arguments and local variables) and Hungarian Naming Convention (Data type identification).
 Coding Standards: All codes will be written as required by the .NET Coding Standards.
 Cost-Effective-To-Maintain: It may covers divers level of documentation, such as system documentation as well as test documentation.
3.3.6 Design Constraints:
There are many aspects of any design project that must be considered to determine the feasibility of the system.
 Software Language: All coding will be done in standard of Microsoft .NET platform.
 Scheduling Constraints: Exhaustive searches of the entire set of combinations of jobs will not be done. Heuristics will be developed for this scheduling problem.
3.4 Assumptions And Dependency:
There is no assumptions in this windows application.
 
4. System Analysis
4.1 Requirements Of New System:
4.1.1 User Requirements:
User must be aware the system works properly with full availability, reliability, security and safety. The user responsibilities are as follows:
 Should know the data needed to address the problem.
 Should know how to use it.
 Should adhere to guidelines and prescribed standard.
4.1.2 System Requirements:
This windows application is designed to display the information of customer regarding their contact number. This information will be displayed on separately attached device. It must fulfill all the functional and non-functional requirements.
4.2 Feasibility Study:
4.2.1 Technical Feasibility:
Technical feasibility determines whether the work for the project is being done with the present equipment, current procedures, existing software’s technology and available persons or not. Thus it is important to check the system to be technically feasible.
System would be implemented using .NET technology which is quite easy to use and user friendly IDE Visual Studio-2010.
 Software Platform:
 Database server- Microsoft SQL Server 2008
 Technologies- ASP.NET using C#.NET
 Development Tool:
 MS Visual Studio-2010
4.2.2 Economical Feasibility:
Economic feasibility looks at the financial aspects of the project. Economic feasibility concern with returns from the investments in project.
The software resources requirements for the proposed system is .NET development environment, SQL Server 2008 that are already owned by the client and do not require additional investment.
4.2.3 Implementation Feasibility:
Implementation feasibility deals with the study whether the service, which is being developed will run in the environment available with us, will the management of the organization approve the system?
Implementation feasibility is about basic infrastructure and material required to develop the system. It is found that:
 Infrastructure provided was a high configuration computer system to implement the application.
 The required software’s like .NET 2010, SQL Server-2008 is provided.
 Literature like books, technical manuals and reports.
 Proper and timely guidance was provided by the guide.
4.3 Requirements Validation:
It is a process in which it is checked that gathered requirements represents the same system that customer really wants or it is showing different. The basic objective of requirement validation is that the SRS reflects the actual requirements correctly and accurately.
The common methods for requirement validation are as follows:
 Requirement Review:
It is review by group of people to find errors and point out other matters of concern. It may be formal or informal.
 Prototype:
The requirements can be checked using executable model of the system. Prototype which is build during analysis, can be used for requirement validation.
 Test Case Generation:
In this technique, various tasks are developed for requirements and they are- Verifiability, Comprehensibility, Traceability and Adaptability.
 
4.4 Features Of New System:
 This system is a windows based application.
 It is an Intranet system which is for specific organization.
 This system has an extra hardware device.
 This hardware device is a Caller-ID Device, which displays all the information.
 Existing number will direct display the information on separately attached device.
4.5 Object Oriented Approach:
4.5.1 Class Diagram:
Fig: 4.5.1 Class Diagram
 
4.5.2 Activity Diagram:
 
4.5.3 Use Case Diagram:
Fig: 4.5.3: Use Case Diagram
4.5.4 Sequence Diagram:
4.5.4.1 Sequence diagram for login:-
 
4.5.4.2 Sequence diagram for whole system:-
 
4.5.5 Collaboration Diagram:
 
5. System Design
5.1 Database Design:
5.1.1 Table Name: Registration
Primary Key: First name
Field Name Data Type Size Constraints Description
First_Name Varchar 15 Primary Key First name of customer.
Last_Name Varchar 15 Not Null Last name of customer.
Email_id Varchar 25 Not Null Email id of customer.
Password Varchar 30 Not Null Password of customer.
Conf_Password Varchar 30 Not Null Confirm password of customer.
Table:5.1.1 : Registration
5.1.2 Table Name: Login
Primary Key: Log_id
Field Name
Data Type Size Constraints Description
Log_id Varchar 15 Primary Key Login id of customer.
Email_id Varchar 25 Not Null Email id of customer.
Log_pwd Varchar 30 Not Null Password of customer.
Table:5.1.2 Login
 
5.1.3 Table Name: Admin
Primary Key: Id
Foreign Key: Log_id
Field Name Data Type Size Constraints Description
Id Int 25 Primary Key Identification of Admin
Name Varchar 25 Not Null Name of admin
Log_id Varchar 25 Foreign Key Login id of Admin
Password Varchar 30 Not Null Password of Admin
Table:5.1.3: Admin
5.1.4 Table Name: Contact Number
Primary Key: Contact_Number
Field Name Data Type Size Constraints Description
Contact_Number Numeric (18,0) Primary Key Contact number of customer
Name varchar 25 Not Null Name of customer
Table:5.1.4 Contact Number
 
5.1.5 Table Name: Customer
Primary Key: Contact_Number
Field Name Data Type Size Constraints Description
Customer ID
Integer
30
Not Null For Customer unique identification
Contact Number
Numeric
(18,0)
Primary Key Customer contact number
Name
Nvarchar
50
Not Null Customer Name
Age
Numeric
(18,0)
Not Null Customer’s Age
Address Nvarchar 150
Not Null To store the Customer Address
Nationality Nvarchar 50 Not Null Customer’s Nationality
City Nvacrhar 50 Not Null City of Customer
Email Nvarchar 50 Not Null For Customer’s email address
Occupation Nvarchar 50 Not Null Customer’s Occupation
Image Varchar – Not Null Image of Customer
Table:5.1.5 Customer
 
5.1.6 Table Name: Call History
Primary Key: Contact_Number
Filed Name Data Type Size Constraints Description
Id Int 30 Not Null Identity of Customer
Contact Number Numeric 30 Primary Key Customer Contact Number
Date Numeric 30 Not Null Call Date
Time Numeric 30 Not Null Call Time
Table:5.1.6 Call History
5.1.7 Table Name: Department
Primary Key: Department ID
Field Name Data Type Size Constraints Description
Department_ID Int 25 Primary Key Department id of user.
Name Varchar 25 Not Null Name of user
No of emp Int 15 Not Null Number of user.
Table:5.1.7: Department
 
5.2 Input Output Design:
Registration page:
Figure 5.2.1: Registration Page
 
Login Page:
Figure5.2.2: Login Page
 
Customer details form:
Figure5.2.3: Customer form
Customer can add his/her requirements along with all the details and specification. Then click on submit button, the details will be send successfully.
 
Click on submit button and displays the message that submitted successfully.
Figure5.2.4: Customer Registration
 
Admin Registration:
Figure5.2.5: Admin Registration
 
Admin Login:
Figure5.2.6: Admin Login
Admin can view all the details from contact number only:
Figure5.2.7: Displaying Information
 
Admin can also delete the registered contact number:
Figure5.2.8: Admin deleted record
5.3 Coding Standards:
Coding conventions are a set of guidelines for a specific programming language that recommended programming style , practices and methods for each aspect of a piece program written in any language. They basically include file organizations, indentation, comments, declarations, statements, naming conventions, programming practices, programming principles and some rules of thumb.
Coding Standards
Checks For Normal Working To Be Checked?
A. Does your system save correct data in database? *
B. In update does your screen load correct data? *
C. Does your system work flow is correct? *
Table 5.3.1: Coding Standards
Basic Validations
Basic Validations
A. Validation for required field is done? *
B. Validation for Integer, String is done? *
C. Type Check/ Type Safety *
D. Boundary Value Analysis *
Table 5.3.2: Basic Validations
 
Coding Sample
Register.cs:
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.SqlClient;
using System.Text.RegularExpressions;
namespace WindowsFormsApplication6
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
private void Form1_Load(object sender, EventArgs e)
{
textBox4.PasswordChar = \’*\’;
textBox5.PasswordChar = \’*\’;
}
private void button1_Click(object sender, EventArgs e)
{
//string Email = textBox3.Text;
// string Password = textBox4.Text;
//string ConPassword = textBox5.Text;
if (textBox5.Text !=textBox4.Text)
{
MessageBox.Show(“confirm password is not matching with passsword”);
textBox5.Focus();
return;
}
if (string.IsNullOrEmpty(textBox4.Text))
{
MessageBox.Show(textBox4, “Password required!”);
}
else if (!Regex.IsMatch(textBox4.Text, @”((?!.* )(?=.*\\d).{8,15})”))
{
MessageBox.Show(textBox4, “Password invalid! Password cannot contain white spaces ,must contain at least one numeric and be at least 8 characters length, max 15″);
return;
}
else
{
errorProvider2.Dispose();
}
if(textBox1.Text==”” || textBox2.Text==””)
{
MessageBox.Show(“enter first name and last name”);
}
else{
SqlConnection con = new SqlConnection(“Data Source=VISARG-PC\\\\SQLEXPRESS;Initial Catalog=caller-id;Integrated Security=True”);
con.Open();
SqlCommand sc = new SqlCommand(“insert into Register values(\'”+textBox1.Text+”\’, \'”+textBox2.Text+”\’,\'”+textBox3.Text+”\’,\'”+textBox4.Text+”\’,\'”+textBox5.Text+”\’)”,con);
sc.ExecuteNonQuery();
MessageBox.Show(“Registered successsfully”);
con.Close();
Form2 f2 = new Form2();
f2.Show();
textBox1.Text =” “;
textBox2.Text =” “;
textBox3.Text=” “;
textBox4.Text =” “;
textBox5.Text =” “;
}
}
private void button2_Click(object sender, EventArgs e)
{
Application.Exit();
}
private void linkLabel1_LinkClicked(object sender, LinkLabelLinkClickedEventArgs e)
{
Form2 f2 = new Form2();
f2.Show();
}
private void textBox3_Validating(object sender, System.ComponentModel.CancelEventArgs e)
{
{
string errorMsg;
if(!ValidEmailAddress(textBox3.Text, out errorMsg))
{
e.Cancel = true;
textBox1.Select(0, textBox3.Text.Length);
// Set the ErrorProvider error with the text to display.
this.errorProvider1.SetError(textBox3, errorMsg);
}
}
}
private void textBox3_Validated(object sender, EventArgs e)
{
errorProvider1.SetError(textBox3, “”);
}
public bool ValidEmailAddress(string emailAddress, out string errorMessage)
{
if (emailAddress.Length == 0)
{
errorMessage = “e-mail address is required.”;
return false;
}
if(emailAddress.IndexOf(“@”) > -1)
{
if(emailAddress.IndexOf(“.”, emailAddress.IndexOf(“@”) ) > emailAddress.IndexOf(“@”) )
{
errorMessage = “”;
return true;
}
}
errorMessage = “e-mail address must be valid e-mail address format.\\n” +
“For example \’someone@example.com\’ “;
return false;
}
private void textBox4_Validating(object sender, CancelEventArgs e)
{
if (string.IsNullOrEmpty(textBox4.Text))
{
errorProvider2.SetError(textBox4, “Password required!”);
}
else if (!Regex.IsMatch(textBox4.Text, @”((?!.* )(?=.*\\d).{8,15})”))
{
errorProvider2.SetError(textBox4, “Password invalid! Password cannot contain white spaces ,must contain at least one numeric and be at least 8 characters length, max 15″);
}
else
{
errorProvider2.Dispose();
}
}
private void textBox1_KeyPress(object sender, KeyPressEventArgs e)
{
if ((e.KeyChar >= 65 && e.KeyChar <= 90) || (e.KeyChar >= 97 && e.KeyChar <= 122) || e.KeyChar == 32 || e.KeyChar == 8)
{
e.Handled = false;
}
else if(textBox1.Text==””)
{
MessageBox.Show(“Invalid Input Please enter character only”);
e.Handled = true;
}
}
private void textBox2_KeyPress(object sender, KeyPressEventArgs e)
{
if ((e.KeyChar >= 65 && e.KeyChar <= 90) || (e.KeyChar >= 97 && e.KeyChar <= 122) || e.KeyChar == 32 || e.KeyChar == 8)
{
e.Handled = false;
}
else if (textBox2.Text==””)
{
MessageBox.Show(“Invalid Input Please enter character only”);
e.Handled = true;
}
}
}
}
Login.cs:
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.SqlClient;
namespace WindowsFormsApplication6
{
public partial class Form2 : Form
{
public Form2()
{
InitializeComponent();
}
private void Form2_Load(object sender, EventArgs e)
{
textBox2.PasswordChar = \’*\’;
}
private void button2_Click(object sender, EventArgs e)
{
Application.Exit();
}
private void button1_Click(object sender, EventArgs e)
{
SqlConnection con = new SqlConnection(“Data Source=VISARG-PC\\\\SQLEXPRESS;Initial Catalog=caller-id;Integrated Security=True”);
con.Open();
SqlDataAdapter da = new SqlDataAdapter(“select * from Register where Email=\'” + textBox1.Text + “\’ and Password=\'” + textBox2.Text + “\’ “, con);
DataTable dt = new DataTable();
da.Fill(dt);
if(dt.Rows.Count>0)
{
//MessageBox.Show(“login succesfully”);
Form3 f3 = new Form3();
f3.Show();
}
else
{
MessageBox.Show(“invalid username or password”);
}
con.Close();
}
}
}
 
6. Testing
6.1 Testing Strategy:
A strategy for software testing integrates the design of software test cases into a well-planned series of steps that result in successful development of the software. The strategy incorporates test planning, test case design and the result collection and evaluation.
Testing begins “in the small” and progresses “to the large”. Initially individual components are tested using white box and black box techniques. After the individual components have been tested and added to the system, integration testing takes place. Once the full software product is completed, system testing is performed. The best specification document should be reviewed like all other software engineering work products.
Strategic Approach to Software Testing:
 Testing begins at the component level and works outward toward the integration of the entire computer-based system.
 Testing is conducted by the developer of the software and by an independent test group.
 Different testing techniques are appropriate at the different points in time.
 Testing and debugging are different activities, but debugging must be accommodated in any testing strategy.
 Software testing is a part of broader group activities called verification and validation that are involved in software quality assurance.
Levels of Testing in Software:
1) Unit Testing:
 Black box and white box testing.
 Module interfaces are tested for proper information flow.
 Local data are examined to ensure that integrity is maintained.
 Boundary conditions are tested.
 Basis path testing should be used.
 All error handling paths are should be tested.
 Drivers and/or stubs need to be developed to test incomplete software.
2) Integration Testing:
Top-down integration testing:
 Main control module used as a test driver and stubs are substitutes for components directly subordinate to it.
 Subordinate stubs are replaced one at a time with real components.
 
Bottom-up integration testing:
 Low level components are combined in clusters that performed a specific software function.
 A driver is written to coordinate test case input and output.
 The cluster is tested.
 Drivers are removed and clusters are combined moving upward in the program structure.
3) Regression Testing:
 Representative sample of existing test cases is used to exercise all software functions.
 Additional test cases focusing software functions likely to be affected by the change.
 Tests cases that focus on the changed software components.
4) Smoke Testing:
 Software components already translated into code are integrated into a build.
 A series of tests designed to expose errors that will keep the build from performing its functions are created.
 The build is integrated with the order builds and the entire product is smoke tested daily (either top-down or bottom-up integration may be used).
 
6.2 Test Cases
1) Admin:
SR NO. LABEL DESCRIPTION EXPECTED RESULT ACTUAL RESULT
1 Email id Email id is added & it is in particular format If particular symbol is not added then it will not take this value Test is successfully completed
2 Password When password is correct after the system is logged on Message will generated “enter valid password” Test is successfully completed
3 Admin Management Admin can change username and password Admin’s username & password changed Test is successfully completed
4 Requirement Management Admin can add or remove the requirements of users Requirements are added or removed in the particular table Test is successfully completed
5 Viewing Details Admin can view all the details of the customer through contact number If number is not registered then admin cannot view the details of the customer Test is successfully completed
6 User Management Providing user name, Email id Searching username Test is successfully completed
Table 6.2.1: Test case for Admin
 
2) Customer:
SR NO. LABEL DESCRIPTION EXPECTED RESULT ACTUAL RESULT
1 Profile Show and update his/her profile On updating profile, he/she can change his/her profile Test is successfully completed
2 Sign Up He/She can sign up by adding proper formatted data in registration form On submitted, without any error registration will be done. On error, field must be filled with proper formatted data by user Test is successfully completed
3 Requirement specification Specify requirements with required contact number, name, address etc Specified requirements can be viewed successfully Test is successfully completed
4 Login He/She can login with their own username and password after registration On submitted, without any error login will be done. On error, field must be filled with proper formatted data by user Test is successfully completed
Table 6.2.2: Test Cases for Customer
 
7 Limitations and Future Enhancement
7.1 Limitations:
 Lot of mundane and repetitive work.
 Inefficiency and estimation of cost.
 Maintenance of records for future references.
 Separate hardware device was not introduced in computer caller-id system.
7.2 Future Enhancement:
 This system allows the call logs on computer for specific organization.
 Discard unwanted calls.
 To identify who wants to communicate.
 Unlimited access to the organization’s largest collection of names and numbers.
 
8 Conclusion And Discussion
8.1 Self Analysis Of Project Viabilities:
When studied about current system, some draw backs are to be found;
 Inefficiency and estimation of cost.
 Maintenance of records for future references.
 Loss of connection may be occurred.
8.2 Problem Encountered And Possible Solutions:
Problems
Possible Solutions
Internet connection loss
Provide Intranet connection.
High power consumption
Low power consumption
Leak of data
Protection of data.
8.3 Summary of Project:
For this project, I have completed the whole analysis phase which includes Project Report, All GTU PMMS Activities (PPR, PSAR, PLAGIARISM, CANVAS).
 
9 References:
 http://csharp.net-tutorials.com/.
 http://www.asp.net/
 http://www.csharp-station.com/
 http://www.techonthenet.com/sql_server/
 www.mssqltips.com/sql-server-tutorials/
 
Appendix
 Design Engineering Canvas