Context Navigation

requirement-validation.yml @ c970d63

Last change on this file since c970d63 was 9499f8b, checked in by Sebastian Huber <sebastian.huber@…>, on 06/04/20 at 08:34:56

spec: Rename required in mandatory attributes

The term "required" is quite overloaded in the specification context.
Use "mandatory" instead.

Shorten the phrase "explicitly defined attributes" to "explicit
attributes".

File size: 1.5 KB

Line
1	SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
2	copyrights:
3	- Copyright (C) 2020 embedded brains GmbH (http://www.embedded-brains.de)
4	enabled-by: true
5	links:
6	- role: spec-member
7	uid: root
8	- role: spec-refinement
9	spec-key: type
10	spec-value: validation
11	uid: root
12	spec-description: null
13	spec-example: null
14	spec-info:
15	dict:
16	attributes:
17	method:
18	description: \|
19	Validation by test is done through ${test-case:/spec-name} items.
20	spec-type: requirement-validation-method
21	text:
22	description: \|
23	It shall provide the validation evidence depending on the validation
24	method:
25
26	* By analysis: A statement shall be provided how the requirement is
27	met, by analysing static properties of the
28	${/glossary/softwareproduct:/term}.
29
30	* By inspection: A statement shall be provided how the requirement
31	is met, by inspection of the ${/glossary/sourcecode:/term}.
32
33	* By review of design: A rationale shall be provided to demonstrate
34	how the requirement is satisfied implicitly by the software design.
35	spec-type: str
36	description: \|
37	This set of attributes provides a requirement validation evidence. The
38	item shall have exactly one link to the validated requirement with the
39	${requirement-validation-role:/spec-name}.
40	mandatory-attributes: all
41	spec-name: Requirement Validation Item Type
42	spec-type: requirement-validation
43	type: spec

Note: See TracBrowser for help on using the repository browser.