Managing Functional Completeness

Problems and Solutions

The results of all plans, projects, change requests, etc. often become available slowly and sometimes arrive too late to apply them in the change process. This results in a further backlog between the latest requirements, the delivery and the testing phase.

With the Enterprise Architects approach, messages and services are based on Data Mapping resulting in a very fast delivery of functionality of the smaller components in which way testing can start almost immediately after agreeing on the requirements. Because functionality is build-up from these smaller components, adjustments on the larger components can also be performed in a very fast way.

To enable this collecting and managing the functional requirements and developing them is almost performed in parallel. This is why managing the functional completeness is very important in the Enterprise Architects’ approach. The following Capabilities are supported:

1. Collecting all PROSA, ISO 25010 Quality Measures and other functional and non-functional requirements
2. Managing the delivery according to the Definition of Done based on the Agile Requirements Management system
3. Reporting the realization and Delivery of Functionalities

Tools to support Managing Functional Completeness

To support Managing Functional Completeness Enterprise Architects delivers the following tools:

Advantages of the Enterprise Architects approach

1. When a component has been designed and generated and/or developed testing of the component the readiness status is automatically
   • Collected for managing the status
   • Registered/Updated in an integrated way to collect and manage the completeness of components using subcomponents
   • Reported to the different team members responsible for the delivery
   • Available in the Delivery Dashboards
2. The SAFe™ Core Values are safeguarded and improved as follows
   • Alignment
   • Built-in Quality
   • Program Execution