Page History
...
| Type of application | Life-span | Changes over time |
|---|---|---|
| Proof of Concept (POC) | short After the proof of concept is done, it is thrown away and replaced by the actual implementation. | none After a high degree of changes during the POC, no changes are done after that. The project is often thrown away, as the knowledge gained is the important part. |
| Short Campaign | short Sometimes a company has a special campaign the which runs between weeks and several months. After the campaign is complete, the application is not needed any more. | none Once the campaign is setup, no changes are planned until its completion. Only bug-fixes are performed which affect the currently running campaign. |
| A Single-Purpose Application and departmental applications | long When creating an application for a single purpose or for a single department, it is intended to fulfill this purpose for a long time, until it is succeeded by another application or the purpose becomes voided. | minor - major When the single-purpose is achieved, the changes to it are often minor. It is usually not affected by everything else that is happening in the company. However, single-purpose applications may become mission critical with many end-users. The life-cycle of the application also differs to the life cycle of the data, leading to changes in the application over time. Changes must be realized with no impact and/or risk. This is true for departmental applications as well, which are only affected to changes for this one department, but not by other changes in the company. |
| Enterprise Application | long It is intended to run the majority of functionality with the application. This includes current functions, as well as new functions that will be added in the future. A function could be the selling of a product (mortgage, loans, subsidies, etc.), the internal process handling, etc. | high As the commitment of the customer is high, it is expected that the application can be extended for years to come. New functions will be added frequently, and existing ones need to be changed to reflect the new way of working, or be consistent with the rest. |
...
Maintainability has to be facilitated on many levels. From naming conventions to the overall architecture. This design guide concerns the latter, and discusses the architecture using the concept of Clean Architecture.
Causes of maintainable en agile models
Solution are usually based on generic modules and a specific modules. The advantage of this is that small changes could be implemented quickly. The disadvantage of this approach is an undesirable growth of the generic layer which leads to a high number of dependencies through the application landscape.
Smalle changes usually are:
...
Overview
Content Tools