The third part of the PointZERO® vision will guide you through the application lifecycle model. In this model, the focus is on quality. The application lifecycle model is based on the holistic view of business solutions starting with Strategy, continuing through Analysis and Change, and ultimately resulting in Operation. These are shown at the edge of application lifecycle model below.

The application lifecycle is read counter-clockwise; and the lifecycles contain a number of activities (not necessarily phases), starting from the Concept (in the Strategy segment) going through Business Case, Change Analysis, and onwards. After the Acceptance activity, a solution is implemented and Maintenance activities are carried out. During Maintenance, new ideas or a need for a change may arise, leading to a new cycle of activities starting with Concept again.
The Supervisior of PointZERO (which is shown at the center of the model) ensures that the application lifecycle is not about the project, but about achieving business value. The focus is on the overview of all activities that other people involved may be lacking. The importance of supervision will be more deeply described in the next parts of the PointZERO vision, which will be published on the Business Technology blog.
One will notice that there is no activity for Architecture. This does not mean that Enterprise Architechture (EA) is not important. The reason why EA is not a lifecycle activity is that it serves as an umbrella for multiple projects which provides the framework within which the solutions are developed.
Another important thing is to define the definition of done (DoD) as it is used to determine if the artifact is good enough. This part of designing the systems architecture is handled in the design activity in the application lifecycle model.
In the next part, I will dig deeper into the three tracks every organization (and situation) should aim to follow when implementing the PointZERO® vision. Stay tuned!