Escolar Documentos
Profissional Documentos
Cultura Documentos
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
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
Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA
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
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
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
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
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
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
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
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
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
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
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
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
Documents
Project Scenario Detailed View
Back
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
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.
Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA
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
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
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
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.
Other Important issues A. The Project Can be developed using either two tiers or three
tiers Architecture
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
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
Other Important issues A. Website must be highly customizable, interactive and user
friendly.
B. Security should be kept a high priority issue.
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
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
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 .
Other Important issues 1. Web application should be highly optimized and easy to use.
2. Application should be scalable (considering future prospects)
Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA
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
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.
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
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
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
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.
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
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
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.
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.
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
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.
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
More over the system need to be available for Access over the
web anytime, anywhere.
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
Other Important issues Take a look to the project management softwares already
available.
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
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
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
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
Other Important issues A. Website should be highly customizable and flexible enough
to easily deploy.
B. Facilities for Localization and Internationalization should be
available.
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
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
Other Important issues A. Website should be highly customizable and flexible enough
to easily deploy without much effort.
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
Objective/Vision A solution that not only caters to the need of a Stock Broking
firm but is also scalable without compromising on performance.
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.
Technologies to be Used UML, J2EE, XML, AJAX, Web 2.0, Web-services, SOA
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
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
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
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.
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.
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
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
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
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?
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
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
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
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
Other Important issues • Any creative ideas from you to support and promote to
urbanize the economy.
Technologies to be Used UML, Java, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
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
Objective/Vision Write one or two paragraphs here on how your proposed web-
based solution will help users. What problem area it is
targeting?
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
Other Important issues Add any other important issues which have not been covered
under any of above headings.
Technologies to be Used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
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