The Great Mind Challenge - Project Scenario Template

Note: Already filled information should not be changed

Name of the
1. Online Library Management System (LiMS)
Project
This project is an Intranet based application that can be accessed
throughout the campus. This system can be used to search for
Objective/ books/magazines, reserve books, find out who is having a
2.
Vision particular book, put in requests to buy a new book etc. This is one
integrated system that contains both the user component and the
librarian component

A. College Students
Users of the B. Faculty
3.
System C. Book authors
D. publishers

i. A Person Should be able to login to the system through the first

page of the application and change the password after login into
the system.
ii. see the status of the books/journals borrowed/reserved by him
and the respective due dates and other relevant details
iii. search for a particular book/journal based on the name of the
book/name of the author/subject/etc and also list for
books/journals based on the name of the autor/subject etc
Functional iv. place requests for purchasing new books to the library, by
giving details about the name of the book, name of the author,
4. Requirements
publisher.
(Atleast Eight) v. see who has borrowed a particular book/journal and when is the
due date for the same
vi. cancel the reservation made earlier for a particular book/journal
vii. reserve a particular book/journal borrowed by others currently
viii. As soon as a reservation is made for a particular book, an
automatic mail should be sent to the person who made the
reservation about the details. Then, a mail should be sent to people
who are having the book currently, stating a reservation has been
made on that book
i. Secure access of confidential data (user’s
details). SSL can be used.
Non-functional ii. 24 X 7 availability
5. requirements iii. Better component design to get better
(Atleast Four) performance at peak time
iv. Flexible service based architecture will be
highly desirable for future extension
6. Optional a. Automatic mails should be sent to the users about the expiry
features of due dates for the books/journals borrowed by them. An
advance notification (say, 4 days before the expiry of the due
date) should be sent as well.
b. The librarian should be able to include new books/journals or
remove some books from the inventory
c. see the purchase requests for new books and be able to
 approve/reject the same

A. Professional look and feel

B. Use of AJAX atleast with all registration forms
C. Browser testing and support for IE, NN, Mozila,
User interface and Firefox.
7.
priorities D. Use of Graphical tool like JASPER to show
strategic data to admin
E. Reports exportable in .XLS, .PDF or any other
desirable format
A. Make a database of books, journals, students and faculty
who would be using the system

B. Create the front-page of the system giving a brief description

about the system and a login box

8. Reports C. Create the help-pages of the system in the form of Q&A. This
will help you also when implementing the system

D. Create other sub-systems like automatic notification, screens

for various functions (like reservation, cancellation of
reservation, purchase request for new books, approval page for
the librarian etc)
A. Implementation of the main screen giving the login, screen
that follows the login giving various options, screens for
students/faculty and librarian for the various functions etc
Other important
9.
issues B. During this milestone period, it would be a good idea for the
team (or one person from the team) to start working on a test-
plan for the entire system. This test-plan can be updated as and
when new scenarios come to mind.
10. Team Size 2–4
Technologies to UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-
11.
be used services, SOA
• ROSE/RSA / WebSphere Modeler
• Eclipse/ RAD / Lotus Forms Designer / Portlet
Factory
12. Tools to be Used • WebSphere Portal/ WAS/ WAS CE / WPS
• DB2 Express – ‘C’ or DB2 UDB
• Tivoli CDP/TSM / Tivoli Directory Server
• Linux will be the preferred OS.
13. Final A. Online or offline help to above said users,
Deliverable Application deployment executive and
must include developer
B. Application archive ( .war/.ear ) with source
code
C. Database backup and DDL Script
D. Complete Source code