Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Employee Management System


Published on


Employee Management System

  1. 1. EMPLOYEE MANAGEMENT SYSTEM<br />GEA Process Engineering (India) Private Limited<br />Submitted By<br />Vivek S. Shah<br />Exam No-230<br />Developed For :<br />
  2. 2. 1. Project Profile <br />
  3. 3. 2. About the Organization<br />GEA Process Engineering (India) Private Limited, formerly known as L&T-Niro Limited and Food Division (Dairy) of Larsen & Toubro Limited, India, are now a part of GEA Process Engineering Division (Processing, Membrane Filtration, Concentration, Drying, Powder Processing & Handling, and supplies customized and advanced plant & equipment with safe and reliable process controls. GEA P-Division is part of the Process Engineering segment of GEA Group Aktiengesellschaft, Germany.<br />GEA Process Engineering (India) Private Limited has a strong Project Management Team and we have supplied several high-tech plants to the leading manufacturers in Food & Dairy, Brewery and Chemical sectors on a turnkey and EPC (Engineering, Procurement & Construction) basis.  We offer total solutions - from "Concept to Commissioning" with GEA's integrated strength in Process Technology, Basic & Detailed Engineering, Equip-Division), world leader in liquid and solid processing technologies. GEA P-Division focuses on Liquid entFabrication, Automation, Project Management, Construction & Commissioning to build turnkey projects for a complete range of plants & systems. <br />GEA Process Engineering (India) Private Limited is a part of the GEA Process Engineering Division (P-Division) of GEA Group Germany. GEA stands for Global Engineering Alliance and is a leading global technology group. <br />
  4. 4. 3.1 Existing System<br />
  5. 5. 3.2 Drawback of existing System <br />
  6. 6. 4.1 Need For New System<br />
  7. 7. 4.2 Advantages of New System<br />
  8. 8. 5.1 Hardware Requirement<br />
  9. 9. 5.2 Software Requirement<br />WEB SERVER SYSTEM<br />DATABASE SERVER SYSTEM<br />CLIENT SYSTEM<br />
  10. 10. 6.1 Project Management |Project Development<br />To solve actual problems in an industry setting, a software engineer or a team of engineers must incorporate a development strategy that encompass the process, methods, and tools layers.<br />Our software is based on Waterfall Model.<br />The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) .<br />The waterfall development model has its origins in the manufacturing  and construction industries; highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development.<br />
  11. 11. 6.1 Project Management |Project Development<br />The unmodified "waterfall model". Progress flows from the top to the bottom, like a waterfall.<br />
  12. 12. 6.2 Project Management |Project Planning<br />Project Management is the discipline of planning, organizing, and managing resources to ring about the successful completion of specific project goals and objectives. <br />The primary challenge of project management is to achieve all of the project goals and objectives while adhering to classic project constraints—usually scope, quality, time and budget. <br />The secondary—and more ambitious—challenge is to optimize the allocation and integration of inputs necessary to meet pre-defined objectives.<br />
  13. 13. 6.2 Project Management |Project Planning<br />
  14. 14. 6.3 Project Management |GANNT Chart<br />
  15. 15. 7.1 System User | Introduction<br />For every web application complexity is directly proportional to the number of user’s categories for the system.<br />The users of “GEA EIM (Employee Information Manager)” reside at three levels in the organization. As requirements of all levels users are considered in development of the system, it can be easily fit to all expectations of all types of system users of any level.<br />There are three types of users:<br /><ul><li> Administrator.
  16. 16. Line Manager.
  17. 17. Employee.</li></ul>Administrator : Can Add, Edit employee information. Permission to build different reports.<br />Line Manager: can access information of employee under his/her department.<br />Employee : can access his own details<br />
  18. 18. 7.2 System User | User Hierarchy<br />The categories of end-user who will interact with the “GEA EIM (Employee Information Manager)” web application. User categories are relatively limited. However, when the number of user categories grows, it is advisable to develop a user hierarchy as shown below:<br />
  19. 19. 8.1 System Analysis | Feasibility Study<br />…not everything imaginable is feasible, not even the software as it may appear basically a software is acceptable if it is technically, financially and operationally feasible.<br /><ul><li> what does Technically Feasibility means</li></ul> whether suggested technology exist or can be acquired from the market or not<br /><ul><li> what does Financial Feasibility means</li></ul> It is financially feasible if it is build at cost which is affordable by its client<br /><ul><li> what doesOperational Feasibility means </li></ul> should be used to reduce the defectsor fulfill the requirements matching the user’s needs. <br /> & should not affect the existing operations of the organization and can be put into use by <br /> easy without resistance (to acquire the new skills required).<br />
  20. 20. 8.1 System Analysis | Feasibility Study<br />TechnicalFeasibility: <br />The minimum requirement to implement the system is Pentium-IV processor with 512 MB RAM, Any Operating System, Java Run Time Environment. These are the software’s which are most popular and easily available in the market.<br /> <br />Economical Feasibility: <br />It is more commonly a cost-benefit analysis of the system. The ratio of one time cost or recurring cost should not exceed the benefits from the system. Cost of acquiring Machine, Software, Operational Setup, training cost. As Said earlier Company is Multinational and it is well infrastructure. No Extra cost for set up of operating environment needed as the computer is already in use for other purposes. And the staff is well conversant and familiar with the computer technology. Only the use of the ‘GEA EIM’ is needed. The system is User friendly and need minimum data entry from the end users, thus is easy to use. <br /> <br />OperationalFeasibility:<br />This system will reduce the work load and loss of information, saves time and would help to the system generalized rather than person dependent<br />
  21. 21. 8.3 System Analysis | Activity Diagram<br />
  22. 22. 8.3 System Analysis | Use Case Diagram<br />For Admin User :<br />
  23. 23. 8.3 System Analysis | Use Case Diagram<br />For Line Manager User :<br />
  24. 24. 8.3 System Analysis | Use Case Diagram<br />For Simple User :<br />
  25. 25. 8.4 System Analysis | Data Flow Diagram<br />Context Diagram :<br />
  26. 26. 8.4 System Analysis | Data Flow Diagram<br />First Level Diagram : <br />
  27. 27. 8.4 System Analysis | Data Flow Diagram<br />Second Level Diagram (Adding Employee) : <br />
  28. 28. 8.4 System Analysis | Data Flow Diagram<br />Second Level Diagram (For tracing employee and reporting utility : <br />
  29. 29. 8.5 System Analysis | Technology Used<br />Servlet<br />Jsp<br />Ajax<br />XML & Java<br />JDBC<br />MVC (Model–View–Control) Architecture<br />Oracle 10g<br />i-Report<br />jQuery<br />JavaScript<br />CSS(Cascading Style Sheets)<br />
  30. 30. 9.1 System Design | Introduction<br />This phase is a move from user requirement to defining how system will work thus it is quite technical it specifies <br /> <br /><ul><li> Exactly each input , output, data audit and control requirement will be handled
  31. 31. Acceptance test plan/ scheduled
  32. 32. Facilities, equipments and personal required
  33. 33. Manual procedures required to operate system.</li></ul>Database Design : <br />The most popular relational database model is used for permanent storage of data. It is two dimensional and easy to handle. Thus logical and physical changes are easy to handle.<br />
  34. 34. 9.2 System Design | Data Dictionary<br />
  35. 35. 9.2 System Design | Data Dictionary<br />
  36. 36. 9.2 System Design | Data Dictionary<br />
  37. 37. 9.2 System Design | Data Dictionary<br />
  38. 38. 9.2 System Design | Data Dictionary<br />
  39. 39. 9.2 System Design | Data Dictionary<br />
  40. 40. 9.2 System Design | Data Dictionary<br />
  41. 41. 9.2 System Design | Data Dictionary<br />
  42. 42. 9.2 System Design | Data Dictionary<br />
  43. 43. 9.2 System Design | Data Dictionary<br />
  44. 44. 9.2 System Design | Data Dictionary<br />
  45. 45. 9.2 System Design | Data Dictionary<br />
  46. 46. 9.3 System Design | PORCEDURAL DESIGN<br />
  47. 47. 9.3 System Design | PORCEDURAL DESIGN<br />
  48. 48. 9.3 System Design | PORCEDURAL DESIGN<br />
  49. 49. 9.4 System Design | Flow Design<br />
  50. 50. 9.5 System Design |Design of Input Screen<br />Input screen are user friendly and care is taken that minimum amount of data entry is done. <br />The master information once entered and stored is displayed in a combo box or as a list for further input thus there are no chances of error in data entry as the use only has to select the information from the provided list. <br />Key data is displayed from the master tables where ever needed if any redundancy exists then the data is not reentered it is fetch form appropriate tables. e.g. while entering master information it is verified that data already exist for that entity only then further data is accepted. Thus duplication and redundancy is properly handled. Link for saving is enabled only after proper verification and validation of data is done.<br />And basic information is first validated and then further data entry is allowed thus it saves unnecessary data typing. Proper messages are provided where ever needed. Thus care is taken for control of data and correctness of data with minimum typing efforts. <br />proper conversions of data type and formats are done. <br />Here domain login is provided so no need to remember user id and password.<br />
  51. 51. 10.1 Implementation | Implementation Environment<br />This application is made by keeping in mind the basic concept of collaboration, the application can be used by each of the person at a time on their respective systems. <br />At a time more than one user can use the web interface made to support the actual application. Also the web site does not require any type of external interaction and makes user able to have dynamic browsing on intranet, it is never ever affected by the number of users accessing it at a time on their respective location.<br />This application is also made in such a way as to provide user with the most effective graphical Interface so that the user can easily perform their task.<br />So, as the conclusion of above two points, this application is having the multiuser and effective GUI environment for the users.<br />
  52. 52. 10.2 Implementation | Security Features<br />Authentication is necessary to enter into the system. This is required to prevent unauthorized access to the system.<br />System can automatically identify user through domain name if it is not in application database then user is not allowed to enter in system.<br />Server maintains the information is Sessions when particular user enters into the system. The Session is regularly checked whenever it is required.<br />
  53. 53. 10.2 Implementation | Coding Standard<br />The Software needs to be updated from time to time according the changing needs of Users. So some standards are to be maintained in implementation and Coding, so that if the software needs to be modified due to some changes in User needs or some enhancements to be done, then it’s easy for the person to find some specific modules, pages, functions, variables or even the tables or stored procedures in the database.<br /><ul><li> Package Standard
  54. 54. Variable Standard
  55. 55. Comment Standard
  56. 56. Functional Standard
  57. 57. General Standard</li></li></ul><li>11 Testing<br />Testing is vital to the success of the system. System testing makes logical assumption that if all <br />the parts of system are correct, the goal will be successfully achieved. This system is tested by <br />following test cases and prepared for final implementation.<br />Test Case 1<br />Case : Testing of the Domain Login<br />Result : All the Operations work successfully.<br />Test Case 2<br />Case : Testing of the Basic Module<br />Result : System is not able to detect and generate correct information and Exception Problem, validation problem. <br />Reason : This occurred because query is not proper format, script problem<br />Solution : After giving the proper function and query, we can able to get correct result.<br />
  58. 58. 11 Testing<br />Test Case 3 <br />Case : Testing of the EMS Module<br />Result : System is not able to generate correct out put.<br />Reason : This occurred because database was not normalized.<br />Solution : After making proper normalized we can able to get correct result<br />Test Case 4 <br />Case : Testing of the Generated Report<br />Result : System is not able to generate correct out put.<br />Reason : his occurred because query is not properly fired<br />Solution : After giving the proper query, we can able to get correct result.<br />Test Case 5<br />Case : Testing of the admin(master) Module(Employee rights)<br />Result : All the Operations work successfully.<br />
  59. 59. 12. Screen Shot | Home Page of Admin<br />
  60. 60. 12. Screen Shot | Add Employee<br />
  61. 61. 12. Screen Shot | Assign Domain Name<br />
  62. 62. 12. Screen Shot | Personal Details Form<br />
  63. 63. 12. Screen Shot | Contact Details Form<br />
  64. 64. 12. Screen Shot | Emergency Contact Details Form<br />
  65. 65. 12. Screen Shot | Immigration Details Form<br />
  66. 66. 12. Screen Shot | Family Details Form<br />
  67. 67. 12. Screen Shot | Qualification Details Form<br />
  68. 68. 12. Screen Shot | Languages Details Form<br />
  69. 69. 12. Screen Shot | Training Details Form<br />
  70. 70. 12. Screen Shot | Experience Details Form<br />
  71. 71. 12. Screen Shot | Nomination (EPF) Form<br />
  72. 72. 12. Screen Shot | Nomination (EPS) Form<br />
  73. 73. 12. Screen Shot | Uploading Photo<br />
  74. 74. 12. Screen Shot | Verification in Pending<br />
  75. 75. 12. Screen Shot | Home page of Admin<br />
  76. 76. 12. Screen Shot | Verification Report<br />
  77. 77. 12. Screen Shot | Employment details Form<br />
  78. 78. 12. Screen Shot | Report to details Form<br />
  79. 79. 12. Screen Shot | Salary details Form<br />
  80. 80. 12. Screen Shot | Employee List View<br />
  81. 81. 12. Screen Shot | Employee Profile View<br />
  82. 82. 12. Screen Shot | Updating an Employee<br />
  83. 83. 12. Screen Shot | Adding more details in future<br />
  84. 84. 12. Screen Shot | Reporting Utility<br />
  85. 85. 12. Screen Shot | Tracking Employee<br />
  86. 86. 12. Screen Shot | Home Page of Line Manager<br />
  87. 87. 12. Screen Shot | EIM View of Line Manager<br />
  88. 88. 12. Screen Shot | Home Page of Employee<br />
  89. 89. 12. Limitation and Future Enhancement<br /> Limitations:<br />GEA Employee management system is limited up to process department of GEA Group only.<br />GEA Employee management system is not on internet application.<br /> Future Enhancement:<br />GEA Employee management system will be enhanced up to all departments of GEA Group.<br />Integrating Leave management and Attendance system.<br />As organization is multinational make application internet base.<br />