Object-Oriented Requirements: Reusable, Understandable, Verifiable

Abstract

Insufficient requirements reusability, understandability and verifiability jeopardize software projects. Empirical studies show little success in improving these qualities separately. Applying objectoriented thinking to requirements leads to their unified treatment. An online library of reusable requirement templates implements recurring requirement structures, offering a starting point for practicing the unified approach.

Seamless Object-Oriented Requirements

“…4) Make the specification drivers work with generic, not actual types; make the generic types part of the enclosing SOORT's declaration. A separate work [14] provides more technical details to help developing new SOORTs.…”

“…• The 23 temporal SRPs for control software [14]. • The repeated real-time semantics [7], through the standard notion of loop variants.…”

“…We have successfully specified all the 23 recurring temporal SRPs in the form of SOORTs [14]. While the complexity of the original temporal SRPs varies significantly, the complexity of SOORs inheriting from our SOORTs remains at the same level.…”

“…While the complexity of the original temporal SRPs varies significantly, the complexity of SOORs inheriting from our SOORTs remains at the same level. In a recent work [14] we polish the notions of SOORs and SOORTs to the level at which the specification of resulting SOORs relies purely on inheritance.…”

“…• The repeated real-time semantics [7], through the standard notion of loop variants. • The 21 ADT specifications recurring in the requirements literature [14]. Some of the control software SRPs have tricky formal semantics.…”