The best practice for applying the Business Model Canvas, including its sustainable variants, is to start with the customer-facing elements. The process begins by defining the target Customer Segments and the Value Propositions offered to them. This establishes the core of the business idea. Subsequently, the model details how to reach and interact with these customers through Channels and Customer Relationships. Only then does it define the internal infrastructure (Key Activities, Resources, Partners) required to deliver the value. Finally, the financial implications (Cost Structure, Revenue Streams) and the overarching eco-social impacts are assessed. This sequence ensures the business model is market-driven and viable before detailing operational and financial aspects.

A: This option incorrectly starts with the financial components (Cost Structure and Revenue Streams), which are outcomes of the business model, not the starting point for its design.

B: This option incorrectly begins with the internal infrastructure (Key Resources, Activities, Partners). The infrastructure should be designed to support the value proposition, not define it.

1. Osterwalder

A.

& Pigneur

Y. (2010). Business Model Generation: A Handbook for Visionaries

Game Changers

and Challengers. John Wiley & Sons. The methodology described throughout the book (e.g.

p. 44

"The 9 Building Blocks") consistently advocates starting with Customer Segments and Value Propositions before moving to the left side (infrastructure) and bottom (financials) of the canvas.

2. Joyce

A.

& Paquin

R. L. (2016). The triple layered business model canvas: A tool to design more sustainable business models. Journal of Cleaner Production

135

1474-1486. This paper

which introduces a sustainability-focused canvas

maintains the logical flow of the original

stating

"The process of designing a business model often starts with the value proposition and customer segments" (Section 3.1). https://doi.org/10.1016/j.jclepro.2016.06.067

3. SAP SE. (2021). Business Model Innovation Services. The methodology used in SAP's innovation services aligns with the Osterwalder & Pigneur approach

emphasizing a customer-centric design process that starts with desirability (Value Proposition

Customer Segments) before moving to feasibility (infrastructure) and viability (financials).

The SAP Integration Solution Advisory Methodology (ISA-M) provides a structured, step-by-step approach for defining an enterprise integration strategy. Option C accurately represents this methodology. It begins with assessing the current state (Step 1) and scoping focus areas (Step 2). Crucially, it introduces the core ISA-M concept of identifying technology-agnostic use-case patterns (Step 3) before mapping them to specific technologies (Step 4). This ensures the architecture is driven by business needs, not by pre-selected technology. The final steps, defining best practices (Step 5) and enabling a practice of empowerment (Step 6), are also integral parts of establishing a sustainable and governed integration practice as prescribed by ISA-M.

A: This option describes a generic project rollout but critically omits the ISA-M-specific step of identifying and clustering technology-agnostic use-case patterns before selecting technology.

B: This option focuses on a tactical gap analysis ("white spots") and re-use assessment, lacking the strategic, pattern-based, and governance-oriented framework that defines the ISA-M approach.

1. SAP White Paper: Grefen

T.

Herbort

M.

& de Barros

G. (2020). Integration Solution Advisory Methodology: A methodology for designing a hybrid integration platform and creating an integration strategy. SAP SE.

Section 3

"The Integration Solution Advisory Methodology in a Nutshell

" outlines the core phases which directly align with the steps in option C: Assess the current state (Step 1)

Define integration domains (Step 2)

Identify integration styles/use case patterns (Step 3)

Map styles to technologies (Step 4)

Define guidelines (Step 5)

and Introduce a practice of empowerment (Step 6).

2. SAP Community Blog: Stagge

H. (2021). SAP Integration Solution Advisory Methodology (ISA-M): The ‘How-to’ guide. SAP Community.

This official blog post details the ISA-M template and its core building blocks

explicitly mentioning the "assessment of the existing integration landscape

" defining "integration domains

" identifying "integration styles and use case patterns

" and mapping them to "integration technologies

" which validates the sequence in option C.

3. openSAP Course: SAP’s Integrated Intelligent Suite.

Week 3

Unit 1: "SAP's Integration Strategy

" and Week 3

Unit 2: "Integration Solution Advisory Methodology

" describe the ISA-M framework

emphasizing the importance of a technology-agnostic view of integration requirements (use-case patterns) as a foundational step before technology mapping and governance definition.

The clean-core strategy for SAP S/4HANA is designed to maintain the integrity and upgradeability of the digital core. This is achieved by ensuring that all extensions and customizations are built in a decoupled manner. The fundamental principle is that extensions must exclusively use stable, released, and supported public APIs and extension points. This approach guarantees that when the core SAP system is upgraded, the custom extensions continue to function without requiring rework. Conversely, changes to extensions do not impact the stability of the core system. This mutual protection ensures operational stability, reduces total cost of ownership (TCO), and facilitates faster innovation cycles.

B: This is incorrect because the clean-core principle explicitly forbids direct access to SAP tables. Such access creates tight coupling and is a primary cause of failures during system upgrades.

C: This statement is too absolute and therefore incorrect. While side-by-side extensibility is a key part of the strategy, on-stack (in-app) extensibility is also a valid and often necessary approach within a clean core, provided it uses released APIs.

1. SAP White Paper: Guiding Principles for a Clean Core with SAP S/4HANA. This document states

"A clean core means that the SAP S/4HANA system is kept as close to the standard as possible... Customizations are implemented in an upgrade-stable way

primarily through the use of released SAP APIs." It explicitly advises against modifications of SAP code and direct access to SAP database tables.

2. SAP Help Portal: Extensibility Guide for SAP S/4HANA Cloud. The guide emphasizes

"To keep the core clean

you can only use released SAP objects (APIs

CDS views

and so on) for your extensions. This ensures that your extensions are upgrade-stable." (Section: Extensibility Concept).

3. SAP Application Extension Methodology: This methodology provides a decision framework for choosing the right extension tool. It does not state that side-by-side is "always" preferable but guides architects to choose between on-stack and side-by-side options based on specific technical and business requirements

thus refuting the absolute claim in option C.

The SAP Enterprise Architecture Framework (EAF) is tool-agnostic. Therefore, when a non-SAP EA tool is already deployed the added value of EAF lies in (1) its TOGAF-aligned methodology and (2) its comprehensive reference architecture content. By comparing the EAF methodology with TOGAF ADM you can recommend the lifecycle approach that best meets Wanderlust’s needs (B). In parallel, analysing SAP’s Reference Business Architecture and Reference Solution Architecture accelerates scoping and target-state definition irrespective of the modelling tool in use (D).

A – EAF is explicitly tool-independent; rejecting it solely because of a non-SAP tool is unfounded.

C – While EAF includes SAP architecture services/practices, evaluating paid services is secondary to assessing the freely available methodology and reference content requested by the CIO.

1. SAP AG

“SAP Enterprise Architecture Framework – White Paper” v2.4

2007:

• Sec. 2.1

pp. 5-8 – EAF methodology alignment with TOGAF ADM and tool independence.

• Sec. 3

pp. 17-22 – Reference Business & Solution Architecture content for scoping/target design.

2. The Open Group

TOGAF Standard

10th Ed.

Part II (ADM)

§1 – Describes ADM lifecycle for comparison with SAP EAF methodology.

This stakeholder mapping exercise classifies individuals based on their attitudes and behaviors toward a proposed business transformation. The categorization aligns with standard change management and stakeholder analysis principles.

• Promoters: These individuals actively support and advocate for the change. The SCM Application Owner (proactively upskilling) and the Europe Business Head (favoring consolidation for clear business reasons) both fall into this category. They see the benefits and are willing to help drive the initiative forward.
• Opponents: These stakeholders are actively against the change and often provide rational, business-based arguments for their position. The Australia Plant Head is an opponent because he discourages the change by citing specific operational concerns regarding regulatory flexibility.
• Resistors: These individuals are also against the change, but their opposition is often rooted in personal fears, attachment to the status quo, or a perceived loss of power, rather than strategic business objections. The Dealer Management Application Owner's preference for continuity due to "fear of losing position" is a classic example of resistance.

MIT OpenCourseWare: The principles of stakeholder classification are a fundamental component of project and systems management. Stakeholders are typically categorized based on their level of support (e.g., advocate, supporter, neutral, resistor, blocker) and influence. The provided scenario uses a common classification scheme (Promoters, Opponents, Resistors) to map stakeholder attitudes.

Source: MIT OpenCourseWare, 16.852J / ESD.34J, Integrating the Lean Enterprise, Fall 2005. Lecture 5: Stakeholder Analysis. (This course material discusses identifying stakeholder positions and interests to manage them effectively).

URL: https://ocw.mit.edu/courses/16-852j-integrating-the-lean-enterprise-fall-2005/a63a557b7f14b30171658e4933948589_lecture5.pdf (Page 11 discusses "Assessing Stakeholder Positions" and "Stakeholder Commitment Analysis").

Peer-Reviewed Publication (IEEE): Academic literature on change management reinforces these classifications. Opponents are distinguished from resistors by the nature of their opposition; opponents often engage in debate with logical arguments, while resistors may be more passive or emotionally driven. Promoters are identified by their active advocacy.

Source: de Souza, C. A., & de Vasconcelos, J. B. (2005). From the stakeholder concept to the stakeholder management process in software engineering projects. 2005 Latin American Conference on Electrical Engineering and Informatics.

URL: https://ieeexplore.ieee.org/document/1560371 (Section III-B, "Stakeholder Analysis," discusses classifying stakeholders based on their potential for threat or cooperation, which aligns with the opponent/promoter dynamic).

Architecture principles are guiding statements that link business strategy to architectural decisions. The pairings reflect this direct link. Minimizing water loss is a specific environmental and compliance goal. A nuanced cloud strategy (reluctant but open) directly matches the "cloud first, not cloud only" principle. Product initiatives like smart batteries are drivers of innovation and business agility. Replacing bespoke applications is an explicit move towards common, standardized software. Finally, optimizing TCO is achieved by reducing technological variety and preferring subscription/purchase over costly custom builds ("subscribe before buy before build"), which simplifies maintenance and support.

The Open Group, TOGAF® Standard, 10th Edition, Section 17.2, "Architecture Principles": This section explains that principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. A good principle is tied to a business outcome. For example, the principle "Minimize technology diversity" directly supports the business outcome of "lower total cost of ownership."

URL: https://pubs.opengroup.org/architecture/togaf-standard/chap-17.html

MIT Center for Information Systems Research (CISR), "Enterprise Architecture as Strategy" by Jeanne W. Ross, Peter Weill, and David C. Robertson: This book emphasizes that a company’s enterprise architecture is a key component of its foundation for execution. The authors discuss how EA choices, such as standardization (substituting bespoke applications) and data access policies (cloud strategy), are direct enablers of strategic objectives like operational efficiency (TCO) and business agility (innovation).

Reference: Chapter 3, "Building a Foundation for Execution."

Carnegie Mellon University, Software Engineering Institute (SEI), "Enterprise Architecture Principles": This resource outlines how EA principles guide decision-making toward a desired future state. It provides examples showing how a principle like "Data is a shared asset" drives specific architectural choices and supports business objectives related to data access and collaboration, aligning with the "cloud first but not cloud only" scenario.

URL: https://insights.sei.cmu.edu/blog/enterprise-architecture-principles/

This sequence logically follows a standard customer lifecycle and marketing funnel. It begins with broad campaign management to generate awareness and attract potential customers (leads). Next, it focuses on nurturing these prospects through lead management and targeted account-based marketing, integrating with a CRM for tracking. Once prospects are engaged, recommendation management is used to drive conversions by suggesting relevant products. Finally, after a purchase, loyalty management is employed to retain the customer and foster repeat business. This progression from acquisition to retention represents a coherent and effective business architecture roadmap.

Academic Publication: The sequence reflects the established stages of customer relationship management, starting with customer acquisition and moving to customer retention.

Kumar, V., & Reinartz, W. (2018). Customer Relationship Management: Concept, Strategy, and Tools (3rd ed.). Springer. (See Chapter 3: "Customer Acquisition" and Chapter 4: "Customer Retention").

Vendor Documentation: SAP's own solution capabilities for the intelligent enterprise align with this flow, typically positioning campaign execution and lead generation before recommendation and loyalty functionalities.

SAP Help Portal, SAP Marketing Cloud, "Solution Overview". The documentation outlines process flows starting from Dynamic Customer Profiling and Campaign Management to Lead and Account-Based Marketing, followed by Commerce Marketing for recommendations and customer loyalty programs.

University Courseware: Marketing management principles taught in university courses emphasize a funnel-based approach (Awareness > Consideration > Conversion > Loyalty) which directly maps to the provided answer.

MIT Sloan School of Management. (2023). 15.812 Marketing Management: Course Notes on The Marketing Funnel. MIT OpenCourseWare. Available at: https://ocw.mit.edu/courses/sloan-school-of-management/15-812-marketing-management-spring-2023/

This order represents a logical, top-down decomposition of strategy into execution. The Goal is the high-level, qualitative strategic objective. The Value Driver quantifies this goal with a specific, measurable target that defines success. To achieve this target, the organization requires a specific Business Capability—the ability to perform a core function. Finally, an Initiative is a concrete project or program implemented to deliver or enhance that necessary capability. This hierarchical linkage ensures that operational projects (initiatives) are directly aligned with and contribute to the overarching business strategy (goal).

The Open Group Architecture Framework (TOGAF®) Standard, Version 10: The TOGAF framework describes the process of deriving architecture requirements from business goals. Phase A, Architecture Vision, explicitly involves identifying "business goals, strategic drivers, and objectives." Business capabilities are then identified as necessary to realize these goals. This establishes the hierarchy of Goal -> Capability.

Source: The Open Group, "TOGAF® Standard, Version 10, Phase A: Architecture Vision."

URL: https://pubs.opengroup.org/architecture/togaf-standard/adm-phase-a.html (Specifically, see Section 3.6, Approach: Business Scenarios, which links business goals to requirements).

University Courseware (MIT Sloan School of Management): Course materials on business and IT strategy frequently cover capability-based planning, where strategic goals are translated into required business capabilities, which are then enabled by specific IT initiatives.

Source: MIT OpenCourseWare, 15.561, "Information Technology as an Integrating Force in Manufacturing," Lecture Notes.

URL: https://ocw.mit.edu/courses/15-561-information-technology-as-an-integrating-force-in-manufacturing-spring-2001/pages/lecture-notes/ (Concepts in lectures on "Strategic Alignment" illustrate the flow from business strategy to IT systems/initiatives).

Peer-Reviewed Publication (IEEE): Academic literature on strategic alignment provides frameworks for linking business objectives to IT projects. These models consistently show a cascading relationship from goals to value propositions, to the capabilities needed, and finally to the enabling initiatives.

Source: Versteeg, G., & Bouwman, H. (2006). "Business architecture: A new paradigm to relate business strategy to ICT." Information Systems Frontiers, 8(2), 91-102.

URL: https://link.springer.com/article/10.1007/s10796-006-7993-y (Page 98 discusses how strategy is translated into business capabilities, which then guide the development of processes and IT systems).

The TOGAF® Architecture Development Method (ADM) is fundamentally an iterative and cyclic process, not a rigid, sequential waterfall model. It is designed to be adapted and tailored, allowing for iterations both within and across its phases. This inherent flexibility makes it compatible with agile delivery approaches. The SAP Enterprise Architecture Framework builds upon this TOGAF foundation, inheriting its adaptability. Therefore, it is well-suited for organizations that employ agile principles, as the framework's structure supports iterative development and continuous feedback loops across the entire architecture lifecycle.

A: This is incorrect because the application of agile principles within the SAP EA Framework is not restricted solely to the Application Architecture domain; it can be applied across multiple domains.

B: This suggests using agile as a separate, preliminary step before engaging the framework. The correct approach is to integrate agile principles within the guided process of the framework itself.

C: This promotes a strict waterfall interpretation, suggesting agile is only for the implementation phase. The TOGAF ADM is designed for iteration throughout all architecture definition phases, not just implementation.

1. The TOGAF® Standard

Version 9.2

The Open Group Standard No. C182.

Section 5.3

Iteration and the ADM: "The ADM is iterative

over the whole process

between phases

and within phases... Each iteration will be for a different scope

and the outputs will be updated... This is illustrated in Figure 5-3." This section explicitly details the iterative nature of the ADM

which is the foundation for applying agile methods.

Section 5.3.1

Iteration Cycles: "The suggested iteration cycles for the ADM are... Architecture Capability iterations... Architecture Development iterations... Transition Planning iterations... Architecture Governance iterations." This demonstrates that iteration is a core concept applied at multiple levels of the process.

2. The Open Group

TOGAF® Series Guide: A Practitioners’ Approach to Developing Enterprise Architecture Following the TOGAF® ADM (G186)

April 2018.

Section 2.4

Agile Enterprise Architecture: "The TOGAF ADM is an iterative process model... This iterative nature of the TOGAF framework lends itself to being executed in an agile manner." This guide directly links the ADM's iterative design to its suitability for agile approaches.

3. SAP. (2022). SAP Enterprise Architecture Framework. (Internal or Partner-accessible documentation for PSAPEA2023).

The SAP EA Framework documentation consistently emphasizes its basis in the TOGAF standard and its adaptability to customer-specific methodologies

including agile. It positions the framework as a guide that can be tailored

not a rigid prescription

supporting the idea that it is suitable for agile organizations. (Note: Specific page numbers depend on the version of the internal SAP document).

TOGAF defines a balanced Enterprise Architecture practice as one that covers the four primary domains: Business, Data, Application, and Technology. Wanderlust’s practice already lists an Enterprise Architect and an Application/Technology focus, but lacks dedicated ownership for the Business and Data domains. Therefore, the missing roles are the Business Architect (to align architecture with business strategy) and the Data Architect (to govern information assets and data standards).

B. Architecture Board – Governance body, not an architecture role; Wanderlust already has an EA steering committee playing this function.

C. Application Architect – Explicitly present in Wanderlust’s current structure, so it is not missing.

1. The TOGAF® Standard

10th Edition

Part VI

chap. 32 “Establishing the Architecture Capability”

§32.4.1 (role descriptions for Business and Data Architects).

2. The TOGAF® Standard

10th Edition

Part VI

chap. 34 “Roles”

Table 34-1 (distinguishes architect roles vs. the Architecture Board).

3. MIT OpenCourseWare

“Enterprise Architecture for Managers

” Lecture 5 slides

pp. 7-9 (four-domain model and need for domain-specific architects).