analyzing conflicting objectives, analyzing risks of not meeting critical objectives, evaluating options against objectives. | Fundamentals of RE Chapter 7 Goal Orientation in RE System objectives are pervasive in RE As seen before . the WHY dimension of RE (Chap. 1) understanding objectives in system-as-is, eliciting objectives of system-to-be (Chap. 2) analyzing conflicting objectives, analyzing risks of not meeting critical objectives, evaluating options against objectives (Chap. 3) specifying the rationale for specific requirements (Chap. 4) checking that system objectives are satisfied by operational requirements (Chap. 5) documenting satisfaction arguments & backward traceability to system objectives (Chap. 6) Þ Goals as key abstraction for driving the RE process Goal orientation in RE: outline What are goals? The granularity of goals and their relationship to requirements and assumptions Goal types and categories Types of goals: behavioral goals vs. soft goals Goal categories: functional goals vs. non-functional goals The central role of goals in the RE process What are goals? Goal = prescriptive statement of intent the system should satisfy through cooperation of its agents "prescriptive statement": in optative mood “shall”, “should”, “must”, . . “Train doors shall be closed while the train is moving” “Loan periods shall be limited to 2 weeks” formulated in terms of problem world phenomena "system": system-as-is, system-to-be software + environment "agent": active system component responsible for goal satisfaction Goal satisfaction requires agent cooperation Maintain [SafeTransportation] on-board train controller + tracking system + station computer + passenger + train driver + . Achieve [BookCopyReturnedToShelves] patron + staff + library software Agent = role, rather than individual must restrict its behavior to meet its assigned goals must be able to monitor/control phenomena involved in assigned goals Agent types software (software-to-be, legacy software, foreign software) device (sensor, actuator, .) human Goals vs. domain properties Domain property = . | Fundamentals of RE Chapter 7 Goal Orientation in RE System objectives are pervasive in RE As seen before . the WHY dimension of RE (Chap. 1) understanding objectives in system-as-is, eliciting objectives of system-to-be (Chap. 2) analyzing conflicting objectives, analyzing risks of not meeting critical objectives, evaluating options against objectives (Chap. 3) specifying the rationale for specific requirements (Chap. 4) checking that system objectives are satisfied by operational requirements (Chap. 5) documenting satisfaction arguments & backward traceability to system objectives (Chap. 6) Þ Goals as key abstraction for driving the RE process Goal orientation in RE: outline What are goals? The granularity of goals and their relationship to requirements and assumptions Goal types and categories Types of goals: behavioral goals vs. soft goals Goal categories: functional goals vs. non-functional goals The central role of goals in the RE process What are goals? Goal = prescriptive
