Employee Management System And Performance Appraisal Computer Science Essay

Published: Last Edited:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Software methodology is a set of activities and associated results which lead to the production of a software product. These may involve the development of software from scratch although it is increasingly the case that new software is developed by extending and modifying existing systems. These activities are mostly carried out by software engineers (Sommerville, 2001).

"A methodology in the domain of information system must cover a number of aspects of the project, although coverage varies from one to another. Avision and Fitzgerald describe a methodology as a collection of many components. Typically, each methodology has procedures, techniques; tool and documentation aids that are intended to help the system developer in his or her efforts to develop an information system" (Avision and Fitzgerald, 1998).

Use Case Diagram of IAHRMS

This project will apply scenario-based technique for requirement elicitation. "Scenarios can be particularly for adding detail to an outline requirements description. They are description of example interaction sessions. Each scenario covers one or small number of possible interaction. Different forms of scenarios have been developed and they provide different types of information at different levels of detail about the system" (Sommerville, 2001).

"Use cases are scenario-based technique for requirement elicitation, it are description of the functionality of the system from the users' perspective. Use case diagrams are used to show the functionality that system will provide and to show which users will communicate with the system in some way to use that functionality" (Simon, McRobb, Farmer, 2002).

Use Case Diagram for Applicant Information System

Use Case Diagram for Applicant Information System

Use Case Description

Make Recruitment: When the applicant applies for job, the applicant fills the application form and the recruiter records the applicant information such as applicant name, address, phone, etc.

Make Interview: After recording the applicant information, the recruiter interview the applicant for applying job and record the interview information such as interview date, apply job title, interview frequency, etc.

Make Contract: After the interview, the applicant make contract with company if the company accept the applying job.

Use Case Diagram for Applicant Information System

Use Case Description

Register Employee Information: After contracting process, the applicant becomes a permanent employee. So, HR manager records the information of employee such as name, employment date, seniority date, location, division, department, etc.

Make Promotion: When the employee promote to one position to another, HR manager records the promotion information such as promotion date, position, etc.

Transfer Employee: When the employee transfers one location to another, HR manager records the transfer information such as location, transfer date, etc.

Resign/Dismiss Employee: When the employee resigns/dismisses from current position, HR manager records the resign/dismiss information on that employee such as resign date, remark, etc.

Use Case Diagram for Employee Miscellaneous System

Use Case Description

Give Award: When the employee gets the award for his/her good performance, HR manager records the award information such as award name, award date, remark, etc.

Give Punishment: When the employee do something wrong, the company give punishment on that employee. So, HR manager records the punishment information such as punishment date, reason, remark, etc.

Give Training: If the employee needs to attend the training in local or foreign, HR manager records training information such as Training, Date, Is local, etc.

Review Employee: HR manager reviews each of employees in every month and records the review information for each employee such as review date, remark, review grade, etc.

Make Test: For improvement of employee, HR manager makes test for employee and records the test information such as test name, test date, grade, etc.

Use Case Diagram for Employee Task Management System

Use Case Description

Get Working Experience: If the employee has working experience from other companies, HR manager records working experience information such as position, location, employer, etc.

Store Task Experience: When the employee has task experience in this company, HR manager records task experience information such as task, start date, end date, etc.

Assign new task: When HR manager assign new task to employee, records the task information such as task name, start date, complete date, due date, etc.

Handover Task: If the employee couldn't complete the assigned task due to many reasons, HR manager records the task experience information such as task, handover employee, accept employee, start date, handover date, complete date, etc.

Use Case Diagram for Employee Leave System

Use Case Description

Schedule Leave: HR manager firstly schedules the leave plan for every leave type and records the leave plan information such as leave type, total give, leave balance, etc.

Request Leave: When the employee wants to leave, he/she requests the leave from HR manager. Then, HR manager records the leave request information.

Calculate Leave Balance: After employee requests leave, HR manager calculate the leave balance for that employee and records leave balance information.

Cause Employee Injury: When the employee causes accident, the HR manager records employee injury records such as injury type, clinic name, injury date, etc.

Give Injury Leave: When the employee causes injury due to accident, HR manager gives injury leave and records the leave records.

Analysis of Agent System

This project will create a problem-solving agent and adopt this agent into HRMS.

Basically, the agent is responsible to solve the user's problem during IAHRMS operation. Once user enters the information about the employee like employee code or employee name, the agent will find out that particular record and present to the users. The agent also adopts report generator function, once users require an employee details, the agent will query the details and shows the data in pre-define form.

The agent also plays an important role as a human resource data dictionary and online help. Once user enters term and key word about the human resource environment, the agent system will display the definitions and solutions to the users.

This agent also will handle all the failure or error. When an error or an unexpected event occurs during the system operation, the agent will handle the error exception and construct meaningful message to the users and help users re-solve the problem.


The search engine is the core component in the agent system. It plays an important role in making sure that the agent system can apply breadth-first search methodology in the searching process. Once input from the string manipulator is triggered, the search engine will execute the first layer searching. If records found, the search engine will return results to presenter and the reset the stage to idle. If there is no record found on first layer searching, the search controller will increase the layer counter and repeat the search process until n level down in the employee database table.

Context Model

Context model will decide the boundaries of HRMS. The boundary between HRMS and its environment is relatively clear. The environments for HRMS are HR staff, HRMS database. From Figure 4.9, the HRMS is connected to HRMS database, HRMS to support the users and help them to carry out their jobs during operating the HRMS.

Data Flow Model

Data flow model is an intuitive way of showing how the data is processed by the system. The models that produced in analyst phase is called level 0 data flow model, the complicated or high level data flow model will be discussed in system design phase. The data is transformed at each step before moving on to the next stage. These processing steps or transformations are program function where data flow models are used to document a software design.

Following Figure shows the data flow model for create new employee record. Once users completed the data entry form, the system will execute data validation process to make sure the data is unique and all the mandatory fields are filled. The employee record will only insert into database if the data is valid.

Following figure shows the data flow model for modify employee records. Once users completed the data entry form, system will execute validation process on the mandatory fields. If the data is valid, system will update the data into database.

Following figure shows the data flow model for database access. Once this module is executed, system will check the availability of database connection. If the connection is stabile, system will continue to execute SQL command. If record set is available, system will return the dataset.

Following figure shows the data flow model for HR system. Once input string sent to HR system, the input string will manipulate to identify what information is needed to find out from database. Next, the input string will transact into SQL statement to query result from database. If no result found, the input string will pass to high level string manipulation to continue query the result. Last, the output will constructed by the module and display at the interface.

Following Figure shows the data flow model for create new agent dictionary. Once the form was completed and mandatory field was filled, the module will execute SQL query to insert a new record.

Following Figure shows the data flow model for update HRMS dictionary. Once the data was modified and mandatory field was filled, the module will execute SQL query to update a record.

Entity Relation Diagram (ERD)

"The entity relation diagram consists of three interrelated pieces of information; there are data objects, attributes that describe the data object and relationships that connect data object to one another" (Roger, 2001). Entity relation diagram is often used in conjunction with data flow models to describe the structure of the information which is being processed. This diagram will show data object, attributes and relationships for the HRMS database schema.

Following figure shows the Entity Relation Diagram for HRMS. The main entity for HRMS is employee, and personal information. Personal information is a super class that has general characteristics that are inherited by contact information, family details, statutory information and income detail.

Basically, the agent can access all the employee records. Each employee will have their own personal information. Employee will have multiple contact information and multiple family member details. Anyway, employee will only have one set of statutory information and one set of income detail. For the employee record, the primary key that links all entity is employee code.

Software and Hardware Requirements

Basically, software and hardware requirement for HRMS can separate into two different types; there are requirement for work station and requirement for server.


Aparicio, M., "IBM Intelligent Agents," FIPA Opening Forum Proceedings, Yorktown, New York, 1996.

Avision, D. and Fitzgerald, G., "Information Systems Development." Oxford: Blackwell Scientific, 1988.

Chess, D., Grosof, B., Harrison, C., Levine, D., Parris, C., and Tsudik, G., "Itinerant Agents for Mobile Computing." IEEE Personal Communications.

Craig, L., Applying UML and Patterns. An Introduction To Object-Oriented Analysis And Design. United State: Prentice-Hall, 1997.

Riecken, D., "Intelligent agents." Communications of the ACM, 37(7), 1994. Weld, D., "The role of intelligent systems in the national information infrastructure." AI Magazine, 1995.

Avison, D. & Hanifa, S., The Information System Development Life Cycle. A First Course in Information Systems. United Kingdom: McGraw-Hill, 1997. Deitel, T. & Deitel, R., Visual Basic 6, How To Program. New Jersey: Prentice-Hall, 1999.

Sellappan, P., Software Engineering, Management and methods, Malaysia: Sejana Publishing, 2000.

Finin, T., McKay, D., Fritzson, R., and McEntire, R., "KQML: An Information and Knowledge Exchange Protocol", in Kazuhiro Fuchi and Toshio Yokoi (Ed.), Knowledge Building and Knowledge Sharing , Ohmsha and IOS Press.

Franklin, D. & Graesser, A., "Is it an Agent, or just a Program?: A Taxonomy for Autonomous Agents", Proceedings of the Third International Workshop on Agent Theories, Architectures, and Languages, Springer-Verlag, 1996.

McDaniel, G., IBM Dictionary of Computing. United State: McGraw-Hill, 1994. Sommerville, I., Software Enginnering, 6th Edition, International Computer Science Series. United State: Addison-Wesley, 2001.

Jennifer, P., Yvonne, R., Helen, S., Interaction design. Beyond human-computer interaction. United State: John Wiley & Sons, 2002.

Maes, P., "Agents that Reduce Work and Information Overload," CACM, 7, 1997.

Mandel,T., "The Elements of User Interface Design." Wiley, 1997

Norman, E.F. and Lawrence, S.P., Software Metric. A Rigorous and Practical Approach. United Kingdom: PWS, 1997.

Parunak, H., "Chapter 4 - Applications of Distributed Artificial Intelligence in Industry," Foundations of Distributed Artificial Intelligence, G. M. P. O'Hare and N. R. Jennings (eds.), John Wiley & Sons, 1996.

Roger, S.P., Software Engineering. A Practitioner's Approach. Fifth Edition. United State: McGraw-Hill, 2001.

Scaife, M. and Rogers,Y., Information the design of virtual environment. International Journal of Human Computer Systems, 55(2), 2001.

Shaw, M. and Garlan, D., "Formulation and Formalisms in Software Architecture, Volume 1000 - Lecture Notes in Computer Science", Springer-Verlag, 1995.

Simon, B., McRobb, S., Farmer, R., Object-Oriented Systems Analysis And Design Using UML. United State: McGraw-Hill, 2002.

Stuart, R., Peter, N., Artificial Intelligence. A Modern Approach. New Jersey: Prentice-Hall. 1995.

Wooldridge, M. and Jennings, N., "Intelligent Agents: Theory and Practice, in Knowledge Engineering Review", Volume 10 No 2.