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

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