Class: hl-req-class:SoftwareRequirementScope
http://www.ontologydesignpatterns.org/cp/owl/hl-requirement-classification.owl#SoftwareRequirementScope
Asserted Class Hierarchy
Annotations (3)
-
comment: "The scope of a requirement is either cross-cutting or non-cross-cutting." (en)
-
comment: "This class is meant for defining two concepts by which early requirements (or high level requirements) can be classified i.e. cross-cutting and non-cross-cutting. In aspect-oriented software development (AOSD) these concepts are used in order to distinguish the type of the aspects of a program. Every major feature of the program, core concern (business logic), or cross-cutting concern (additional features) is an aspect. Aspects can be multi-dimensional by allowing both functional and non-functional behaviour to cross cut any other concerns, instead of just mapping non-functional concerns to functional requirements. For example, logging code can cross-cut many modules, yet the aspect of logging should be separate from the functional concerns of the module it cross-cuts. Isolating such aspects as logging and persistence from business logic is the aim of the aspect-oriented software development (AOSD)."
-
label: "scope of a software requirement"
Equivalents (1)
Superclasses (1)
Disjoints (2)
Usage (5)