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 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more