Chat now with support
Chat mit Support

erwin Enterprise Architect Agile v3 - User Guide

erwin EA Agile_V3_User Guide
Administration MetaModel Data Source Views Diagrams Top Tips

Business Capability Increment Viewpoint

Business Capability Increment Viewpoint

The Business Capability Increment viewpoint can show how a project can bring about one or more capability increments, and a single increment can be realized by one or more projects.

This view is usually for a single capability increment, and includes the motivation aspects of the increment.

The object types for this viewpoint are:

Driver, Assessment, Metric, Goal, Work package, Deliverable, Capability increment, Plateau and Business capability. 

 

 

Idea to Delivery Viewpoint

Idea to Delivery Viewpoint

The Idea to Delivery viewpoint is used to show how an idea is realised through to implementation.

The motivation behind the idea and work packages is included.

This view is ideal to those users modelling both Innovation Management and Agile EA concepts.

The object types for this viewpoint are:

Idea, Requirement, Goal, Driver, Assessment, Constraint, Principle, Deliverable, Work package, and any Core element.

 

 

Capability to Application Component Viewpoint

Capability to Application Component Viewpoint

The Capability to Application Component viewpoint provides a view of how business capabilities are related with application components.  This view is ideal for users that want to show application portfolios and how they are linked to the capabilities of the business.

The object types for this viewpoint are:

Application component, and Business capability.

 

 

 

Relationship Manual Edit Mode

Relationship Manual Edit Mode

Provides a mode that a diagram can be placed into to 'hide' the representational consistency of our tool within chosen diagrams. This will allow users to build diagrams that they may consider 'snapshotted' or 'finished', that they do not want to then be updated with relationships between model objects, that may be out of context for the particular diagram.

The mode will stop any model relationships being added and made visible to a diagram without input from a user.

The check box on the diagram configure page allows the diagram to be placed in the Manually Update Relationships mode. It will also provide a view of how many hidden relationships the diagram has hidden currently.

Once in this mode when a user opens a diagram, if there has been a relationship added to the model that would have been auto-added to the diagram, they will be presented with a dialog box showing the changes that have not yet been applied

The user can either choose to

Selecting the checkbox of a relationship, which will add the relationship to the diagram and make it visible.

Not selecting the checkbox of a relationship, which will add the relationship to the diagramand then hide it.

 

The diagram is still consistent with the model, but the representation has been chosen by the user...which then allows existing features to work as-is.

Users can continue to update the diagram by drawing relationships - This works as normal.

If a user adds an existing object from the model to the diagram, any existing relationships will be shown to the user in a panel – again they can choose to add or hide

If the user Duplicates an object on the diagram, all of the possible relationships will be presented in the dialog box to select from...Again the user chooses how to update the diagram with this information.

When the diagram is taken out of the mode, the hidden relationships remain hidden (unless the user makes them visible again), and the daigram will go back to auto-adding relationships from the model objects to the diagram.

The diagram is still consistent with the model and will continue to be, with the removal of relationships, objects and changes to objects still being displayed as normal.

 

 

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen