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

New way of product development

Today is the era of fast-paced world and competitive world. Companies are realizing that the old sequential approach to developing new products won’t get the job done and product can’t be reached to market when compared to competitors. The 4 stages of product development are as follows – R&D, Growth, Maturation, and Decline. Instead of sequential approach, companies are using holistic approach – as in rugby game, the ball gets passed within the team as it moves as a unit up the field. This holistic approach has six characteristics: 1)     Build-in-instability 2)   Self-organizing project teams 3)   Overlapping development phases 4)   Multi-learning 5)   Subtle (very clear and strong) control 6)   Organizational change to explore and learning The above six characteristics forming a fast and flexible process for new product development with advantage of act as a change agent, creative, market driven ideas, flexi...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more