| | | |

Requirements Oracles

Ivan Jureta

A requirements database contains the information elicited or otherwise collected, used, and produced during requirements engineering. From a requirements database, the requirements oracle selects information relevant for the resolution of the requirements problem, such as which goals are
satisfied, which domain assumptions are violated or maintained, which tasks cannot be executed together. Implemented oracles should enable the resolution of the requirements problem to
become an interactive process, in which the oracle provides feedback about the effects of the changes in the requirements database on the candidate solutions to the requirements problem. We give a definition of the pronouncements of requirements oracles by formally defining their desirable properties.

On-Pronouncements-of-Requirements-OraclesDownload

Unpublished draft; written together with Alex Borgida, Rutgers University.

Similar Posts

What Is Destructive in a Requirements Loop?
| |

What Is Destructive in a Requirements Loop?

ByIvan Jureta

Why is a Requirements Loop a loop, and why is it a destructive loop? Any Requirements Loop has three explanations: an explanation of requirements, of a solution to these requirements, and of how to show that the solution satisfies requirements. Simply put, if an explanation gives the mechanism generating some events of interest (as in…

| | | |

Acceptability Condition for the Relative Validity of Requirements

ByIvan Jureta

A requirements engineering artifact is valid relative to the stakeholders of the system-to-be if they agree on the content of that artifact. Checking relative validity involves a discussion between the stakeholders and the requirements engineer. This paper proposes (i) a language for the representation of information exchanged in a discussion about the relative validity of…

Choice in Absence of Utility and Probability Estimates
| |

Choice in Absence of Utility and Probability Estimates

ByIvan Jureta

In expected utility models, utility quantifies preferences, probability quantifies uncertainty. Sounds simple, elegant, but tends to be expensive. What if options can be identified, but there is no information about preferences or uncertainty in a format that can be translated into, respectively, utility and probability? What is an alternative decision process, which is still structured…

| | | | |

Revisiting the Core Ontology and Problem in Requirements Engineering

ByIvan Jureta

In their seminal paper in the ACM Transactions on Software Engineering and Methodology, Zave and Jackson established a core ontology for Requirements Engineering (RE) and used it to formulate the “requirements problem”, thereby defining what it means to successfully complete RE. Given that stakeholders of the system-to-be communicate the information needed to perform RE, we…

From Decision Theory to Techne, and back
| | |

From Decision Theory to Techne, and back

ByIvan Jureta

I gave two talks on the topic of qualitative decision analysis, which is what Techne was designed to support. At the time, we were looking for conceptual foundations for doing qualitative decision analysis, an alternative to standard decision analysis, which assumes richer information than what we typically have during requirements engineering and system design. Much…

| | | |

Clarifying Goal Models

ByIvan Jureta

Representation and reasoning about information system (IS) requirements is facilitated with the use of goal models to describe the desired and undesired IS behaviors. One difficulty in goal modeling is arriving at a shared understanding of a goal model instance, mainly due to different backgrounds of the system stakeholders who participate in modeling, and the…