Homework 2: Employee Project Tracking System

This homework continues your practice with Oracle's Data Modeler. The goal is to model how a company tracks which employees are working on which projects, along with equipment usage and training certifications.

Assignment

Create an ER diagram to model an Employee Project Tracking system. The company needs to know not just who is on a project, but what their specific role is and how many hours they have dedicated to it. You'll also track equipment assigned to projects and employee certifications.

Entities and details:

Employee

  • Unique Employee ID
  • First Name
  • Last Name
  • Job Title
  • Hire Date
  • Department Name

Project

  • Unique Project ID
  • Project Name
  • Start Date
  • Estimated End Date
  • Total Budget

Assignment (the "work log" between Employee and Project)

  • Unique Assignment ID
  • Role Description (e.g., Lead Developer, QA Tester, Project Manager)
  • Total Hours Worked
  • Date Assigned

Equipment

  • Unique Equipment ID
  • Equipment Type (Laptop, Server, Projector, etc.)
  • Serial Number
  • Purchase Date
  • Status (Available, In Use, Under Repair)

Certification (tracks employee training credentials)

  • Composite Key: Employee ID + Certification Name (together they uniquely identify a certification record)
  • Certification Name (e.g., "PMP", "AWS Solutions Architect", "Scrum Master")
  • Date Earned
  • Expiration Date
  • Issuing Organization

Relationship requirements:

  • An Employee can have many Assignments; an Assignment belongs to one Employee.
  • A Project can have many Assignments; an Assignment belongs to one Project.
  • A Project can use many pieces of Equipment; Equipment can be used by many Projects over time (think about how to model this).
  • An Employee can have many Certifications; each Certification belongs to one Employee.
  • Use common sense for optionality (e.g., Can a Project exist before any Assignments? Can Equipment exist without being assigned to a Project yet?).
  • Indicate primary keys.

Submission requirements:

  1. Use the class standard format in Oracle Data Modeler.
  2. Include your name on the diagram.
  3. Fit the entire diagram on one page (ready to print).
  4. Submit a zip containing both the file and its folder.


This topic: CenterForComputing > WebHome > Syllabi > SyllabiSpring2026 > CSC210SylS2026 > CSC210S2026SyllabusHome5
Topic revision: r1 - 2026-03-02 - CathyBareiss
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback