Enterprise Architecture

Enterprise Architecture

1. Architecture can vary in differenes

   • such as scale, process, costs and schedule and skills and development skills required to make the architect. without an architecture, things can go bad in the making of buildings etc.. not thought out right.
   • Poor achitecture = bad design and fails to meet requirements
     • Good architecture means its coherent and fit for purpose.

2. IEEE 1471-2000

   • This is the software architecture standard! Recommended Practice for Architectural Description of Software-Intensive Systems

3. software architecture is driven by

   • performance, resilience, usability and maintainability. 
   • Stakeholders
     • stakeholders need to be part of the software design and architecture as these are the people who will be using it. 

4. Departments that need to be taken into consideration with architecture..

   • Finance Human resources Manufacturing Marketing and distribution Entertainment

5. EA Levels

   • An enterprise architecture is typically thought of as comprising a number of levels.
   • Business
     • Business goals, organisation business processes e.g. how the business is organised. 
     • Application
       • The software application e.g.g HR, CRM (customer relationship management)
       • Technology
         • The infrastructure s/w and h/w capabilities

6. EA offers

   • EA offers a way to understand the as-is enterprise, it’s business processes, applications and infrastructure

7. Archimate illustrates Enterprise Architecture

   • provides languages for modelling at the business, application and technology level.

8. application layer should support the business layer