Information Hubs Caller ID System Project

Information Hub (Caller Id System)

A PROJECT REPORT

Submitted By

Mansi Patel (130770107101)

Priya Patel (130770107113)

In fulfillment for the award of the degree of

BACHELOR OF ENGINEERING

Information Technology

SILVER OAK COLLEGE OF ENGINEERING AND TECHNOLOGY

OPP. BHAGWAT VIDYAPITH, NEAR GOTA CROSS ROAD,

AHMEDABAD- 382481.

Candidate’s Declaration

We hereby declare that project report titled “Information Hub (Caller Id System)” submitted towards the completion of project in 7th semester of bachelor of Computer Engineering in Silver Oak College Of Engineering & Technology, Ahmedabad is an authenticate record of our work carried out.

We further declare that to the best of our knowledge the report of I.T. 7th semester.

Candidate’s signature :

First candidates name : Mansi D. Patel

Branch : CE

Enrollment Number : 130770107101

Candidate’s signature :

Second candidates name : Priya S. Patel

Branch : CE

Enrollment Number : 130770107113

Submitted to:

Silver Oak College Of Engineering & Technology, Ahmedabad

Affiliated to:

Gujarat Technological University

CERTIFICATE

The report entitled “Information Hub(Caller-ID System)” prepared by Patel Priya Shaileshbhai for Project Phase-I (Semester – 7) for the partial fulfilment of degree of Bachelor of Engineering , has been carried out under my supervision in Department of Computer Engineering, Silver Oak College Of Engineering and Technology Her present work has been found satisfactory.

Date of Submission:

Prof. Archan Thakkar Prof. Satvik Khara

Project Guide Head of Department

Assistant Prof, CE Dept. Computer Engineering

SOCET SOCET

CERTIFICATE

The report entitled “Information Hub(Caller-ID System)” prepared by Patel Mansi Darshanbhai for Project Phase-I (Semester – 7) for the partial fulfilment of degree of Bachelor of Engineering, has been carried out under my supervision in Department of Computer Engineering, Silver Oak College Of Engineering and Technology Her present work has been found satisfactory.

Date of Submission:

Prof. Archan Thakkar Prof. Satvik Khara

Project Guide Head of Department

Assistant Prof, CE Dept. Computer Engineering

SOCET SOCET

Acknowledgement

No task can be accomplished without proper support, guidance and appraisal. We are highly thankful to many people who contributed either directly or indirectly for this project and provided their invaluable cooperation to us to complete it.

We would like to thank our Head of Department, Prof.Satvik Khara and our faculty members of Computer Engineering for constantly guiding and showing us the correct way to reach towards the desired goal.

Then we would like to thank our internal guide Prof. Archan Thakkar who has helped us out in each every phase of the project and without their support and guidance the project would not have been completed successfully.

The wholehearted help and co-operation by our friends is gratefully acknowledged.

Mansi D.Patel Priya S.Patel

ABSTRACT

This is an Integrated Application for Information Hub (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.

It is a windows based application which is hardware integrated system. It is build by 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.

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. Creating a database and tables.

ii. Configuration of SQL Management Studio.

iii. Implementing it by query firing using WPF.

List Of Tables:

4.5.1

Registration

4.5.2

4.5.3

Customer

4.5.4

Call History

4.5.5

Department

4.5.6

Admin

4.5.7

Contact Number

List of Figures:

1.5.1

Microsoft.net

1.5.2

Visual studio-2010

1.5.3

SQL Server-2008

1.5.4

Caller-ID Device

1.5.5

RS-232 Cable

1.5.6

Ethernet Cable

2.1.1

Waterfall Model

2.2.1

Gantt Chart

2.4.1

AEIOU Summary

2.4.2

Product Devlopment Canvas

2.4.3

Ideation Canvas

4.4.1

Use case diagram

4.4.2

Activity diagram

4.4.3.1

Sequence Diagram for login

4.4.3.2

Sequence Diagram for whole system

4.4.4

Class diagram

5.1.1

Registration Page

5.1.2

5.1.3

Customer Form

5.1.4

Customer Registration

5.1.5

Admin Registration

5.1.6

Admin Login

5.1.7

Displaying Information

5.1.8

Admin deleted record

Index

Chapter-1

Introduction

1.1 Project Summary

1.2

Project Purpose

1.3 Project Scope

1.4 Project Objective

1.5

Technology Review

Chapter-2

SOFTWARE PROJECT MANAGEMENT

2.1

Project Planning

2.1.1

Project Development Approach And Justification

2.1.2

Project Plan

2.2

Project Scheduling

2.3

Risk Management

2.3.1

Risk Identification

2.3.2

Risk Analysis

2.4

Canvas Designing

2.4.1

AEIOU Summary

2.4.2

Product Development Canvas

2.4.3

Ideation Canvas

Chapter-3

System Requirement Study

3.1

User Characteristics

3.2 Hardware And Software Requirements

3.3 Constraints

Chapter-4 SYSTEM ANALYSIS

4.1

Requirements Of New System

4.1.1

User Requirements

4.1.2

System Requirements

4.2

Feasibility Study

4.2.1

Technical Feasibility

4.2.2

Economic Feasibility

4.2.3

Implementation Feasibility

4.3

Requirements Validation

4.4 Function Of the System

4.5 Data Dictionary

Chapter-5

SYSTEM DESIGN

5.1

Input Output Design

Abbreviations

 My Project definition is “Integrated Application for Information Hub(Caller-Id 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.

CHAPTER: 1

INTRODUCTION

Chapter-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 Information Hub (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. Information Hub 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.

1.2 Project Purpose

The aim of this windows application is to get customer’s information regarding their contact number and display all the information. This application can facilitate the job 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

Information hub 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 is 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 information hub, 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.

CHAPTER: 2 SOFTWARE PROJECT MANAGEMENT

CHAPTER -2

SOFTWARE 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.

Fig: 2.1.1 Waterfall Model

Tasks Jul-14 Aug Sept Oct Nov Dec Jan-15 Feb Mar Apr

Requirem

ents

Gathering

System

Analysis

System

Design

Coding

Implemen

tation &

Testing

Learning

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 is written in such a way that maximum functionality is 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 before, 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:

The second step of risk management is risk analysis. 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

Figure: 2.4.1-AEIOU Summary

2.4.2 Product Devlopment Canvas

Figure:-2.4.2-Product Development Canvas

2.4.3 Ideation Canvas:-

Figure:-2.4.3-Ideation Canvas

CHAPTER 3

SYSTEM REQUIREMENT

STUDY

CHAPTER-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

 Admin:

The main work 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 Constraints:

There are many aspects of any design project that must be considered to determine the

feasibility of the application.

 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.

CHAPTER- 4

SYSTEM ANALYSIS

CHAPTER-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 application to be technically feasible.

Application would be implemented using .NET technology which is 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 Economic 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 application 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.

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 requirement represents the same

application that customer really wants or it is showing different. The basic objective of

requirement validation is that the SRS reflects the actual requirements accurately.

The common methods for requirement validation are as follows:

 Requirement Review:

It is review by group of people for finding errors and point out other matters of

concern. It may be formal or informal.

 Prototype:

The requirements will be checked using executable model of the application. Prototype

which is build during analysis, will 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 Function Of the system

4.4.1 Use case Diagram

Customer

Contact Number

Verify the contact

number

New number is

arrived, ask the customer

number

Directly display the

information, if the number is

existing

To get all the

information

Admin

System

Fig:-4.4.1-Use case diagram

4.4.2 Activity diagram

Yes No

Get all the information from customer

Display all the information

The number is already exists

Directly display the information

Contact Number

Contact

number is

new?

Customer

Fig: 4.4.2 Activity diagram

4.4.3 Sequence Diagram:

4.4.3.1 Sequence diagram for login:-

:Customer :System :Admin

Request for login

verify login details verified

Logout

commit

Close connection

Display the home page

Fig: 4.4.3.1 Sequence Diagram for login

4.4.3.2 Sequence diagram for whole system:-

:Customer :System :Admin

Contact Number

Verify the contact number

Verified

Number verified

New Customer

Ask all information to customer

Give all information

Old (Exists) Customer

Directly display all the information

Fig: 4.4.3.2 Sequence Diagram for whole system

4.4.4 Class Diagram:

+Manage the system()

+Add()

+Select()

+Update()

+Select()

+View()

-A_id: char

-A_name: char

Admin

+Select()

+Remove()

-C_id: char

-C_number:int

-C_name: char

-C_age: int

-C_address:char

-C_city: char

Customer

+Add()

+Remove()

-D_ID: int

-D_name: char

-D_no of user:int

Department

+Add()

+Remove()

-H_id: int

-H_name: char

-H_date: int

Call History

Fig: 4.4.4 Class Diagram

4.5 Data Dictionary

4.5.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: 4.5.1 : Registration

4.5.2 Table Name: Login

Primary Key: Log_id

Table: 4.5.2 Login

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.

4.5.3 Table Name: Customer

Primary Key: Contact_Number

Field Name Data Type Size Constraints Description

Customer ID

Integer

Not Null

For Customer

unique

identification

Contact

Number

Numeric

(18,0)

Primary Key

Customer

contact

number

Name

Nvarchar

Not Null

Customer

Name

Age

Numeric

(10,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: 4.5.3 Customer

4.5.4 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: 4.5.4 Call History

4.5.5 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 20 Not Null Name of user

No of emp Int 30 Not Null Number of

user.

Table: 4.5.5: Department

4.5.6 Table Name: Admin

Primary Key: Id

Foreign Key: Log_id

Field Name Data Type Size Constraints Description

Id Int 30 Primary Key Identification

of Admin

Name Varchar 30 Not Null Name of

admin

Log_id Varchar 30 Foreign Key Login id of

Admin

Password Varchar 30 Not Null Password of

Admin

Table :4.5.6: Admin

4.5.7 Table Name: Contact Number

Primary Key: Contact Number

Field Name Data Type Size Constraints Description

Contact_Number Numeric (12,0) Primary Key Contact

number of

customer

Name varchar 20 Not Null Name of

customer

Table :4.5.7 Contact Number

Chapter-5

SYSTEM DESIGN

Chapter-5

System design

5.1 Input Output Design:

Registration page:

Figure 5.1.1: Registration Page

Figure5.1.2: Login Page

Customer details form:

Figure5.1.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.1.4: Customer Registration

Admin Registration

Figure5.1.5: Admin Registration

Admin Login:

Figure5.1.6: Admin Login

Admin can view all the details from contact number only:

Figure5.1.7: Displaying Information

Admin can also delete the registered contact number:

Figure5.1.8: Admin deleted record

Essay: Information Hubs Caller ID System Project

Essay details and download:

Text preview of this essay:

About this essay:

Essay details and download:

Text preview of this essay:

About this essay:

Essay Categories: