A Reference Model for Requirements and Specifications

By Carl A. Gunter, Elsa L. Gunter, M. Jackson, Pamela Zave. IEEE Software, 2000

305 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Research Directions in Requirements Engineering (2007, background): “For example, RE reference models [75, 77, 131] decompose requirements-related descriptions into the stakeholders’ requirements, the specification of the proposed system, and assumptions made about the system’s environment.”
On Non-Functional Requirements in Software Engineering (2009, result): “This is consistent with the spirit of the reference model [29], in which (functional) requirements are satisfied through the collaboration between the software system behavior and environment phenomena that are caused by agents in the environment, although here we are also concerned with softgoals t”
Design science as nested problem solving (2009, methodology): “In software engineering this is known as the“reference model for requirements and specification” [11], where in terms of this paper the requirements are stakeholder goals, and specifications are specifications of solution designs.”