Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to E leave
Similar to E leave (20)
Recently uploaded
Recently uploaded (20)
E leave
- 1. e-Leave: Online Leave Application System
- 2. Agenda 2 Introduction Project Philosophy System Architecture Functional and System Capabilities System Demo Discussion Conclusion Q & A
- 3. Introduction Why automating leave application process important? Manual (paper-based) leave application process is time- consuming and less efficient Effective leave management lead to significant reduction in costs and improvement in productivity Automating leave application makes every application paperless, convenient, fast and efficient
- 4. Introduction Automated Leave Application would help in Track status of all leave records Convenience of time and location for applicant as well approver Reduced workload of Administration staff Reduce costs
- 5. Project Philosophy – con’t Pre-requisites Java Platform : Jdk 1.7 Web Container : Tomcat 7.0 Web Server : Apache Database :Mysql 5.5 IDE for Java : Esclipe 3.6 IDE for Mysql Database : Mysql WorkBench 5.2 Tools / Technology J2EE, Servlet and JSP JavaScript JQuery CSS (Cascading style sheet)
- 6. Project Philosophy 2 Major Features Leave Application System User Management System e-Leave Online Leave Application System Leave Application System User Management System
- 7. Project Philosophy – con’t Roles and Responsibilities Four team members Four development phases 1. Modeling (10%) 2. System Development Design (20%) 3. Coding and Unit Testing (50%) 4. Integrated Testing and Bug Fixing (20%)
- 8. System Architecture Servlet : processes HTTP request s and responses, serve as controller JSP : display dynamic content Java Classes : implement backend ‘business’ codes
- 9. System Architecture – con’t High level model – build with Use Case diagram – define interaction between stakeholders and system
- 10. Use Case Diagram
- 11. System Architecture – con’t Database design - use ER diagram - specifies relationship between entities in database
- 12. ER Diagram
- 13. Functional and System Capabilities Mainly, there are four modules 1. Login 2. Leave application module 3. Approval module 4. Admin module
- 14. Functional and System Capabilities 1. Login module - Every user needs to login to access to the system
- 15. Functional and System Capabilities 2. Leave Application Module a) Leave Application Listing - employee uses for viewing leave information
- 16. Functional and System Capabilities b) Leave Form - employee uses for applying leave - Enforces form completion through required field validation
- 17. Functional and System Capabilities 3. Leave Approval Module a) Leave Approval Listing - manager uses for pending leave information
- 18. Functional and System Capabilities b) Approval Form - manager uses for approving or rejecting leave - Leave records are updated automatically once approved
- 19. Functional and System Capabilities 4. Admin Module a) User Account Listing - system admin uses for managing application
- 20. Functional and System Capabilities b) User Form - system admin uses for managing user information. - immediate creation and update of records
- 21. Functional and System Capabilities
- 22. Discussion The knowledge on Java technologies is fundamental skill required. There was a challenge in the data manipulation in database system. It is recommended to do deeper feasibility study as organizational standard, culture and leave policies vary one another. Non-functional requirements such as security, performance etc. need to consider.
- 23. Discussion – con’t Future enhancements - Task List : display tasks need to be done by logon user - Email/SMS Notification : notify approver as well as applicant - Audit Trail : tracing error and exception handling - Reporting : provide facility to generate report
- 24. Conclusion Fulfilled the main goal – reduces physical movement and paper work. Implemented e-leave system by providing essential and basic functional requirement within certain time limit. Designed to make sure that the user can comfortably and efficiently utilize it. Follow look-and-feel standards – consistent layouts and design throughout application.
- 25. DEMO
- 26. Question 26
- 27. Thank you! 27
Editor's Notes
- two styles of mashups: Web-based and server-based. Whereas Web-based mashups typically use the user's Web browser to combine and reformat the data, server-based mashups analyze and reformat the data on a remote server and transmit the data to the user's browser in its final form.
- <Content> section is where the real work of your gadget happens. It is where you specify the type of gadget, your programming logic, and often the HTML elements that determine the appearance of your gadget. <UserPrefs> section defines controls that allow users to specify settings for the gadget. <ModulePrefs> section in the XML file specifies characteristics of the gadget, such as title, author, preferred sizing, and so on.
- <Content> section is where the real work of your gadget happens. It is where you specify the type of gadget, your programming logic, and often the HTML elements that determine the appearance of your gadget. <UserPrefs> section defines controls that allow users to specify settings for the gadget. <ModulePrefs> section in the XML file specifies characteristics of the gadget, such as title, author, preferred sizing, and so on.