SYNOPSIS ON

Live Support and Remote Management System

FOR

Perpetual Infotech
IN PARTIAL FULFILLMENT OF MASTER IN COMPUTER APPLICATION

BY Kothale Prashant Diliprao MCA III SEM - VI 2012-2013

SUBMITTED TO

UNIVERSITY OF PUNE

SINHGAD INSTITUTE OF MANAGEMENT

PUNE-411 041

1|Page

Live Support and Remote Management System Perpetual InfoTech Karvenagar, Pune-52

College Guide: Prof. Deshmukh Anuprita M. Company Guide: Mr. Pankaj Agarwal Sir

Students Name & Signature Date: 23 - 01 -2013 Place: Pune. ___________________ ______ Kothale Prashant Diliprao

SINHGAD INSTITUTE OF MANAGEMENT

2|Page

PUNE-411 041

3|Page

Sr. No 1

Contents
INTRODUCTION A) Company Profile B) Existing System and Need for System C) Scope of Work D) Operating Environment Hardware and Software E) Detail Description of Technology Used

PROPOSED SYSTEM 2.1 Proposed System 2.1.1 Feasibility Study Technical Feasibility Economic Feasibility Operational Feasibility 2.2 Objectives of System 2.3 User Requirements

Tasks for Iterative Phases/Development Cycle

4|Page

1. INTRODUCTION Live Support and Remote Management System is an online Application as complete solution of all scenarios: a single software for support, administration, meetings, home office, and training purposes in real time. The main objectives to allow any computer to control clients system at remote place and give live support to user. A. Company Profile Perpetual InfoTech is a globally renowned software services company that specializes in providing a complete range of Software Services and Web development Solutions. Perpetual InfoTech is one of the software development and professional Web design, Web development Company, We are also specialized in graphic designing and multimedia works. It is Banglore base company. It has branches in Pune, Delhi, and Ahmdabad. We are also providing software solutions to the healthcare industry since 2009. Our aim is to provide unique, innovative Medical Software Services in India & abroad. Perpetual InfoTech offers progressive end-to-end solutions with its combined business domain, technical expertise, profound knowledge and quest for the latest industry and technology trends. Our quality-driven delivery model reinforces Delivery On-time, treating our customers as partners. B. Existing System and Need for System

5|Page

 Existing System: There are many systems available in market to work with this functionalities. The existing system deal with connecting two computers remotely. Need for System: The existing systems in market are dealing with connecting two or more systems remotely but never allow to transfer voice with screen sharing. This system is being used to support or help the clients of a firm from a remote place with voice chat as well as text chat. Along with this, the proposed system consists of following features: Authorization levels: 1. Operat or. 2. Client. Clients Profile. Meeting Scheduler. Online Experts and Colleagues. Textual & Voice Chat.

C. Scope of Work Managing Administrative and Customer account and profiles. Providing live support to the customers of a software product. Providing Expert advice and colleagues chat facility.

6|Page

Allowing voice chat with live support provider. Allow scheduling Meetings.

D. Operating Environment Client required Microsoft based technology hence we have following requirements. Hardware Environment: Processor: 1.6 GHz. RAM: 512MB and Above. Hard Disk: 20 GB or above. Display: 1024x768 Resolution and Above. Network: LAN /WIFI /Broadband network

Software Environment: Operating System: Windows XP and later Versions Front End: JAVA. JSP / Servl et. Eclips e SDK Tool. Back End: MySQL.

E. Detail Description of Technology Used 7|Page 3- Tier Architecture:

Basically the technology is used at various levels of Development Architecture. We are going to use 3-Tier architecture. It contains 3 layers: 1. 2. 3. Application Layer (AL) or
Business Access Layer (BAL) or

Presentation Layer (PL)

Business Logic Layer (BLL)

Data Access Layer (DAL)

1. Application

Layer(AL)

or

Presentation Layer(PL) Presentation layer contains UI part of our application i.e., our .jsp pages or input is taken from the WebPages designed. This layer mainly used for design purpose and

8|Page

for getting or setting the data back and forth. Our Project designs the pages like this and code behind consist of statements manipulate to data retrieve to and and from

database. This entire process related to Business Logic Layer and Data Access Layer. 2. Business Access Layer (BAL) or
Business Logic Layer (BLL)

This layer contains our business logic, calculations related with the data like insert data, retrieve data and validating the data. This acts as an interface between Application layer and Data Access Layer Now we need to create Data Access Layer. This layer will act as only mediator between Business logic layer and data layer. 3. Data Access Layer(DAL) Data Access Layer contains methods to connect with database and to perform insert, update, delete, get data from database based on our input data.

9|Page

2. PROPOSED SYSTEM A. Proposed System

The proposed system is a web base service providing application which help the software firms to give support as a help line to their customers who have purchased a software product form them. The system is also used to manage records and details of product owned by customer e.g. expiry dates of service and information about updates. Firstly customer have to register their software on web site. Then server gives them a login id and password and a client side application through which they can access the services provided by Live Support and Remote Management System. System can provide many services to their customers like live chat with experts and voice chat regarding advices for handling software product purchased by them. The main use of system is to share customers screen and handle there queries form a remote location for solving their problems about the software. The system also allows to schedule future meetings with clients. It allows to give training to its customers. It also shows access remote computer similar to remote desktop for direct handling by experts.

10 | P a g e

11 | P a g e

B.

Feasibility Study a) Technical Feasibility

Technical feasibility determines whether the organization has the technology and skills necessary to carry out the project and how the technology and skills necessary to carry out the project and how should this is obtained. The system can be technically feasible because of the following grounds. All necessary technology exists to develop the system. The existing resources are capable and can hold all the necessary data. The system is too flexible and it can be expanded further. The system can give guarantee of accuracy, ease of use. Reliability and the data security. The system can give instant responses to inquiries. So Live Support and Remote Management System can conclude that the system is technically feasible.

b) Economic Feasibility Economic feasibility determines whether projects goal can be achieved within the resource limits allocated to it. It must determines whether it is worthwhile to process with the project all or whether the benefits obtained from the new system is not worth the costs. After conducting cost benefit analysis, it reveals that the objectives of the proposed system can be achieved 12 | P a g e

within the allocated resources. Proposed system requires no extra manpower, cost almost nil. Also the cash invested to implement the proposed system can be easily recoverable. So the system is economically feasible. c) Operational Feasibility Operational feasibility determines if the proposed system satisfied user objectives and can be fitted into the current system operation. The present system Distribution management system can be justified as operationally feasible based on the following grounds. The methods of processing and presentation are completely accepted to the administrator since they can meet all the requirements. The administrator has been involved in the planning and development of the system. The proposed system will not cause any problem under any circumstances. Is proposed system will certainly satisfy the user objectives and it will also enhance their capability. The proposed system can be best fitted into current operation. Also there is no need to replace any existing staff. Therefore the system is operationally feasible.

13 | P a g e

C.

Objectives of System Authentication and Authorization. A complete solution for all scenarios: a single software for support, administration, meetings, home office, and training purposes in real time. Supports UAC (user account control). View system information of the remote computer. Drag & drop functionality for file transfers in both direction. Schedule and organize meetings. Manage stack of customers requested for service. Reporting about customer requests for service.

D.

User Requirements Basic knowledge of English and Computer. Internet Connection with proper speed and stability. Email account for Contact and Authorization verification.

3. DEVELOPMENT CYCLE 14 | P a g e

As the requirements are wellknown but approach of customer is ever changing, also no prior system is available so iterative SDLC is chosen for development.

15 | P a g e

Note:
(a) The font size standard 12 pts in 1.5 line space and print in black ink only (b) Margins must be Left 2 inches Right 1.5 inches Top 2 inches Bottom 1.5 inches (c) Paper A4 size Bond or normal Paper (e)Two hard-bound copies (with proper file folder) (f) One original and One Xerox Copy. (g) Page Numbering at page bottom left side (f)Duly signed by of stu0dent+

16 | P a g e