Enterprise Architecture

Annotations:

• 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.

1. Poor achitecture = bad design and fails to meet requirements
   1. Good architecture means its coherent and fit for purpose.

Annotations:

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

Annotations:

• performance, resilience, usability and maintainability. 

1. Stakeholders

   Annotations:

   • stakeholders need to be part of the software design and architecture as these are the people who will be using it. 

Annotations:

• Finance Human resources Manufacturing Marketing and distribution Entertainment

Annotations:

• An enterprise architecture is typically thought of as comprising a number of levels.

1. Business

   Annotations:

   • Business goals, organisation business processes e.g. how the business is organised. 
   1. Application

      Annotations:

      • The software application e.g.g HR, CRM (customer relationship management)
      1. Technology

         Annotations:

         • The infrastructure s/w and h/w capabilities

Annotations:

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

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