Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
DOCUMENT PAPERS FOR PROJECT FOR FINAL YEAR PROJECT.......
Typology: Papers
1 / 16
This page cannot be seen from the preview
Don't miss anything!
Batch -1 Group-
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
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
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. ”
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
2. Overall Description
The website is aimed with idea to facilitate the leave system in whole, provide an output to other system working in the company like
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
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.
This system uses javascript for front-end to give a uniform and minimalistic user interface. This system requires an server compatible container for php.
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.
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
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.
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.
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.
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 – Usability Reliability Performance Supportability + Miscellaneous OR you can use the 4 non-functional requirements shown on p.90 of the textbook: Operational - Performance Security Cultural / **Political
This section describes any external system user interfaces that may be required by the system, e.g., a console window.
This section describes any external system hardware interfaces, e.g., an analog to digital converter that may be required by the system.
This section describes any external software interfaces, e.g., input files to this system that were created by another software system.
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
