Leave management of IIPS

Overview of Existing System

In International Institute Of Professional Studies the work of leave management of faculties is done manually.Leave Register is used for storing the information.

Register contain the following attribute( Faculty name , Post,Type of leave, Date To, Date From,Total leave,Sign Of HOD, Sign Of Director,Remark,Reason).By

our Proposed system we can manage all the leave of the faculties. Using this system faculties and other user can check their leave Status at any time . And can

apply for leave.

Aim Automate the Casual Leave System for faculties.

Feature of system:

The system should be

1. Single sign On

2. This system should be integrated so that it act as one of the module of iips website.

Report

Date 31.10.12

How can we study the feasibility of system?

Ans.

1. Feasibility study from the view of à Teaching staff , Nonteaching Staff, others.

conclusion: After discussion we will work on the teaching staff module.

( Economical , Behavioral, Technical)

2. By studying the existing system

Discussion between (Misha ,Komal,Chitrank)

1. Faculty fill the leave register than it is approved by the authority. The leave register contain the information. Faculty name ,Post, Leave Date(to ,from), Total days ,Nature of leave, Sign of authority ,Signature of AO ,Remarks

2. This leave register form and application is given to the authority and then verify leave and then give back to faculty.

After this discussion there are some question arises.

1. Which type of system is this? Online or offline(Desktop based) ?

To find out its answer we met with Kirti Ma’m. After meeting with Kirti Ma’m the following points are clear.

What is existing System?

1. Faculty write application for leave with specified date and reasons.

2. This application is taken by head of (computer science / Management) if the reason of the leave satisfied the HOD then HOD forwarded the application to the director sir.

3. Then Director sir give permission for their leave.

4. Once the permission is allowed then Register leave form is filled by clerk.

Please provide following documentation before 30/1/2013

Schedule

- SPMP ?
- Software Project Management Plan (SPMP)
- (which conforms to IEEE SPMP format)
- Gantt Chart ?
- SRS ?
- Submission of Software Requirements
- Specification (SRS)
- (which conforms to IEEE SRS format)
- SDD ? Submission of Software Design Description
- (SDD)
- (which conforms to IEEE SDD format)
- Software Verification and Validation
- Plan (SVVP)
- Software and System Test
- Test plan?
- Implementation and Deployment plan ?
- User Manual/Documentation Plan
- Software Quality Assurance (SQA) Plan
- Demonstration ,submission,User approval
- hard and soft copy of Project Report

Conclusion after meeting with Kirti Ma’mThe first three section can’t be automated.

1. The fourth section is to be automated.

2. The Casual leave count = 13.

Question after discussion.

1. Does HOD Check Status of application?

2. When leave is not allowed? Exam time \ Voting time \ Other activity.

3. How many faculty give leave application to you in per month?

4. Do you check the history of faculty leave status?

5. How many Teachers take leave on same days.

6. Atleast how many leave You can give to faculty at a time?

7. Can leave can be converted to other?

8. Combination of leave is possible or not?

9. If leaves are left then it added to next session or not?

10. If a faculty takes emergency leave and fail to submit the leave application form?

11. Within how many days leave is approved?

Date 15.12.12

Discussion with Shaligram sir about the Existing System and the conclusion after this discussion is that

1. System should be of web based.

2. When system is in working state then it will used parallaly with existing system.

3. So our first step is that we will work on the automation of the Faculty Leave register form .

Date 16.12.12

Discussion ( Chitrank ,Komal)

Data Collection

1. total 13 Casual leave.

2. If in leave duration Sunday occur at the end or at the beginning it can not added to the cl.

3. If the Sunday comes in between the leave duration then the Sunday is counted.

4. If leave is remains in the end of the session and it is not used then it is elaps.

5. Every session start with new 13 Casual leave.

6. Types of leave

i. Casual leave ii. Optional leave (Leaves declared by Govt.

and employee can take 3 leaves from declared leave by Govt.)

iii. Earn leave iv. Medical leave v. Half pay leave v.Leave without pay

User Interface Design

See below the attach file cl_leave_prototype.jpeg (Work done by Chitrank)

Date 24.12.12

Discussion (Komal,Misha,Shiv)

Schema design

1. Leave :

Faculty_name,Faculty-id,Post,Type of leave,Date To,Date From,Remaining leave,Total leave1,Total days of taken leave.

2. Report generate:

Attributes

Faculty name Type of leave Total Remaining

Discussion on User Interface

See below the attach file Prototype_1.pdf (Work done by Shiv)

1.1.13

System Design

About:

I use those attributes which should be required in the implementation.

Entity Description

1. Faculty( Sno,Faculty_name,Post, Date _of_ apply leave, No_of_days, Type of Leave, Date_From

, Date_To, Current_year, Current_month,Status)

1. SNo: this is an auto number each entry has unique SNo.

2. FacultyFirstName: this attribute is used to identify the faculty uniquely

MiddleName: This field is maindatary.

Last _Name: This will be used when the two faculty have the same first name

“ For our first implementation I use only Faculty name(full name)

3. Post: This give the information of faculty’s work area in university.

4. Date _of_ apply leave:

This will be used for following the rules of university.

5. No_of_days:

This is used in updating the status of leave .

(Remaining Leave=Total - No_of_day(for first updation)

Remaining_Leave=Remaining-No_days

6. Type of Leave:

In university Their so many types of leave and each leave have its own rules so this attribute is

Important.

7. Date_From: this attribute give the information about from which date the employee is not

coming in the university.

8. Date_To:

This attribute give the information that upto which date employee is not come in the university.

9. Current_year:

This attribute is useful to store current session. and used in validation and updation of leave.

10. Current_month

This attribute is useful to store current month. and used in validation and updation of leave.

11. Status: This attribute give the information that leave is granted or not granted(two values Granted

,not granted).

2. Leave _table( Sno , Faculty_name, Type_of_leave , Remaining Leave ,Total Leave):

Explaination: Different Different faculties have the different status of different type of leave ,therefore to maintain these I make a different

table which contain the status of each leave.

Attributes:Sno ,Faculty_name,Type_of_leaveRemaining LeaveTotal Leave.

Note : This work is done on the basis of our investigation( there is no involved university rule book rule book.

___________________________________________

Testing

Page updated

Report abuse