Call Management System A Report Submitted (In partial fulfillment of the award for the degree of)
MCA
Submitted By: ANUPRIYA SINGH 0411624405
(MCA) (Session 2005-2008) School Of Computer Science No. 3, Lodhi Estate,New Delhi-110003 Under the Guidance of Mr. Rajendra Prasad (Senior System Analyst)
National Informatics Centre A-Block, CGO Complex Lodhi Road New Dellhi-110003
1
GOVERNMENT OF INDIA MINISTRY OF COMMUNICATIONS & INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION TECHNOLOGY
National Informatics Centre This is to certify that ANUPRIYA SINGH, ID.N0 10575,a student of MCA from SCHOOL OF COMPUTER SCIENCE, IP UNIVERSITY has done her full-semester project training at TRAINING Division, NIC, New Delhi, from JAN 08 to JUNE 08. The project work entitled “CALL MANAGEMENT SYSTEM” embodies the original work done by her during her above full semester project training period.
Project Guide/HOD
Head, Training Division
2
ACKNOWLEDGEMENT It is a great sense of satisfaction and a matter of privilege to me to work at National Informatics Center, New Delhi. I wish to express my heartiest thanks to Training Division for providing me the opportunity to under go training in the esteemed organization. It is my pleasure to thank Dr. S. C. Gupta, Head Training Division (NIC), to whom I owe a lot for giving me an opportunity to do my training in this organization. My heartfelt thanks to Mr. Rajeev Rathi, Technical Director, who accepted me as a project trainee in his group and helping in the projects with words of encouragement and has shown full confidence in my abilities. The project would not have been a success without the valuable guidance of Mr. Rajendra Prasad, Senior System Analyst, who rendered all sorts of help as and when required.
Anupriya Singh
3
ABSTRACT Project Title: Call Management System Call Management System will provide the smooth technical support in solving the problems of the end users. Earlier, when the problem came up, end user contacts the project leader or the person who has developed the product, but now, end user can lodge their complaints at the centralized call centre & get the solution to their problems through email or telephone. This project is web-based application. The main idea of this project is to record the details of the end-user, their problems, & the action taken by various experts in solving/resolving those problems. The project report consists of two major phases. In the first phase, along with the information regarding the organization, the project assigned to me has been mentioned. Second phase provide an insight into the development process involved. The first chapter gives the information regarding National Informatics Centre (NIC). It also gives brief introduction about the project & its objective. The next chapter is on Requirement Analysis, which is mainly concerned with study of various requirements. It includes DFD, ER Diagram & Database Design. It also includes feasibility study of the system. The next chapter is on System Design, which is concerned with detailed System Specification (DSS). It includes structure chart, interface design, validation checks & use case diagram.
4
The next chapter is on Testing, which consist of various test cases performed in the system. The next chapter is on Platform/Tool used, which describes the various hardware & software requirements of the system. The last chapter is regarding Conclusion about the above-mentioned project. In the end, Appendix is attached which includes Definitions & notations used. Then Reference is attached which includes a list of books and sites used during the system development.
Hardware Interface: Pentium IV Processor, 1 GB RAM, 20 GB HDD
Tools & Technologies used: . Net framework 2.0, Microsoft Sql Server 2000 Professional, Microsoft Windows XP
Keywords: Call Management System, Asp.Net, Sql Server 2000, VB.net, National Informatics Centre, NIC, CMS, etc.
NIC Division: Training Division
Name of Student Trainee: Anupriya Singh
5
ID -10575 Jan,08 – June,08
6
TABLE OF CONTENT (In partial fulfillment of the award for the degree of)..............1 ..............................................................................2 ...................................................................................................................2 National Informatics Centre..................................................................................2 Anupriya Singh.........................................................................................................3
TABLE OF CONTENT..........................................................................7 ..................................................................................................................7 DFD NOTATIONS USED:....................................................................................80 External Entities/Terminator ..................................................................................80 These lie outside of the system being modelled. Terminators represent where the information comes from & where it goes. In designing a system, we have no idea about what these terminators do or how they do it.................................................80 Processes.................................................................................................................80 Modify the inputs in the process of generating the outputs....................................80 Data Stores..............................................................................................................80 Represent a place in the process where data comes to rest. A DFD does not say anything about the relative timing of the processes, so a data store might be a place to accumulate data over a year for the annual accounting process.........................80 Data Flows..............................................................................................................80 Represents how data moves between terminators, processes, & data stores (those that cross the system boundary are known as IO or Input Output Description).....80 Symbols used for DFD:..........................................................................................81 ER Diagram:.......................................................................................................82 Symbols used for ER Diagram:..........................................................................84
Interface Testing / Unit Testing...........................................................89 Performance Testing...........................................................................................91
7
CHAPTER 1 INTRODUCTION
8
1.1 ABOUT THE ORGANIZATION NATIONAL INFORMATICS CENTRE National Informatics Centre (NIC) of the Department of Information Technology is providing network backbone and e-Governance support to Central Government, State Governments, UT Administrations, Districts and other Government bodies. It offers a wide range of ICT services including Nationwide Communication Network for decentralized planning, improvement in Government services and wider transparency of national and local Governments. NIC assists in implementing Information Technology Projects, in close collaboration with Central and State Governments, in the areas of (a) Centrally sponsored schemes and Central sector schemes, (b) State sector and State sponsored projects, and (c) District Administration sponsored projects. NIC endeavours to ensure that the latest technology in all areas of IT is available to its users. NIC Headquarters is based in New Delhi. At NIC Headquarters, a large number of Application Divisions exist which provide total Informatics Support to the Ministries and Departments of the Central Government. NIC computer cells are located in almost all the Ministry Bhawans of the Central Government and Apex Offices including the Prime Minister’s Office, the Rashtrapati Bhawan and the Parliament House. Apart from this, NIC has various Resource Divisions at the Headquarters which specialize into different areas of IT and facilitate the Application Divisions as well as other NIC Centres in providing state-of-the-art services to the Govt.
9
At the State level, NICs State/UTs Units provide informatics support to their respective State Government and at the District level lie the NIC District Informatics Offices. NIC has conceptualised, developed and implemented a very large number of projects for various Central and State Government Ministries, Departments
and
Organisations. Many of these projects are continuing projects being carried out by various divisions of NIC at New Delhi Headquarters and State/District centres throughout the country. Some of the most important note worthy projects, which offer a glimpse of the multifaceted, diverse activities of NIC, touching upon all spheres of e-governance and thereby influencing the lives of millions of citizens of India is given below: •Agricultural Marketing Information Network (AGMARKNET) •Central Passport System •Community Information Centres (CICs) •Computerized Rural Information Systems Project (CRISP) •Court Information System (COURTIS) •Department of Agriculture Network (DACNET) •Examination Results Portal •India Image •Land Records Information System (LRIS) •National Hazardous Waste Information System (NHWIS) •Spatial Data Infrastructure (SDI) •Training •Video Conferencing 10
Website of NIC
http://indiaimage.nic.in/
1.2 INTRODUCTION TO THE PROBLEM NIC undertakes many projects, which are accomplished by Govt. officials from various Ministries/department on relevant & thrust areas of IT. During the project development, implementation and afterwards, if any problem occurs, end user contacts the project leader for technical support. There is no central location where end user of the system can lodge complain and monitor the project’s progress. In order to provide smooth technical support and timely resolve the issues, it is felt that
There should be a centralized call centre, where the end user can lodge their complaints and get the solutions to their problems through e-mail or telephone.
These problems should be handled and managed by the experts who are meant for these purposes.
The progress status of the problem should be properly maintained.
. .
11
1.3 OBJECTIVE To develop a proper call lodging system, for a NIC centralized call centre, where the end user can lodge their complaints and get the solutions to their problems through email or telephone. The intended audiences of this project are the development team, the testing team and the end users of the product.
12
1.4 THE ENVISIONED SYSTEM This System will provide the smooth technical support in solving the problems of the end users. Earlier, when the problem came up, end user contacts the project leader or the person who has developed the product, but now, end user can lodge their complaints at the centralized call centre & get the solution to their problems through email or telephone.
13
1.4.1 Proposed System Features: 1.4.1.1
A centralized database is used to store records. Centralized data storage will help in faster data access & in implementing security measures to secure data stored.
1.4.1.2
Registration of the caller’s information & their problems.
1.4.1.3
Automatic generation of caller’s registration number & complaint number.
1.4.1.4
New, pending & solved problems can be viewed.
1.4.1.5
The list of actions can be viewed by selecting the complaint number.
1.4.1.6
The problem is forwarded to the selected expert through e-mail.
1.4.1.7
The caller’s information & his/her problem can be updated.
1.4.1.8
The status of the problem gets updated depending upon the action taken.
1.4.1.9
Automatic generation of E-mail format that has to be sent to the expert.
1.4.1.10
The caller can easily know the status of their problems through e-mail or telephones.
1.4.1.11
The Centralized call centre will send the status of the caller’s problem to the caller’s email.
1.4.1.12
The email format can be viewed & hard copy can be taken, if necessary.
1.4.1.13
Maintaining the project, expert & project-expert details. 14
1.4.1.14
Creation of new users to access the functionalities & features of the system.
15
1.4.2 Proposed System Module 1.4.2.1
A login module to verify the credentials of users before granting them rights to access or modify data. This will ensure the security of the data.
1.4.2.2
A new call registration module:
1.4.2.2.1
To store the details of the callers & their problems.
1.4.2.2.2
To search the caller’s information based on registration number, mobile number, landline number& email-Id.
1.4.2.3
A call status module to view the progress or status of the problems.
1.4.2.4
An action taken module:
1.4.2.4.1
To view the action taken against the particular problem.
1.4.2.4.2
To update the status of the problem.
1.4.2.4.3
To update the caller’s & their problem information.
1.4.2.5
An expert level module to send the details of the caller & his/her problem to the selected expert through e-mail.
1.4.2.6
A show details module to view the format of the sent e-mail & to take the print out, if required.
1.4.2.7
An expert module to add, modify & delete experts details.
1.4.2.8
A project module to add, modify & delete projects details.
1.4.2.9
A project-expert module to add, modify the project& their experts details.
16
1.4.2.10
A create new user module to authenticate & authorize new users to access the system.
17
1.4.3 System Architecture This system follows the 3 tier architecture 1.4.3.1
Presentation tier: Consisting of Asp. Net & HTML. HTML pages can be used for accepting the data & displaying the final results to the users.Asp.Net can be used to manage application flow depending upon user requests.
1.4.3.2
Business Logic Layer: Consisting of VB.Net. It contains the logic to implement the various operations in managing the application & database connections.
1.4.3.3
Data tier: Consisting of Sql Server 2000 database to store the relevant data.
18
CHAPTER 2 REQUIREMENT ANALYSIS
19
2.1 FEASIBILITY STUDY The aim of a feasibility study is to see whether it is possible to develop a system at a reasonable cost or not and after that a decision is taken whether to proceed or not. Four key considerations are involved in the feasibility analysis:
2.1.1 Technical Feasibility: Technical feasibility centres on the existing computer system (hardware or software etc) and to what extent it can support the proposed addition. This CMS software is technically feasible. The primary technical requirement includes the availability of Windows 2000 or higher version of operating systems installed in the network. SQL Server is also required which was already installed. To develop programs VB.NET 8.0 was required which was also available. Reliability, access power and data security was also available. Thus, through all the ends technical feasibility was met.
2.1.2 Economic Feasibility: Most commonly known as cost benefit analysis, the procedure is to determine the benefits and savings that are expected from the candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system. Otherwise, further justification or alterations in the proposed system will have to be made if it is to have a chance of being approved.
20
This CMS software is economically feasible. As the hardware was installed from quite beginning, the cost on project of hardware is low. Similarly, the software loaded for this project was used for many other applications. The software cost was under budget. As student trainees were developing the application, there were no major personnel costs associated. Moreover, the technical requirements were already available so there was no further expenditure for buying software packages.
2.1.3 Behavioural Feasibility: An estimate should be made of how strong a reaction the user staff is likely to have toward the development of the computerized system. This CMS software is behaviorally feasible. It takes very less time for comparison. Hence it saves time and cost.
2.1.4 Operational Feasibility: Issues to be studied are, is there sufficient support for management and users? Is the current method acceptable to users? Will the proposed system cause any harm? This CMS software is operationally feasible. It is very easy to use the webbased application of extreme. User can navigate through the tool by simply clicking on the menu button. There is a simple flow of data between various screens.
21
This application provides the necessary information to the user such as how to enter the information regarding different operations performed on the database. The application was planned in such a way that no prior knowledge was required to go through the various operations. The user just needed to have the basic knowledge of computers.
22
2.2 DATA FLOW DIAGRAM 2.2.1 Zero Level DFD
Project-Expert info. Entry
Call Entry Operator
Project info. Entry
Caller info. Entry
User Account maintenance
Call Management System
Problem info. Entry
Caller Info. Generated Problem info. Generated
Call status info. Generated
Project-Expert info. Generated
23
Expert info. Entry
Expert Info. Generated
Project Info. Generated
Administrator
2.2.2 One Level DFD
24
2.2.3 Two Level DFD 2.2.3.1
USER ACCOUNT MAINTAINENCE
Display User Account info.
Access user info.
Administrator
Retrieve user info.
User Account Info. Enter / Update / Delete user info.
Validate/ Process User info.
25
Update / Delete user info.
2.2.3.2
LOGIN
Call Entry operator
Enter uid, pwd
Login User Account Info
Enter uid, pwd
Administrator
26
2.2.3.3
Call entry operator
CALLER INFO. MANAGEMENT
Access Caller Info
Display Caller Info.
Retrieve caller info.
Caller details
Enter / Update Caller Info.
Validate / Process Caller Info
27
Update caller info
Caller Details generated
2.2.3.4
Call entry operator
PROBLEM INFO. MANAGEMENT
Access Problem Info
Display Problem Info.
Retrieve problem info.
Problem Details generated
Problem details
Enter problem Info
Validate/ Process Problem Info.
28
2.2.3.5
Administrator
EXPERT INFO. MANAGEMENT
Access Expert Info
Display Expert Info.
Retrieve Expert info.
Expert details Enter / Update / Delete Expert info
2.2.3.6
Validate/ Process Expert info.
2.2.3.7 2.2.3.8 2.2.3.9
29
Update / Delete Expert info.
Expert Details generated
2.2.3.10
Administrator
PROJECT INFO. MANAGEMENT
Access Project info.
Display Project Info.
Retrieve project info.
Project details Enter Project info.
Validate/ Process Project Info.
30
Project details generated
2.2.3.11
PROJECT-EXPERT INFO. MANAGEMENT
Project – Administrator
Access ProjectExpert info.
Enter / update Project-expert info.
Display Project Expert info.
Retrieve project-Expert info.
Expert Details generated
Project-Expert details
Validate/ Process ProjectExpert Info.
31
2.2.3.12
Call Entry Operator
CALL STATUS MANAGEMENT
Access Call Status info
Display Call Status Info.
Retrieve Call Status info.
Call Status Details Generated
Call Status details Update Call Status info.
Validate/ Process Call Status Info.
32
2.2.3.13
Call Entry Operator
ACTION TAKEN MANAGEMENT
Access Action Taken info
Display Action Taken Info.
Action Taken Details Generated Retrieve Action taken info.
Action taken details Update Action Taken info.
Validate/ Process Action Taken Info.
33
2.2.3.14
Call Entry Operator
EXPERT LEVEL MANAGEMENT
Display Expert Level Info.
Sent Email Details Generated Retrieve expert Level info.
Project-Expert details
34
2.3 ER DIAGRAM
35
2.4 DATABASE DESIGN 2.4.1 Caller Detail
Entity Name
Caller_detail This caller_detail table stores all necessary
details of
Entity Description S.No 1 2 3 4 5 6 7 8 9 10
Attribute Registration_no Mobile_no Landline_no Email Name State District Block Address1 Pincode
caller. Type Char Char Char Char Char Char Char Char Char Char
Length 11 11 14 50 50 30 30 30 50 6
36
Key/constraints Primary key Null Null Null Not null Null Null Null Null Null
Description Registration number Caller’s Mobile number Caller’s Landline number Caller’s Email Id Caller’s Name State name District name Block name Caller’s Address Pincode
2.4.2 State Detail Entity Name
State_detail This state_detail table stores the details of state,block &
Entity Description S.No 1 2 3 4
Attribute state_code District_code Block_code Name
district Type Length Char 2 Char 2 Char 4 Char 30
37
Key/constraints Not null Not Null Not Null Not Null
Description Code of state Code of district Code of block Name
2.4.3 Problem Detail
Entity Name
Problem_detail This problem_detail table stores details of caller’s
Entity Description Problem pertaining to the project. S.No Attribute Type Length Key/constraints 1 Call_transaction_id Char 11 Primary key 2 Registration_no Char 11 Not Null 3 Project code Char 7 Not Null 4 Main_category Varchar 25 Not Null 5 Sub_category Varchar 50 Not null 6 Problem_type Varchar 50 Not Null 7 Subject Text Not Null 8 Problem_detail Text Not Null 9 Call_entered_by Char 8 Null 10 Call_entered_time Datetime Not Null 11 Call_status Char 7 Not Null 12 Call_closed_by Char 8 Not Null 13 Attached_file Varchar 50 null
38
Description Complaint number Registration number Project code Main project’s name Sub project’s name Problem type’s name Subject Problem detail Call Operator‘s code Time of call Status of call
2.4.4 Project Detail
Entity Name
Project_detail
Entity Description
This project_detail table stores the details of the project
S.No 1 2 3 4
Type Char Varchar Varchar Varchar
Attribute Project_code Main_project Sub_project Problem_type
Length 7 25 50 50
39
Key/constraints Primary key Not Null Not Null Not Null
Description Code of project Main project’s name Sub project’s name Problem type’s name
2.4.5 Project-Expert Detail
Entity Name
Project_Expert_detail This project_expert_detail table stores the details of
Entity Description S.No 1 2 3 4
Attribute Expert_code Project_code Expert_Level Project_Level
5
Service_Status
6 7 8
Activate_date Deactivate_date Deactivate_remarks
expert corresponding to the project Type Length Key/constraints Char 11 Not Null Char 7 Not Null Char 3 Not Null Char 3 Not Null Not Null/ Char 1 default ‘y’ DateTime DateTime Text
40
Description Code of expert Code of project Level of expert Level of project Expert’s service status
2.4.6 User Detail 2.4.7 Entity Name
User_detail This user_detail table stores all the necessary details of
Entity Description various users. Type Length Char 8 Char 128 Char 11 Char 24
S.No 1 2 3 4
Attribute Login_id Password User_id Role
5
Login_creation_date Datetime
6
Login_closed_date
Datetime
7
Status
Char
Key/constraints Primary key Not Null Not Null Not Null
Description Login Id Password Expert code Role of the user Date of login
Not Null
1
41
created Null Date of login closed Not Null/ default Status of the user value ‘y’
2.4.8 Action Taken Detail 2.4.9 Entity Name
Action_taken_detail This action_taken_detail table stores the actions taken by
Entity Description S.No 1 2 3 4 5 6 7
Attribute Registration_no Complaint_no Project_code Expert_action action_date Expert_code Attached_file
the experts on the caller’s project problem Type Length Key/constraints Description Char 11 Not null Registration number Char 11 Not Null Complaint number Char 7 Not Null Code of project Text Not Null Action taken by expert Datetime Not Null Date of action Char 11 Not Null Code of expert varchar 50 Not Null
42
2.4.10Expert Detail
3.1 Entity Name
Expert_detail
Entity Description
This expert_detail table stores the details of the expert
S.No 1 2 3 4
Attribute Expert_code Name Organization Email
Type Char Char Char Char
Length 11 50 50 50
Key/constraints Primary key Not Null Not Null Not Null
5
LandlineNo
Char
12
Null
Description Code of expert Name of expert Expert’s organization Expert’s Email Id Expert‘s Landline number Expert‘s
6
MobileNo
Char
11
Not Null
7
Address
Char
50
Not Null Not Null /
8
Service_status
Char
1
9 10 11
Service_start_date Datetime Service_end_date Datetime Remarks Text
default ‘y’ Null Null
43
Mobile
number Expert‘s address Expert’s service status
3.2
STRUCTURE CHART
Login Page
Welcome Page
New Call Registration
Add/ Search Caller detail/ Problem detail
View Registration no., Complaint no/ searched caller detail
Expert
Call Status
Closed Call
Add /Modify/ Delete Expert
View/select Call Status
View closed status calls
View Expert Detail
View action details View/ select expert, send mail
View sent mail
44
Project Expert
Create New User
Add /Modify Project
Add/ Modify Project-Expert
Add new user
View Project Detail
View ProjectExpert Detail
Project
3.3
MODULE DESCRIPTION & VALIDITY CHECKS
3.3.1 Application’s First Page
3.3.1.1
Description
This page authorizes the users to access the system based upon their login_id and password provided in the textbox controls. 3.3.1.2
Validity Check
1) Login Id field cannot be blank. 2) Password field cannot be blank.
45
3.3.2 Welcome Page
3.3.2.1
Description
This page displays the welcome message of the application when the user successfully logged in. 3.3.2.2
Validity Check
No validity check applicable.
46
3.3.3 New Call Registration page
3.3.3.1
Description
The call entry operator to register the call made by end user and store their problems pertaining to the projects accesses this page. 3.3.3.2
Validity Check
1) The e-mail field should be in appropriate format. 2) The Mobile No field must contain digits only. 3) The Mobile No. Field must be of length 10 or 11. 4) The Pin code field must contain digits only. 5) The Pin code field must be of length 6. 6) The main Category field cannot be blank. 47
7) The sub category field cannot be blank. 8) The problem Type cannot be blank. 9) The Subject field cannot be blank. 10) The state field cannot be blank. 11) The Name field cannot be blank. 12) The address field cannot be blank. 13) The address cannot contain more than 50 characters.
48
3.3.4 Call Status Page
3.3.4.1
Description
This page displays the status of the problem, registered by end user. Status can be ‘new’, ‘pending’,’closed’& ‘escalated’. ‘New’ means no action has been taken. ‘Pending’ means problem is forwarded to first level expert. ‘Closed’ means problem is closed. ‘Escalated’ means problem is forwarded to next levels of expert. Only Call Operator has privileged to access this page. 3.3.4.2
Validity Check
No validity check applicable.
49
3.3.5 Action Detail Page
3.3.5.1
Description
The call operator to edit the caller or problem details & to change the status of the problem by taking appropriate action against the problem uses this page. 3.3.5.2
Validity Check
1) Call action must be selected.
50
3.3.6 Expert Level Selection Page
3.3.6.1
Description
This page is used by the call operator to select the expert for solving / resolving the problem & to forward the details of the caller & problem to the selected expert. 3.3.6.2
Validity Check
1) Expert must be selected from the grid.
51
3.3.7 Call Sheet Page
3.3.7.1
Description
This page displays the email detail that has been sent to expert by call operator to solve or resolves the problem. This page can be used to take hard copy of sent email.
3.3.7.2
Validity Check
No validity check is applicable.
52
3.3.8 Project Expert Page
3.3.8.1
Description
This page is used to insert / modify the details of the experts who deal with project’s problems corresponding to the project assigned to them. Only administrator has privileged to access this page. 3.3.8.2
Validity Check
1) Main project must be selected. 2) Expert name must be selected.
53
3.3.9 Project Page
3.3.9.1
Description
This page is accessed by the administrator to insert, delete and modify the details of project as desired. 3.3.9.2
Validity Check
1) Main project must be selected or entered. 2) Sub project must be selected or entered. 3) Problem type must be selected or entered. 4) Main project cannot be blank.
54
3.3.10Expert Page
3.3.10.1
Description
The administrator to insert, delete and modify the expert’s details as desired accesses this page 3.3.10.2
Validity Check
1) The name field cannot be blank. 2) The organization field cannot be blank. 3) The e-mail field should be in proper format. 4) The address field cannot be blank. 5) The mobile number field cannot be blank.
55
3.3.11Closed Call Page
3.3.11.1
Description
This page displays the problems with ‘closed’ status only. Call operator has privileged to access this page. 3.3.11.2
Validity Check
No validity check is applicable.
56
3.3.12Create New User Page
3.3.12.1
Description
This page is used to create new users, who will access the system based upon their assigned roles. Only administrator has privileged to access this page. 3.3.12.2
Validity Check
1) Login Id cannot be blank. 2) Password cannot be blank. 3) Confirm password field should match the password field.
57
3.2 USE CASE DIAGRAM
Login
Maintain User Account
Maintain Project Details
Maintain Expert Details
Maintain Project Expert Details
Administrator Maintain Caller Details Maintain Problem Details Maintain Call Status
Select Expert to solve the problem
Call Entry Operator System
Forward Problem to Expert
Takes Printout of Sent Mail
Generates E-mail format
58
4.1TEST PLAN & TEST RESULT 4.1.1 Login page ID
Objective
Steps Enter
To
check
Test data the
The
Login
the address of the
TC a1
Result
functionality of Login specified
-
page
of
website should
page. website. Enter
appear. the
username
&
TC a2 password
Username,
The
Password
should
login be
for successful.
login. Error message Enter TC a3
wrong Username,
‘Check
Password
username’
your
username and password. Enter
Should appear. Error message
wrong
username and Username,
‘Check
correct
username’
your
TC a4 Password
password. Enter correct
Should appear. Error message
username and Username,
‘Check
wrong
password’
your
TC a5 Password
password.
59
should appear.
ID
Objective
Steps
Test data
Enter
Result ‘Please
username and TC a6
password’ Username
leave password
validation
field blank. Enter
should appear. ‘Please
password and TC a7
enter
Password
enter
username’
leave validation username should appear. blank. Enter correct username,
TC a8
Username,
The
welcome
Password
should appear.
password and click
submit
button. Enter username,
The textboxes Username,
TC a9
Password and
should Password
click
cancel
button.
60
reset.
get
4.1.2 New Call Registration page ID
Objective
Steps
Test data
Result
Click the tab To
check
the ‘New
Call
functionality of New Registration’ TC-b1 Call Page.
Registration available at the side
of
The New Call
-
the
Registration page
should
appear.
page. Fill the entries Name, mobile TC-b2
click no, etc.
and
The textboxes and dropdowns should
get
Cancel button. reset. The
details
should
be
inserted
and
Fill the entries Name, mobile automatic TC-b3
and
click no, etc.
Submit button.
registration number
and
complaint number should be generated.
61
ID
Objective
Steps
Test data
Result The
Click the new
-
TC-b4 call button.
fields
should
be
available
for
entering
new
details. Fill one of the Name, mobile The and no,
entries TC-b5
landline corresponding
search no, email.
click button.
record
should
be shown.
4.1.3 Call Status Page ID
Objective
Steps
Test data
Result
Click the tab To TC-c1
check
the ‘Call
Status’
functionality of the available at the Call Status page.
side
of
The Call Status
-
the
screen
should
appear.
page.
ID TC-c2
Objective
Steps
Test data
Select one of
-
the records in
62
Result The
Action
Taken
Detail
page
should
appear
with
the grid. selected record.
4.1.4 Action Taken Details Page ID
Objective
Steps
Test data
Result The Call Status
To
check
the
Page
should
Click the functionality of the TC-d1
-
Closed option Action Taken details
appear & the status of the
on the page. page.
call should get closed. The required Click the Edit fields
TC-d2
should
option on the get enabled to page. edit.
ID
Objective
Steps
Test data
Result The current action
Click the New TC-d3 Action option.
-
field should get enabled desired.
63
as
The expert level page Click
should
the appear,
TC-d4
Forward
with
option selected details &
on the page. the level1 expert’s list. The expert level page Click
should
the appear,
TC-d5
with
Escalated option selected details & on the page. the list of higher level experts. The Call Status Page
should
Click the appear TC-d6
&
the
Abandon option status of the call on the page. should abandoned.
64
get
4.1.5 Expert Level Page ID
Objective
Steps
Test data
Result
If the call is To
check
the forwarded from The level1 expert
functionality
of call status page,
-
TC-e1 the Expert Level click the level1
list
should
get
enabled. page.
option to select the expert. The
selected
Select the expert
expert
name
from the grid.
should
get
TC-e2 displayed. The mail should be sent to expert, Click the send TC-e3
caller
&
Tech
mail button. Support
e-mail
ids. Message
should
Remove Click the send TC-e4
get displayed “No expert
mail button.
email expert Email Id
id. available” The sent e-mail Click the print TC-e5
details should be button viewed.
65
ID
Objective
Steps
Test data
Result The
Click the print TC-e6 button.
-
call
page
sheet should
appear. If the call is escalated
from The level2 expert
call status page, TC-e7
list
should
get
click the level2 enabled. option to select the expert.
4.1.6 Expert Page ID
Objective
Steps
Test data
Result
Click the expert To
check
the tab available at
TC-f1
functionality
of the side of the
-
The expert page should appear.
the Expert page.
TC-f2
page. Click the Edit
The
button
fields should get
on
the
form.
ID TC-f3
Objective
required
enabled to edit.
Steps
Test data
Click the delete
-
button
on
66
the
Result The
selected
expert should get
TC-f4
form. Click the new
deleted. A form
button
appear to insert
on
the
form.
new expert details. Validations should
Leave
‘Name’ appear
TC-f5
should
‘Name
field blank while field
cannot
be
inserting. blank’. Validations should Leave appear ‘Organization’ TC-f6
‘Organization field blank while field
cannot
be
inserting. blank’. Validations should Leave ‘Address’ appear TC-f7
‘Address
field blank while field
cannot
be
inserting. blank’. Validations should Leave ‘Mobile’ appear TC-f8
‘Mobile
field blank while field
cannot
be
inserting. blank’.
ID
Objective
Steps
Test data
Result Error
message
Enter ‘Email ID’ TC-f9
field in wrong
-
‘Enter
correct
email id’ should
format. TC-f10
Leave ‘Email Id’ 67
appear. An Expert detail
field
blank
& should
get
rest fields filled inserted. while inserting.
4.1.7 Closed Call Page ID
Objective To
TC-g1
check
functionality
Steps
Result
the Click the closed of call tab available
the Closed Call at the side of the page.
Test data
-
Closed Call page should appear.
page. Click the closed All the calls with call tab available
TC-g2
closed
status
at the side of the should appear. page.
68
4.1.8 Project Page ID
Objective
Steps
Test data
Result
Click the project To
check
TC-h1 functionality
the tab available at of the side of the
-
Project
page
should appear.
the Project page. page. Click
insert
button
Validation should
without
appear
‘main
TC-h2 selecting
TC-h3
any
project cannot be
field. Click the main
blank’. Validation should
project
appear
dropdown
and
project must be
don’t select any
selected
option. Click the
entered’. Validation should
sub
project TC-h4
‘Main
or
appear
dropdown
&
‘Sub
project must be
don’t select any
selected
or
option. Click the Cancel
entered’. All the
button.
should be reset.
fields
TC-h5
ID TC-h6
Objective
Steps Click Problem
the type
69
Test data
Result
-
Validation should appear
‘Problem
dropdown
&
Type
must
be
don’t select any
selected
option. Click the
entered’. The grid should be
edit
or
TC-h7 button. Click
displayed. The required the
edit fields should get
TC-h8
button
in
the enabled
to
be
grid. Click the cancel
edited The fields should
button in the grid
get read only.
TC-h9
4.1.9 Project-Expert Page ID
Objective
Steps Click
To
check
Test data the
the project-expert
functionality
of
TC-i1
tab available at the
Result
Project-
The
-
the side of the
project-
expert page should appear.
Expert page. page.
ID
Objective
Steps
Test data
Result The fields should
Click the refresh TC-i2 button.
-
get cleared.
70
refreshed/
Click the submit
Validation should
button
appear
without
‘Expert
TC-i3 selecting ‘Expert
name
name’ field.
selected’. The required grid
Click
the
must
be
edit
TC-i4
should
be
button. Click the submit
displayed. Validation should
button
appear
without
‘Main
TC-i5
TC-i6
selecting ‘Main
Project must be
Project’ field. Click the edit
selected’. The field should
button
get enabled to be
in
the
grid.
edited.
71
4.1.10 Create New User Page ID
Objective To
check
Steps
Test data
Result
the Click the Create The Create New
functionality
of New User tab
-
TC-j1 the Create New available at the
User page should appear.
User page.
side of the page. Click the Cancel
The field should
TC-j2 button.
get reset. Validations should appear: ‘Login Id
Do not fill any cannot be blank’ TC-j3
entry
&
click &
submit button. ‘Password cannot be blank’. Do not fill Login name
field
TC-j4 click
Password,
Validation should
Confirm
appear: ‘Login Id
Password
cannot be blank’.
&
submit
button. Do not
fill
Validation should Login name,
Password field & TC-j5
appear: Confirm
click
submit
‘Password cannot Password
button.
ID TC-j6
Objective
be blank’.
Steps Do
not
Test data fill Login
Confirm
name, Validation should
password
72
Result
appear: ‘Confirm
Password
field, password
field
& fill password should match the field
&
click password field’.
submit button. Enter different Validation should Confirm
Login
name, appear: ‘Confirm
Password
& Password,
TC-j7
password
field
Password field & Confirm should match the click
submit Password password field’.
button. Login Enter TC-j8
data
name, Message
should
correct &
Password,
display:
Confirm
successfully
Password
created’.
click
submit button.
73
‘login
5.1 PLATFORM / TOOLS USED 5.1.1 Hardware Requirement For Developer:
PC with 500 megahertz or higher processor clock speed recommended
1 GB RAM
10 GB hard disk.
Super VGA (1024X768) or higher-resolution video adapter and monitor.
CD-ROM or DVD drive.
Keyboard and Microsoft Mouse or compatible pointing device.
For application server:
4GB
80 GB hard disk
PC with 500 megahertz or higher processor clock speed
Client Desktop:
500 MHz or above Processor
512 MB or above RAM.
74
5.1.2 Software Requirement For developer:
Visual studio as development tool
SQL SERVER 2000 professional as database.
Any windows-based operating system (2000/XP)
IE 6.0 Browser
For application server:
Windows 2000 server
IIS server 6.0
SQL Server 2000
Client Desktop:
OS: Windows (98, NT, XP, 2000, 2003, Vista)
Browser: Internet Explorer 6.0 or above
75
6.1 CONCLUSION The final product is web application which will provide an interface, which in turn will make problem recording much less difficult & time consuming. It requires little or no time at all to see the status of various problems, as well as make this process more manageable in the long run. The software product “Call Management System” will enhance and simplify the work of the NIC‘s employees and will easily resolve the problems of the end user through proper communication & without delay.
76
6.2 FUTURE SCOPE OF THE PROJECT Till now, this software is used to monitor only 3 projects, but, in future, more projects can be monitored. Addition of other future functionalities, like online registration of the problems can be implemented. Login Ids to the end-users can be provided so that they can see the progress status of their problems.
77
6.3 LIMITATION 6.3.1
Being a web based project requiring a web server to be used to deploy the application, sometimes due to network issues the project might not run properly.
6.3.2
Debugging the web application is a tedious task.
6.3.3
There is no online registration of problem feature which can be highly beneficial for the end-user to describe his/her problem.
6.3.4
It will be very difficult for the person, to tell all the details of himself like address, mobile number etc & the details of the problem on phone.
.
78
APPENDIX DFD: A Data Flow Diagram (DFD) is a graphic representation of the "flow" of data through business functions or processes. More generally, a data flow diagram is used for the visualization of data processing. It illustrates the processes, data stores, and external entities, data flows in a business or other system and the relationships between these things. Physical DFD's represent physical files and transactions, while logical or conceptual DFD's can be used to represent business functions or processes. Data Flow Diagrams (DFDs) are a graphical/representation of systems and systems components. They show the functional relationships of the values computed by a system, including input values, output values, and internal data stores. It's a graph showing the flow of data values from their sources in objects through processes/functions that transform them to their destinations in other objects. Some authors use a DFD to show control information, others might not. A DFD can be seen as a method of organizing data from its raw state.
79
DFD NOTATIONS USED: External Entities/Terminator These lie outside of the system being modelled. Terminators represent where the information comes from & where it goes. In designing a system, we have no idea about what these terminators do or how they do it. Processes Modify the inputs in the process of generating the outputs. Data Stores Represent a place in the process where data comes to rest. A DFD does not say anything about the relative timing of the processes, so a data store might be a place to accumulate data over a year for the annual accounting process. Data Flows Represents how data moves between terminators, processes, & data stores (those that cross the system boundary are known as IO or Input Output Description).
80
Symbols used for DFD:
An Open rectangle is used to represent a Data Store.
The rectangle is used to represent the Data Source / Data Destination within the system.
The arrow is used for showing the Data Flow in the system.
Ovals are used for showing the Process of the system.
81
ER Diagram: Data models are tools used in analysis to describe the data requirements and assumptions in the system from a top-down perspective. It is a major data modeling tool & will help organizing the data in our project into entities & define the relationship between the entities. They also set the stage for the design of databases later on in the SDLC. The Entity-Relationship model is a data model for high-level descriptions of conceptual data models, and it provides a graphical notation for representing such data models in the form of entity-relationship diagrams. Such data models are typically used in the first stage of information-system design; they are used, for example, to describe information needs and/or the type of information that is to be stored in the database during the requirements analysis.
82
Basic elements in ER models: Entities: A data entity is anything real or abstract about which we want to store the data. Entity type falls into five classes: roles, events, location, tangible things or concepts.
Attributes: A data attribute is a characteristic common to all or most instances of a particular entity. An attribute or combination of attributes that uniquely identifies one & only one instance of an entity is called primary key or identifier.
Relationships: Relationship provides the structure needed to draw information from multiple entities. It is a natural association that exists between one or more entities. Cardinality: Cardinality defines the number of occurrences of one entity for a single occurrence of related entity.
83
Symbols used for ER Diagram:
Rectangles are used for showing the Entities in the database design.
Ovals are used to represent the Attributes of a relation or entity.
Rhombus is used for representing the Relationship between entities.
84
UML Diagram: The Unified Modelling Language is a standard language for specifying, visualizing, constructing &documenting the artifacts of software system, as well as for business modelling & other non-software system. The UML design process involves creation of various graphical or text based documents. In UML, these documents are called artifacts & they describe the outputs of a step in the process. The UML design process has two main parts: Analysis-What the problem? Design-How should the problem be solved? The reason for this analysis & design process is to allow the project to be broken down into component parts which provide the following project characteristics: •
Detail is hidden.
•
The system is modular.
•
Components are connected & interact.
•
Layer complexity.
•
Components may be reusable in other products.
•
Variations on a theme.
A use case diagram is “a diagram that shows the relationships among actors & use cases within a system”. Use case diagram are often used to: •
Provide an overview of all parts of the usage requirements for a system or organization in the form of an essential model or a business model.
•
Communicate the scope of a development project.
85
Use case diagram would consist of: Use cases: A use case is a description of a system's behaviour as it responds to a request that originates from outside of that system. The use case technique is used in software and systems engineering to capture the functional requirements of a system. Use cases describe the interaction between a primary actor—the initiator of the interaction—and the system itself, represented as a sequence of simple steps. Actors: Actors are something or someone which exists outside the system under study, and that take part in a sequence of activities in a dialogue with the system, to achieve some goal. They may be end users, other systems, or hardware devices. Each use case is a complete series of events, described from the point of view of the actor. Relationships: There are several types of relationship that may appear on a use case diagram: •
An association between an actor & a use case.
•
An association between two use cases.
•
A generalization between two actors.
•
A generalization between two use cases.
System Boundary: The rectangle around the use cases is called the system boundary box & as the name suggests it indicates the scope of your system – the use case inside the rectangle represent the functionality that you intend to implement.
86
Symbols used for Use Case diagram:
The ovals are used to show use case.
The rectangle is used to show system boundary.
This is used to show an actor.
87
TESTING: In a software project, errors can be injected at any stage during development. Because code is the only product that can be executed frequently & whose actual behavior can be observed, testing is the phase where the remaining errors from all the previous phases must be detected. Testing performs a critical role for quality assurance & for ensuring the reliability of software. During testing, the program to be tested is executed, with a set of test cases, & the output of the program for the test cases is evaluated to determine if the program is performing as expected. Due to this approach, dynamic testing can only ascertain the presence of errors in the program; the exact nature of errors is not usually decided by testing. Testing a large system is a complex activity, so for a project, incremental testing is generally performed, in which components & subsystems of the system are tested separately before integrating them to form the system for system testing. Testing is a procedure to execute a program with the intent of finding errors. Testing is an important part of the software development process, to detect bugs, improve software design and to reduce usability problems. There are a number of test techniques such as the traditional unit, system, integration and acceptance tests, and a large number of software tools which support testing in different ways. Testing flow proceeds from left to right and from top to bottom, user visible elements of the web application design are tested first followed by infrastructure design element.
88
Testing Objectives Testing is a process of executing a program with the intent of finding errors. A good test case is one that has a high probability of finding an as yet undiscovered error. A successful test is one that uncovers an undiscovered error. Testing Principle •
All tests should be traceable to the customer’s requirements.
•
Tests should be planned long before the testing begins.
•
Testing should begin “in the small” & progress towards “the large”.
•
Exhaustive testing is not possible.
Interface Testing / Unit Testing The overall strategy for interface testing is to: Uncover errors related to specific interface mechanisms. For e.g. errors in the proper execution of a menu link or the way the data is entered in the form. Uncover in the way the interface implements the semantics of navigation, web application functionality, or content display. To accomplish this strategy, a number of objectives must be achieved: Interface features are tested to ensure that design rules, aesthetics and related visual content are available for the user without error. Individual interface mechanisms are tested that are equivalent to unit testing. Each interface is tested to ensure that it performs the requisite task. The interface is tested within a variety of environments to ensure that it will be compatible.
89
Navigation Testing The job of this testing is: To ensure that the mechanisms that allow the web application user to travel through the web application are all functional and To validate that each navigation semantic unit can be achieved by the appropriate user category. The first phase of navigation testing actually begins during Interface Testing. Navigation mechanisms are tested to ensure that each performs its intended function. Following navigation mechanisms should be tested: 1) Navigation links: Internal links within the web application, external links to other web application should be tested to ensure that proper content or functionality is reached when the link is chosen. Integration Testing The purpose of unit testing is to determine that each independent module is correctly implemented. This gives little chance to determine that the interface between modules is also correct, and for this reason integration testing must be performed. One specific target of integration testing is the interface: whether parameters match on both sides as to type, permissible ranges, meaning and utilization. The individual modules were aggregated one by one and functional testing was performed. The integrated product was considered as a black box and the output (report) is generated depending upon the data present in the flat files.
90
System Testing Software is to be incorporated with other system components (e.g. new hardware, information), and thus a series of special tests are to be conducted. Many times, software products are designed to run on a variety of hardware configurations. The software should actually be tested on much different hardware set – ups, although the full range of memory, processor, operating system, and peripheral possibilities may be too large for complete testing. There are many types of specifications and we should be aware of those as we perform system testing. During system testing, we should evaluate a number of attributes of the software that are vital to the user. These attributes represent the operational correctness of the product. Some of the attributes tested are: Usable: The product is convenient and easy to use. A naïve user can also compare the flat files by browsing the files from their computer and selecting the corresponding interface. User can also add the new interface and can also make modifications in the existing interface. Secure: Only the authorized user is able to use this tool. Compatible: The product runs correctly using YUI_EXT Library, works correctly in conjunction with existing software. Performance Testing Performance testing is used to uncover performance problems that can result from lack of server-side resources, inappropriate network bandwidth, inadequate database capabilities, faulty or weak operating system capabilities, poorly designed web application functionality, and other hardware and software issues that can lead to degraded client-server performance.
91
REFERENCES 1)
Wrox Professional ASP.NET 2.0
2)
NIC ‘ s website elearning.nic.in (for student trainee)
3)
Software Engineering By K.K. Aggarwal
4)
www.google.co.in
5)
Database Management Systems By Korth
92
