Main features

Still under construction. will be completed before end of november

Manage traceability, especially with links in models

Capture all links useful for program traceability

Between requirements

Between one requirement and any other artefact (design element , test, code...) including model elements (especially SysML traceability links)

Between artefacts (for instance: allocation of functions on components)

Display aggregated traceability and provide queries and navigation facilities to models that participate to traceability

Can capture traceability links coming from various sources of data and models according to the registered connectors. For instance, with sysML traceability engine, we can collect "satisfy", "refine", "verify" links but also "allocate" links between SysML model elements. All links captured are automatically displayed in a table. You can also use a traceability viewer to show some specific traceability links. You start with one or several root elements and the treeview will display all traceability paths starting from root elements: either in downward direction or in upward one.

Ability to complete and guide traceability

Links captured can come from various languages but sometimes we need to establish links between several models that might be of different language. We can define own traceability link types between elements that can exist in different languages. Once defined, those link types are used to support creation of dynamic links. If you try to drag one object to another object and if there exist at least one traceability link type matching this context, the traceability link type popups and you can use it to create a link. Note: there can be several traceability link types that popup: it is up to you to choose the one you want. Because those links appear dynamically according to the context, it gives contextual guidance.

Ability to export traceability

Can export traceability links with requirements in both Excel and CSV formats. Note: currently this export is restricted to links with requirements. Other links (for instance SysML "allocate") are not exported.

manage requirements sources

Ability to define custom requirement data models

Can define own custom data model with custom requirement types (for instance "functional", "safety", "security"...) and associated attributes, and scopes to classify requirements into levels (system, subsystem, SW, HW...).

Ability to import or reference requirements, align them on a given data model and aggregate them for efficient follow-up

Can extract requirements from any external source and import them in ReqCycle (copy) or reference them (link). Currently only "import" is supported (Reference is under progress at design stage). Note: when requirements are imported or referenced, they are aligned on a data model (mapping).

Ability to create own requirements at current engineering level

Can also create own requirements with ReqCycle.

Ability to identify requirements within models

ReqCycle provides an OCL connector able to provide queries to identify requirements from an EMF model.

[back to ReqCycle wiki main page: https://polarsys.org/wiki/ReqCycle]