04.06.2015 Views

Database Modeling and Design

Database Modeling and Design

Database Modeling and Design

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

62 CHAPTER 4 Requirements Analysis <strong>and</strong> Conceptual Data <strong>Modeling</strong><br />

Division<br />

1<br />

1<br />

contains<br />

N<br />

Department<br />

1<br />

1<br />

has<br />

ismanaged-by<br />

isheaded-by<br />

N 1<br />

Employee<br />

1<br />

(a) Management view<br />

Figure 4.3<br />

Example of data modeling<br />

ing workstation (or computer). Secretaries <strong>and</strong> managers are each allocated<br />

a desktop computer. A pool of desktops <strong>and</strong> workstations is maintained<br />

for potential allocation to new employees <strong>and</strong> for loans while an<br />

employee’s computer is being repaired. Any employee may be married to<br />

another employee, <strong>and</strong> we want to keep track of these relationships to<br />

avoid assigning an employee to be managed by his or her spouse. This<br />

view is illustrated in Figure 4.3b.<br />

The third view, shown in Figure 4.3c, involves the assignment of<br />

employees, mainly engineers <strong>and</strong> technicians, to projects. Employees<br />

may work on several projects at one time, <strong>and</strong> each project could be<br />

headquartered at different locations (cities). However, each employee at<br />

a given location works on only one project at that location. Employee<br />

skills can be individually selected for a given project, but no individual<br />

has a monopoly on skills, projects, or locations.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!