Downloaded 12 times
![Data Dictionary
Table 5.1.1 [student]
Field Name Data Type(Size) Constrain
id INT(11) Primary Key
first_name VARCHAR(255) NOT NULL
middle_name VARCHAR(255) NOT NULL
last_name VARCHAR(255) NOT NULL
mobile BIGINT(20) Unique Key
email VARCHAR(255) Unique Key
city VARCHAR(255) NOT NULL
department VARCHAR(255) NOT NULL
semester ENUM NOT NULL
enrollment_no VARCHAR(255) NOT NULL
password VARCHAR(255) NOT NULL
leave_count INT(11) NOT NULL
url VARCHAR(255) Unique Key
is_active ENUM NOT NULL](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-21-2048.jpg)
![ Table 5.1.2 [master]
Field Name Data Type(Size) Constrain
Id INT(11) Primary Key
name VARCHAR(255) NOT NULL
Mobile BIGINT(20) NOT NULL
user_name VARCHAR(255) NOT NULL
password VARCHAR(255) NOT NULL
is_activa ENUM NOT NULL](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-22-2048.jpg)
![ Table 5.1.3 [faculty]
Field Name Data Type(Size) Constrain
id INT(11) Primary Key
first_name VARCHAR(15) NOT NULL
middle_name VARCHAR(255) NOT NULL
last_name VARCHAR(255) NOT NULL
mobile BIGINT(20) Unique Key
email VARCHAR(255) Unique Key
city VARCHAR(255) NOT NULL
department VARCHAR(255) NOT NULL
Semester ENUM NOT NULL
user_name VARCHAR(255) NOT NULL
Password VARCHAR(255) NOT NULL
url VARCHAR(255) Unique Key
is_active ENUM NOT NULL](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-23-2048.jpg)
![ Table 5.1.4 [leave]
Field Name Data Type(Size) Constrain
id INT(11) Primary key
leave_type VARCHAR(255) NOT NULL
start_date VARCHAR(255) NOT NULL
end_date VARCHAR(255) NOT NULL
day_count INT(11) NOT NULL
reason TEXT NOT NULL
current_date DATE NOT NULL
enrollment_no BIGINT(20) Unique Key
name VARCHAR(255) NOT NULL
semester ENUM NOT NULL
department VARCHAR(255) NOT NULL
url VARCHAR(255) NOT NULL
status ENUM Unique Key](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-24-2048.jpg)
![ Table 5.1.5 [bonafide_certificate]
Field Name Data Type(Size) Constrain
id INT(11) Primary key
name VARCHAR(255) NOT NULL
enrollment_no VARCHAR(255) NOT NULL
branch VARCHAR(255) NOT NULL
semester ENUM NOT NULL
mobile_no VARCHAR(255) NOT NULL
dob VARCHAR(255) NOT NULL
apply_date VARCHAR(255) NOT NULL
reason VARCHAR(255) NOT NULL
status ENUM NOT NULL
url VARCHAR(255) NOT NULL](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-25-2048.jpg)
![ Table 5.1.6 [fee_structure]
Field Name Data Type(Size) Constrain
id INT(11) Primary key
name VARCHAR(255) NOT NULL
enrollment_no VARCHAR(255) NOT NULL
branch VARCHAR(255) NOT NULL
semester VARCHAR(255) NOT NULL
mobile_no VARCHAR(255) NOT NULL
dob VARCHAR(255) NOT NULL
apply_date VARCHAR(255) NOT NULL
for VARCHAR(255) NOT NULL
reason VARCHAR(255) NOT NULL
status ENUM NOT NULL
url VARCHAR(255) NOT NULL](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-26-2048.jpg)
![ Table 5.1.7 [railway_pass]
Field Name Data Type(Size) Constrain
id INT(11) Primary key
name VARCHAR(255) NOT NULL
enrollment_no VARCHAR(255) NOT NULL
branch VARCHAR(255) NOT NULL
Semester VARCHAR(255) NOT NULL
mobile_no VARCHAR(255) NOT NULL
dob VARCHAR(255) NOT NULL
apply_date VARCHAR(255) NOT NULL
for VARCHAR(255) NOT NULL
reason VARCHAR(255) NOT NULL
status ENUM NOT NULL
url VARCHAR(255) NOT NULL](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-27-2048.jpg)
![ Table 5.1.8 [s_t_bonafide]
Field Name Data Type(Size) Constrain
id INT(11) Primary key
name VARCHAR(255) NOT NULL
enrollment_no VARCHAR(255) NOT NULL
branch VARCHAR(255) NOT NULL
semester ENUM NOT NULL
mobile_no VARCHAR(255) NOT NULL
dob VARCHAR(255) NOT NULL
apply_date VARCHAR(255) NOT NULL
depo VARCHAR(255) NOT NULL
from VARCHAR(255) NOT NULL
status ENUM NOT NULL
url VARCHAR(255) NOT NULL](https://image.slidesharecdn.com/leavemanagementsystemupdated-190811103713/75/Leave-management-system-28-2048.jpg)
Uploaded byHemal Joshi
Leave management system
The document outlines the development of a Leave Management System tailored for engineering colleges, aiming to automate leave processes and reduce reliance on paperwork. It employs a spiral model for software development, detailing system requirements, user roles, and various data diagrams, alongside a robust data dictionary to manage users and leaves efficiently. The project emphasizes enhancing communication between students and administration while ensuring data integrity and validation throughout the leave management process.
More Related Content
Similar to Leave management system
Leave management system
- 1. Gujarat Technological University DrSubhash Technical Campus Diploma (CE) Semester VI Leave Management System Prepared By: Hemal Joshi Hardik Bhuva Arshad Vijariwadha (156950307522) (156950307508) (156950307557) Guided By Prof D.N.Marsonia
- 2. Outline Introduction Objective About Technology Software Development Life Cycle Model System Requirement Diagrams Data Dictionary Implementation Validation Reference
- 3. Introduction This LeaveManagement System is a great solution for all leave related problem of all Engineering Colleges. In most of the Colleges the leave related information’s are maintained through the letter/paper work which is a very difficult task because as the time passed the information will be lost. The administrator can view the information of a particular students’ that for how many days he was on the leave so that he can have information about the remaining leave period of an employee. This Leave Management System Final Year Project streamlines communication between your Students and employees. Users involved: 1. Admin 2. Faculty 3. Student
- 4. Objective To automatethe existing Leave Management in educational institutes. To decrease the paperwork and enable the process with efficient, reliable record maintenance by using centralized database, thereby reduces chances of data lose. To provide for an automated leave management system that intelligently adapts leave policy for students and employees in any organization. The main feature of our project is : 1) Leave 2) Leave Report 3) Application 4) Application Report
- 5. About Technology Platform: PHP Client Authoring : BOOTSTRAP,HTML,CSS,JAVASCRIPT,JQUERY Server side : MySQLi Code behind : PHP Web server : XAMPP server Development tools : Php Storm JetBraines
- 6. Software Development LifeCycle Model Spiral Model: Definition: The spiral model is a risk-driven process model generator for software projects. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
- 7. Figure : SpiralModel
- 8. Why weuse Spiral Model : 1. Because the requirement of client is fully fulfilled by this model. 2. If there is any error in particular model it can be solved at a time. 3. Client will be engaged during hall project. 4. Less time consuming compare to other model. 5. Less risk throughout the project. 6. When new requirement is needed then easily add after development.
- 9. System Requirement 1.Memory : 1 GB RAM 2. Hard disk : 100 GB 3. Processor : Pentium 4. Browser : Google Chrome, Mozilla Firefox, Internet Explorer and Other 5. Network Interface Card
- 10.
- 11. Use CaseDiagram
- 12. Data FlowDiagram Context Level
- 13. Data FlowDiagram User Level 1
- 14. Data FlowDiagram User Level 1
- 15. Data FlowDiagram Faculty Level 1
- 16. Data FlowDiagram Admin Level 2
- 17. Data FlowDiagram User Level 2
- 18. Data FlowDiagram Faculty Level 2
- 19.
- 20.
- 21. Data Dictionary Table5.1.1 [student] Field Name Data Type(Size) Constrain id INT(11) Primary Key first_name VARCHAR(255) NOT NULL middle_name VARCHAR(255) NOT NULL last_name VARCHAR(255) NOT NULL mobile BIGINT(20) Unique Key email VARCHAR(255) Unique Key city VARCHAR(255) NOT NULL department VARCHAR(255) NOT NULL semester ENUM NOT NULL enrollment_no VARCHAR(255) NOT NULL password VARCHAR(255) NOT NULL leave_count INT(11) NOT NULL url VARCHAR(255) Unique Key is_active ENUM NOT NULL
- 22. Table 5.1.2[master] Field Name Data Type(Size) Constrain Id INT(11) Primary Key name VARCHAR(255) NOT NULL Mobile BIGINT(20) NOT NULL user_name VARCHAR(255) NOT NULL password VARCHAR(255) NOT NULL is_activa ENUM NOT NULL
- 23. Table 5.1.3[faculty] Field Name Data Type(Size) Constrain id INT(11) Primary Key first_name VARCHAR(15) NOT NULL middle_name VARCHAR(255) NOT NULL last_name VARCHAR(255) NOT NULL mobile BIGINT(20) Unique Key email VARCHAR(255) Unique Key city VARCHAR(255) NOT NULL department VARCHAR(255) NOT NULL Semester ENUM NOT NULL user_name VARCHAR(255) NOT NULL Password VARCHAR(255) NOT NULL url VARCHAR(255) Unique Key is_active ENUM NOT NULL
- 24. Table 5.1.4[leave] Field Name Data Type(Size) Constrain id INT(11) Primary key leave_type VARCHAR(255) NOT NULL start_date VARCHAR(255) NOT NULL end_date VARCHAR(255) NOT NULL day_count INT(11) NOT NULL reason TEXT NOT NULL current_date DATE NOT NULL enrollment_no BIGINT(20) Unique Key name VARCHAR(255) NOT NULL semester ENUM NOT NULL department VARCHAR(255) NOT NULL url VARCHAR(255) NOT NULL status ENUM Unique Key
- 25. Table 5.1.5[bonafide_certificate] Field Name Data Type(Size) Constrain id INT(11) Primary key name VARCHAR(255) NOT NULL enrollment_no VARCHAR(255) NOT NULL branch VARCHAR(255) NOT NULL semester ENUM NOT NULL mobile_no VARCHAR(255) NOT NULL dob VARCHAR(255) NOT NULL apply_date VARCHAR(255) NOT NULL reason VARCHAR(255) NOT NULL status ENUM NOT NULL url VARCHAR(255) NOT NULL
- 26. Table 5.1.6[fee_structure] Field Name Data Type(Size) Constrain id INT(11) Primary key name VARCHAR(255) NOT NULL enrollment_no VARCHAR(255) NOT NULL branch VARCHAR(255) NOT NULL semester VARCHAR(255) NOT NULL mobile_no VARCHAR(255) NOT NULL dob VARCHAR(255) NOT NULL apply_date VARCHAR(255) NOT NULL for VARCHAR(255) NOT NULL reason VARCHAR(255) NOT NULL status ENUM NOT NULL url VARCHAR(255) NOT NULL
- 27. Table 5.1.7[railway_pass] Field Name Data Type(Size) Constrain id INT(11) Primary key name VARCHAR(255) NOT NULL enrollment_no VARCHAR(255) NOT NULL branch VARCHAR(255) NOT NULL Semester VARCHAR(255) NOT NULL mobile_no VARCHAR(255) NOT NULL dob VARCHAR(255) NOT NULL apply_date VARCHAR(255) NOT NULL for VARCHAR(255) NOT NULL reason VARCHAR(255) NOT NULL status ENUM NOT NULL url VARCHAR(255) NOT NULL
- 28. Table 5.1.8[s_t_bonafide] Field Name Data Type(Size) Constrain id INT(11) Primary key name VARCHAR(255) NOT NULL enrollment_no VARCHAR(255) NOT NULL branch VARCHAR(255) NOT NULL semester ENUM NOT NULL mobile_no VARCHAR(255) NOT NULL dob VARCHAR(255) NOT NULL apply_date VARCHAR(255) NOT NULL depo VARCHAR(255) NOT NULL from VARCHAR(255) NOT NULL status ENUM NOT NULL url VARCHAR(255) NOT NULL
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 37.
- 38.
- 39.
- 40.
- 42. S.T.Bonafide Application(Approved)
- 43. S.T.Bonafide Application(Rejected)
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57. Bonafide CertificateApplication
- 58. View BonafideCertificate Application
- 59. Bonafide CertificateApplication Report
- 60. Validation Required fieldvalidation It indicate filed must be required to enter. First name, Middle name, Last name validation It should be more than 3 alphabet required. Mobile number validation It should be 10 digits required and also unique. Email address validation Email address must be valid.
- 61. User namevalidation User name minimum 3 digits and alphabet required. Password validation Password minimum 6 digits and alphabet required. URL validation URL will be change all time (unique).
- 62.
- 64.