simondelliott

Architecture principles

To ensure the objectives and expectations of the project are achieved, try and use these principles in the design decision making processes.

• Re-use: Components of the platform that are already in place (e.g. components exiting in the manufacturing chain, etc.) should be re-used where possible.
• Integration: into existing infrastructure: The design should not adversely affect the existing infrastructure, networks or business procedures.
• Cost: To deliver a cost-effective solution which presents future opportunities for re-use and increased scope of operation.
• Openness: The design should be compliant to open standards where applicable in order to support flexibility and a modular architecture (reducing risk and cost of change).
• Performance: The performance of the design is important to the success of the service; it is a key factor to user satisfaction. The design should consider performance in the functional and technical design of each area and component.
• Robustness: The design should ensure service availability in the event of key component failure, the design must also offer a sliding scale of redundancy.
• Operability: The design should support robust and efficient operations management.
• Scalability: The design should be able to support short term increases in load (planned and unplanned), and long term growth in application resources.
• Presentation: The design should be documented and presented in a manner that is comprehensible to all stakeholders.

It is anticipated that requirements may change, evolve or even be de-scoped from the project brief stage to the point of implementation, however you must always endeavor to ensure business objectives are met from an architecture standpoint using the above guiding principles.