Project Topics

53
Project Scenario Detailed View Name of the Project Back To My Village Objective/Vision BTMV is a charity group of professionals those want to voluntarily contribute in their village/town’s development. Issues like Primary education, people’s health, government policies awareness and availability of basic facilities/infrastructure are on main focus among others. Through the website group want to help their members collaborate, to plan, assess and implement different activities and learn with others experience/feedbacks/suggestions. Group also wants to encourage others to join their initiatives and recognize their contributions User of the System A. Anonymous B. Group members C. Web Administrator Functional Requirements i. Secure registration and profile management facilities for group members ii. Tracking member’s activities and progress. iii. Facilitating communication - Discussion forum/chat/mail – very important iv. Assessment of current situation: With the help of online questionnaires, members need to access the mature ness of primary education, health facilities etc. and based on the assessment need to categorize (total 5 categories) and chalk out a plan of actions by choosing from system suggested activities. v. Each plan of action would be shared with other members before execution so that they can share their experiences, feedbacks and suggestions. vi. Your creativity is required to frame the activities in each field. For example, to promote child education one can start giving scholarship to top 3 students in each class, you can also award best teachers on the basis of class result etc. These activities may be executed in many phases. vii. Group promotes its activities by providing online information and Face-to-face meetings with professionals to raise funds. They create case studies and share with everyone to motivate them to contribute. viii. Members are advised to develop a volunteers group in the village so that they can monitor, stabilize the changes and report to you. ix. Group also runs a monthly magazine and mails it to all members and those who had subscribed. Any one can

Transcript of Project Topics

Project Scenario Detailed View

Name of the Project Back To My Village

Objective/Vision BTMV is a charity group of professionals those want to

voluntarily contribute in their village/town’s development. Issues

like Primary education, people’s health, government policies

awareness and availability of basic facilities/infrastructure are

on main focus among others. Through the website group want

to help their members collaborate, to plan, assess and

implement different activities and learn with others

experience/feedbacks/suggestions. Group also wants to

encourage others to join their initiatives and recognize their

contributions

User of the System A. Anonymous

B. Group members

C. Web Administrator

Functional Requirements i. Secure registration and profile management facilities for

group members

ii. Tracking member’s activities and progress.

iii. Facilitating communication - Discussion forum/chat/mail –

very important

iv. Assessment of current situation: With the help of online

questionnaires, members need to access the mature ness of

primary education, health facilities etc. and based on the

assessment need to categorize (total 5 categories) and chalk

out a plan of actions by choosing from system suggested

activities.

v. Each plan of action would be shared with other members

before execution so that they can share their experiences,

feedbacks and suggestions.

vi. Your creativity is required to frame the activities in each

field. For example, to promote child education one can start

giving scholarship to top 3 students in each class, you can also

award best teachers on the basis of class result etc. These

activities may be executed in many phases.

vii. Group promotes its activities by providing online information

and Face-to-face meetings with professionals to raise funds.

They create case studies and share with everyone to motivate

them to contribute.

viii. Members are advised to develop a volunteers group in the

village so that they can monitor, stabilize the changes and

report to you.

ix. Group also runs a monthly magazine and mails it to all

members and those who had subscribed. Any one can subscribe

for it for free.

x. Basic and advance admin facilities like add/update members,

backup/recovery of data, generating various reports etc

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features 1. Java based client for Administrator

2. Customizable color scheme or skins

3. Interface to admin to change static web contents

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. State/areawise list of adopted villages and their timely

progress report

B. Activities list and plan of action

C. Magazine Subsciption statistics

D. Members list and their activities

Other Important issues Website should be highly customizable and flexible enough to

easily deploy.

Group also seeking for any creative ideas from you to support

and promote their mission

Team Size (Maximum) 4

Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA

Tools to be Used RAD/ROSE/RSA/Eclipse/WSAD/ WebSphere Portal

WAS/WAS CE

DB2 Express – ‘C’ or DB2 UDB

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

Documents

Project Scenario Detailed View

Name of the Project Chess Masters Club

Objective/Vision Creating and managing an Online Chess Club where game

lovers can learn and play Chess games by different means

(Chess tutorial, puzzle, game with computer or other player

etc.). Professional players can take part in tournaments that is

totally a commercial activity for site owner.

User of the System A. General end-users for fun.

B. Chess tournament players.

C. Admin/managers

Functional Requirements i. Registration and profile management for Players with their

preferences.

ii. Provision for Chess pieces movement polices.

iii. Chess Watch must be available to all users.

iv. Players rating evaluation algorithm.

v. Tournament game management activities.

vi. Game stop, resume and saving options

vii. Facilitate communication between players using

forums/online chat

viii. Help, tutorial and instructions for end-users to learn chess

game and puzzle

ix. Strategic data and graphs for admin and authority

x. Basic and advance admin facilities like backup/recovery of

data, generating various reports etc.

Non-Functional Requirements i. Board will be loaded once in browser, then we send geometric

notation of the board for refreshing. So board will be refreshed

in micro seconds.

ii. Use of SSL for data transmission during game.

iii. 24x7 Availability

Optional Features • Java based client for User B & C

• Basic level chess between User & computer

• Customizable color scheme or skins

User Interface Priorities A. Professional look and feel but light interface that can attract

viewers

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/reports to admin

E. Reports exportable in .XLS, .PDF or any other desirable format

Reports A. Shows all the moves played in the game.

B. Top 100 games between most rated players.

C. Particular User’s play pattern based on last 10-100 games

D. Other general reports

Other Important issues Analysis of other players move in history will help a player to

make a winning strategy. If you can provide any such feature(s)

that would be highly appreciated.

Team Size (Maximum) 4

Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA

Tools to be Used Rational Rose/RSA

RAD/Eclipse/WSAD/ WebSphere Portal

WAS/WAS CE

DB2 Express – ‘C’ or DB2 UDB

Linux will be the preferred OS.

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

Documents

Project Scenario Detailed View

Name of the Project Development of an auto-summarization tool

Objective/Vision This has some applications like summarizing the search-engine

results, providing briefs of big documents that do not have an

abstract etc. There are two categories of summarizers, linguistic

and statistical. Linguistic summarizers use knowledge about the

language to summarize a document. Statistical ones operate by

finding the important sentences using statistical methods.

Statistical summarizers normally do not use any linguistic

information.

User of the System A. Used to generate summaries of electronic documents

B. Using statistical techniques

C. techniques involve finding the frequency of words, scoring

the sentences, ranking the sentences

D. To handle the document types like Plain Text, HTML, Word

Document

Functional Requirements i. Study about auto-summarizing techniques (some references

are given in the references section of this document) and

concentrate more on summarizers based on statistical

techniques

ii. Collect the list of stop-words from an Internet site

iii. Come up with algorithms for the different functional

components listed in the previous section. Some heuristic

methods could be used to come up with modification of any

existing algorithm

iv. Implement the pre-processor/sentence separator/word

separator/word frequency calculator. These do not require much

work on the algorithm side and existing algorithms will do fine.

v. Implement the scoring and ranking component

vi. Test it with some documents and tune the algorithms, if

needed

vii. Bench-mark your tool against some tools available on the

Internet

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. This algorithm determines the score of each sentence.

Several possibilities exist. The score can be made to be

proportional to the sum of frequencies of the different words

comprising the sentence The score can also be made to be

inversely proportional to the number of sentences in which the

words in the sentence appear in the document. Likewise, many

such heuristic rules can be applied to score the sentences.

b. The sentences will be ranked according to the scores. Any

other criteria like the position of a sentence in the document

can be used to control the ranking. For example, even though

the scores are high, we would not put consecutive sentences

together

c. Based on the user input on the size of the summary, the

sentences will be picked from the ranked list and concatenated.

The resulting summary file could be stored with a name like

<originalfilename>_summary.txt

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. Text pre-processor. This will work on the HTML or Word

Documents and convert them to plain text for processing by the

rest of the system

B. Sentence separator. This goes through the document and

separates the sentences based on some rules

C. Word separator. This separates the words based on some

criteria

D. User Interface. The tool could use a GUI or a plain command-

line interface. In either case, it should have easy and intuitive

ways of getting the input from the user.

Other Important issues A. After finalizing on the algorithms, the system is integrated so

that it is possible to test using a GUI or a command line

interface

B. The tool should be tested with documents of different size

and content

Team Size (Maximum) 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

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

Documents

Project Scenario Detailed View

Back

Name of the Project e-Cops

Objective/Vision "Serving those who protect"

To deliver next generation police and law enforcement reporting

tools, and setting up intelligence platforms that agencies use to

take incoming incident reports, lessen live employee resources

and allow these enforcement agencies to reallocate resources to

much needed community areas

User of the System A. Citizen

B. Police officers (Constable to DGP)

C. Detectives

D. Administrator

E. Hotel and Cyber café employee

Functional Requirements i. Administrator should be able to create/edit a virtual police

station (PS) which represents a real police station as a first time

setup.

ii. Appointing of police officers to a particular police station

which is present in a specific zone or to a specific district as a

first time setup, he should be transferable at later time.

iii. PS should have areas of control which can be modified at

later time.

iv. Police station has several departments like Law and Order,

Women Protection, Cybercrime, Traffic and control, CBI, etc.

Separate module for each dept would be needed.

v. When a complaint is made it undergoes various processes like

FIR, Charge Sheet, Property Seizure, court disposal etc all these

activities are performed by a PS.

vi. Traffic and Control has important part where the Traffic

inspector would be filing a charge sheet from a mobile or PDA.

vii. Maintaining the criminal information state wise/area

wise/age wise is mandatory

viii. Sharing of case details with PS in other states is needed.

Note : Other state may use different database and different

platform (use of IBM MQ is necessary)

ix. Communication between officers is mandatory through

forum, chat, polls.

x. The magistrate should be able to access the case details and

provide/deny the arrest warrant.

xi. Citizens should be able to apply for various licenses like

Arms, loud speaker, Hotel/lodge, browsing centre, mass

meetings etc., and the officer should be able to approve/reject

which will be notified to the applicant via SMS and Mail

xii. Secured registration of citizens is needed where they need

to provide proof of citizenship, which will be cross checked by

the police officer of that area.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Integration of E cops with Prison management and Court is an

immediate requirement

b. Chat using XMPP provides added feature

c. Biometric authentication (Face detection or Fingerprint).

d. Administrator should have a java client end (i.e. java swing

end) rather than web end.

e. Use of JMS for communication between other state databases.

f. Predicting criminal faces in various conditions using digital

image processing via face points would be additional feature.

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, Mozilla, Safari 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. Complaints filed in a day and action taken to it. It should also

report unattended complaints.

B. Crime rate due to various types of crimes in a month/year

and also in district/state wise.

C. Report regarding most wanted criminals and bounty

information if available.

D. Police officers often export the FIR copy to PDF format.

Other Important issues A. The Police station should go online, i.e., even the Station

Diary; Station House Officer Diary should go online.

B. Everything should be customizable by Administrator i.e. even

the home page contents.

C. It should be start of an E-governance system, so the

registered member details may be used for various purposes

Team Size (Maximum) 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

Final Deliverable m

ust 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

Documents

Project Scenario Detailed View

Back

Name of the Project E-Mentoring for Women

Objective/Vision Developing an online mentoring system to promote more

women to splurge into the field of Science and technology

breaking the myths and taboo's society imposes. Also, to give

them a platform to be on power with a working woman.

User of the System A. Students

B. Working women (mentors)

C. Data Manager

D. Master Mentor

E. NGOs

Functional Requirements i. It should showcase successful women in various fields and

their success stories, which should be motivation for young girls

around the globe.

ii. It should create profiles of both registered students and

mentors.

iii. Profile matching should give results of best suited mentor for

each student based on the profile.

iv. Forum's for both students, mentors and NGOs.

v. Students can take up EQ(emotional quotient) tests and

various other tests which help the student to realize her in built

talents for various fields.

vi. Based on these a list of the top universities and schools

should be displayed based on various factors namely

geographic location, university ranking, etc. Also, relevant

scholarships should be displayed.

vii. It should also provide various tutorials and tests to be

accessed by the mentor, who would make it available to their

student.

viii. Also, the progress made by the student should be sent to

the respective mentor.

ix. A regular news-letter should be sent to various universities to

make them aware of the e-mentoring system.

x. Mentors could suggest certain students who according to

them require assistance in non-technical matters to members of

the registered NGOs thus enabling a private communication

between the student and the NGO.

This could also be a platform for conducting various e-

conferences on gender equity and related issues. The

participation of NGOs working towards the cause of

empowerment would be a great positive.

Non-Functional Requirements Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Online MCQ's testing facility.

b. Upload various files and photographs to be displayed on the

users profile.

c. Customizable color schemes or skins.

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. Student wise reports for each mentor for various tests.

B. Collective report of all students under a mentor.

C. Tutorial utilization reports.

D. Reports of participation in various forums, blogs, e-

conferences should be displayed on the profile.

Other Important issues A. The website should be adaptable to more than two groups

i.e , segregation of students into two namely school going and

university going

B. It should also accommodate the transition of a student into a

mentor with the passage of time.

C. Forums focusing on the day to day challenges in the working

world faced by women.

Team Size (Maximum) 4

Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA

Tools to be Used RAD/ROSE/RSA/Eclipse/WSAD/ WebSphere Portal

WAS/WAS CE

DB2 Express – ‘C’ or DB2 UDB

Linux will be the preferred OS.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Farmers Buddy

Objective/Vision It is the agriculture portal which provides solutions to small

farmers and agriculture students of India. Besides Salt &

fertilizer analysis for particular region this portal also helps

farmers to know about government loan and insurance

schemes. It also helps them make decisions on mandi/market

and best prices. NGOs are trying to spread messages to make

agriculture more eco-friendly through this site.

User of the System A. General public

B. Farmers and Agriculture students

C. Agriculture officers

D. Administrator

Functional Requirements i. Individual profile management for all kind of users.

ii. Basic soil analysis for all regions and suggestions on which

fertilizers to use where & how much? Which crop, herb or

vegetable can be grown where and in which season?

iii. Online query handlings for all users. Queries can be general

or directed to a particular officer.

iv. Officers/NGOs can schedule trainings and publish it online.

User-A&B can request training online.

v. Facilitate communication between user, experts and general

public through - Discussion forum/chat/mail/polls

vi. Foreign agriculture experts/businessman can upload the info

about their tools and solutions on chargeable basis.

vii. Information about major crop markets (mandi) and their

current price for crop should be published daily.

viii. Awareness drive Govt schemes specially loan and insurance

based for farmers.

ix. Website should support local language so that farmers can

get the best of it.

x. Information pages should be dynamic so that User-C & D can

change it from their interface easily.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Customizable color scheme or skins

b. Java based interface for User C & D.

User Interface Priorities A. Professional look and feel

B. Use of AJAX (MUST 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. Different types of reports on daily, monthly, weekly, annual

basis, date range and type of interactions.

B. Searching information based on Soil analysis, Leaf analysis

and Fertilizer analysis.

C. Daily Mandi price Reports on selected crops.

D. Various reports on government policies, loan/insurance

procedure are to be generated.

Other Important issues A. User-interface easily handled by ordinary people also.

B. Website should be highly customizable and flexible enough to

easily deploy without much effort.

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Feature-rich Resume Builder

Objective/Vision Develop an Intranet Application for Winner Technologies Ltd. for

automating the process of Resume Writing. This would be

facilitating the employees to make and print their resumes in a

proper format. In addition, it will be facilitating the higher

management to search the employees depending upon their

skills sets and other attributes

User of the System A. End-Users(Employees)

B. System administrator.

C. Job seekers

Functional Requirements i. The Users can perform the following tasks End Users and

System administrator.

ii. The system has the following Interfaces Login and Interface

for filling up the following information

iii. Interface for searching a student on various attributes

iv. Interface for searching a student on various attributes

v. Come up with the database design. The Login to the system is

database driven i.e. a user will be allowed to access the system

if and only if he is the valid user of the system

vi. Decide a format in which you want the resume to get printed

in word document

Non-Functional Requirements Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. The Users can Enter information into their Resume / Edit

Resume

b. The Users can Search for a particular employees.

c. Interface for filling up the information like Skill sets, Training

and Visa Details.

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. Filling up the Educational Information

B. Filling up the Skill sets

C. Filling up the Visa Details

Other Important issues A. The Project Can be developed using either two tiers or three

tiers Architecture

Team Size (Maximum) 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

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

Documents

Project Scenario Detailed View

Back

Name of the Project Manage Group of Hotels

Objective/Vision Developing a central system that will help management of a

group of hotels from a central authority. This system will be

owned by a Hotel Group of national or international repute. The

system will incorporate all features of hotel management and

customer relationship management plus central management of

the group of hotels by the firm head. This integrates customer

services like online and ‘any place’ booking along with features

like central assessment of performance reports by the Managing

Director. It provides a complete concoction of solutions to all

hotel management problems like financing, accounting,

inventory management so on and so forth. It will usher an

environment which will not only provide unlimited services to

the customers but also help the Managers, Employees and other

people related to the hotels to function effectively and

efficiently.

User of the System A. Managing Director (MD)(Admin) – Chain head

B. General Managers. (GM) – Hotel head

C. Employees.

D. Customers.

E. Agents.

F. Suppliers

Functional Requirements i. Registration & user profile management.

ii. Managing Director can view performance reports of every

hotel and compare each hotels performance visually in terms of

expenditure, profits etc.

iii. Finances and Accounts Management of the hotel is

supervised by the GM and they submit regular reports to the

MD.

iv. GM contacts suppliers for Quotations of various tenders

online. GM accepts tenders and quotations online from the

Suppliers and evaluates them and sends back replies.

v. Hotel can notify customers about various offers and packages

by means of e-mails and SMS.

vi. Online booking by customers at any branch of the hotel.

Customer can search for a branch and book online. Online Order

placement for home delivery of food from the nearest hotels

restaurant by customers.

vii. Employees / Customers can give online feedback or report

grievances online. Customers can directly contact the GM by

means of e-mails.

viii. Employees profile would be maintained and they would be

ranked according to their performance, employees can regularly

check their ranks.

ix. Suppliers can fill in tenders online and submit their

quotations online.

x. Agents like travel agents and reservation agents provide

conformation of services like local conveyance and air or rail

booking online to the GM.

xi. Facilitate communication among all Users via mail, chat,

forum, SMS etc.

xii. Online Library for customers will be available for getting

information about that particular place or area like tourist spots,

suggested visiting areas and their timings etc.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Java Client for MD, GM and hotel employees

b. Drag and Drop functionality.

c. Customizable color schemes and skins.

User Interface Priorities A. Professional look and feel

B. Use of AJAX (MUST 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. Hotel Expenditure Reports.

B. Hotel Profit Reports.

C. Hotel Audit Reports.

D. Employee Performance Reports.

E. Inventory Status Reports.

Other Important issues A. Website must be highly customizable, interactive and user

friendly.

B. Security should be kept a high priority issue.

Team Size (Maximum) 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Monitor Smart Gadgets Online

Objective/Vision Vision is to provide an online monitoring system to the users to

manage all their smart gadgets (I Pods, mobile phone, pen drive

etc) through a single interface by establishing a direct bridge

between product and manufacturer via our remote server. Main

idea involved here is to make use of online service (monitoring

tool) that can automatically scan electronic gadgets for any

hardware or software defect as the product is brought online. It

will then make a log of errors, report it to the manufacturer and

provide feasible solution back to customer. The application will

also be useful in case of theft by tracking down unauthorized

use of gadget. It can also be used as a platform where users can

find solutions to all other problems pertaining to their gadgets

and manufacturer may showcase their various products and

provide service in better way.

User of the System A. manufacturers ( smart gadgets)

B. customers

C. service providers

Functional Requirements i. Creating user account for customer to monitor product

functionality

ii. Automatic Scanning of product for defects

iii. Reporting of defects to manufacturers

iv. Providing the solution back to customer through auto-

generated email

v. In case of theft , stolen product can be tracked

vi. Maintains database of all information pertaining to the

gadget

vii. Provides users single interface to monitor his different

gadgets.

viii. Makes it very easy for service providers to be in contact

with users and provide them all the necessary details

ix. User can get all the relevant updates for his different

products through single interface.

Non-Functional Requirements Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension .

Optional Features a. Manufacturers can showcase their new products/offers

through this portal

b. Java based clients for user A & C

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. log of details, each time the device is plugged in to computer

B. details of all the gadgets available with the customers

C. details of all the customers

D.log of all the defects detected in device

Other Important issues 1. Web application should be highly optimized and easy to use.

2. Application should be scalable (considering future prospects)

Team Size (Maximum) 4

Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA

Tools to be Used RAD/ROSE/RSA/Eclipse/WSAD/ WebSphere Portal

WAS/WAS CE

DB2 Express – ‘C’ or DB2 UDB

Linux will be the preferred OS.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Online Data Visualization

Objective/Vision Data visualization simplifies complex structure of

analytical/large data which helps a broad range of users to help

in decision making. Data experts and analysts can understand

complex statistical reports but most of the time it’s difficult for

decision makers to interpret it accurately and test all what-if

conditions.

Objective of this project would to integrate different available

data visualization methods with different consumability factors

to make the available data/information more acceptable and

useful to general users. Consumability can be created by

understanding the business context, user’s role and expertise

level.

User of the System A. Administrator

B. Data expert level

C. Manager level

D. Supervisor level

Functional Requirements i. Understanding user’s preferences, expertise level and his

business requirements through a friendly questionnaire.

ii. Input data can be in four different forms - Relational DB, text

files, .xls and xml files. For testing and demo you can choose

data from any domain. User-B can provide business data as

input.

iii. User-B should be able to see queried/drilled down standard

report along with scientific visual models. They should be able

to find patterns using general statistical methods. He is

responsible to prepare the data on which User-C can take

business decisions.

iv. User-C is responsible to make decisions so he would want to

see visual models with which he can predict, optimize and

understand what-if based situations.

v. User-D is responsible to monitor/control day-by-day

operations. He is more to visualize daily/weekly/monthly

comparisons on many criterias.

vi. Users can create, save and share reports and visualization

templates for later use.

vii. Any user can work with visual models who work with text.

Please note text data may be numerical or simple memo.

viii. User-A is responsible for user management and

backup/recovery of the system

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. System can be customized for particular industry like

banking, telecom or retail.

b. Use of Web 2.0 features is highly desirable.

c. Java clients can be created for User-B,C & D.

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. Different types of role based flat reports

B. Business sensitive and template based reporting

C. Different graphical reports for managers

D. User’s preferences, their expertise levels and business

context report

Other Important issues None

Team Size (Maximum) 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.

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

DocumentsTGMC09 Scenario - Online Data Visualization System

suppliment.doc

Project Scenario Detailed View

Back

Name of the Project Online Library Management System (LiMS)

Objective/Vision This project is an Intranet based application that can be

accessed throughout the campus. This system can be used to

search for books/magazines, reserve books, find out who is

having a 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

User of the System A. College Students

B. Faculty

C. Book authors

D. publishers

Functional Requirements 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

iv. place requests for purchasing new books to the library, by

giving details about the name of the book, name of the author,

publisher.

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

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Automatic mails should be sent to the users about the expiry

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

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. 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

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)

Other Important issues 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

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.

Team Size (Maximum) 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.

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

Project Scenario Detailed View

Back

Name of the Project Online National Polling

Objective/Vision We live in a democracy and voting is one of our fundamental

duties as responsible citizens of the country, but nowhere

around the country a 100% people come to vote during the

elections in their territory. There have been many reasons for

that some of them are:

• In the rural areas the influential people keep their men at the

polling booths to threaten the common man to vote for them

• There are many portions of the country like the North East

where there is locally sponsored terrorism, at such places the

security conditions are also not very bright, so naturally people

feel afraid to come out of their houses and go to vote

• Net savvy new generation want hassle free voting system.

Also the people in metros want a system thru which they can

vote for their territory without traveling.

Keeping in mind these situations and to improve the state of

democracy in the country Online Polling System can be thought

as a solution, in conjunction with the ongoing current manual

voting system.

User of the System A. General Public

B. Candidates

C. Administrators (Election Commission Officers)

D. Field Officers

Functional Requirements i. Online registration for the voter id card which will be verified

by the field officers (address and identity validation) and after

receiving the field officer's report only the registration will be

validated and a voter id will be issued (a photograph will have to

be uploaded). You can also think about any other secure method

like digital signature.

ii. Those already having a voter id card can register for the

online voting system, they will use their voter id as their user

name and a separate password will be used for secure

authentication.

iii. The election commission will be able to use the site to let the

candidates register for their nomination on the site and their

officers will validate it. Candidates can run their election

campaign through forums and chat-room.

iv. A detailed profile of all the candidates constituency wise will

be maintained so that voters can always know about the

candidates of their area.

v. Once registered when ever polling is done in any area that

areas' people will be able to vote for their favorite candidates.

vi. Devise a mechanism that ensures duplicates voting (online &

offline) is not happening.

vii. The system would show the current statistics as well on the

web site about how many votes which candidates have got.

viii. Later when the voting ends the administrator can add the

manual poling results to the database to calculate the final

results which will immediately be flashed on the site.

ix. Facilitate appropriate communication between all

stakeholders - Discussion forum/chat/mail/polls

x. Candidates should be able to modify selected portions of their

profile after registration for nomination like the promises they

make about the things to do after winning the election, their

previous works, their experiences and a comprehensive about

me, etc.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features 1. Java based client for User-C & D

2. SMS based inquiry of the voting results

3. Customizable color skins.

User Interface Priorities A. Professional look and feel

B. Use of AJAX (MUST 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. Percentage voting done in different areas, regions, the overall

voting percentage.

B. Number of votes that different candidates got based on the

areas, regions etc.

C. The statistics of all the elections done so far should be

available based on date or year of election.

D. Reports containing details of voters, candidates based on

many criterions should be available to administrator.

Other Important issues A. The architecture should be highly scalable and the web site

should be tuned for better performance at the peak time.

B. Website should be highly customizable and flexible enough to

easily deploy.

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project On-line Project Management

Objective/Vision The need for managing the projects using international

standards & monitoring through the web from across the

worldwide organization branches are directing towards having

an online project management tool.

The basic project monitoring should have the Clear personalized

dashboard views provide at-a-glance summary of your status

across all projects, Allocation of resources and view resource

load across all projects and activities, All the information you

need at your fingertips – Project status and plans, related

documents, notes and discussions, Projects status and related

data is securely shared in real time, based on each user’s role

and permissions.

More over the system need to be available for Access over the

web anytime, anywhere.

User of the System A. Project Manager

B. Team Leads

C. Individual Project members

Functional Requirements i. Project Dashboard

Project Management Dashboard updates automatically to

provide you with an up-to-date graphical view of the current

health of your projects, while it's happening.

ii. Project Planner

Using the Project Planner you can create a detailed task list,

schedule the start and end dates of tasks and add links between

them. You can assign durations and allocate resources, to

ensure that the right tasks are completed at the right time, by

the right people.

iii. Time Tracking

Your entire team can track their time spent, quickly and easily

using this Online Timesheet. On each Timesheet you can record

the time spent, tasks completed and denotes to each Online

Timesheet entry.

iv. Expense Tracking

This helps you identify, monitor and report on project expenses.

The Expense Tracking form also helps you track the total cost of

your project to date. Using this Expense Tracking information,

you can ensure that your project stays within budget!

v. Risk, Issues & Changes

As your team-enter new risks, you'll immediately see the results

on your project dashboard. It will instantly tell you whether your

project has a low, medium or high level of risk. As you made

new changes to the software, that need to be tracked in

Highlighted views.

vi. Project Reporting

By generating these stylish Project Reports, you can show your

sponsor that the project is on track and has been well managed.

You can View, Email and Print any Project Status Report at any

time.

vii. Online Storage

Every project involves creating documentation. Whether it's a

business case, project charter or project report, you'll want to

keep it all in a central location. You can store templates here,

along with the deliverables for each project.

Non-Functional Requirements Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Create a log for every activity

b. Create new users & block the users by super users

c. Protects the documents as it uploaded, needs password to

download the online documents

d. Takes backup of uploaded documents on demand

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. Daily, weekly & monthly project reports including resource

utilization, risk & time lines

B. User Activity reports

C. Security reports including incorrect sign-in attempts,

password changes

Other Important issues Take a look to the project management softwares already

available.

Team Size (Maximum) 4

Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA

Tools to be Used Eclipse/ RAD, Rose/RSA, WAS/WASCE, DB2 Express – ‘C’ or DB2

UDB, Tivoli Storage Manager, Lotus forms, portal

Linux will be the preferred OS.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Save Her From Cancer

Objective/Vision Spread awareness about the various and most harmful cancers

which can affect women:

• Breast Cancer

• Cervical Cancer

• Endometrial Cancer

• Fallopian Tube Cancer

• Ovarian Cancer

• Vaginal Cancer

• Vulvar Cancer

Awareness about these life taking diseases can lead to the

enormous decrease in the number of victims. Early diagnosis

and treatment can help cure the disease easily.

User of the System A. Admin

B. Doctors and Medical Activists

C. Woman Welfare Organizations

D. Disease affected or cured women

Functional Requirements i. The site should contain write-ups which give a general

awareness to the public about the hazardous cancers which can

affect women.

ii. The users should be able to clarify their doubts about the

disease with medical practitioners.

iii. Woman Welfare organizations should be able to announce

the launch of programs or diagnosis camps through the site.

iv. A regular newsletter should be sent to registered users about

the latest developments in regard to the disease.

v. Admin should be able to view strategic data and graphs about

contributors to the site, regular users, age groups of users etc.

vi. Disease affected or cured women should be able to share

their experiences through the site. Their names should be

disclosed only if they wish to do so.

vii. Users should be able to attend Multiple Choice Questions

(MCQs) to help identify whether they have started to show the

initial symptoms.

viii. Information must be provided regarding the nearest hospital

which provided diagnosis facility as well as treatment for the

disease according to the address given by the users.

ix. The most active doctor or medical practitioner in each

disease category should be given “e-certificate of appreciation”

on yearly basis.

x. Facilitate appropriate communication between all

stakeholders - Discussion forum/chat/mail/polls

Non-Functional Requirements Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. An online chat with Medical practitioners or affected women.

b. Customizable color schemes and profiles.

c. Medical Practitioners should be able to upload their photos

and videos about case studies on their profile if necessary.

User Interface Priorities A. Professional look and feel

B. Use of AJAX (MUST 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. Result of MCQs attempted by the users.

B. Reports regarding the statistics about infected women and

their age groups.

C. Area –wise report about the spread of the disease.

D. Most active doctor or Medical practitioner category-wise (for

Award of Appreciation)

Other Important issues A. Website should be highly customizable and flexible enough to

easily deploy.

B. Facilities for Localization and Internationalization should be

available.

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Smart City

Objective/Vision If you are desirous to give a web based platform to your city to

be showcased for all it has in terms of unique business, places

to see, things to do, use local transport for a new traveler – how

would you structure this information and also try and make

some money by charging people for atleast 4 services you may

offer.

User of the System A. Any one looking for information of your city

B. Tourists coming to your city

C. Businessmen coming to your city

D. People trying to get some help to do business remotely

Functional Requirements i. Complete Map of the city with key markets and places to see

marked – preferably usage of static map and live Map option

ii. Complete History of the city – social, political

iii. Complete overview of the businesses in the city

iv. Secure registration of all users including a personal profile –

only at the time of a transaction providence

v. Complete Search/Site Map of the entire site for easy access

vi. Start atleast 4 paid services like SMS alerts for city news,

market daily rates, advertises etc.

vii. Local news, government notices, update

viii. Facilitate communication between user, experts and general

public through - Discussion forum/chat/mail/polls

ix. Local language support at user-interface and database level.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

v. Web site URL should be of the following nomenclature

www.citinamesmartcity.com example

www.madurismartcity.com or www.noidasmartcity.com etc

Optional Features a. Downloadable guided city tour video/PPTs/animated movie

b. Engage local media and police and other government

department like passport to make your portal more useful

c. Customizable color schemes or skins

D. Use Google Analytics to track traffic on portal

User Interface Priorities A. Great visualize appearance and user-friendly interface.

B. Use of AJAX (MUST 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. Customized report for tourists, businessmen, government

B. Graphical representation of city’s historical data

C. Survey reports for social researchers

D. Analysis reports areawise, sexwise, city health, business &

agriculture growth etc.

Other Important issues A. Website should be highly customizable and flexible enough to

easily deploy without much effort.

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Stock and Portfolio Management Solution

Objective/Vision A solution that not only caters to the need of a Stock Broking

firm but is also scalable without compromising on performance.

User of the System A. Stock Agent/Broker

B. Customers (who buys stocks)

C. Management

Functional Requirements i. Brokers should have access restricted to the portfolio it is

taking care of.

ii. Customers should have remote access. And should be able to

conserve and place request online. An audit trail should be

maintained of it.

iii. A sub-system for brokers to execute customers' requests and

orders.

iv. Customers should be notified automatically on execution of

their requests and orders. A sub-system should be available to

customers to track the status. And a way to escalate to

management in case of grievances.

v. Management and Customers should have access to various

reports. The access to reports should be role based.

vi. System should provide a REST service to current stock prices

vii. Management should be able to use reporting solutions like

BIRT to create custom reports.

viii. Because the market rules change quite often, the system

parameters like commission charges, TDS, should be

configurable by management. However, brokers should be able

to extend discounts to their customers.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability. 99.9% Uptime during business hours. It

should mitigate system failure risks.

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

v. High Scalability. The solution should be able to accommodate

high number of customers and brokers. Both may be

geographically distributed.

Optional Features a. Context Sensitive Help

b. Auto-generated Reports sent by e-mail

c. Backup and Restore of system data

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. Customer Reports: Portfolio status report, Stock performance

report, Order/Request History Reports

B. Broker Reports: Portfolio Status Report, Order and Request

report by status.

C. Management Reports: Broker Performance Report, Income

Report

D. Custom Reports

Other Important issues A. Customers will need a secure web access.

B. Brokers too should be able to carry out important business

remotely.

Team Size (Maximum) 4

Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA

Tools to be Used RAD/ROSE/RSA/Eclipse/WSAD/ WebSphere Portal

WAS/WAS CE

DB2 Express – ‘C’ or DB2 UDB

Linux will be the preferred OS.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Stop Global Warming

Objective/Vision This is a social website for encouraging people to abstain from

various pollution causatives. It works on the principles of health

promotion and strengthening the society. It not only makes the

users aware of the diseases caused but also how to prevent

them. It encourage, conduct and participate in investigations

and research relating to problems of water, land and air

pollution and its prevention, control and abatement thereof.

User of the System A. Anonymous users

B. Group members (registered users)

C. Government or non government agencies, Doctors

(Physicians & Counselors)

D. Site administrators

Functional Requirements i. To shed light on the various inspiring stories of those who

have contributed against pollution. Group members will have

opportunities to run various anti-pollution awareness

programmers in public places, colleges, etc.

ii. It should spread awareness about the ways (direct, indirect

etc) in which a person can help to overcome pollution.

iii. To evolve efficient methods of disposal of sewage and trade

effluent on land.

iv. To monitor the generation, transportation, treatment, storage

and disposal of hazardous wastes.

v. To facilitate members to interact with people, conduct

counseling and clear doubts via discussion forums/chat/mail.

vi. Secure registration and profile management facilities for

registered members and government and non government

agencies.

vii. A regular news-letter should be sent to registered users to

spread awareness.

viii. To collaborate with Central Pollution Control Board in

organizing the training of persons engaged or to be engaged in

programmers relating to prevention, control or abatement of

water/air pollution and to organize mass education programmed

relating thereto.

ix. To identify and monitor the isolated storage of hazardous

chemicals.

x. Basic and advance admin facilities like add/update members,

back up/recovery of data, generating various reports, etc.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

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.

d. Customizable color scheme or skins.

User Interface Priorities A. Professional look and feel

B. Use of AJAX (MUST 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. Activities of members and counselors by area.

B. Weakly, monthly and yearly population reports of various

cities.

C. Reports about the participation of various members in the

discussion forums etc.

D. Newsletter review statistics.

E. Users who contributes against pollution.

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 anti-pollution activities.

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Supply Chain Management

Objective/Vision Develop an online system to provide the management of the

flow of materials, information, and funds across the entire

objects of supply chain.

User of the System A. Manufacturer

B. Distributor(Wholesaler)

C. Retailer(Shopkeeper)

Functional Requirements i. Maintained transparency between all the three users. For e.g.

User C must have no idea about transaction between users A &

B.

ii. Retailer placing bulk orders can directly communicate with

the manufacturer.

iii. Online ordering of products & bill generation for users B, C.

iv. User A,B can add products, decide prices of products & can

change prices according to market

v. A, B system returns an error message, for non-existent & for

less available quantity of selected products.

vi. Users B, C must provide feedback for products.

vii. For new products SMS alerts by manufacturer.

viii. Delivery time limit must be provided at the time of ordering.

ix. Separate notice is sent by supplier describing modes of

transportation & other details of products

x. Facilitate appropriate communication between all

stakeholders - Discussion forum/chat/mail/polls

Non-Functional Requirements Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Places can be added where manufacturer can place their

advertisements.

b. Manufacturer can ask quality of products to the wholesaler &

retailer.

c. Supplier can send a shipping SMS notification.

User Interface Priorities A. Professional look and feel

B. Use of AJAX (MUST 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. Recent marketing strategies adopted by objects of chain.

B. Monthly profit report for each objects of supply chain

C. Which product is more popular in each category.

D. Which manufacturer products are more popular.

Other Important issues A. It should also accommodate the transition of a retailer into a

wholesaler with the passage of time

B. Website should be highly customizable and flexible enough

for easy deployment.

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Virtual Medical Home

Objective/Vision Objective is to provide essential medical services online to

everyone hardly matters you live in metro or a remotely located

village. Users can connect through their home internet or

approach any nearby kiosk to get these services. What motivate

to build this system are:

1) Very few or no doctors at remote locations

2) Limited hour services and lack of sophisticated medical

equipments

3) No patients history/lab data management

User of the System A. Patients

B. Doctors

C. Kiosk Manager

D. Admin

Functional Requirements i. Users profile management and registrations

ii. Patients to make online appointment, look their previous

health records, doctor’s prescriptions, lab reports and medical

expenses

iii. Doctor’s to give appointments, e-prescriptions, view patient’s

history.

iv. Web-cam based interaction between patient and doctor.

v. Kiosk Manager to see/adjust appointments, perform day open

& close activities and calculate his commission.

vi. In case of any medical error (wrong medication or lab report)

patient can register a complaint. Patient’s grievance and

feedback goes to Admin he can forward it to any doctor to

answer.

vii. Facilitate appropriate communication between all

stakeholders - Discussion forum/chat/mail/polls

viii. Site should have details online help manual for patients.

Local language support is essential.

ix. Admin to take backup of all kind of data, view log and

generate system reports.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. Java SWING client for User-B, C and D

b. Customizable color schemes and profiles.

c. Implementation of Google analytics

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. Patients history, lab reports and prescriptions

B. Doctors register, logs and list

C. Daily reports, appointment lists for Kiosk owners

D. Admin’s area wise, illness category wise reports

Other Important issues A. A. Website should be highly customizable and flexible enough

to easily deploy.

B. Facilities for Localization and Internationalization should be

available.

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project WebApp Scanner

Objective/Vision This 24x7 online web application will help developers and

security professionals protect against the threat of attacks and

data breaches. If you use your Web applications to collect or

exchange sensitive or personal data, this system would give you

a detailed automated report on :

• How secure your website is?

• How easily it can be hacked?

• Where exactly is the problem and

• What are the remedies?

This would be a paid service which any web

developer/development company can avail. Static pages of this

site should give you detailed information of different

vulnerabilities and risks.

We expect only HTML, JSP, Servlet, xml and Bean files to be the

part of input web module (.war file) to begin with. No database

connections only XML files.

User of the System A. Administrator

B. Platinum Customer

C. Gold Customer

D. Silver Customer

Functional Requirements i. Customer registration and profile management

ii. From to input .war file and criteria on which report should be

generated.

iii. Static information about most common risks and

vulnerabilities like SQL injection, path tampering, Cross site

scripting, Suspect content & cookie poisoning. Please refer

attached pdf for more info.

iv. Customers are divided into 3 categories. Users can see their

historical scan data and reports.

v. Silver Customers are free users accessing the solution so they

can use limited features.

vi. Gold customers are independent developers who can be

charged per scan or per application (many scans).

vii. Platinum customers are corporate customers. On their

account many team members from same project team can scan

application many times. Pricing should be per application or per

month.

viii. User-A is responsible for user management, maintain user

log and backup/recovery of the system.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features a. System can be customized for particular industry like

banking, telecom or retail.

b. Use of Web 2.0 features is highly desirable.

c. Java clients can be created for User-B & C.

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. Different types of risk/vulnerability webapp scanning report

B. Business sensitive and template based reporting

C. Historical scanning report and logs

D. Comparison report of different scanning versions of same

application.

Other Important issues None

Team Size (Maximum) 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.

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

Documents dirtydozen-hackerattacks.pdf

Project Scenario Detailed View

Back

Name of the Project Work to Worker - Services to unorganized sector

Objective/Vision Objective of this system is to providing a work to worker. Solution

focused on the workers of unorganized sector includes mason,

carpenters, gardener, painter etc. Work to Worker is a Web-based

solution through which worker (s) registered them selves for a

specific skill. Using this system general public or organized sector

user can select the worker(s) as per their need. At the time of

worker selection he/she can view the skill, references given by

those who have taken their service in the past, area (worker

location) and availability of a particular worker(s). System sends

SMS to a selected worker(s) regarding work and customer details.

Worker(s) confirms either through phone or this system and

either fixed up meeting or work start date. Organized sector user

or general public can rate worker skill, charges, particularity

about time, dedication, behavior, habits etc through this system.

Users can put their demands regarding particular skill workers

along with project location, and project details.

User of the System A. Administrators

B. Worker from unorganized sector

C. Customer - Organized sector (builder, contractor)

D. General public

Functional Requirements i. Secure Registration of users (workers) and customers (general

public/ organize sector user) with any type of centralized security

mechanisms (election card, passport, pan card etc.) .

ii. Workers are classified into various groups & categorized

namely aware skilled, semiskilled, etc...

iii. State can be modified by feedback system & workers rating

evaluation algorithms.

iv. Profile management facilities for both laborers and customers.

v. Chat/mail/SMS services (preferably multilingual )

vi. Customer can make a community for reference purpose etc.

vii. Customer can give their feedback for worker(s) who worked

for them.

viii. Worker can view details information project (organized

sector) in particular location.

ix. Worker can maintain the work calendar which should be

exported to txt; xls or pdf format, there must be mechanisms for

face-to-face meeting with customer.

x. Local language support.

xi. Administrator able to generate various reports graphs on

strategic data which should be exported on xsl or csv format, also

able to backup/recovery data.

xii. Facilitate appropriate communication between all

stakeholders - Discussion forum/chat/mail/polls

xiii. User Manual

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features • Java based client for Administrator

• Customizable color scheme or skins Customizable color Scheme

or skins

• Interface to admin to change static web contents.

User Interface Priorities A. Professional look and feel

B. Use of AJAX (MUST 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 • Different levels of reports on worker(s) and customer - region,

work-type, category, rating and others

• Area wise project details along with requirements

• Daily report on work request from customer.

• Weekly progress reports of laborers to admin

• Worker wise feed back report

• Category & area wise worker list

Other Important issues • Any creative ideas from you to support and promote to

urbanize the economy.

• Web services should be highly customizable and flexible

enough to easily deploy.

• High dependability/low downtime

Team Size (Maximum) 4

Technologies to be Used UML, Java, 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.

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

Documents

Project Scenario Detailed View

Back

Name of the Project Your own project scenario**

Objective/Vision Write one or two paragraphs here on how your proposed web-

based solution will help users. What problem area it is

targeting?

User of the System Proposed users of your system.

Functional Requirements You must collect and mention atleast eight functional

requirements.

Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be

used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak

time

iv. Flexible service based architecture will be highly desirable for

future extension

Optional Features Add identified optional features of your system.

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 Add identified reports your system provides.

Other Important issues Add any other important issues which have not been covered

under any of above headings.

Team Size (Maximum) 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.

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

DocumentsTGMC09 Scenario - Template.doc

TGMC09 Scenario - Template.doc