Presentation is loading. Please wait.

Presentation is loading. Please wait.

CL2 Proposal #9: Mapping requirements to requisites.

Similar presentations


Presentation on theme: "CL2 Proposal #9: Mapping requirements to requisites."— Presentation transcript:

1 CL2 Proposal #9: Mapping requirements to requisites

2 Current Situation Current –The Requisites element identifies SDD packages that can be used, if necessary, to satisfy requirements. –The only way to know if a Requisite satisfies a requirements is to compare the resulting resource and resulting change elements of the requisite package with the requirement statements. Issues –Comparing requirements to result definitions is complex and error prone. –Result definitions at the package level cannot take into account conditions and features and so cannot be accurate in every situation.

3 Schema for one requisite definition

4 Proposal Explicit mapping. SDD authors know when they decide to include a requisite which requirements it can satisfy. This proposal allows that information be encoded in the SDD by allowing requirements to state directly which requisites can be used to satisfy the requirement. This is done by giving requisites an ID and referencing the ID in the requirement. Requirements / Alternatives / ResourceConstraints / Individual constraints Requirements are made up of those four parts. A requisite might satisfy only one individual constraint, a requirement as a whole, or any combination of any of the intermediate parts. This proposal allows the mapping to be defined in the Requirement, the Alternative or the ResourceConstraint but not in the lowest level constraints. The specification will explain how to choose where to put the mapping.

5 Proposed Schema Add this attribute definition: To these three type definitions:

6 Proposed Specification Text (This a rough draft.) When defining requirements, the SDD author can indicate which requisites can be used to satisfy the requirement. When one requisite will satisfy the entire requirement, including all constraints and alternatives, the requisiteRef field in the Requirement element can be set to the ID of the requisite. When one requisite will satisfy an entire alternative of a requirement including all constraints defined within the alternative, the requisiteRef field in the Alternative can be set. When a requisite will only satisfy one or more ResourceConstraints defined within the Requirement or alternative, the resourceRef field in the ResourceConstraint(s) can be set.


Download ppt "CL2 Proposal #9: Mapping requirements to requisites."

Similar presentations


Ads by Google