Entity-relationship Model and Mountain View Community
Turgut Tezir TEZIR-1
CS 504.2354
Mountain View Community Hospital
Project Case 3
Project Question:
1. Why would Mountain View Community Hospital want to use entity-relationship modeling to understand its data requirements? What other ways might the hospital want to model its information requirements?
This hospital wants to use E-R modeling to understand data requirements. E-R modeling is very easy to understand and shows all the business rules. • Entity-relationship modeling is logical representation of the data for an organization or for a business area. The E-R model is expressed in terms of entities in the business environment, the relationship among those entities, and attributes of both entities and their relationship. E-R model is normally expressed as entity-relationship diagram, which is graphical representation of the E-R model.
This Hospital also can use Object-Oriented model. • (It is not recommended)Traditional File processing system, but there are lots of disadvantages with this using this system? Hospital can use information engineering, a top-down information systems planning approach.
2. Do there appear to be any weak entities in the description of the Mountain View Community Hospital data requirements? If so, what are they?
No weak entity. However, treatment can be a week entity. • Treatement_ID 1. Threatment _Num 2. Threatment_Name
3. What is the significance in developing an E-R diagram for Mountain View Community Hospital to the third entry the preceding list, which states that some patients are assigned to a bed, but outpatient are not assigned to bed?
Some patient assigned to a bad, some of them don’t PATIENT has two subtypes • In Patient (has relationship between Bed) • Out Patient
4. Is Mountain View Community Hospital itself an entity type in a data model to represent its data requirements?
No. We don’t need to model Hospital entity type.
PROJECT
CS 504.2354
Mountain View Community Hospital
Project Case 3
Project Question:
1. Why would Mountain View Community Hospital want to use entity-relationship modeling to understand its data requirements? What other ways might the hospital want to model its information requirements?
This hospital wants to use E-R modeling to understand data requirements. E-R modeling is very easy to understand and shows all the business rules. • Entity-relationship modeling is logical representation of the data for an organization or for a business area. The E-R model is expressed in terms of entities in the business environment, the relationship among those entities, and attributes of both entities and their relationship. E-R model is normally expressed as entity-relationship diagram, which is graphical representation of the E-R model.
This Hospital also can use Object-Oriented model. • (It is not recommended)Traditional File processing system, but there are lots of disadvantages with this using this system? Hospital can use information engineering, a top-down information systems planning approach.
2. Do there appear to be any weak entities in the description of the Mountain View Community Hospital data requirements? If so, what are they?
No weak entity. However, treatment can be a week entity. • Treatement_ID 1. Threatment _Num 2. Threatment_Name
3. What is the significance in developing an E-R diagram for Mountain View Community Hospital to the third entry the preceding list, which states that some patients are assigned to a bed, but outpatient are not assigned to bed?
Some patient assigned to a bad, some of them don’t PATIENT has two subtypes • In Patient (has relationship between Bed) • Out Patient
4. Is Mountain View Community Hospital itself an entity type in a data model to represent its data requirements?
No. We don’t need to model Hospital entity type.
PROJECT