[Yea

r]

AMRITA SCHOOL OF ARTS AND

SCIENCE

LEAVE
MANAGEMENT
[Type the document subtitle]
Synopsis
This document contain the synopsis for “LEAVE
MANAGEMENT”

[Pick the date]

[Type text]

Table of Contents

Purpose..............................................................................................................................................4
Scope.................................................................................................................................................4
The scope of this portal is to provide a person (administrator), get full details about the leave
taken by the faculity members , in Amrita School of Arts and Sciences..........................................4
Definitions, Acronyms and Abbreviations........................................................................................4
References.........................................................................................................................................5
Technologies to be used....................................................................................................................5
Overview...........................................................................................................................................6

Overall Description....................................................................................................................................6
Product perspective:..........................................................................................................................6
Use-Case Model Survey....................................................................................................................9
Architecture diagram & database design.........................................................................................12
1.1Assumptions and Dependencies.................................................................................................14

Specific Requirements ............................................................................................................................14

Use-Case Reports............................................................................................................................14

TEAM DETAILS

TEAM MEMBERS:
2
[Type text]

ARUN JOY

GOPIKRISHNAN.G.S

HARIPRASAD

HARIKUMAR

PROJECT GUIDE:

Mr.MUKUNTH

LEAVE MANAGEMENT
1. Introduction
1.1 About “LEAVE MANAGEMENT”
The portal “LEAVE MANAGEMENT” is to deliver a full package of information
about the leave that the faculity was taken.

3
[Type text]

Purpose
This portal “LEAVE MANAGEMENT” is being made to offer information about the
leave that faculity of Amrita School of Arts and Science was taken.

Scope

The scope of this portal is to provide a person (administrator), get full details about
the leave taken by the faculity members , in Amrita School of Arts and Sciences.
There are basically 2 types of users namely

1. Administrator
2. Faculty members(Permanent/Temparory)

It also provides a user friendly set of WebPages that are easy to

navigate and at the same time provides information about the
various faculity members. This portal also gives search facility for
finding specified faculity members.

Benefits of using this website include:

 Information about the faculity of“Amrita School of Arts and

Sciences”, Mysore.
 Details about
i. Courses
ii. Faculty members(Permanent/Temparory)
iii. Department

 Current information about college.

 Search facility of faculty, and department.
 Add,delete,update,search of faculty Leaves

Definitions, Acronyms and Abbreviations

• DB2: DB2 Database is the database management system that
delivers a flexible and cost effective database platform to build
robust on demand business applications

4
[Type text]

• EJB: Enterprise Java Beans

• HTTP: Hypertext Transfer Protocol is a transaction oriented
client/server protocol between web browser & a Web Server
• HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL
(secure socket layer)
• HTML: Hypertext Mark up Language is a mark up language used
to design static web pages
• J2EE: Java 2 Enterprise Edition is a programming platform— part
of the Java Platform—for developing and running distributed
multitier architecture Java applications, based largely on modular
software components running on an application server.
• RDA: Rational Data Architect is a Database Design and Modeling
tool.

References
• Problem definition provided by IBM.
• Mastering UML with Rational Rose- Wendy Boggs, Michael Boggs

Technologies to be used
• J2EE: Application Architecture
• Rational Software Architect: Development Tool
• Rational Data Architect: Data Base Designing Tool
• ApacheTomcat Application Server: Application Server
• DB2 v9.1: Database
The software uses DB2 9.1 database. The following features of
DB2 9.1 were

utilized for the development of the software :

 Storage optimization - Reduces the cost of storing data & improve

system efficiency
 Advanced access control - Minimizes the risk of unauthorized access

5
[Type text]

Overview
This SRS includes two sections

• Overall Description will describe major components of the system,

interconnection and external interfaces.
• Specific Requirements will describe the functions of actors, their
role in the system and constraints.

Overall Description

Product perspective:
• The WebPages are presented to provide a user interface to the users.
Communication between the client and server is provided through HTTP/HTTPS
protocols.
6
[Type text]

• This portal is a new portal and has no earlier versions. a future version may be
needed to incorporate new ideas that are learned from this version
• The administrator is provided with a client so that he can create and manage every
actor in the system.

External
Database
s (XML
format)

USER
Internet

Websphe
re
WEB HTTP/HTTP
Applicati
BROWS S
on Server DB2
ER
Intranet

ADMINISTRAT 7
OR
[Type text]

Software Interface
Sl
No

1 Client on the Web browser, Operating System(Any)

Internet

2 Client on the Web Browser, Operating System(any)

Intranet

3 Application Server WAS, Operating System(Any)

4 Database Server DB2, Operating System(Any)

5 Development Rational Software Architect(J2EE, Java,

Environment EJBs, Servlets, OS(Windows), DB2)

Hardware Interface

Sl No

1 Client on the Web browser, Operating

Internet System(Any)

2 Client on the Web Browser, Operating

Intranet System(any)

3 Application Server WAS, Operating System(Any)

4 Database Server DB2, Operating System(Any)

5 Development Rational Software Architect(J2EE,

Environment Java, EJBs, Servlets, OS(Windows),
DB2)

8
[Type text]

Use-Case Model Survey

ADMINISTRATOR
HEAD OF DEPARTMENT
SEARC

LEAVE

SEARCH
UPDAT
STAFF DETAILS

UPDAT
LEAVE OF FACULTYMEMBERS
LEAVE DETAILS

APPLY FOR

DELETE

FACULTY
MEMBERS

9
[Type text]

• Administrator: Responsible for managing users,viewing details of

courses,faculty members Leaves etc
 Managing users: The administrator is responsible for managing the users
that are registered to the portal, add or update current users, delete or ban
certain registered users. .
 Report creation: Administrator is responsible for creating reports of
various kind like details of registered users, number of users registered, reports
about leave of faculty members etc
 View details: the administrator can view all the details like registered user’s
details(add, delete, update, and search).

• Faculty Members: Faculty members can login for applying leaves ,

search,view the leave details,for leave conformation etc.

 Log in
 Apply for Leave
1. Types of leave
 Delete
 View the Leave Details

10
[Type text]

11
[Type text]

Architecture diagram & database design

FACULTY
MEMBER
S

DATABASE DESIGN

12
[Type text]

REGISTRATION

NAME

PASSWORD

DESIGNATION ID IS A

DEPARTMENT

ADDRESS

HEAD OF ADMINISTRATOR FACULTY MEMBER

DEPARTMENT
LEAVE APPROVAL LEAVE DETAILS
LEAVE APPROVAL
SEARCH APPLY FOR LEAVE
SEARCH
DELETE DELETE
DELETE
UPDATE
UPDATE
LEAVE OF FACULTY
MEMBERS

STAFF DETAILS

IS A

PERMANENT STAFF
TEMPARORY STAFF
TYPES OF LEAVES
MONTHLY LEAVE

13
[Type text]

1.1Assumptions and Dependencies

 Administrator is created in the system already.

 Roles and tasks are predefined.

Specific Requirements

Use-Case Reports

Administrator: Responsible for managing users, viewing logs, viewing details of

courses,staff,department,facility etc
 Managing users: The administrator is responsible for managing the
users that are registered to the portal, add or update current users, delete or ban
certain registered users.
 Report creation: Administrator is responsible for creating reports of
various kind like details of registered users(faculty members),number of users
registered, reports about the leave that the faculty members have been taken ,
department, etc
 View details: the administrator can view all the details like registered user’s
details (add, delete, update, and search).

Managing users :

MANAGE USER

ADMINISTRATOR LEAVE APPROVAL

VIEW DETAILS STAFF

VIEWING THE
LEAVE OF USERS

14
[Type text]

Name of use case: Manage user.

 Actor: Administrator

 Description: View the details of the user.

 Preconditions:

• The administrator is already logged in.

 Normal flow of events:

• Select user.

• Query is submitted.

• The output is shown.

 Alternate flow of events: None.

 Post Condition: None.

SELECT USER

[ROL

PERMISSIONS WHICH
ARE ASSIGNED TO USER

[SYSTEM

DETAILS

15
[Type text]

Name of use case: View details

 Actor: Administrator

 Description: View the details of staff leaves.

 Preconditions:

• The administrator is already logged in.

 Normal flow of events:

• Log in.

• Query is submitted.

• The output is shown.

 Alternate flow of events: None.

 Post Condition: None.

Log in

Display error

Leave Details showing

16
[Type text]

Name of use case: creating report of registered user.

 Actor: Administrator

 Description: A report of selected user is created.

 Preconditions:

• The administrator is logged in.

• Users are already created .

 Normal flow of events:

• A registered user is selected.

• Query is submitted.

• All the user details are shown

• Query is submitted to create a report.

 Alternate flow of events: None.

Post Condition: a report of the user containing all the details is created

REGISTERED USER

USER DETAILS NO USER

REPORT

17
[Type text]

STAFF: Three types of staff include H.O.D(Head Of Department),Permanent Lectutre and Temparory
Lecture. Permanent Lectutre and Temparory Lecture can log in using log in id and password. Log in
users can apply for leave ,can view leave details, delete their own leave details.

Name of use case: Log in

 Actor : H.O.D (Head Of Department)

 Description : using user id and password teaching staff can log in

 Precondition :

• The portal’s server system is working.

 Normal flow of events :

• Entering user name and password

• Viewing the leave request of Lecture

 Alternative flow of events : None

 Post condition: Portal can be viewed by the user in the browser.

TYPE USER ID AND PASSWORD

VIEWING THE LEAVE DETAIL OF LECTURES

Name of use case: Leave Approval

18
[Type text]

 Actor : Head Of Department

 Description : Approve the leave request which has been sent by lecture and it will send
to principal

 Precondition :

• Entering user name and password of H.O.D

 Normal flow of events :

• Leave Request Verified

• Sent to Principal for leave Permission

 Alternative flow of events : None

 Post condition: Portal can be viewed by the user in the browser.

LEAVE REQUEST VERIFIED

SENDING TO PRINCIPAL FOR VERIFICATION

SUCESSFULL

Name of use case: Leave Request of Permanent Lecture

 Actor : Permanent Lecture

19
[Type text]

 Description : Leave Request done by permanent Lecture

 Precondition :

• Entering user name and password

 Normal flow of events :

• Type of Leave

• Apply for Leave

 Alternative flow of events : None

 Post condition: Portal can be viewed by the user in the browser.

SELECT THE TYPE OF LEAVE

SUCESSFULL

Name of use case: Leave Request of Temporary Lecture

 Actor : Temparory Lecture

20
[Type text]

 Description : Leave Request done by temporary Lecture

 Precondition :

• Entering user name and password

 Normal flow of events :

• Monthly Leave

• Apply for Leave

 Alternative flow of events : None

 Post condition: Portal can be viewed by the user in the browser.

SELECT A LEAVE

SUCESSFULL

Name of use case: Update Lecture information

 Actor : H.O.D (Head Of Department)

21
[Type text]

 Description : Update Lecture information from database

 Precondition :

• Entering user name and password

 Normal flow of events :

• Select the Lecture

• Update the Details

 Alternative flow of events : None

 Post condition: Portal can be viewed by the user in the browser.

SELECT THE STUDENT

UPDATE THE DETAILS

Name of use case: Delete Lecture information

22
[Type text]

 Actor : H.O.D(Head Of Department)

 Description : Delete Lecture information from database

 Precondition :

• Entering user name and password

 Normal flow of events :

• Select the Lecture

• Delete the Details

 Alternative flow of events : None

 Post condition: Portal can be viewed by the user in the browser.

SELECT THE STUDENT

DELETE THE DETAILS

23