Instructions:

1. Create an ER Modeling (Entity - Relationship Diagram)

2. Consider the fictional Online Work Order System (OWOS) described below. (OWOS) has been drastically (and somewhat unrealistically)simplified.Construct a reasonable ERD to capture the data requirements of the project. List the entities, relationships with multiplicities, and attributes. Specify the primary key of an entity whenever possible. Note that you should use the Crow's Foot notation as supported by EA Assistant v2.1. EA Assistant supports attributes for relationships and your ERD may have relationship attributes

Online Work Order System (OWOS)

A company would like to build a secured online work order system so that employees can submit work order requests(called jobs). Technicians can be assigned to work on a job.The following specification is highly simplified.

An employee can submit a job request. A job may apply to a computer (e.g. upgrade Acrobat Pro on computer with tag D241-90182),a group of computers (e.g. install ER-Assistant on all computers in the computer group CS-1014), or no computer (e.g. reset a password for employee 1020200 on the domain UCL6).

A computer has a unique tag and some descriptive information. A computer group contains one or more computers. A computer group may have a parent computer group. A computer group may contain one or more computer sub-groups. For example, the computer group 'MBSE Lab' may have several subgroups 'MBSE Lab G#1', 'MBSE Lab G#2', etc., and 'MBSE Lab G#1' may have five computers, etc.A computer is always owned by an employee. A computer group is managed by an organization unit.

An employee can only be assigned to work for multiple organization unite(unit) An employee has a unique id(EmpId), a name (last and first), an email, and a phone.

A unit has a unique id, a name, and a phone. A unit may be a sub unit for a bigger unit. For example, the employee 'Katherine Perry may work for the unit 'Computer Science', which may be a sub-unit of 'Computing Sciences,' which is in turn a sub-unit of 'Science and Engineering.' A computer group must be managed by a unit that assumes responsibility of the group and may submit jobs concerning the group.

A unit usually has a head and can have a number of assistants.For example, Caroline Kent may head the unit 'Computing Sciences,' and has Ken Beck and Josie Lane as assistant administrators. The unit Of course, Caroline, Ken and Josie are employees.Note that employees can work for many units, they can only lead or assist on one unit at most.

When a job request is made by an employee, the start time and description of the task are noted with a unique job id. A job request may target a computer or a computer group. The requester is noted. The requester can be the owner of the computer or an administrator of the unit that owns the computer group or the computer. When a job is closed, the closed time is recorded

A job has a status selected from many predefined statuses, such as 'started', 'assigned', 'postponed', 'tested', 'aborted', 'closed', etc. This list may be expanded in the future.

There are technicians serving the job requests. Technicians are employees with a privilege level (a number, e.g. 1 for minimal technician clearance, etc.). A job can be assigned to a technician. The assignment's start time should be recorded. A job is assigned to only one technician at a time, but it may be reassigned any number of times. For example, request id #1580 may be:

assigned to technician T1 at 2020/5/12:07:10:18

(re)assigned to technician T3 at 2020/5/21:14:22:14

(re)assigned to technician T2 at 2020/7/11:20:22:37

Technicians can make any number of comments on a job. The comment times should be stored with the comments.

Reports and Functions

Some functions and reports:

Online Work Order Request Page:

Allow an employee to logon and make a work order request by specifying which computers or computer groups are concerned with, and provide a description of the job.

Technician Work Page:

Allow a technician to logon and see all jobs assigned to him. When a particular job is selected, the technician can see all information about the task, including assignment history and all comments made on the request.

Daily, Weekly,and Monthly Job Report:

The report shows all jobs made in a specific day, week, and month. For each request,the request id, description, owner, targeted computer or computer group, current assigned technician, and its current status is shown.

Status Report:

For every predefined status, show all jobs(ids and descriptions) and the assigned technicians. This allows the manager to communicate with technicians on identified jobs that should be worked on more urgently.