CALL LOG SYSTEM

1

CALL LOG SYSTEM

1. Project Profile

A. Project Title:Call Log System

B. Project Definition:Call Log System is an increasingly important of to all customer as the use of all electronics company like (Dell,Lenovo,Asus etc..) becomes a popular method of centralizing information services and problem solving, streamlining order taking and providing valuable customer support

C. Organization: bit Infotech Ltd.

D. Front End Tool:Microsoft Visual Studio 2010

E. Back End Tool:Microsoft SQL Server 2008

F. Technology:ASP.Net 4.0 with C#

G. Documentation Tools:Microsoft Word, Microsoft Visio

2

CALL LOG SYSTEM

2. Company Profile

3

CALL LOG SYSTEM

BIT InfoTech is ISO 9001-2008 certified Company. , Bit Infotech Ltd establish in 2007. The combined record of its past and present faculty and student along with the alumni spreads across the world is awe-inspiring. With path-breaking innovations in both curriculum and research, the institute is rapidly advancing and adopting, thrust maintaining its legendary reputation.

Our Organisation has acquired a prominent status by providing quality services in different areas like Website Development, Desktop Application And Android Application Development, windows application Our Organisation has been persistently attaining ‘excellence’ with an ultimate objective of providing the Clients an opportunity to become ‘productive consumers and perfect individuals’.

The Management is confident that in this new Endeavour, it can count on the determination, strength, loyalty and commitment to our ‘mission and guiding philosophy’ adopted for the cause of education.

I assume that by joining BITInfotech Ltd all the young aspirants of Development will be able to witness and experience the difference. It will certainly help them to become successful Professional Developer, Engineers & Managers in future.

Preparing young generation to effectively face the challenge of tomorrow is our motto.

4

CALL LOG SYSTEM

3. Project Planning

5

CALL LOG SYSTEM

3.1Project Definition:

A call Log System is a centralized office used for the purpose of receiving and transmitting a large data of request by the request from. A call Log System is operated by a company to administer incoming product support or information inquiresany type of queries (Hardware & Software) from customer.

1. Support the queries of customer (Company,Regular Customer,Small organization).

2. It can maintain all the customer details of database inventory.

3. By the system can create a fake queries then call log system can remove automatically the queries.

4. Save the time to going the service station in customer can create a queriesin the application form.

5. Maintain the call log date and time and which type of customer.

6. Maintain the call status and status should be(Running, Pending,and Solving).

7. Customer can create a queries then engineer are also there in customer address.

3.2

6

CALL LOG SYSTEM

Existing System:

The existing system is a manual system. Here the employees needs to save the information in the form of excel sheets or Disk Drives.

There is no sharing is possible if the data is in the form of paper or Disk drives.

The manual system gives us very less security for saving data; some data may be lost due to mismanagement.

It’s a limited system and fewer users friendly.

Searching of particular information is very critical it takes lot of time.

It is very critical to maintain manually call records of customers, because call centre receives huge no of calls per a day.

It is a tedious job to maintain different customers are asking different service details, normally solve these queries are not possible. Automated system is needed.

Every employee having different rosters, different shift timings, manually handle these roster is tough work.

Search an employee roster in call Log System is a tedious job.

3.3

7

CALL LOG SYSTEM

Problem areas and need for new system:

The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach.

User Friendliness is provided in the application with various controls provided by system Rich User Interface.

The system makes the overall project management much easier and flexible.

It can be accessed over the Internet.

The user information can be stored in centralized database which can be maintained by the system.

This can give the good security for user information because data is not in client machine.

Authentication is provided for this application only registered Users can access.

There is no risk of data management at any level while the project development is under process.

The automated system will provide to the customers for reliable services.

The speed and accuracy of this system will improve more and more.

3.4

8

CALL LOG SYSTEM

New System (Project initiation):

1. Reliability:-

The Project Perform some automated system will provide to the customers for reliable services. It’s provide the customer to easily understand the all GUI Form.

2. Feasibility:-

The Project maintains is a very easy to modification in all customer details. And call log details date and time and which type of customer records are maintain.

3. Online Processing:-

The Online Processing of the project is very simple following the existing (link: http::\www.vhd.com). Manual method without changes and suitable validation is provide for the all form and easy to access of the user.

4. Security:-

Security measures are taken to our mishandling of database password(...) restrictions are provided to enter into a database. A correct password only will access to the database. Throw a security we can maintain the data of customer. We can regular back in our database.

3.5

9

CALL LOG SYSTEM

Scope of the System:

TO provide user-friendly environment in our WEB-Application.

Time Saving To All Type of Customer.

To Provide Engineer and he/she has provide the Perfect Queries solution in our customer.

Our applications are maintain to all type of customer details

Easily manage the all type of customer and easily maintain his queries.

Centralise the all customer records and his queries.

Faster access the queries and customer records.

Our Application can provide the quality of service in our customer.

Provide the high level securities such as (Md5, ASCII) that caninigrate in our system.

3.6 Feasibility Study:

10

CALL LOG SYSTEM

Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility studyportion of thepreliminary investigation:

Technical Feasibility Operational Feasibility Economical Feasibility

TECHNICAL FEASIBILITY:

The technical issue usually raised during the feasibility stage of the investigation includes the following:

Does the necessary technology exist to do what is suggested? Do the proposed equipments have the technical capacity to hold the

data required to use the new system? Will the proposed system provide adequate response to inquiries,

regardless of the number or location of users? Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of access

and data security?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current system developed is technically feasible. It is a web based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The database’s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.

OPERATIONAL FEASIBILITY:

11

CALL LOG SYSTEM

Proposed projects are beneficial only if they can be turned out into information system. That will meet the organization’s operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -

Is there sufficient support for the management from the users? Will the system be used and work properly if it is being developed and

implemented? Will there be any resistance from the user that will undermine the

possible application benefits?

This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.

ECONOMICAL FEASIBILITY:

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs.

The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at NIC, There is nominal expenditure and economical feasibility for certain.

3.7 Development Tools:

12

CALL LOG SYSTEM

Hardware Requirements:

I3 Processor 2GB RAM 500GB Hard Disk

Software Requirements:

Front End Tool: Microsoft Visual Studio 2010 Back End Tool: Microsoft SQL Server 2008 Technology: ASP.Net 4.0 with C# Documentation Tools: Microsoft Word, Microsoft Visio

13

CALL LOG SYSTEM

4. System Analysis

14

CALL LOG SYSTEM

4.1System Flow Diagram:

4.2System Features (Detailed Description of modules):

15

CALL LOG SYSTEM

The system after careful analysis has been identified to be presented with the following modules:

1. Admin

2. Company

3. Small Organization

4. Regular Customer

5. Engineers

Admin Module:

Admin is the chief of the Call Log System. He can have all the privileges to do anything in this system. Admin can register new Company Details, small organization details, regular customer Details, departments into the system. Admin can keep track team Engineer and their performance. For every call receive the admin taking feedback report. New services are introduced by the admin into the call Log system. Call activity done by administrator. For every call the admin capture the information...,

Company Module:

Company module can show all details of his id. Company can add the call log. Company can show the call details. Company can check the call status. Company can communicate to admin regarding his call status.

Small Organization Module:

Small organization module can show all details of his id. Small organization can add the call log. Small organization can show the call details. Small organization can check the call status. Small organization can communicate to admin regarding his call status.

Regular Customer Module:

16

CALL LOG SYSTEM

Regular module can show all details of his id. Regular can add the call log. Regular can show the call details. Regular can check the call status. Regular can communicate to admin regarding his call status.

Engineers Module:

Engineer module can show all details of his id. Engineer can show the task records and his owner task. Engineer can solve the task then he/she has updated the task reports. Engineer can. Show all compliant and which type of complaint.Engineer can always report to admin. Engineer can send the customer problem regarding solution to customer id

4.3Context Level Diagram:

17

CALL LOG SYSTEM

4.41 st Level DFD:

18

CALL LOG SYSTEM

19

CALL LOG SYSTEM

20

CALL LOG SYSTEM

4.52 nd Level DFD:

Process 1: Login Details

21

CALL LOG SYSTEM

2 nd Level DFD: Process 2: Make Complaint Details

22

CALL LOG SYSTEM

2 nd Level DFD: Process 3: Provide Services Details

2 nd Level DFD:

23

CALL LOG SYSTEM

Process 4: Payment Details

4.6

24

CALL LOG SYSTEM

Entity-Relationship Diagram (ERD) :

S_type

S_name

S_close_date

C_id

S_open_date

S_id

Services

Cus_name

PaymentamountDate

P_id

Eng_SpecialityEng_name

Eng_id

TypeEng_id

Cus_id

Problem_des

comp_id

Utype

Phone

Email

Country

City

Name

Address

State

Cus_id 1

1

Make

1

M

M

M

1

1

1

1

Engineer

Payment

Assign

ProvideServices

AdminCheckComplain

Registration

Customer(Company,Small

Organization,Regular)

1

1

4.725

CALL LOG SYSTEM

Data Dictionary:

Registration:-

Description:-

All user information is stored in this table

Field Data type Size Constraint DescriptionCus_id Int (10) Primary key

Auto IncrementThis field contain auto generate Unique ID

Name Varchar (30) Not Null This field contain Name

Address Varchar (40) Not Null This field contain Address

City Varchar (10) Not Null This field contain CityState Varchar (10) Not Null This field contain

StateCountry Varchar (10) Not Null This field contain

CountryPhone Varchar (11) Not Null This field contain

PhoneEmail Varchar (20) Not Null This field contain

EmailUtype Varchar (30) Not Null This field contain

User type

26

CALL LOG SYSTEM

Call_Master:-

Description:-

All customer call records is stored in this table

Field Datatype Size Constraints DescriptionC_id Int (10) Primary key This field contain auto

generate Unique IDCus_id Int (10) Foreign key This field contain

Customer idCall_Des Varchar (30) Not Null This field contain Call

DescriptionCall_detail Varchar (50) Not Null This field contain Call

detail

Inventory_Master:-

Description:-

All Inventory details are stored in this table

Field Datatype Size Constraints DescriptionH_id Int (10) Primary key This field contain auto

generate Unique IDCus_id Int (10) Foreign key This field contain

Customer idH_name Varchar (20) Not Null This field contain

Hardware namePurches_date Date (10) Not Null This field contain

purches dateWarranty_time Varchar (3) Not Null This field contain

warranty timeShop_details Varchar (30) NotNull This field contain

shop details

27

CALL LOG SYSTEM

Task_Master:-

Description:-

All Engineer task details is stored in this table

Field Datatype Size Constraints DescriptionT_id Int (10) Primary key This field contain

auto generateUnique ID

Eng_id Int (10) Foreign key This field contain Engineer Id

Task_details Varchar (30) Not Null This field contain Task Details

Taskassign_date Date (10) Not Null This field contain Task assign Date

Taskstatus Vrachar (30) Not Null This field contain Taskstatus

Engineer_Master:-

Description:-

All Engineer information is store in this table

Field Datatype Size Constraints DescriptionEng_id Int (10) Primary key This field contain auto

generate Unique IDEng_name Varchar (20) Not Null This field contain

Engineer nameEng_Speciality Varchar (30) Not Null This field contain

Engineer Speciality

28

CALL LOG SYSTEM

Message_Master:-

Description:-

All message are store in this table

Field Datatype Size Constraints DescriptionM_id Int (10) Primary key This field contain auto

generate Unique IDM_message Varchar (100) Not Null This field contain

M_messageM_Des Varchar (100) Not Null This field contain

Message Description

Company_Master:-

Description:-

All company details are stored in this table

Field Datatype Size Constraints DescriptionCom_id Int (10) Primary key This field contain auto

generate Unique IDH_id Int (10) Foreign key This field contain

Hardware IdCom_name Varchar (20) Not Null This field contain

Company name

29

CALL LOG SYSTEM

Service_Master:-

Description:-

All customer service details are stored in this table

Field Datatype Size Constraints DescriptionS_id Int (10) Primary key This field contain auto

generate Unique IDC_id Int (10) Foreign key This field contain Call

IdS_name Varchar (20) Not Null This field contain

Service nameS_type Varchar (20) Not Null This field contain

Service typeS_open_date Date (10) Not Null This field contain

Service opendateS_close_date Date (10) Not Null This field contain

Service close date

Complaint_Master

Description:-

All customer complaint are store in this table

Field Datatype size Constraints Descriptioncomp_id Int (10) Primary key This field contain

auto generate Unique ID

Cus_id Int (10) Foreign key This field contain Customer id

Eng_id Int (10) Foreign key This field contain Engineer id

Type varchar (30) Not Null This field contain complaint Type

Problem_des varchar (50) Not Null This field contain Problem description

30

CALL LOG SYSTEM

Offers_Master

Description:-

All offers are store in this table

Field Datatype size Constraints DescriptionOf_id Int (10) Primary key This field contain

auto generate Unique ID

Of_date Date (10) Not Null This field contain Offers date

To_date Date (10) Not Null This field contain To_date

Of_type varchar (30) Not Null This field contain Offers type

Payment_master

Description:-

All customer payment details store in this table

Field Datatype Size Constraints DescriptionP_id Int (10) Primary key This field contain

auto generate Unique ID

Paymentamount Int (10) Not Null This field contain Payment amount

Cus_name varchar (30) Not Null This field contain Customer name

Date Date (10) Not Null This field contain Date

31

CALL LOG SYSTEM

32