18:14

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



  1.  
Name of the Project
IT Service Help Desk
  1.  
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.
  1.  
Users of the System


(ALL the EMPLOYEES in a company separated as)

A. Project team members
B. IT Support Team

  1.  
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.
  1.  
Non-functional requirements (Atleast Four)
  1.  Secure access of confidential data (user’s details). SSL can be used.
  2.  24 X 7 availability
  3. Better component design to get better performance at peak time
  4. Flexible service based architecture will be highly desirable for future extension
  1.  
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.
  1.  
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
  1.  
Reports
A. Number of Tickets rose.
B. Number of Tickets solved.
C. Number of Tickets updated.
  1.  
Other important issues
A. Website must be highly customizable, interactive and user friendly.
B. Security should be kept a high priority issue.
  1.  
Team Size
   4
  1.  
Technologies to be used
UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
  1.  
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.
  1.  
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

18:13

The Great Mind Challenge - Project Scenario of Indian Wildlife


Note: Already filled information should not be changed

  1.  
Name of the Project
Indian Wildlife
  1.  
Objective/ Vision
An amusing website for promoting awareness and conservation of India’s wildlife. Apart from arousing the alertness it will posses detailed information on various rare Indian animals along with coverage of all species of animals that roam in the woods of INDIA. With this, it will act as a platform for wildlife conservationists and ecologists to share their knowledge and recent trends in this field. It will incubate research and participation on subjects like animal communications, habitats, wildlife health issues, effects of global warming and various disasters.    
  1.  
Users of the System
A. Anonymous users
B. Group members (registered users)
C. Government and private organizations, Wildlife conservationist,     ecologists, veterinarians and wildlife enthusiasts.
D. Site administrators
  1.  
Functional Requirements
(Atleast Eight)
  1. To monitor statistics related to endangered species, jeopardized habitats, unbalanced ecosystems and unfavorable climatic changes.  
  2. To facilitate members to form groups to organize local meetings, wildlife forums, periodicals and Wildlife camps.
  3. To provide a space for registered users to post interesting photos, videos and presentations on Indian Wildlife.
  4. Secure registration and profile management facilities for registered members and, government and non government agencies.
  5. To acquaint users with various career opportunities in the field of wildlife, along with list of universities offering Wildlife Degrees, fellowships and certifications.  
  6. It will portray recent wildlife success stories with an opportunity for users to participate in Wildlife blogs, forums, internships, conferences and other awareness programs. 
  7. A regular news-letter should be sent to registered users to spread awareness.
  8. To setup a reviewers panel to have a tab on data being posted for the website and select appropriate contents from them to be posted. Moreover, this panel will be responsible for solving various queries of website users.        
  9. Basic and advance administration facilities like add/update members, back up/recovery of data, generating various reports, etc.
  1.  
Non-functional requirements (Atleast Four)
  1.  Secure access of confidential data (user’s details). SSL can be used.
  2.  24 X 7 availability
  3. Better component design to get better performance at peak time
  4. Flexible service based architecture will be highly desirable for future extension
  1.  
Optional features
a.     Java based client for User.
b.     Web service architecture to integrate other government web services.
c.      A CMS (Content management System) interface to admin for Web content updating.
  1.  
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
  1.  
Reports
A. Graphical representation of Wildlife Surveys on species, climates, lands and ecologies.
B. Reports on news and recently updated data on the website.
C. Reports on recently concluded Wildlife conferences and workshops.
D. Newsletter review statistics.
  1.  
Other important issues
A. Website should be highly customizable and flexible enough to easily deploy.
B. Group also seeking for any creative ideas from you to support and promote environmental activities.
  1.  
Team Size
4
  1.  
Technologies to be used
UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
  1.  
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.
  1.  
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

08:10

IBM Technologies to be used



ECLIPSEEclipse IDE, developed by an open source community focused on developing a universal platform of frameworks and powerful tools that make it easy and cost-effective to build and deploy software. The Eclipse Platform is a multi-dimensional tool that different types of developers use in different ways. Eclipse provides a platform to quickly prototype, collaborate, and share ideas built on a common architecture. This powerful and extensible platform also makes it easy to develop large-scale applications developed by far-flung teams.
For Java™ developers, Eclipse is:
Eclipse along with WTP plug-in can be used for J2EE Web Development also
WebSphere
IBM WebSphere® Application Server Community Edition is a free lightweight Java™ 2 Platform, Enterprise Edition (J2EE) application server built on Apache Geronimo, the open source application server project of the Apache Software Foundation. It harnesses the latest innovations from the open-source community and provides a readily accessible and flexible foundation for building Java applications. WebSphere Application Server Community Edition helps you accelerate your development and deployment efforts by offering technology that is quick to download and easy to use. Community Edition includes Apache Tomcat and IBM Cloudscape, and now offers an enhanced Eclipse plugin
 DB2 Express-C Production ready, Innovative Technology and Developer Community
DB2 Express-C, a version of DB2 Universal Database Express Edition (DB2 Express) for the community, is a no-charge data server for use in development and deployment. Providing the same core data server features, development interfaces as well as system limits as DB2 Express in a smaller package, DB2 Express-C offers a solid base to build and deploy all applications. DB2 Express-C is available for Linux and Windows running on 32 or 64 bit hardware.
SOA & Web Services
Service-Oriented Architecture (SOA) is an IT architectural style that supports the transformation of your business into a set of linked services, or repeatable business tasks that can be accessed when needed over a network. This may be a local network, it may be the Internet, or it may be geographically and technologically diverse, combining services in New York, London, and Hong Kong as though they were all installed on your local desktop. These services can coalesce to accomplish a specific business task, enabling your business to quickly adapt to changing conditions and requirements.
 
AJAX, Mashups, WiKi, blogs, RSS - sounds familiar?
Web 2.0 is a term often applied to a perceived ongoing transition of the World Wide Web from a collection of websites to a full-fledged computing platform serving web applications to end users. Ultimately Web 2.0 services are expected to replace desktop computing applications for many purposes.
Java Technology
Java technology is both a high-level, object-oriented programming language and a platform. Java technology is based on the concept of a single Java virtual machine (JVM) -- a translator between the language and the underlying software and hardware. All implementations of the programming language must emulate the JVM, enabling Java programs to run on any system that has a version of the JVM.

Preferred Platform: Linux

Other Technology Resources:
RFID:

 Redbooks: