Skip to main content

Certified Enterprise Architect Professional (CEAP) - Module 12: The Enterprise Continuum

The Enterprise Continuum is a framework that classifies all the assets available to an enterprise, and helps to organize and communicate them.

The Enterprise Continuum includes assets like business goals, strategic initiatives, capabilities, policies, standards, and principles. It also includes assets from the wider environment, such as products, research, market factors, and legislation.

It helps:

  1. categorising architecture and solution artefacts.
  2. structuring of virtual repositories.
  3. improves the efficiency of engineering.
  4. helps organise reusable architecture and solution assets.
  5. visual repository for all architecture assets

Two concepts combine to create the Enterprise Continuum:

1)Solutions Continuum 
The assets included in an Enterprise Continuum are determined by the architecture governance function.
2)Architecture Continuum
Practically, the application of an Enterprise Continuum occurs through an Architecture Repository.

In the context of an Enterprise Continuum, "COTS products" refers to commercially available, off-the-shelf software or hardware components that an organization can readily purchase and integrate into their systems, essentially pre-built solutions from the market that can be used without extensive customization, as opposed to developing custom solutions from scratch; within the Enterprise Continuum, these COTS products are considered as readily accessible building blocks that can be leveraged to construct a wider enterprise architecture, allowing for faster implementation and cost-efficiency by utilizing existing, proven technology.

Example of COTS in the Enterprise Continuum:
  1. An organization building a new e-commerce platform might choose to use a COTS shopping cart application to handle online transactions instead of developing one from scratch.
  2. A company looking to implement a project management system could evaluate various COTS options like Asana or Jira or Microsoft Office Suite or Windows Operating System or Standard network security solutions to find the best fit for their needs. 

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