Skip to main content

Certified Enterprise Architect Professional (CEAP) - Module 13: The Architecture Repository

The Architecture Repository:

An enterprise architecture repository (EAR) is a centralized storage system that stores and manages an organization's IT architecture components, standards, and relationships. It can also be used to document and maintain these components. 

An EAR can store a variety of architecture artifacts, including:

Data, Models and diagrams, Frameworks, Roadmaps, Capabilities, Design patterns, References, Principles, and Governance Register.

example:

The repository architecture style is widely used in various domains and applications. For example, database management systems (DBMS) are based on the repository style, where the database is the central repository and the applications are the components that query and update the data.

Six categories of information should feature within an Enterprise Architecture:

1) The Architecture Metamodel describes the application of an architecture framework, which is adopted by organisations.

2) The Architecture Capability states the processes, structures, and restrictions that support architecture repository governance.

3) The Architecture Landscape shows the state of the operating Enterprise at particular points in time.

4) The Standards Information Base defines the compliance criteria for work governed by architecture.

5) The Reference Library provides templates, guidelines, and models etc. to boost the construction of new architectures.

6) The Governance Log a record of governance activities carried out in the enterprise.

The Architecture Landscape:

Considering the varied and large quantity of stakeholder requirements, the Architecture Landscape is divided into three levels:

1) Strategic Architectures

Provides a long term overview.

Suggests new frameworks for operations and development activity, allowing for executive direction.

2) Segment Architectures

Provides a detailed model to organise and operationally coordinate change .

3) Capability Architectures

Outlines how the enterprise can provide support to a particular component of capability.

Used to provide an indication of current capability, target capability, and capability increments.

The Governance Log:

A Governance Log contains shared information concerning the continuing governance of projects.

Sustaining a shared source of governance information is essential.

Throughout a project, it is important that records are kept of any decisions made

Stakeholders often express interest in governance

The Standards Information Base:

The Standards Information Base is a source of specifications that must be followed by architectures.

The types of specifications are:

  1. Legal and Regulatory
  2. Industry
  3. Organisational

Labels:

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more