CASE STUDY 3: TELEMAT, INC.

Telemat, Inc. is small software development company with over 250 employees. Telemat, Inc. works on projects of large IT companies and educational institutes. It computes all its billing based on the number of hours its employees spend working on that project. Therefore, tracking time against projects is critical for creating accurate invoices. Telemat has been tracking employee records, project records, financial records and client records separately, by using Microsoft Office Excel. It has decided to automate all its operations to improve data accessibility, consistency, and efficiency.

Business Problem
Telemat, Inc. maintains all its employee records, project records, financial records, and client records in Excel. The management is aware that it needs to store and manage different records by using a single solution. It has decided to automate all its operations.

Goal
Telemat, Inc. has decided to develop a system to automate the employee inventory and project records in the first stage. The projects first stage development should be completed in two weeks and a pilot should be performed in the third week. In order to start the project: 1. The project manager creates the requirement details (RD) by using Microsoft Office Word 2007. 2. Based on the RD, the team leader presents the database design to the project manager. Based on the presentation, the project manager decides to use Microsoft Office 2007. This system offers a complete set of business and personal productivity tools to increase the employees efficiency. To automate the employee inventory and project records by using Microsoft Office 2007, Telemat needs to perform the following tasks: 1. Create the Telematix.mdb database by using Microsoft Office Access 2007. 2. Create the following tables: Employee_Details Department_Details Project_Details

1.12

IT Fundamentals and Office Productivity Tools

Project_Transaction_Details Leave_Details Their structure is shown in the following tables. Field Name Emp_No Emp_FName Emp_LName Residential_ address Ph_No Date_of_Birth Basic_Sal Bonus Deductions Dept_ID Project_ID Leaves_ Available Skills Data type Text Text Text Text Number Date Number Number Number Text Text Number 4 4 Width 4 50 50 50 Description Employee number Employee first name Employee last name Employee home address Employee phone number Employee date of birth Employee basic salary Bonus awarded if any Deductions of an employee if any Department number Project number Number of leaves available for the employee 100 Employee_Details Skills possessed by an employee

Memo

IT Fundamentals and Office Productivity Tools

1.13

Field Name Dept_ID Department_ Name Emp_No

Data type Text Text Text

Width 5 15 5

Description Department number Department name Employee ID of the employee who is heading the department

Department_Details

Field Name Project_ID Project_Start_Date Project_End_Date Project_Name Client Project_Status

Data type Text Date Date Text Text Text

Width 5

Description Project number Project start date Project end date

50 50 10

Name of the project Client for the project Status of the project can be ongoing or closed.

Project_Details

1.14

IT Fundamentals and Office Productivity Tools

Field Name Emp_No Project_ID Project_Joining_Dt

Data type Text Text Date/Time

Width 5 5

Description Employee number Project ID Date on which employee joined the project Project leaving date of employee

Project_Leaving_Dt

Date/Time Project_Transaction_Details

Field Name Emp_No Date_Of_Leave Leaves_Availed

Data type Text Date/Time Number

Width 5

Description Department number Leave date of employee Number of leaves availed by the employee

Leave_Details 3. Validate the points mentioned in the bulleted lists while creating the structure of the respective tables.

Table: Employee_Details
Emp_No should be unique and should not be left blank. The Emp_Fname, Emp_Lname, Residential_address, Ph. No, Date_Of_Birth and Skills fields should not be left blank. Basic_Sal should be greater than 0. The system should display a list of Dept_IDs from the Department_Details table. The system should display a list of Project_IDs from the Project_Details table.

IT Fundamentals and Office Productivity Tools

1.15

Table: Department_Details
Dept_ID should be unique. Department_Name should not be left blank. The system should display a list of Emp_Numbers from the Employee_Details table.

Table: Project_Details
Project_ID should not be left blank. Project_Start_Date should be less than the Project_End_Date. Before a new project is assigned to an employee, a check should be performed to ensure that the start date of the new project is greater than the end date of the current project to which that employee has been assigned. 4. Create appropriate relationships between the tables. 5. Create a query to find out the details of employees who are working on projects. 6. Create a query to find out the details of employees whose projects are completed. 7. Generate a query that displays the skills of the employee before an employee is assigned to a new project. 8. The system should not allow the user to assign an employee to a new project if the current project in which he/she is working is not completed. 9. Create forms to enable the user to input data in all the tables. 10. Update the Project_ID field in the Employee_details table whenever a project is allocated to an employee. 11. Create reports of projects that are ending in a particular month. 12. Create a report that displays the projects undertaken by an employee in a specific year. 13. Create a leave report for an employee. 14. Create a chart that displays the analysis of the leaves taken by an employee. 15. Create a chart that displays the projects that have not met a deadline in a particular month. Telemat, Inc. will perform the pilot of this project and then move to the second stage for integrating the finance records and the client records.

1.16

IT Fundamentals and Office Productivity Tools