ReqCycle Architecture is divided in 10 parts (corresponding to features)
- org.polarsys.reqcycle.core
o this set of component provides all the core features of ReqCycle which are :
§ core services
· uri identification services for every artifact
· Type identification for uris
· Operation available for elements
·
§ Core tools
· Predicates definition
§ Core utilities
· Injection utilities
· Collection & Iterators APIs
§ EMF Tools
· Generic EMF implementation of services
- org.polarsys.reqcycle.requirement
o this set of component provides all the features needed for requirement management which are :
§ connector services and local connector implementation
§ meta model and services for requirement storage
§ services for impact analysis and sources update
§ generic exporter
§ styling capabilities of requirements views
- org.polarsys.reqcycle.traceability
o this set of component provides all the features needed for traceability which are :
§ Traceability engines for querying traceability
§ Traceability builders to detect traceability
§ Traceability storage for cache and explicit traceability links
§ Set of commands for drag and drop
§ Table and tree views for traceability display
- And 7 features which corresponds to adaptation to technologies :
o org.polarsys.reqcycle.document
§ for document import
o org.polarsys.reqcycle.ocl
§ for ocl connectors
o org.polarsys.reqcycle.papyrus
§ for papyrus integration
o org.polarsys.reqcycle.sirius
§ for Sirius integration
o org.polarsys.reqcycle.rmf
§ for reqif integration
o org.polarsys.reqcycle.xcos
§ for xcos integration
o org.polarsys.reqcycle.jdt
§ for java integration
- Do you certify that the Reqcycle features contain the “incubation” word?
Modification done.
