[423340] [proposal] polarsys.polarsys.reqcycle
Updates as requested (see comment #5).
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=423340
diff --git a/polarsys.reqcycle/proposal.html b/polarsys.reqcycle/proposal.html
index 6a724b8..fe91e95 100644
--- a/polarsys.reqcycle/proposal.html
+++ b/polarsys.reqcycle/proposal.html
@@ -84,12 +84,16 @@
annotations in code…) and to give ability to define links from
those requirements to any development artefact including models, but
also test cases, code…</p>
- <p>There exist open source solutions to manage requirements but
- they generally provide limited flexibility in requirement
- organization/classification. Industry needs tooling able to classify
- requirements and links through a customizable data model to organize
- requirements and links according to scopes (customer, system,
- subsystem A, SubSystem B, …).</p>
+ <p>There exist open source solutions to manage requirements but
+ they generally provide limited flexibility in requirement
+ organization/classification. Industry needs tooling able to:
+ 1) classify requirements and links through a customizable data
+ model to organize requirements and links according to scopes
+ (customer, system, subsystem A, SubSystem B, …);
+ 2) check coverage with traceability matrices and perform impact
+ analysis from customer needs to models. (and models to requirements); and
+ 3) check coverage with traceability matrices and perform impact analysis
+ from customer needs to models. (and models to requirements).</p>
<p>There exist open source solutions that allow creating links
between requirements and other objects but there the creation of links
is generally too generic to provide required guidance and semantics.
