Question

Goal Models for Software requirements engineering class:

Consider a simplistic engine-control system whose specification includes the following:

(Goal) If PressureToLow then AlarmRaised
(Domain Property) If StartMode then not PressureTooLow

Explain why the condition: StartMode and not AlarmRaised cannot be considered as an obstacle to that goal.

Answer 1

The engine control system like we use in case of vehicles mostly cars, it increases the safety of the user.

The goal modeling is used in the initial phase of the system development. It enables requirements completion to be measured.

In case of a simple engine-control system, there are several components like pressure measuring instrument, an alarm that will raise in case of fatal condition, mode of the start of the engine.

The main goal of a simplistic engine control system is to raise an alarm in case of pressure lowering below a certain level. The pressure in the system is measured using the instrument if it's below the par value that raises to the fatal condition. This will raise the condition to raise the alarm to notify of the situation.

The main property or the domain property states that when engine control system starts, then pressure must not be too low, like when engine control system is switched on using start mode, then it will inform the control system to not lower the pressure.

When StartMode is activated that causes the system to not lower the pressure, that will not fall below the pressure par value. So, it will not raise any fatal condition that might cause the raise the alarm.

So, StartMode and not AlarmRaised cannot be considered as an obstacle in the goal model for the simplistic engine control system.