| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
Sometimes the pre-conditions in an action requirement are not
independent and it is necessary to mark pre-conditions as not applicable
in a particular transition.
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
|
|
|
| |
This allows to state the requirement for an interface group directly in
the item.
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
|
|
| |
Remove extra "X" character in some labels.
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
|
|
|
|
|
| |
Add support to specify functional requirements for actions (functions or
macros) via a transition map of pre-conditions to post-conditions. This
will be the work horse for functional requirements. Generation of
corresponding validation tests is supported.
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
| |
Update #3715.
|
|
|
|
|
|
|
|
|
| |
The documentation of the specification items is generated by an RTEMS
qualification tool from a specification of specification items.
Move non-generated content to "req-for-req.rst".
Update #3715.
|
|
This allows to more easily generate the specification item section with
a script using specification items.
Update #3715.
|