1. A Project Summary On
eTL
Prepared By
Ashish Mishra : 110320116003
Nitesh Mehta : 110320116025
Aakash Panchal : 110320116043

2. Project Details
 eTL system manages all the events which are conducted in
college/University.
 This system automatically generate certificate and issue it/mail it.
 System very efficiently store, maintain and retrieve data from its
database and can be use for further analysis(data mining & OLAP).
 This system provides latest notification to its user.
Time saving activity .

3. Propose
Manual hours that need to spend in record keeping and generating
reports.
The data in a centralized way which is available to all the event
managers.
Easy to manage historical data in database.
Participants can register for any happening event from anywhere.
Event manager can keep records of participants.
Easily generate certificates for participants and winners.
Certificates automatically mail to particular participants.

4. Scope
This web application includes the IT fields.
 Secure Administrative panel.
 Normal users are the participants.
 They have to register for the events.
 Users will have following functions:
Easy communication with the manager
 Event time
 Get instant message about any change Updates easily
 Will get winner certificate directly by downloading

5. Hibernate Benefits
Open source and lightweight
framework
 Fast Performance : Two cashes
1)First level cache
2)Second level cache
First level cache is enabled
internally
 Database independent query :
HQL(Hibernate query language)
Database independent query
Automatic table generation

6. Technology
Programming language: JAVA, J2EE
Front-End: HTML, CSS, JavaScript, JQUERY, Ajax, JSP
Hardware interface: 512 MB RAM, WINDOWS 7/8
 Database: MySQL Server
 Web Server: Apache Tomcat 8
 Tools: Eclipse LUNA, SQL yog
 Frame work: Hibernate with MVC

7. Literature
Websites:
http://www.w3schools.com/sql
http://www.javatpoint.com/hibernate-tutorial
http://en.wikipedia.org/wiki/Freelancer
https://www.guru.com
https://www.odesk.com
https://www.peopleperhour.com
Books:
Web application development
Core java (The complete reference)
Advance Java (M. T. Savaliya)
OO Modeling and design with UML.
Software engineering book for SRS.

8. Feasibility Study
Product : eTL is a event management system. By using this system various users can login
and participate in different events. It eases registration process so it’s a user friendly
product.
Operational Feasibility : Operation of the proposed system depend on its various users.
These various user-type mentioned below.
(1)Admin
(2)Manager
(3)Normal User (Participants)/Volunteer
Admin will make managers for different events. And allocate Login ID. Thereafter Normal
User enters their details i.e Name, Enrollment Number, Course, Branch, College and also
select events.
Then manager will check user entries and will allot registration id for authentication
purpose. Manager can also change date, time of the events. Here manager responsible to
check team size, details. And manager is responsible to restrict unauthorized people or
wrong entries.
After these all process Admin will check all detais of user, work of manager. Admin can

9. Technical Feasibility : eTL is a web-application which avoids more manual
hours that need to spend in record keeping and generating reports. This
application keeps the data in a centralized way which is available to all the
event managers. It is very easy to manage historical data in database.
Participants can register for any happening event from anywhere. Event
manager can keep records of participants and system can easily inform them
by message and emails. Using this system, event managers can easily
generate certificates for participants and winners and it’s automatically mail to
particular participants.
Social Feasibility : Proposed system would be acceptable by the other
peoples. Because eTL is better than ordinary registration process and
management in the following issues :
1. Faster than other older systems
2. Database keeps records
3. Time saving

10. Economic feasibility : As no papers required so it
reduce cost. It would be beneficial because only one time
development efforts required. All people are aware of
technologies so no special skills required to run the
system.

11. Scheduling
Requirement Analysis
• Analysis
4 weeks
• Gathering Information
• Determining Requirements
• Defining scope
Design
• Database Design
10 weeks• Design Modules
• Design Input Screen
Implementation
• Development of Module
12 weeks
• Refinement of developed modules
Testing 4 weeks

12. Timeline

13. Gantt Chart
ID Task Name Start Finish Duration
2014 2015
Aug Sep Oct Nov Dec Jan Feb Mar Apr
1 17d25-08-201401-08-2014Requirement Analysis
2 45d07-11-201408-09-2014Design
3 58d30-01-201512-11-2014Implementation
4 29d13-03-201503-02-2015Testing
5 9d27-03-201517-03-2015Deployment
6 23d30-04-201531-03-2015Maintenance

14. System Requirement Study
1) Hardware Requirements
1) The Hardware Requirements are:
 RAM: 512 MB
 Processor: Pentium - IV onwards
 HDD Space: 2 GB or more
2) Software Requirements
2) The Software requirements are:
 Operating System – Windows
 Internet Browser (Mozilla Firefox/Google Chrome/IE 7-8)
 Front End – JSP, Servlet, Hibernate, JSTL, Cloud
 Front End Tool – Eclipse LUNA
 Back End – My SQL
 Web server - Apache Tomcat 8

15. 3) Functional Requirements
R1 : Registration
Description : To enter into this site user has to register himself first. Requirements of
registration are first name, last name, user name, email-id, password, confirm password etc.
Input : User Details
Output : Filled Registration Details.
Processing : User details are checked with database. Password constraint is checked as per
validation.
R2 : User Login
Description : The System provides facility to login into the system.
Input : Enter username and password
Output : User Profile page
Processing : The system will check the input of user and if valid then login is done.
Otherwise user will be asked to re-enter the username and password.

16. Description : The user can select the event and also select payment method.
Input : Main event , Sub event, Enrollment number, Add team member .
Output : Event selected Successfully ,also see all detail and delete also .
Processing : The system will add selected data into database.
R4 : Forgot Password
Description : The user can send reset link to the mail id to reset password.
Input : Email id
Output : Reset link send to Email id.
Processing : By reset link we can easily change the password and update store in database
.
R3 : Select the event

17. Description : The Admin can add manager ,main event ,sub-event also.
Input : main event, sub-event, manager.
Output : Add successfully in database.
Processing : The system will add selected data into database.
R6 : Manager panel
Description :The manager can add volunteer ,main event and sub-event also .
Input :Main event, sub-event , volunteer.
Output : Add successfully in database .
Processing : The system will add selected data into database.
R5 : Admin panel

18. R8 : Logout
Description : The system provides the facility to logout from the site
Input : Select logout option
Output : Logout from the system
Processing : User will logout

19. 4) Non-Functional Requirements
Performance requirements:
 The system need to be reliable
 If unable to process the request then appropriate error message
 Web pages are loaded within few seconds
Safety Requirements:
 The details need to be maintained properly
 Users must be authenticated
 The database must be kept backed up
Security Requirements:
 After entering the password and user id the user can access his profile
 The details of user must be safe and secure
 Sharing of details

20. Flowchart

21. UseCase

22. Sequence Diagrams for Admin

23. Sequence Diagrams for Admin

24. Sequence Diagrams for Volunteer

25. Activity Diagrams

26. DFD O

27. DFD Level : 1

28. Class Diagram

29. Object diagram

30. ER - Diagram

31. Modules
1.Registration – Participants can register online for any event.
2. Event – Event manager can generate event by this module. They can
edit, delete the information of any generated event.
3. Certificate – eTL can generate certificated automatically and system
can mail it to particular participant.
4. Notification – Participants can get notification about event timing,
place or any updates.
5. User Module – User can register for event. Can easily check event
details times and can contact event manager easily.
6. Volunteer Module – Volunteer can view the details of his/her event
participants. Volunteer has to update the winner of his/her event in the
system.
7. Admin Module – DBA has all the rights. He can add, edit, delete any
information in the system. He can add new event, event manager,

32. Thank You