INDEX
No. Title Page No.
1) Literature Review Report
1. Abstract 1
2. Keywords 2
3. Tools and Technology 2
a) Front End 2
b) Back End 4
c) Extra Hardware Device 5
d) Platform 6
4. Study of Current Existing System 8
5. Limitations of Existing System 9
6. Usability of the Project 9
7. Innovative Ideas 9
2) Software Requirement Specification
1. Introduction 14
1.1) Purpose 14
1.2) Scope 14
1.3) Definitions, Acronyms, Abbreviations 14
1.4) References 15
1.5) Overview 15
2. Overall Description 15
3. Specific Requirements 16
3.1) Functionality 17
3.2) Usability 17
3.3) Reliability 17
3.4) Performance 18
3.5) Supportability 19
3.6) Design Constraints 19
3.7) On-Line User Documentation and Help 20 System Requirements
3.8) Purchased Components 20
3.9) Interfaces 20 3.9.1) User Interface
3.9.2) Hardware Interface
3.9.3) Software Interface
3.9.4) Communication Interface
3) System Diagrams
1. Class Diagram 21 2. System Activity Diagram 22 3. Use Case Diagram
3.1)Use Case for Admin 23
3.2) Use Case for Whole System 24 4. Sequence Diagram 25
5. Collaboration Diagram 26
4) Data Dictionary
1. Login Table 27
2. Admin Table 27
3. Parameter Table 28
4. Customer Table 29
5. Call Log Table 30
Literature Review Report
1.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.
2. KEYWORDS
1) Caller-ID
2) Identification
3) Integrated
4) CPN(Caller Party Number)
5) CLI(Calling Line Identity)
6) CNAM(Caller Name)
7) Screen POP
3. Tools and Technology
3.1 Front End:
.NET Framework Architecture
Figure 3.1.1: .NET Framework Architecture
• The .NET Framework has two components: the .NET Framework
Class Library and the Common Language Runtime (CLR).
• The .NET Framework Class Library facilitates types (CTS) that are common to all .NET languages.
• The Common Languages Runtime consists of (class loader) that load the IL code of a program into the runtime, which compiles the IL code into native code, and executes and managed the code to enforce security and type safety, and provide thread support.
Technology Used:
This is a windows based application, developed using technology ASP.NET with C#.NET in the front end.
ASP.NET, the latest version of Active Server Pages (ASP), is Microsoft’s technology for building dynamic pages, database-driven Web sites. Active Server Pages is one of the most popular languages for building scalable, interactive Web sites.
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.
C#(pronounced as see sharp) is a multi-paradigm programming language encompassing strong typing, declarative, imperative, functional, generic, object-oriented(class-based) and component-oriented programming disciplines. It was developed by Microsoft within its ASP.NET.
• Easy Programming Model
• Flexible Language Options
• Great Tool Support
• Rich Class Framework
• Compiled execution
• Memory Leak, Deadlock and Crash Protection
• Dynamic update of running application
3.2 Back End:
Microsoft SQL Server 2008
Figure 3.2.1: Microsoft 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.
Features of Microsoft SQL Server 2008:
• Web enabled enterprise database.
• Introduction of built in support for the extensible Mark-up Language, XML.
• Improved distributed query capabilities.
• Replication and administration enhancement.
• High speed in application development and transaction processing.
• English Query tools and full text search features.
• Improved security features.
• Support for file network and encryption.
• Enhances analysis services including data mining support.
• Data Transformations services.
• User defined functions and administration tools like Enterprise Query.
3.3 Extra Hardware 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.
The Caller-ID Device is connected through 2 types of cables:
1) RS-232 Cable:
In telecommunications, RS-232 is a standard for serial communication transmission of data. 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. Nevertheless, RS-232 devices are still used, especially in industrial machines, networking equipment and scientific instruments.
2) Ethernet Cable:
Ethernet cable is a family of computer networking technologies for Local Area Networks (LAN) and Metropolitan Area Networks (MAN). The Ethernet standards comprise several wiring and signaling variants of the OSI Physical Layer in use with Ethernet. As per OSI Model, Ethernet provides service up to and including the Data Link Layer (DLL).
RJ45 connectors are used for Ethernet computer network cables referred as RJ45 connectors.
3.4 Platform:
Microsoft Visual Studio 2010
Figure 3.4.1 : Microsoft 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. Visual Studio 2010 helps individuals and organizations rapidly to create and deliver complete connected, comprehensive and compelling software solutions with breakthrough user experience.
Microsoft Visual Studio supports different programming languages. Built-in languages included VB.NET (Via Visual Basic .NET), C#.NET (Via Visual C#), F# (Via Visual Studio 2010). Support for other languages such as M, Python and Ruby among others is available via language service installed separately. It also supports XML/XSLT, HTML / XHTM , JavaScript and CSS. Java ( and J#) were supported in the past.
Visual Studio Architecture Figure 3.4.2 : Visual Studio Architecture
It delivers the following key advances:
• Rapid Application Development
• Work with Data in Unified and Integrated Way
• Build Application That Run on Multiple Versions of the .NET Framework
• Collaborate Across The Development Cycle
• Integrate Database Features into the Application Lifecycle Management
• Enable Seamless Collaboration Between Developers and Designers
• Experience New Tools and Support for Web Development
• Build Reliable and Scalable Applications for the Microsoft Office System
• Build Stunning Application for Windows Visit.
4.Study of Current Existing System
There are 3 similar systems as follows:
a) 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.
b) 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.
c) 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.
5. 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.
6. 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.
7. Innovative Ideas
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.
Software Requirement Specifications
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, Abbreviations
1.4 References
1.5 Overview
2. Overall Description
3. Specific Requirements
3.1 Functionality
3.2 Usability
3.3 Reliability
3.4 Performance
3.5 Supportability
3.6 Design Constraints
3.7 On-Line User Documentation and Help System Requirements
3.8 Purchased Components
3.9 Interfaces
3.9.1 User Interfaces
3.9.2 Hardware Interfaces
3.9.3 Software Interfaces
3.9.4 Communications Interfaces
1) Introduction:
A Software Requirements Specification (SRS) is a description of a software system to be developed, laying out functional and non-functional requirements. Software requirements specification establishes the basis for an agreement between customers and contractors or suppliers.
The software requirements specification document enlists enough and necessary requirements that are required for the project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed or being developed. This is achieved and refined with detailed and continuous communications with the project team and customer till the completion of the software.
1.1) 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.2) 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.3) Definitions, Acronyms, Abbreviations:
My Project definition is "Integrated Application for Caller-Identification System."
An acronym, 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.
1.4) References:
csharp.net-tutorials.com – C#.Net
w3schools.com, tutorialspoint.com – for SQL server
1.5) Overview:
This document, the Software Requirements Specification (SRS), identifies the software requirements in the form of a task and system object model. The model presented within this document is an implicit statement of the requirements. It exhibits the boundaries and capabilities of the system to be built.
2) Overall Description:
The basic aim of this application is to display customer’s information based on their contact number. It is important to handle as many requests as possible on the first contact, and handle them as efficiently as possible.
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.
Constraints:
• Hardware Limitations:
Interface problem in system found at the stage of integration which leads to hardware limitations problem. Problems of uncoordinated system components also create a barrier thus resulting in issues related to hardware.
• Regulatory Policies:
The software works on the basic fundamentals of 3-tier architecture. Hence necessary software is needed to be installed on the computer. The system is relatively heavy and therefore requires huge bandwidth.
• Reliability Requirements:
User is ensured that the system would be reliable at the time if Power Failure. A reliability program plan also improves and evaluates availability of the system by strategy of focusing on increasing maintainability and testability. It checks whether the system is highly reliable or not and generates updates information in correct order.
Assumptions and Dependencies:
The schedules, estimates and costs are based on many assumptions. If any assumptions are incorrect then specific organization reserves the right to re-estimate both the schedule and the cost for this project.
3) Specific Requirements:
This section of the Software Requirements Specification should contain all the details of the developer need to create. This is the largest and most important part of the SRS.
• Specific requirements should be organized in a logical and readable fashion.
• Each requirement should be stated such that its achievement can be objectively verified by a prescribed method.
• Sources of a requirement should be identified where that is useful in understanding the requirement.
• This should be classify as follows:
3.1) Functionality:
Admin response for feedback.
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.
This Caller-ID on PC is used for specific organizations as well as for Home Purpose too.
This is also one of the Home Purpose features as Bright House Network Gadget.
3.2) Usability:
This subsection specifies the required learning, operate and training time for a normal user and a power user.
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) Reliability:
Requirements for reliability of the system should be specified as below:
Availability: A reliability program plan also improves and evaluates availability of the system by strategy of focusing on increasing maintainability and testability.
MTBF (Mean Time Between Failures): MTBF is a reliability term used to provide amount of failures per million hours for a system or product. This windows based application can take minimum 6 to 7 months for developing the whole application for normal user.
Accuracy: This term is used to describe the system that estimate, measure or predict. The true value of this windows application is customer’s contact number and measured value is customer’s name and all details. Hence the developer must maintain accuracy between these two values.
3.3.1) Reliability Requirements: There are other requirements for reliability of the system. Some are as below:
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.4) Performance:
Performance characteristics of the system are described as below:
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.
3.4.1) Performance Requirements:
Cost Sensitivity: Under all circumstances, the maximum cost payable as submitted by the user will be the maximum cost charged to the user.
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.
3.5.1) Supportability Requirements:
Cost-Effective-To-Maintain: It may covers divers level of documentation, such as system documentation as well as test documentation.
3.6) Design Constraints:
This section represents design decisions that have been mandated and must be adhered to. There are many aspects of any design project that must be considered to determine the feasibility of the system.
3.6.1) Design Constraints Requirements:
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.7) On-line User Documentation and Help System Requirements:
Online help and the guide to install and maintain the system must be sufficient to educate the users on how the use the system without any problems. All documentations will be made in accordance with requirements pertaining to open source software.
3.8) Purchased Components:
In this Caller-ID system, extra Caller-ID device is purchased and used as displaying the information of customer regarding their contact number.
3.9) Interfaces:
This section defines the interfaces that must be supported by the application. It should contain following interfaces:
User Interface:
The term "User Interface" is used in the context of Personal Computer Systems and electronic devices. The system would be developed with user friendly Graphical User Interface (GUI) making it is to understand at the initial phase.
Hardware Interface: This system can be implemented on system platform as:
Microsoft Windows XP/7/8
Dual Core Processor
RAM- 2GB and above
Hard Disk-100GB and above
Software Interface:
Platform: Microsoft .NET
Technology: ASP.NET
Language: C# (C Sharp)
For Development: Microsoft Visual Studio-2010
Back End: Microsoft SQL Server-2008
Communication Interface: Communication is very important between customers and organizations. Physical connection is required as the LAN cabling.
Diagrams
.NET Technology is following Object-Oriented Approach.
Object-Oriented UML Diagrams are as below:
1. Class Diagram
2. System Activity Diagram:
3. Use Case Diagram:
I. Use Case for Admin:
II. Use Case for Whole The System:
4. Sequence Diagram:
5. Collaboration Diagram:
Data Dictionary
1. 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 25 Not Null Password of Customer
2. 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 25 Not Null Password of Admin
3. Table Name: Parameter
Primary Key: ParameterID
Field Name Data Type Size Constraints Description
ParameterID Int 30 Primary Key To identify unique parameter
Name Varchar 30 – Parameter Name
4. 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
5. Table Name: Call Log
Primary Key: Contact Number
Field Name Data Type Size Constraints Description
Id Int 30 Not Null Identity of Call logs
Contact Number Numeric 30 Primary Key Customer Contact Number
Date Numeric 30 Not Null Call Date
Time Numeric 30 Not Null Call Time