Answer:MVCH wants to use entity relationship modelling to understand data requirements. Entity relationship modelling Covers to basic points i.e.
1)It is very easy to understand and
2)It shows all the business rules.
Entity relationship modelling is logical representation of the data for an organization or for a business area. The entity relationship model is expressed in terms of;
1)entities in the business environment
2)the relationship among those entities
3)the attributes of both entities and their relationship.
MVCH also can use Object-Oriented model. Traditional File processing system, but there are lots of disadvantages with this using this system. Hospital can use information engineering i.e. 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?
Answer: There is no such weak entity. However, treatment can be consider as week entity I.e.
• Treatement_ID
1. Treatment _Num
2. Treatment_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?
Answer: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?
Answer:No. We don’t need to model Hospital entity type.