CIS 266 – Developing Database Applications Term Project: Project Tracking

This application is to track projects, tasks and the time employees spend working on each task. • • • • Project information includes project name, description and status (pending, underway, delayed, and completed), start date, end date, and project manager. Projects are made up of tasks. Each task is part of a project, and has a name, description, start date, end date, and status (pending, underway, delayed, completed). Employee information includes name, title, and employee ID. Any employee can manage a project. All employees can work on tasks. Employees work on tasks; information needed includes which task, which employee, date, and hours worked.

Employees (including managers) need to be able to enter their name, select a project, select a task, and enter the date and number of hours spent working on that task. Employees should only be able to select from projects and tasks that are designated as underway. Employees should also have the ability to change the time spent on a specific project for a particular day; a task should have only one entry per employee per day. Managers need to be able to enter/edit employees, projects and associated tasks, and change project and task status. Managers also need to be able to view information in several ways (using forms). A project and all associated tasks Project Data (name, status, etc.) Task Task1 (name) Task2 (name) Description (description) (description) Status Underway Pending

A project and list of employees working on that project, including the task, date, and hours worked Project 1 Data (name, status, etc.) Employee Name1 Name1 Name2 Task Task1 (name) Task2 (name) Task1 (name) Date ##-##-## ##-##-## ##-##-## Hours XX XX XX Total HoursXX

An employee and the projects, tasks, dates, and hours worked Employee 1 Data (name, title, id.) Project Project 1 Project 1 Project 2 Task Task1 (name) Task2 (name) Task1 (name) Date ##-##-## ##-##-## ##-##-## Hours XX XX XX Total HoursXX

Application Notes
Each form showing summary information should provide the ability to select different projects or employees (the “one” side), either through navigation or a search feature. For all forms, choose controls that help employees select and navigate through the information correctly. A MDI form should serve as the container for your application, with child forms providing the methods to work with data. Don’t worry about security. All employees have access to entering work information, for changing project status, adding employees, or looking at the summary forms, since any employee can manage a project. Data changed in one form should be reflected in other forms.

Database Design & Planning Documents
Design the database to support this application. Identify each table, the fields in each table, and the field data types. Describe table relationships, including primary and foreign keys and any validation rules. Planning documents should identify classes (including parent and child forms) and the purpose of each; the principle procedures for each class; and data associated with each form. The database design and planning documents are due 5/13/2011. Turn in a printed description of the database and planning documents in a folder with your name. Database documentation should include tables, fields, data types, validation rules, primary and foreign keys. Database design and planning materials are worth 20 points.

Final Project
The term project is due 6/13/2011. Copy your project solution to the R: Drive, and submit a folder with print outs of your code (including comments), and the tables and relationships in your database. Make sure that all necessary files are included in your project folder. PROJECT APPLICATION GRADING Meets specifications and runs correctly Forms/interface easily understood and used Code is concise; proper use of selection and looping statements TOTAL 40 points 30 points 30 points 100 points

3/28/2011