61439
Enterprise Architecture
- Architecture can vary in differenes
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.
- Poor achitecture = bad
design and fails to meet
requirements
- Good architecture
means its
coherent and fit
for purpose.
- Good architecture
means its
coherent and fit
for purpose.
- IEEE 1471-2000
Annotations:
- This is the software architecture standard! Recommended Practice for Architectural Description of Software-Intensive Systems
- software architecture is driven by
Annotations:
- performance, resilience, usability and maintainability.
- Stakeholders
Annotations:
- stakeholders need to be part of the software design and architecture as these are the people who will be using it.
- Departments that need
to be taken into
consideration with
architecture..
Annotations:
- Finance Human resources Manufacturing Marketing and distribution Entertainment
- EA Levels
Annotations:
- An enterprise architecture is typically thought of as comprising a number of levels.
- Business
Annotations:
- Business goals, organisation business processes e.g. how the business is organised.
- Application
Annotations:
- The software application e.g.g HR, CRM (customer relationship management)
- Technology
Annotations:
- The infrastructure s/w and h/w capabilities
- EA offers
Annotations:
- EA offers a way to understand the as-is enterprise, it’s business processes, applications and infrastructure
- Archimate illustrates Enterprise Architecture
- provides languages for modelling at the
business, application and technology
level.
- provides languages for modelling at the
business, application and technology
level.
- application layer should support the business layer
Want to create your own Mind Maps for free with GoConqr? Learn more.