Realisation Perspective

Content included here is relatively static, that it does not cover implementation specific that could change.

The statements contained here provide a validation guide for implementation proposals. Needing to change the guide to suit a proposal is a good indicator that proposal is not suitable. Alternatively, it could indicate the requirement of an unusual cross-cutting refactoring activity.

• Code Style & Standard, are the least volatile of all the approaches that have been adopted here and hence is greatly automated and closed to variation.

• Axioms & Idioms describe generic reusable implementations for common code task. Written in the cookbook style the objective is to provide dependable code arrangments which are aligned the to implementation objectives.

• Architectural Structure focuses on the application lifecycle of the large-scale elements and the patterns which are discernable within them.

• Code Form aligns with the structure to drive the arrangement of directories files and the exposure of internal API's and their dependencies.