Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Motivations

Industrial context:

More and more incremental development and reuse in industry: products start from existing baseline and are modified/adapted.

There are many emerging technologies that can be used to deliver new products and it makes a lot of architecture trade-offs to perform and assess.

In order to address those challenges fast and keep or even reduce time to market, industry needs very good impact analysis capabilities from the very beginning of product definition stage.


What are current industrial practices about impact analysis?

Best situation: there are traceability matrix up to date. They give ability to follow change propagation down to team borders: other domains/engineering specialties, other levels of engineering, partners or suppliers....

Else: need to ask experts and have to read a lot of documents to analyse impacts...


Two improvements ideas : better traceability synthesis and better navigation through models

1. get a traceability tree larger and deeper

2. get links between this tree and all concerned models

Here we are: those ideas represent ReqCycle' ambition and main motivations !


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

Back to the top