Article - Principles Haki & Legner 2013 Flashcards

1
Q

What is EA according to Haki & Legner?

A

The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is included in EA artifacts?

A
  1. Representation Models
    Conceptualized by means of different EA methods, models and frameworks
  2. Principles
    Guiding principles for an architecture’s design and evolution.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are 5 general characteristics of principles?

A
  1. Can be attributed to different architectural layers.
  2. Should be based on business and IT strategies
  3. Refer to the construction of an organization
  4. Metrics can be identified for each principle to measure its fulfilment.
  5. Each principle should be described in a principle statement, along with a rationale to explain why this principle is helpful in attaining a predetermined goal, as well as implications that describe how to implement the principle.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the three most important characteristics for principles to be considered principles instead of non-principles?

A
  1. Principles are used to govern architecture design and evolution;
  2. Principles should be used to limit design space and guide design decisions;
  3. Principles should harmonize IT projects to predefined (business) goals;
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are three kinds of non-principles?

A
  1. Confusion of principles and EAM goals
    (I.e. Develop competencies)
  2. Confusion of principles and EAM practices
    (I.e. IS planning as integral part of business planning)
  3. Confusion of principles with low-level governance means, representing standards and guidelines
    (I.e. Access rights must be granted at the lowest level necessary)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Why is confusion with EAM goals a non-principle?

A

They do not limit design space or guide design decisions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Why is confusion with EAM practices a non-principle?

A

They do not provide guidance or contribute to design decisions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Why is confusion with governance a non-principle?

A

That is if they are low-level governance policies, which are merely standards - not principles.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the most important principles (ranked according to experts) ?

A
  1. Standardization
  2. Compliance
  3. Data consistency
  4. Modularity
  5. Reusability
  6. Interoperability
  7. Integration
  8. Usability
  9. Simplicity
  10. Portability
  11. Centralization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What do experts want to change to the list?

A
  • Remove centralization. Replace it with Technology Independence
  • Add ‘Reduce technology variatons’ - can be added to standardization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is standardization?

A

Uniformity in data, documents, programming language, applications and processes. This reduces technical diversity and complexity

  • Can be enforced through compliance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is compliance?

A

Conformity with corporate, industry specific and universal standards as well as laws and regulations.

-> supports standardization by setting procedures to enforce standards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is data consistency?

A

Level of shared definitions and consistency for stored data. Includes the degree to which datasets satisfy integrity constraints.

-> minimum requirement for integration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is modularity?

A

Degree to which an IT portfolio’s decomposition into loosely subsystems that communicate through standardized interfaces. Having minimum interdepenencies.

-> prerequisite of reusability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is reusability?

A

Having applications for common use. Develop them so that they an be used across the organization.

-> Requires modularity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is interoperability

A

Compatibility and connectivity among all hardware, software & communication components. Early design decision to ensure integration.

->Prerequisite for integration

17
Q

What is integration?

A

The integration of enterprise, process, data, application and infrastructure. Example: one application to access all functionalities.

-> Requires interoperability and data consistency

18
Q

What is usability?

A

Shared look-and-feel and support of ergonomic requirements. Note: strong emphasis on usability at the cost of functionality is not advised.

-> Requires simplicity in the interfaces

19
Q

What is simplicity?

A

Minimal dependencies between different modules in business and application and architecture

-> Supports usability (ease-of-use)

20
Q

What is portability?

A

Ability of a system to run in different computing environments. Leads to flexibility in hardware & vendor selection, lower cost and facilitates migration to new technologies.

21
Q

What is centralization?

A

Centralization of application components throughout the organization. Feasibility is questioned due to high cost.

22
Q

What does reusability improve?

A

Maintainability, quality, portability and software productivity.

23
Q

What two principles are required for integration?

A
  1. Interoperability

2. Data consistency

24
Q

How can standardization be enforced?

A

Through compliance

25
Q

What is required for reusability?

A

Modularity

26
Q

What is required for usability?

A

Simplicity of interface architecture

27
Q

What are EA principles’ roles and application (4) ?

A
  1. They should guide and limit design decisions
  2. Enable reaching EA goals and keep consistency in the EA
  3. High level granularity to impact EA decision on all enterprise levels
  4. Limited number, understandable and supported by key members.