Synopsis

The name of project is Testing Integration Help Desk Management System. Help Desk Management System is a scalable Web-based application designed for employees in organization to communication. Help Desk Management System is designed to provide the tool to everyone in the organization to book a ticket for any IT service required. Ticket is a logical construct to claim any IT service. Help Desk Management System serves as an important tool for the employees to book tickets to get timely services. Ticket is a task requiring documentation, follow up and proof of execution in an organization. Help Desk Management System is a tool that helps keep respective co-coordinator to track the progress of the ticket. Help Desk Management System follows all the business rules of the required system. It is a very sophisticated, reliable, scalable, robust, durable and highly efficient approach which tackles almost all the business details and complexities. It consists of user friendly GUI for data entry, reports for ticket. Most enhancing feature is that any novice person can handle it easily and comfortably. Help Desk Management System provides different reports to different authorities to track each and every aspects of their work. Hence allows taking useful and quick decisions which helps an organization to make fast communication.

Synopsis
Product Overview and Summary:
2.1 Purpose:
The Help Desk Management System is intended to communicate (i.e. Organizational internal communication). It also keeps the track of ticket.

2.2 Scope:
Describes the scope of this requirements definition effort. Introduces the requirements elicitation team, including employee, system engineers, and coordinators. This section also details any constraints that were placed upon the requirements elicitation process, such as schedules, costs, or the software engineering environment used to develop requirements. Definitions, Acronyms and Abbreviations: All the definitions, acronyms and abbreviations are mentioned in the Appendix A.

2.3 References:
http://google.com.

http://cooltext.com.

2.4 Overview:
Section 3.0, the Overall Description, provides an overview of the components and the relationship between them. Section 4.0 provides the Specific Requirements of the product. In the subsection (4.1) and (4.2) of which the various functional requirements and various interface respectively are discussed. Section 5.0 describes Supporting information, Appendices, and gives some implementation details.

Synopsis
1. Overall Description:
3.1 Product Perspective:
The Product is a web-based product, which will be used by multiple users i.e. employee, coordinator, engineer and global administrator. Administrator will be provided with the Interface, in which he has can create roles, add department and add locations of that department. Employee who wants service can book a ticket. These tickets of all users are displayed on respective departments coordinator. Coordinator assigns these tickets to engineers of that department. When engineers done with their work then they close the ticket. Then coordinator can close ticket. Employee can see problem solved or not. As far as the future perspectives are concerned, the scope of improvement will be, employee can see progress of service or add extra roles for manager.

3.2 Product Functions and user Characteristics:

This product is mainly designed to keep the information about the employees problems and service provided to them. It is also be used for maintaining performance of engineers. There will be number of employees, number of departments having one coordinator and one team of engineers. Each employee, coordinator, engineer, administrator will be provided a login id and password to interact with the system. Initially administrator will enter the information about the departments and its locations. He can enter the information GUI given to him. And he will be responsible person to generate the default login id and password for Employee, engineers and coordinator. Coordinator of respective department can see the tickets uploaded by employees. His job is to assign ticket to the engineers in his department and keep the track of consistency. When he comes to know that work has been done by his engineer he closes ticket. These effects are reflected in employees account. Engineer when done with their work then they close the ticket. These effects are reflected in coordinators account. Then coordinator can take respective action.

3.3 General Constraints:

The Help Desk Management System should run on all Internet Browser and all processors which supports the Internet Browser.

Synopsis
4 Requirements:
Armed with the importance of the computerization, It is also necessary to know the hardware and Software available in the market can be easily adopted for the library and information services to cater of the user depending upon the nature and scope of services

4.1 Hardware requirement:

Computer Hard disk RAM : - P.C. compatible Pentium IV. : - 40 GB/10GB. : - 1 GB / 128 MB.

Visual Display: - Color with EGA/VGA/SVGA card. Keyboard Mouse Network : - Standard 101 keys. : - Logitech. : - Intranet/Extranet/Internet.

4.2 Software requirement :Operating System Application Server Database Server :::::::WinXP/WinVista/Linux. Windows 2000/2003 Server. MS-SQL Server 2000/2005. IIS 5.0/6.0. IE6 with SP1, IE7. 2.0 with Ajax Toolkit 2.0. MS-Office 2000/2003/2007 with OWC11.

Web Server Web Browser .NET Framework MS-Office

Synopsis