Module 3 and 4: Architecture and Architects. Precursors

What is the primary role of an IT architect?

• Designing websites

• Designs and plans the structure of information systems, technology platforms, and IT environments

• Managing construction sites

• Writing software code

Answer explanation

The correct answer is: Designs and plans the structure of information systems, technology platforms, and IT environments. This perfectly encapsulates the role. IT architects are responsible for the high-level design of an organization's IT landscape, ensuring that different systems, applications, and technologies work together effectively to support business goals. This involves understanding business requirements, selecting appropriate technologies, defining standards, and creating blueprints for implementation

Which of the following is NOT typically part of an architect's responsibilities?

• Meeting with clients

• Assessing existing systems and infrastructure

• Coding

• Ensuring compliance with regulatory standards and organizational policies

Answer explanation

The activity that is NOT typically part of an architect's responsibilities (specifically in the context of an IT architect or a traditional architect) is:

• Coding. Here's a breakdown:

• Meeting with clients: Architects (both IT and traditional) regularly meet with clients to understand their needs, present designs, gather feedback, and ensure alignment with project goals.

• Assessing existing systems and infrastructure: IT architects spend significant time analyzing the current state of an organization's IT systems and infrastructure to identify strengths, weaknesses, and areas for improvement, which informs their design of future solutions. Traditional architects assess existing structures for renovations or new builds.

• Coding: While IT architects often have a strong technical background and may have previous coding experience, their primary role is high-level design and planning of systems, not writing the actual software code. That's the responsibility of software developers. Traditional architects design buildings, they don't physically construct them.

• Ensuring compliance with regulatory standards and organizational policies: Architects must ensure that their designs adhere to relevant regulations, industry standards, and internal policies (e.g., building codes, security standards, data privacy regulations). This is a critical responsibility to avoid legal issues and ensure the effectiveness and safety of the architecture.

Enterprise Architects are responsible for:

• Designing landscapes

• Setting guidelines for future growth

• Writing code for business applications

• Selling company products

Answer explanation

Enterprise Architects are responsible for: Setting guidelines for future growth. Here's why:

• Designing landscapes: This refers to a landscape architect, a different profession.

• Setting guidelines for future growth: This is a core responsibility of an Enterprise Architect. They develop the overarching blueprint for an organization's IT strategy, processes, and technology, ensuring that current and future initiatives align with business goals and support long-term growth and evolution. This includes establishing standards, principles, and roadmaps.

• Writing code for business applications: This is the role of a software developer or programmer, not typically an Enterprise Architect. While EAs have a strong technical understanding, they focus on the high-level design and strategic direction, not the hands-on coding.

• Selling company products: This is the role of sales professionals.

What does “SMART” in objectives stand for?

• Specific, Marketable, Ambitious, Relevant, Timely

• Strategic, Measurable, Achievable, Realistic, Transparent

• Specific, Measurable, Achievable, Relevant, Time-framed

• Simple, Manageable, Actionable, Repetitive, Testable

Answer explanation

The correct answer is: Specific, Measurable, Achievable, Relevant, Time-framed

The SMART acronym is a widely used framework for setting effective objectives. Here's what each letter stands for:

• Specific: Objectives should be clear and well-defined, leaving no room for ambiguity.

• Measurable: There should be a way to track progress and determine when the objective has been achieved.

• Achievable: Objectives should be realistic and attainable, considering available resources and constraints.

• Relevant: Objectives should align with broader goals and be meaningful to the individual or organization.

• Time-framed: Objectives should have a deadline or a specific timeframe for completion, creating a sense of urgency and accountability.

Which of the following is NOT a perspective in Enterprise Architecture?

• Application Architecture

• Client-Management Architecture

• Technology Architecture

• Business Processes Architecture

Answer explanation

The correct answer is "Client-Management Architecture" . It is NOT a standard perspective in Enterprise Architecture. While client management is a critical business function, it would typically be described and analyzed within the Business Processes Architecture and supported by the Application Architecture (e.g., CRM systems) and Data Architecture.

In Enterprise Architecture, the common perspectives (often called "domains" or "layers") that provide a holistic view of an organization are:

• Business Architecture: Focuses on the organization's strategy, capabilities, value streams, processes, and organizational structure.

• Data Architecture / Information Architecture: Deals with the structure, organization, and flow of information within the enterprise.

• Application Architecture: Describes the individual applications, their functionalities, and how they interact and integrate with each other.

• Technology Architecture / Infrastructure Architecture: Encompasses the underlying hardware, software, networks, and platforms that support the applications and data.

The balanced scorecard was developed to focus on which of the following?

• Exclusively financial matrices

• Company vision using four areas beyond finance

• Daily operational activities

• Legal compliance

Answer explanation

The balanced scorecard was developed to focus on: Company vision using four areas beyond finance.

Here's why:

• Exclusively financial metrics is incorrect because the very purpose of the balanced scorecard was to move beyond an exclusive focus on financial performance.

• Daily operational activities is partially true in that the balanced scorecard helps link strategic goals to daily operations, but its primary focus is on strategy execution and overall vision, not just the day-to-day.

• Legal compliance is important for any business, but it's not the central focus of the balanced scorecard framework.

A “Statement of Architecture Work” is created by the Enterprise Architect after:

• Analyzing past architecture projects

• Defining needs, scope, and requirements

• Selecting building materials

• Designing technical components

Answer explanation

A "Statement of Architecture Work" is created by the Enterprise Architect after: Defining needs, scope, and requirements.

This document, particularly prominent in frameworks like TOGAF (The Open Group Architecture Framework), essentially acts as a contract or agreement to formally initiate and define an architecture project. It outlines:

• Objectives: What the architecture work aims to achieve.

• Scope: The boundaries of the architecture work, clearly stating what's in and out.

• Deliverables: The specific outputs of the architecture project (e.g., architecture descriptions, models, roadmaps).

• Roles and Responsibilities: Who is involved and what their roles are.

• Timeline and Resources: Estimated timeframes and resources required.

• Acceptance Criteria: How the successful completion of the architecture work will be measured.

In the Aim Hierarchy, what level is characterized by quantitative or qualitative measurements?

• Requirements

• Goals

• Directives

• Objectives

Answer explanation

The correct answer is: GOALS. In the Aim Hierarchy - Goals are defined as the top-level aims that can be qualitative or quantitative, often using the SMART framework.

Goals:

• Top-level in the aim hierarchy.

• Can be qualitative or quantified.

• May be Business or Technical in nature.

Objectives on the other hand are:

• Middle-level aims.

• Directly support goals.

• Typically more detailed and specific than goals.

• Often include KPIs (Key Performance Indicators) and are measurable, but not always the level where qualitative/quantitative distinction is first emphasized.

Which of the following describes a “Directive”?

• An engineering process

• A governance tool to guide objectives

• A financial target

• A building permit

Answer explanation

A "Directive" is best described as: A governance tool to guide objectives.

Here's why:

• An engineering process: While directives might be part of an engineering process (e.g., a directive to follow certain design standards), they are not an engineering process themselves.

• A financial target: Financial targets are a type of objective or goal, not a directive.

• A building permit: A building permit is a legal authorization, a type of permission, not a directive in the broader sense of guiding strategy or behavior.

In an organizational or strategic context, a directive is essentially an instruction, rule, or policy issued by an authority (e.g., management, a governing body) that guides actions, decisions, and objectives. They are used to ensure alignment, compliance, and consistent behavior towards achieving overall goals. They dictate how certain things should be done or what priorities should be followed.

Business Rules in a Directive Hierarchy are typically used to:

• Generate marketing plans

• Manage architectural designs

• Direct and restrict procedures in data processing

• Define company strategy

Answer explanation

Business Rules in a Directive Hierarchy are typically used to: Direct and restrict procedures in data processing.

Here's a more detailed explanation:

• What are Business Rules? Business rules are statements that define or constrain some aspect of the business. They reflect the policies, practices, and guidelines that an organization follows. They dictate what can or cannot happen, when it can happen, and under what conditions.