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 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