| | |

Requirements Contracts: Definition, Design, and Analysis

Ivan Jureta

What are the necessary and sufficient conditions for a proposition to be called a requirement? In Requirements Engineering research, a proposition is a requirement if and only if specific grammatical and/or communication conditions hold. I offer an alternative, that a proposition is a requirement if and only if specific contractual, economic, and engineering relationships hold. I introduce and define the concept of “Requirements Contract” which defines these conditions. I argue that seeing requirements as propositions governed by specific types of contracts leads to new and interesting questions for the field, and relates requirements engineering to such topics as economic incentives, interest alignment, principal agent problem, and decision-making with incomplete information.

Requirements-Contracts-Definition-Design-and-AnalysisDownload

Jureta, I.J., 2021. Requirements Contracts: Definition, Design, and Analysis. arXiv preprint arXiv:2104.14110.

Similar Posts

| | |

Theory of Regulatory Compliance for Requirements Engineering

ByIvan Jureta

Regulatory compliance is increasingly being addressed in the practice of requirements engineering as a main stream concern. This paper points out a gap in the theoretical foundations of regulatory compliance, and presents a theory that states (i) what it means for requirements to be compliant, (ii) the compliance problem, i.e., the problem that the engineer…

| | |

An Agent-Oriented Meta-model for Enterprise Modelling

ByIvan Jureta

The model identifies constructs that enable capturing the intrinsic characteristics of an agent system such as autonomy, intentionality, sociality, identity and boundary, or rational self- interest; an agent being an organizational actor and/or a software component. Such an approach of the concept of agent allows the analyst to have a holistic perspective integrating human and…

Opaque, Complex, Biased, and Unpredictable AI
| |

Opaque, Complex, Biased, and Unpredictable AI

ByIvan Jureta

Opacity, complexity, bias, and unpredictability are key negative nonfunctional requirements to address when designing AI systems. Negative means that if you have a design that reduces opacity, for example, relative to another design, the former is preferred, all else being equal. The first thing is to understand what each term refers to in general, that…

| | |

Finding Incremental Solutions for Evolving Requirements

ByIvan Jureta

This paper investigates aspects of the problem of software evolution resulting from top-level requirements change. In particular, while most research on design for software focuses on finding some correct solution, this ignores that such a solution is often only correct in a particular, and often short-lived, context. Using a logic-based goal-oriented requirements modeling language, the…

Requirements Satisfaction ≠ Customer Satisfaction
| |

Requirements Satisfaction ≠ Customer Satisfaction

ByIvan Jureta

There is engineering quality of a product or service, which is fitness to the specification, and there is perceived quality, or subjective quality, which is proportional to the distance between expectations and experience of the person asked. What is the relationship between these, between specification, requirements, expectations, and experience? This is a longstanding question in…

Requirements as Decision Criteria
|

Requirements as Decision Criteria

ByIvan Jureta

Assuming two or more alternative solutions are available, to make a decision means to pick only one of these, or, equivalently here, to commit to one and ignore others. What role do requirements play in such decision making situations?  In classical decision theory [1], the best solution is the one that yields the highest expected…