Question: Requirements Engineering System Model Diagram - Meeting Scheduling System Consider the root obstacle ConstraintsNOTTransmitted in the obstacle diagram anchored on the goal ConstraintsTransmitted. Explain why

Requirements Engineering System Model Diagram - Meeting Scheduling System
Consider the root obstacle ConstraintsNOTTransmitted in the obstacle diagram anchored on the goal ConstraintsTransmitted.
Explain why the OR-refinement of this root obstacle into the sub-obstacles shown here - namely ParticipantNotCheckingEmail and RequestFilteredByAntiSpammer - is certainly NOT domain complete.
MaximumAttendance ConvenientMeeting ScheduledFromRequest Participantinformed OfScheduledMeeting Attendance If Informed | And MeetingConvenient Participant Not Informed OfScheduledMeeting Informed And Convenient And Not Attends ConstraintsKnown FromRequest Meeting Forgotten NoLonger Convenient Schedules Confused Constraints Requested Constraints Transmitted Communication Working Dates Confused Locations Confused Constraints Not Requested Constraints Not \ Communication Transmitted Not Working ParticipantNot CheckingE-mail RequestFiltered ByAntiSpammer MaximumAttendance ConvenientMeeting ScheduledFromRequest Participantinformed OfScheduledMeeting Attendance If Informed | And MeetingConvenient Participant Not Informed OfScheduledMeeting Informed And Convenient And Not Attends ConstraintsKnown FromRequest Meeting Forgotten NoLonger Convenient Schedules Confused Constraints Requested Constraints Transmitted Communication Working Dates Confused Locations Confused Constraints Not Requested Constraints Not \ Communication Transmitted Not Working ParticipantNot CheckingE-mail RequestFiltered ByAntiSpammer
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
