Mountain View Community Hospital Project Case Chapter 14

1
Mountain View Community Hospital Project
CaseChapter 14
Team 5

• Jonathan Cooper
• Tammy Horne
• Cedric Love
• Jeremy Thielemier

2
Entities

• There are four groups of persons on whom the
  hospital is most dependent
• Employees
• Physicians
• Patients
• Volunteers

3
Common Attributes

• These are shared by all persons (entities)
• personID
• name
• address
• cityStateZip
• dateOfBirth
• phone

4
Unique Attributes

• Each of the four groups of persons has at least
  one unique attribute.
• Employees - datehired
• Physicians - specialty pagernumber
• Patients - dateOfContact
• Volunteers - skill

5
Unique Methods

• Each person also has one unique method.
• Employees - calcBenefit
• Volunteers - assignToCenter
• Physicians - treats
• Patients - calcAge assignToLocation
• An Employee or Physician who is also a Patient
  has an attribute specialService.

6
Relationships

• Each patient has one and only one physician.
• A physician may not be responsible for a patient
  or may be responsible for one or more patients at
  any given time.

7
Relationships cont

• Patients are divided into
• Resident
• dateOfAdmission
• assignToBed
• Outpatient scheduled for zero or more visits
• Visit
• date (partial identifier)
• Comments
• An instance of visit cannot exist without an
  outpatient entity.

8
Employee Groups

• Nurse
• Staff
• Technician

9
Employee Groups cont

• Nurse
• Attribute - certificate (indicates RN, LPN,
  etc.)
• Relationship - assigned one and only one care
  center
• Staff
• Attribute - jobClass
• Technician
• Attribute skill
• Relationship assigned one or more laboratory

10
Care Center

• Examples of care centers are Maternity,
  Emergency, and Cardiology.
• Attributes
• Name
• Location
• Care Center may have one or more nurses assigned
  to it.
• One nurse is appointed nurse-in-charge and must
  have an RN certificate to be appointed.

11
Care Center cont

• Care Centers may have no beds or may have one or
  more beds assigned to it.
• Bed attributes
• Bed ID (components bedNumber and roomNumber)
• Each resident patient must be assigned to a bed.
• A bed may or may not have a resident patient
  assigned to it at a given time.

12
Building

• Buildings contain Care Centers.
• Attributes include
• Building number
• Building name
• Building code

13
Laboratory

• Each technician is assigned to one or more
  laboratories.
• Attributes
• Name
• Location
• Laboratories are housed in only one building, but
  a building can have more than one lab.
• A laboratory includes equipment and employees and
  has a method called numberOfEmployees.

14
Project Question 1

• Is the ability to model superclass/ subclass
  relationships likely to be important in a
  hospital environment such as Mountain View
  Community Hospital? Why or why not?

15
Project Answer 1

• The ability to model superclass/ subclass
  relationships plays an important role in this
  case. Many of the classes share common
  attributes and behavior. Generalizing much of
  the common attributes and behavior into
  superclass facilitates a better understanding and
  simplification of the system. This leads to
  improved system redesign if necessary and
  extensions to the system in the future.

16
Project Question 2

• Do there appear to be any link objects in the
  description of the data requirements in this
  project segment? If so, what are they?

17
Project Answer 2

• There do not appear to be any link objects,
  although it could be argued that the association
  between the Nurse class and Care Center class
  could be represented with a class that would
  contain information as to whether or not the
  nurse is in charge.

18
Project Question 3

• Are there any abstract object classes in the
  description of this hospital? Why or why not?

19
Project Answer 3

• Both the Employee and Care Center classes are
  complete and serve as an abstract class for
  generalizing much of the information needed by
  their subclasses.

20
Project Exercise 1

• Draw a class diagram to accurately represent
  this set of requirements, carefully following the
  notation from this chapter.

21

22
Project Exercise 2

• Develop definitions for each of the following
  types of objects in your class diagram from
  Project Exercise 1. Make reasonable assumptions
  based on your own knowledge and experience.
• A. Classes
• B. Attributes
• C. Relationships
• D. Methods

23
Project Exercise Answer 2

• Classes A place to store information and
  actions associate with entities in the real
  world.
• Attributes A place to store a piece of
  information.
• Relationships The connection or dependence upon
  other classes to help define the hospital system.
• Methods The actions and procedures the classes
  perform.

24
Project Exercise 3

• You should recognize the statement A nurse
  cannot be appointed nurse_in_charge of a care
  center unless she or he has an RN certificate as
  a statement of a business rule. How did you
  model this business rule differently from what
  you did in the project case in Chapter 4? What is
  the constrained object? Is it an entity, an
  attribute, a relationship, or some other object?

25
Project Exercise Answer 3

• In Chapter 4 a business rule was modeled as an
  entity, attribute, or relationship pointed to by
  a restricted arrowhead from the entity,
  attribute, or relationship that is constraining
  it. The object NurseInCharge is the constrained
  object because she must be certified to be a
  nurse in charge of CareCenter. The constraining
  object is not an entity, and attribute, or a
  relationship.

26
Project Exercise 4

• Compare the class diagram you developed in
  this chapter with the EER diagram that you
  developed in Chapter 4 and with the E-R diagram
  you developed in Chapter 3 in Project Exercise 2.
  What are the differences between these two
  diagrams? Why are there differences?

27
Project Exercise Answer 4

• An object-oriented model is built around objects
  just as the E-R diagram from Chapter 4 is built
  around entities. Object-oriented model
  encapsulates both data and behavior, implying
  that we can use it for data modeling as well as
  for process modeling. In the E-R diagram the
  entity relationships are shown, but in the
  object-oriented model the object has state,
  behavior, and identity.

28
Project Exercise 5

• Did you find any examples of aggregation or
  composition in the description of the project in
  this chapter? Why or why not?

29
Project Exercise Answer 5

• Yes, because aggregation is a part-of
  relationship between a component object and an
  aggregate object. Like the example of a Care
  center with Maternity, Emergency, and Cardiology
  as other objects that aggregate care centers.

30
Student Question 1

• Explain why CareCenter and its subclasses
  Maternity, Emergency, and Cardiology have a
  semantic constraint of complete and disjoint.

31
Student Question 2

• Why are Employee and Carecenter abstract classes?

32
Student Question 3

• Identity the semantic constraints among the
  subclasses Employee, Physician, Patient, and
  Volunteer. Define these constraints as they
  pertain to the subclasses.

33
Student Question 4

• Why does Outpatient have a relationship to visit?