Skip to main content

Certified Enterprise Architect Professional (CEAP) - Module 3 - Architecture and Architects

Architecture and Architects:

Enterprise Architects provide navigation and guidelines to achieve future goals, thus generating growth and progression.

Enterprise Architects must consider architecture from several perspectives, including:

1) Application Architecture:

Application architecture is the blueprint for designing and building a software application.

Example:

Microservices architecture

2) Technology Architecture:

Technology architecture is a component of enterprise architecture that focuses on the technical aspects of an organization's IT infrastructure.

Example: 

interconnected hardware and software, like networks, clouds, servers, clients, printers, tablet PCs, and smartphones.

3) Business Process Architecture:

In enterprise architecture, "Business Process Architecture" refers to a hierarchical model that maps out an organization's key business processes, outlining their relationships, dependencies, and interactions to ensure alignment with the overall business strategy, essentially providing a visual representation of how work is done within a company to achieve its goals; it's a critical component of enterprise architecture that focuses specifically on the design and structure of business processes within an organization. 

Example:

  • Customer Order Processing
  • Inventory Management
  • Product Delivery
  • Customer Support

4) Information Architecture:

In enterprise architecture, "information architecture" refers to the structured design that defines how an organization manages and accesses its data and information assets, including the structure, classification, and relationships between different data sources, essentially acting as a blueprint for how information flows within the entire enterprise and supports business operations; it's considered a key component of the broader enterprise architecture framework, focusing specifically on the information layer and how it interacts with other architectural elements like applications and business processes. 

Example:

An example of information architecture within enterprise architecture would be a large retail company like Walmart, where their "Retail Link" system acts as a central hub for managing product data, inventory levels, sales information, and supply chain logistics across all stores, allowing them to access real-time information for efficient decision-making and optimized operations, effectively structuring and organizing data from disparate systems across the enterprise to provide a unified view for analysis and action; this structured data access is a key component of their information architecture within the broader enterprise architecture. 

5) Business Service Architecture:

This perspective focuses on the business processes that the organization uses to carry out its operations. It includes aspects such as workflow, business rules, and process automation.

Example:

Customer order processing: This service would encompass the entire process from when a customer places an order to when the product is shipped, involving interactions with different systems like inventory management, payment processing, and shipping logistics.


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