Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Software Requirements Specification for E-Leave Management System, Papers of Java Programming

DOCUMENT PAPERS FOR PROJECT FOR FINAL YEAR PROJECT.......

Typology: Papers

2021/2022

Uploaded on 02/11/2022

BEINGDJ
BEINGDJ 🇮🇳

1 document

1 / 16

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software Requirements Specification for Shri Narkesri Prakashan Pvt.Ltd, E-Leave Management System Page 1
Software Requirements
Specification
for
E-Leave Management
System for shri Narkesri
Prakashan Ltd.
Version 1.0
Prepared by
Batch -1 Group-1
1. Akash Hedau, Roll No 23;
2. Vedang Bhange, Roll No 8;
3. Rahul Baviskar, Roll No 7;
4. Abdulrahman Ahmed, Roll
No 1;
5. Umesh Gaikwad, Roll No 17;
FYMCA, Viswakarma Institute of Technology, Pune
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff

Partial preview of the text

Download Software Requirements Specification for E-Leave Management System and more Papers Java Programming in PDF only on Docsity!

Software Requirements

Specification

for

E-Leave Management

System for shri Narkesri

Prakashan Ltd.

Version 1.

Prepared by

Batch -1 Group-

  1. Akash Hedau, Roll No 23;
  2. Vedang Bhange, Roll No 8;
  3. Rahul Baviskar, Roll No 7;
  4. Abdulrahman Ahmed, Roll No 1;
  5. Umesh Gaikwad, Roll No 17;

FYMCA, Viswakarma Institute of Technology, Pune

  • DATE-10 February

3.2 Apply Leave......................................................................................................................................... 11 2.3 User Classes and Characteristics.......................................................................................................... 11 2.4 Operating Environment........................................................................................................................ 11 2.5 Design and Implementation Constraints............................................................................................... 11 2.6 Assumptions and Dependencies........................................................................................................... 12

**3. System Features............................................................................................................................ 12

  1. Non-Functional Requirements.................................................................................................... 13
  2. External Interface Requirements................................................................................................ 13** 5.1 User Interfaces..................................................................................................................................... 13 5.2 Hardware Interfaces............................................................................................................................. 13 5.3 Software Interfaces.............................................................................................................................. 13 5.4 Communication Interfaces................................................................................................................... 14 **6. Specific requirements................................................................................................................... 14
  3. Detailed Use Cases........................................................................................................................ 15
  4. Appendix........................................................................................................................................ 15 Revision History** **Name Date Reason For Changes Version
  5. Introduction** Modern HR Tools can help you remove the friction in the process and let it practically run itself with an inbuilt online leave management system. A leave approval process is one of those things that seems simple on the outside, but actually takes a lot of time if you haven’t set up for it. Once managers receive a leave request, they need to evaluate an employee’s eligibility, check for compliance with leave policies, ensure sufficient staffing for the day, and arrive on a decision that doesn’t impact employee satisfaction. So its proposed to make a leave management system which will facilitate the process of leave and save the time and money of Employees as well as Leave Approval Authorities like HODs and HR.

1.1 Purpose and Intended Audience

Shri Narkesri Prakashan Ltd is Publication company which have around 200 Employees working on daily bases. Since the increased dynamism in the type of roles that have changed in company and new policies announced regarding the Employee leaves. It has created a need for automation of Leave Management system in the company. Where Employee itself can apply through a dedicated app rather than making it large official mails and manual documentations of leave records. Project

shall be made solely as per the requirement specified by the company and every functionality is to be added as per the company standards, policies and rules for Leave. This document aims to specify all the required specifications with regards to the functionalities in the system. The intended audience involves three important 3 stakeholders as end users of this system

  1. The Employees 2. The Departmental Heads 3. The Human Resource authority While system should also provide outcome which helps to find the trends in the leave system

1.2 Project Scope

E-Leave Application system for Shri Narkesri Prakashan Pvt.Ltd is web-based system considering large scope of adaptability. It will provide facilities to apply, approve and document the leave application process in the company in order to consolidate and output considering all the eligibility factors of the respective stakeholders. The leaves system will enable the company's top management to decide for other policies on the basis of trends which will be an outcome of this product. It should also ensure adequate reliability in generating and output which will maintain each employee's record for each process and transaction that has taken place with respect to the leave. The scope extends from apply-approval process to documentation and analytical outcomes Scope extends to all the types of leaves and exceptions to the attendance in Office that are officially authorised by respective authority. It will generate different outputs for different stakeholders considering the three important one as employee, HOD, HR. Issues beyond those identified  Scope of the project does not extend to the salary system but its outcome should be an important document as input to the salary system.  The attributes like leave without pay , Maternity/ paternity leave , leave for official purposes with respect to work permit should also be considered with giving a special comment.  Further more Project will also be flexible to integrate itself with current system ongoing in company and ensure soft technological transition. If this is part of a larger system, or will only include certain features, then note it. Example: This product will address the student record functionality only. It will not store information on professors or courses offered at the University. ”

1.3 Terms, Definitions, and Acronyms

Domain Specific Terms:

i. Leave - It is pre or post applied Request of absence of Employee on certain

it is a leave which is only given to type A Employees which are 10 all over the years and the total stack is 45 same as the Earned leaves that means that every year 10 Sick leaves are credited to Type A employee account and balance is added of last year till the number is 45. Above 45 days. Rest over Leaves are lapsed

xiv. Leave without pay- It is Leave granted in the company either when the all

the balance leaves are lapsed/Consumed or Long span Leave under

special circumstances.

xv. Maternity Leave- It is long span paid leave specifically to Women who are

under pregnancy care which around 24-26 weeks as per government

guidelines. (Can be applied only 2 times)

xvi. Medical certificate- It is an official document of proof to be submitted by

Employee applying for sick Leave more than 2 days which is to be signed

by licensed Medical Practitioner (Doctor).

xvii. Leave for official Purposes -Tour- It is an absence of Employee in the

company for some official work. Official work permit document is to be

submitted by respective department validating his/her office absence

xviii. Work Permit- Official document to generated by HOD of department for

validating the Tour Leave.

xix. Monthly Leave Report- It is report which is to be generated by the system

as output in order to find the trends in leave Apply-Approval Process.

xx. Leave Balances- Records of Leave with types visible to Employee, HOD, HR

of No leaves consumed and remaining

Technical Terms used in Application

i. Login – User Authentication page available to all the user with their unique

employee id and password ensuring security.

ii. Employee Id- Unique Id issued by company to Employee

iii. Profile – Web page which includes individual Leave information current

available and consumed leaves.

iv. Apply for Leave- Web page form for application of leave

v. Leave Balance- Account of number leave currently available

vi. Leave Calendar- Calendar including information about Weekly leaves,

Yearly leaves of press, and Applied leaves by person.

vii. Leave transaction history’- Transaction history of Apply approval process

of leave with status of approval or disapproval

viii. Leave reason – Comment explaining the reason for leave

ix. Approval- Sanctioning the Leave Request

x. Approval Notification- The Notification message to respective account

about approval/disapproval at HOD side and message of

approval/disapproval at Employee side.

1.4 References

2. Overall Description

2.1 Product Perspective

The website is aimed with idea to facilitate the leave system in whole, provide an output to other system working in the company like

  1. Salary Management System
  2. Appraisal Records
  3. Employee Portfolio etc It will also integrate the current leave system ongoing in the company and also adapt to it providing flexible outputs as per required. .

2.2 Product Features

1.1 User Classes and Characteristics

There are three types of users for System are they are as follows ● Employees Verified Employees are those users who have an active account to use Leave system. They have access to E-LMS. ● HOD HOD can verify number of leaves available, Current individuals on work depending on that can grant the leave. He can see all that information which will make him ensure that granting leave won’t cost the daily work at company ● HR Payment

  1. Web Application must follow the standard design which includes the typography, colours, universal margin and paddings.
  2. Interface should ensure adequate usability of all the types of User and also guide through appropriate headings to understand and implement and adopt faster

2.2 Server & Hosting Interface Requirements

The system uses Local Server’s Service for its API and database maintenance. The Server should offer kubernetes and PHP files to return in documentable format.

2.3 Software Interfaces

This system uses javascript for front-end to give a uniform and minimalistic user interface. This system requires an server compatible container for php.

2.4 Communications Interfaces

For Centralised Database communications such as retrieval and insertion, an API is to be developed. The API must support various parameters and should also have ability to work with multiple parameters. The API must use https and however there is no key required for retrieval of information.

3. System Features This subsection contains the features and functions that E-LMS System possesses_._ Features and Functions are organised by functionality/action.

3.1 Employee Registration

4.1.1 Description and Priority This component enables a user to register himself as a Employee. Registering as a Employee enables a user to know the past leave transaction and control further such transactions. 4.1.2 Stimulus/Response Sequences This component is required when a user access E-LMS website. Upon successful completion of this component, a Employee is added to the database and is given access to the dashboard. 4.1.3 Functional Requirements

  1. The user needs an active Internet connection.
  2. The user needs an active Mobile Phone Number and be able to receive a text message.
  3. The user has an android phone/Mac from where any website can be visited.

3.2 Apply Leave

There shall be of the features that the product will possess. As an example, for an accounting program the features might include customer account maintenance, preparation of customer statement, and invoice preparation without mentioning the vast amount of detail that each of those functions requires. Features should generally correspond to major functional capabilities of your product and might be something that you would want to include in advertising literature if you were going to market the product commercially. The features should be organized in a way that makes them understandable to the customer or to anyone else reading the document for the first time. Features should be identified and described in terms common to the user's or problem's domain. They are not to be confused with specifying the structure of individual portions of programs or subprograms.

2.3 User Classes and Characteristics

This section describes (in general terms) the computer experience and knowledge of the potential user. This section provides the foundation for the performance and usability requirements addressed within Section 3.

2.4 Operating Environment

What kind of environment (single/multiple locations, retail, academic, outdoor, etc.) is the system intended to be operated in? Instructor Note: how, where, under what conditions the system would be used.

2.5 Design and Implementation Constraints

This section details all constraints upon the product being developed, whether customer mandated or policy/regulatory requirements, e.g., a particular operating system. Instructor Note: limitations on the requirements and/or operating conditions or design requirements that must be satisfied or met.

4. Non-Functional Requirements  Here you will Address FURPS+ (Group by Category) Instructor Note: This section is either FURPS+:  Functionality –  UsabilityReliabilityPerformanceSupportability+ Miscellaneous OR you can use the 4 non-functional requirements shown on p.90 of the textbook:  Operational -  PerformanceSecurityCultural / **Political

  1. External Interface Requirements**

5.1 User Interfaces

This section describes any external system user interfaces that may be required by the system, e.g., a console window.

5.2 Hardware Interfaces

This section describes any external system hardware interfaces, e.g., an analog to digital converter that may be required by the system.

5.3 Software Interfaces

This section describes any external software interfaces, e.g., input files to this system that were created by another software system.

5.4 Communication Interfaces

This section describes any external communication interfaces, e.g., TCP/IP communication sockets that are necessary for the operation of this system.

6. Specific requirements

  1. Specific requirements to Employees i. The Employees must be able to see the Their own current balance leave with real time in system info which and also HR will see as same info of employees. ii. The requirement of such Tool which is used to Apply for Leave (such as Application form) iii. Security measures (Protected Login)- Whole system is made along with all specific security measures, all credentials must be abstract as per use, system should not allow any third party to get access to the system without any authentication.
  2. specific requirements to Heads of Respective Departments (HODs) i. Every employee must have Balance Leaves available with each respective Department. ii. There should have Options to Approve the Leave Application of employees. and also, in case of Rejection of the application and also provided facility of send message back to employee. iii. HOD should able to see the calendar with future applied leaves of Employees iv. Security Measures (Unique protected login)-There must be highly scecured login available to HOD ,All Security Constraints must be Applied , all credentials must be abstract as per user ,system should not allow any third party to get access to the system without any authentication.
  3. specific requirements to Human Resource Manager i. Every employee must have Balance Leaves available with each respective Department. ii. There should have Options to Approve the Leave Application of employees. and also in case of Rejection of the application and also provided facility of send message back to employee. iii. Manager should able to see the calendar with future applied leaves of Employees iv. The generation a master report of all the Employees with special comments (Leave without pay, Maternity/Paternity Leave and Official Tour leave) All types of leaves ,Number of Leaves taken by employee,Balance leave of employees,Number of Approved leaves of employees and Rejection of leaves v. Security Measures (Unique protected login )-There must be highly scecured login available to Manager ,All Security Constraints must be Applied ,

Delete the first page , any unused language from the

original template <for example, the instructions under Appendix>, and all Instructor

Notes before submitting.