Last change
on this file since 244b277 was
244b277,
checked in by Sebastian Huber <sebastian.huber@…>, on 07/27/20 at 07:23:13
|
validation: Support N/A in the action transitions
Sometimes the pre-conditions are not independent and it is necessary to
mark pre-conditions as not applicable in a particular transition.
|
-
Property mode set to
100644
|
File size:
978 bytes
|
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 | spec-description: null |
---|
9 | spec-example: null |
---|
10 | spec-info: |
---|
11 | str: |
---|
12 | assert: |
---|
13 | and: |
---|
14 | - re: ^[A-Z][a-zA-Z0-9]+$ |
---|
15 | - not: |
---|
16 | eq: NA |
---|
17 | description: | |
---|
18 | It shall be the name of a condition or a state of a condition used to |
---|
19 | define pre-conditions and post-conditions of an action requirement. It |
---|
20 | shall be formatted in CamelCase. It should be brief and abbreviated. |
---|
21 | The rationale for this is that the names are used in tables and the |
---|
22 | horizontal space is limited by the page width. The more conditions you |
---|
23 | have in an action requirement, the shorter the names should be. The name |
---|
24 | ``NA`` is reserved and indicates that a condition is not applicable. |
---|
25 | spec-name: Action Requirement Name |
---|
26 | spec-type: requirement-action-name |
---|
27 | type: spec |
---|
Note: See
TracBrowser
for help on using the repository browser.