Enterprise Project Guiding Principles

on Tuesday, 01 January 2013. Posted in Blog, Enterprise Architecture

 

The following higher level “Guiding Principles” should be used to help shape key decisions as to which software components would deliver functional requirements to a Business Transformation.  Underpinning these guiding principles are some design principles that address specific areas of the solution. These design principles at a higher-level principle are:

             Buy vs. Build - Where possible use a suite rather than the development of bespoke applications. This helps to reduce delivery risk and total cost of ownership;

             Configuration, not Customization - The approach should emphasize “Configuration” rather than “Customization”.  This will help to reduce the implementation timescales, reduce some of the risk associated with software development, and make future changes easier to undertake;

             Good Enough vs. Best of Breed - Solutions should be selected based on them being "Good Enough" to meet Business Needs rather than selecting "Best of Breed."  This prevents over-engineered solutions that deliver minimal additional business benefit;

             Integrated, Resilient and Robust Technology Architecture – The approach to the choice of hardware, software and operating systems should be based on:

             The need to provide architecture that is aligned to the Clients Corporate Technology Framework; (important to listen and respect roadmap)

             The need to provide architecture components that are recognized as reliable choices for mission critical business solutions;

             The need to integrate new architectural components with existing applications using a robust and open middleware platform; and

             The need to minimize data duplication and minimize the risk of loss of data quality.

             Use of Open Standards – The approach to the suggested System Architecture should be based on the use of open standards wherever possible to minimize development time and costs as well as providing a future proof architecture.  In addition, the use of open standards ensures that the resources required to implement and support the architecture going forward do not require specialized knowledge of particular (proprietary) standards.  This minimizes the associated learning and development costs, allowing the focus to be on delivering the functionality required by Business Transformation.

 

Comments (1)

  • Diandra

    Diandra

    20 January 2013 at 19:55 |
    Kewl you souhld come up with that. Excellent!

Copyright 2015 Appsconsultant.com. All rights reserved.