The Great Mind Challenge - Project Scenario of IT Service Help Desk

	Name of the Project	IT Service Help Desk
	Objective/ Vision	Developing a web application which is directed to the employee’s in a company. Our goal is to serve as the simulation to them.          This system will be owned by a Company, to serve for their people. This web application will incorporate all requirements needed for the interaction between Project team (who work on the resources allocated) and IT support team (i.e. Network administrator’s, who provide requirements needed for the project people) and get the project team members problems solved, like installations, access to other resources across the network, etc.         This integrates other services like online and ‘any place’ access of this application. It provides a complete concoction of solutions to all IT Service management problems like installations, network resource allocation so on and so forth. It will usher an environment which will not only provide unlimited services to the Project team but also help the Reporting Managers, IT Support team to function effectively and efficiently.
	Users of the System	(ALL the EMPLOYEES in a company separated as) A. Project team members B. IT Support Team
	Functional Requirements (Atleast Eight)	I. The entire employee’s are provided with Unique Login ID,          with    which they can get into the Website. ii. The website guide them to solve their problem through the tutorials (.pdf,.doc) provided. iii. If not the Project member can raise the Ticket (request with unique number) and check the status of the same, while the IT support team can raise the Request and also check and Update or Solve the Ticket raised by the Project Team. iv. They are provided with list of problems usually occurred which can be selected while raising the request. There is also a space provide to describe their problem. v. Depending upon the request type the ticket is even directed to Reporting Manager for Approval status to be updated. vi. The raising, update and closure of the ticket is informed to the members who raised the ticket and the one who Updated/solved the same through the Email along with Time/Date vii. The ticket owner (who raises the request) is provided with Reopen option to again raise the same problem if ticket is closed without proper solution. viii. The Ticket if not solved as per the Service Level Agreement (SLA) the ticket is more prioritized automatically. ix. IT support team is provided with the flexibility of sharing the Tickets. x. Total tickets solved can be listed and viewed.
	Non-functional requirements (Atleast Four)	Secure access of confidential data (user’s details). SSL can be used.  24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension
	Optional features	a.     Secured access over the internet. b.     Intimation of ticket status to the handset c.     Administrator should have a java client end (i.e. java swing end) rather than web end.
	User interface priorities	A. Professional look and feel B. Use of AJAX atleast with all registration forms C. Browser testing and support for IE, NN, Mozila, and Firefox. D. Use of Graphical tool like JASPER to show strategic data to admin E. Reports exportable in .XLS, .PDF or any other desirable format
	Reports	A. Number of Tickets rose. B. Number of Tickets solved. C. Number of Tickets updated.
	Other important issues	A. Website must be highly customizable, interactive and user friendly. B. Security should be kept a high priority issue.
	Team Size		4
	Technologies to be used		UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
	Tools to be Used		ROSE/RSA / WebSphere Modeler Eclipse/ RAD / Lotus Forms Designer / Portlet Factory WebSphere Portal/ WAS/ WAS CE / WPS DB2 Express – ‘C’ or DB2 UDB Tivoli CDP/TSM / Tivoli Directory Server Linux will be the preferred OS/windows.
	Final Deliverable must include		A. Online or offline help to above said users, Application deployment executive and developer B. Application archive ( .war/.ear ) with source code C. Database backup and DDL Script D. Complete Source code