SCHOOL 

OF COMPUTER APPLICATIONS
UNION CHRISTIAN COLLEGE ALUVA

SOFTWARE REQUIREMENTS SPECIFICATION

ON

MCA LEAVE APPLICATION

Internal Guide:
Submitted By
Ms Sherna Mohan
Mr Ashik Joy

Mr Basil Babu

S4 MCA

Submitted On: 24/08/2020

MCALA SRS

Contents
1. EXECUTIVE SUMMARY.............................................................................................................................3
2. PROJECT OVERVIEW................................................................................................................................4
2.1. OBJECTIVE OF THE PROJECT.............................................................................................................4
2.2. STAKEHOLDERS.................................................................................................................................4
2.3. SCOPE OF THE PROJECT....................................................................................................................5
2.4 FEASIBILITY ANALYSIS........................................................................................................................5
2.4.1 Technical feasibility.....................................................................................................................5
2.4.2. Operational feasibility................................................................................................................6
2.4.3. Schedule feasibility....................................................................................................................6
3. OVERALL PROJECT PLANNING.................................................................................................................7
3.1 Development environment................................................................................................................7
3.2 Constraints.........................................................................................................................................7
3.3 Assumptions and Dependencies........................................................................................................8
3.4 Risks...................................................................................................................................................8
3.5 Process model....................................................................................................................................9
4. ITERATION PLANNING...........................................................................................................................10
4.1. Schedule.........................................................................................................................................10
4.2. Risks................................................................................................................................................11
5. HIGH LEVEL SYSTEM ANALYSIS..............................................................................................................12
5.1 User characteristics.........................................................................................................................12
5.2. Summary of system features/Functional requirements.................................................................12
5.2.1. Administration.........................................................................................................................12
5.2.2 Registration...............................................................................................................................12
5.2.3 Manage Leave...........................................................................................................................13
5.3 Non Functional Requirements.........................................................................................................14
5.3.1 Database:..................................................................................................................................14
5.3.2 Security:....................................................................................................................................14
5.3.3 Performance:............................................................................................................................14
5.3.4 Backup and Recovery:...............................................................................................................14
5.4 Use case...........................................................................................................................................14
5.5 Use case diagram.............................................................................................................................15

UCC-MCA
MCALA SRS

1. EXECUTIVE SUMMARY

Every organization, whether big or small has challenges to overcome and managing the
information of faculty, student, leave details. Every Leave Application has different leave needs.
The objective of this project is to automate leave management. With the help of this application
users can apply leave through online, Head of the department can approve and can update leave
status online. The user can see the status of all leave taken and their remaining leave through this
application. Head of the department can view the leave status of all staffs with the help of this
application. The work flow is designed in such a way that the leave system generates notification
to the respective users. Head of the department them to act upon.

Leave management system is very simple to understand, easy to use and more convenient for
implementation. The major use of designing such an application is to provide faculty better way
for scheduling and calculating their leave details. As the existing system increases the paper
work and record maintenance which is a tedious work, so there is a need of new system which
makes the record maintenance easy that is the common requirement for the management or an
organization.

2. PROJECT OVERVIEW

UCC-MCA
MCALA SRS

2.1. OBJECTIVE OF THE PROJECT

The main objective of the project on Mca Leave Application is to automate leave

management. Users (Student and Faculty) can apply leave through online. User can see the status
of all leave taken and their remaining leave through this application. User will receive notifications
when your leave is approved/rejected. It manages all the information about leave, leave type.
The project is totally built at administrative end and thus only the administrator is
guaranteed the access. The purpose of the project is to build an application program to
reduce the manual work for managing the leave, faculty, leave records. It records all the
details about the leave records, approvals, leave type.

2.2. STAKEHOLDERS
Head of the department

In this module the Hod has the privileges to add all the Faculty and
Student ,register them in the application and check the information of the Faculty,
students and check the status of the leave when they have taken and what type of leave
they have taken and search is done based on the faculty and can approve the leave of the
faculty.

Faculty

In this module the Faculty has the privileges to add leave and check the
information of the Faculty, check the status of the leave when they have taken and what
type of leave they have taken. Faculty can also approve the leaves.

Student

In this module the Student has the privileges to add leave and check the information of
the Student check the status of the leave when they have taken and what type of leave
they have taken.

2.3. SCOPE OF THE PROJECT

Mca Leave Application is to manage the details of leave, leave records, approvals, leave
type. It manages all the information about leave, leave type. The project is totally built at
administrative end and thus only the administrator is guaranteed the access. The purpose

UCC-MCA
MCALA SRS

of the project is to build an application program to reduce the manual work for managing
the leave, faculty, leave records. It records all the details about the leave records,
approvals, leave type.

2.4 FEASIBILITY ANALYSIS

2.4.1 Technical feasibility

The Mca leave Application is an web application. The main technology and tools
that are associated with Mca Leave Application are:

• PHP

• MySQL server 5.1

• Wampserver

Technical feasibility canters around the existing computer system (hardware and
software etc.) and to what extend it support the proposed addition. If the budgets are serious
constraints, then the project is judged not feasible. The procedure is to determine the
benefits and savings that are expected from a system and compare them with cost.

In this project, all the necessary cautions have been taken care to make it technically
feasible. Here the system is developed using php for user interface designing and coding,
Mysql for maintaining the database, which is faster, flexible and stable. Technical feasibility
is computer oriented. Now a day the hardware cost is comparatively less. The existing
technology can support the proposed system to a high extend and hence the new system is
technically well feasible.

2.4.2. Operational feasibility

Here the user only need to have the general knowledge of browsing internet and
he/she need to register in order to access the web application and for doing other respective
tasks.

UCC-MCA
MCALA SRS

2.4.3. Schedule feasibility

A project will fail if it takes too long to be completed before it is useful. Typically
this means estimating how long the system will take to develop, and if it can be completed
in a given time period. The outcome of this study is proved to be positive for the proposed
system.

3. OVERALL PROJECT PLANNING

3.1 Development environment

The main software and hardware technology used is as follows-

Software Requirements

Operating System : Windows XP/Windows 7

UCC-MCA
MCALA SRS

Language : PHP

Back End : MYSQL Server

Browser : Any of Mozilla, Opera, Chrome etc

Software Tool Kit : XAMP

Hardware Requirements

Processor : Pentium III 630 MHz

RAM : 128 MB

Hard Disk : 20 GB

3.2 Constraints
 MySQL server is used as SQL engine and database
 Correct username and password must be provided for login.
 User must be aware to enter correct data into databases

3.3 Assumptions and Dependencies

The assumptions are:

 The coding should be error free

 The system should be user friendly so that the users can easily access data
 The system should have more storage capacity and provide fast access to database
 The system should provide system search facilities and provide quick search results
 The system should save money and time unlike the existing system
 The user must provide correct user name and password to enter to the system.

The dependencies are:

UCC-MCA
MCALA SRS

 The specific hardware and software due to which the product will run
 On the basis of listing requirements and specification, the system will be
developed and run
 The end-users should have knowledge about the system
 Updates are to be made correctly and data entered without any mistakes

3.4 Risks
Risk is future uncertain events with a probability of occurrence and a potential for loss.
Risk identification and management are the main concerns in every software project.
Effective analysis of software risks will help to effective planning and assignments of work.
The main risk that, we face in this software solution are,

• Any changes in the requirements may lead to the change in the entire solution.

• If the scope of the project is more widen then it may affect the budget of the software.

• If no advance technology is available it may lead to a risk.

• Wrong time estimation- If the software is not developed within the time duration it
may lead to a risk.

3.5 Process model

We choose Iterative Process model in which the system requirements are analyzed,
designed, implemented and deployed. The iterative process model is a step by step
procedure in which it performs sequential design process, often used in software
development processes, through the phases of Analysis, Requirement Specification, Design,
Implementation, Testing and Integration and Operation and Maintenance.

If in the beginning of the project failures are detected, it takes less effort (and
therefore time and money) for this error. It is believed that the phases are correct before

UCC-MCA
MCALA SRS

proceeding to the next phase. In the iterative process model laid the emphasis on
documentation.

4. ITERATION PLANNING
4.1. Schedule
Project planning is the most importance phase of a software development life cycle. The project
plan discusses what should be done and how it should be done to reach the final goal. It is unlike
any other project activity because software is contracted in mind and one personnel
interpretations are not the same as another’s, even both are involved in the same software
project. These differences in options are the core of software errors. Therefore, a specific,
detailed project plan must be developed.

Project planning means plotting activities against a time frame and developing a network based
on an analysis of the tasks that must be performed to complete the project. The basic goal of
planning is to look into the future, identify the activities that need to be done to complete the
project successfully. A good plan is flexible enough to handle the unforeseen events that
inevitably occur in lagged project.

Task July Aug Sept Oct Nov

Requirement gathering

UCC-MCA
MCALA SRS

System analysis

System design

Form design

Coding

Testing

Build

4.2. Risks
Risk is future uncertain events with a probability of occurrence and a potential for loss. Risk
identification and management are the main concerns in every software project. Effective
analysis of software risks will help to effective planning and assignments of work. The main
risk that, we face in this software solution are,

Any changes in the requirements may lead to the change in the entire solution. If the scope
of the project is more widen then it may affect the budget of the software. If no advance
technology is available it may lead to a risk. Wrong time estimation- If the software is not
developed within the time duration it may lead to a risk.

UCC-MCA
MCALA SRS

5. HIGH LEVEL SYSTEM ANALYSIS

5.1 User characteristics
The users under the system are Admin (hod) and Faculty and student. The entire system
is under the control of the admin. User can be Facultys or Students of the college. The users
must need knowledge about basics of computer and about the browsing web applications.
User characteristics that are expected to use the proposed system are,

• User need to know how to browse web application in internet.

• User needs to know basics of computer.

• The user needs to know English.

5.2. Summary of system features/Functional requirements

The system functions can be described as follows:

5.2.1. Administration
Introduction : In this section admin can approve the leave and manage faculty and
students details.

Inputs : Admin can approve/reject the leave application.

Processing : Leave status get updated.

Outputs : View leave of faculty, student, approve/reject the leave application.

UCC-MCA
MCALA SRS

5.2.2 Registration
Introduction : Faculty and student should register in the application

Inputs : For Faculty Faculty_id, Name, Address, Subject and For Student
Student_id, Name, departments and request leave.

Processing : Send details to admin.

Outputs : Faculty and student will get username and password for login.

5.2.3 Manage Leave

Introduction : Faculty and student can request leave, check leave status, approve
leave

Inputs : Leave Date, Reason.

Processing : Send leave details to admin.

Outputs : Faculty and student can track their leave status from admin. And get
notification when approved / rejected.

5.2.3.1 Request leave

Introduction : Faculty and student should login and can request leave.

Inputs : Leave Date, Reason.

Processing : Send leave details to admin.

Outputs : View the leave details.

5.2.3.2 Leave Status

Introduction : Faculty and student can track their leave status.

Inputs : By pressing the leave status button.

Processing : Leave status can be viewed.

Outputs : Faculty and student can track their leave status from admin.

5.2.3.3 Approve Leave

Introduction : Faculty can update the leave status of the student.

Inputs : Faculty can approve/reject leave of student.

UCC-MCA
MCALA SRS

Processing : Leave status get updated.

Outputs : Get notification when approved/rejected.

5.3 Non Functional Requirements

5.3.1 Database:
The database consists of several tables needed to store the all kind of necessary information
related to admission process.

5.3.2 Security:
Security systems need database storage just like many other applications. Before any user
can access the system, they shall be required to input a username and password.

5.3.3 Performance:
System provides good performance.

5.3.4 Backup and Recovery:

The details of online admission system is backed up which will be done at regular intervals.

5.4 Use case

 Admin : Admin add the department, faculty and student and approve leave
 Faculty: Faculty applies for leave.
 Student: Student applies for leave.

UCC-MCA
MCALA SRS

5.5 Use case diagram

UCC-MCA