[Zurück]

H. Kaindl, M. Smialek, A. Ambroziewicz, D. Svetinovic, J. Bojarski, W. Nowakowski, T. Straszak, M. el Jamal, L. Hotz, K. Wolter, T. Krebs, H. Schwarz, D. Bildhauer, J. Falb, J. Brogan:
"Structural Requirements Language Definition - Defining the ReDSeeDS Languages";
Bericht für EU, ReDSeeDS, Projektnr. IST-2006-033596; Berichts-Nr. D2.2, 2007; 60 S.

Existing approaches to object-oriented software development mostly focus on software objects, i.e., something within the software. Referring to such objects in a Requirements Specification would blur the distinction between Requirements Specification and SoftwareDesign, however.

The structural part of our requirements specification language deals with models and descriptions of objects existing in the domain (environment) of the software system to be built - domain objects. These objects are part of a Domain Model (to-be) and/or described in a defined vocabulary. This facilitates a better understanding of the requirements.

This deliverable contains the structural part of the requirements specification language, i.e., all the parts of the meta-model and other descriptions dealing with abstractions of important objects existing in the environment of the software system to be built, as well as their attributes and relations, including their relationships to the software system. Note, that this is a structural requirements language definition, but it is not about "structural requirements". This deliverable first gives a conceptual overview of this structural requirements specification language. In the second part, it provides a comprehensive language reference including concrete syntax.

Structural requirements, Requirements Language

http://publik.tuwien.ac.at/files/pub-et_13406.pdf

Projektleitung Hermann Kaindl:
Requirements Driven Software Development System