| 修訂 | 7baef335ad4505517add3374c33f093c618b11eb (tree) |
|---|---|
| 時間 | 2020-02-01 01:21:27 |
| 作者 | Albert Mietus < albert AT mietus DOT nl > |
| Commiter | Albert Mietus < albert AT mietus DOT nl > |
cleanup text
SoftwareCompetence/RequirementsTraceability-demo/demo/demo1-tracking.rst (diff) SoftwareCompetence/RequirementsTraceability-demo/index.rst (diff)| @@ -20,6 +20,13 @@ | ||
| 20 | 20 | .. needflow:: |
| 21 | 21 | :tags: demo1 |
| 22 | 22 | |
| 23 | +.. attention:: | |
| 24 | + | |
| 25 | + The graph (as well as the table) clearly shows there is no tests for :need:`CALC1_DIV`. For this demo, it’s | |
| 26 | + intentional. Note, however, that *--as there are 4 tests defined--* one can easily oversee this; even in this simple | |
| 27 | + case! | |
| 28 | + | |
| 29 | + | |
| 23 | 30 | Summary |
| 24 | 31 | -------- |
| 25 | 32 |
| @@ -10,9 +10,9 @@ | ||
| 10 | 10 | :width: 33% |
| 11 | 11 | :align: right |
| 12 | 12 | |
| 13 | - * For a simple development cycle it easy to trace the validation the product: | |
| 13 | + * For a simple development cycle, it easy to trace the validation the product: | |
| 14 | 14 | *All features should be covered by a test, and all should pass*. |
| 15 | - * When multiple products --or multiple releases-- are mandatory this becomes quickly ambiguous: | |
| 15 | + * When multiple products --or multiple releases-- are mandatory, this becomes quickly ambiguous: | |
| 16 | 16 | *Some test have to pass and only the essential specifications needs test-cases.* |
| 17 | 17 | * Then ‘requirements traceability’ becomes crucial: |
| 18 | 18 | **It gives insight in which ‘specs’ are required by each product/release and which tests are essential.** |
| @@ -34,8 +34,8 @@ | ||
| 34 | 34 | |
| 35 | 35 | |
| 36 | 36 | .. rubric:: Content |
| 37 | -.. toctree:: XXX | |
| 38 | - :maxdepth: 1 | |
| 37 | +.. toctree:: | |
| 38 | + :maxdepth: 2 | |
| 39 | 39 | |
| 40 | 40 | goal/index |
| 41 | 41 | demo/index |
Fork