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