Retiring

When systems and processes are no longer required

Portfolio Manager provides a way to retire elements from your model in a controlled way, because if the element you want to delete is being deleted in the real world, then deleting it from the model is only a small part of the story.

For example, if the element represents a business process which you won’t use any more, or a software system which is being decomissioned, then EA needs to support that removal. A simple delete-from-model won’t help you manage the orderly removal of that business idea.

As well as branching to update elements, or adding new proposed content, Portfolio Manager also includes a state of ‘branched-to-retire’.

When a project creates branched to retire elements, the impact analysis immediately notifies at the time of the branch if other projects are dependent on this element – either the baseline or future planned versions. The project teams can then get together to discuss, cancel, or revisit the scope of their projects.

When those elements are promoted to ‘planned-to-retire’, then the impact analysis again alerts the project team of any dependencies which still exist – so that the necessary conversations  can happen.

Other projects. which are dependent on the baseline or planned version of this element, will see their dependency flagged as ‘fatal’ when they run an impact analysis.

For more information see the Help article Retiring elements