S90-04 practice question 1 of 35

When collecting information for the purpose of defining business logic for potential service encapsulation, which of the following types of information would not be useful?

Full set: 100 questions
Answer options
A: business documents from which business entity definitions can be derived
B: database schemas that define the attributes of business entities
C: business policies that regulate the flow of data
D: All of the above. Correct answer
Correct Answer:
D. All of the above.
Explanation

From a purist, top-down service-oriented analysis perspective, the primary goal is to define an ideal "to-be" business logic model that is independent of past or current implementation constraints. In this context, existing artifacts such as legacy business documents, current database schemas, and established policies represent the "as-is" state. Relying on these sources can improperly influence the service design, coupling it to legacy constraints rather than aligning it with future-state business goals. Therefore, for the specific purpose of defining ideal, unconstrained business logic for encapsulation, all these existing information sources are considered not useful as they can hinder the creation of a truly agile and business-aligned service architecture.

Why Incorrect

A, B, C: These options are incorrect because they are not comprehensive. Within the purist top-down analysis context, it is not just one of these sources that is considered not useful, but all of them, as they collectively represent the legacy "as-is" state that the new design seeks to improve upon.

References

1. Erl, T. (2008). SOA: Principles of Service Design. Prentice Hall.

Chapter 5, Section: "Service-Oriented Analysis (Service Modeling)": This chapter introduces different approaches to service modeling, including top-down, bottom-up, and meet-in-the-middle. The rationale for the correct answer (D) is rooted in the philosophy of a strict top-down approach. On page 158, the text explains that the top-down approach begins with business process analysis to "produce a service-oriented business model that is not constrained by technology or existing application logic." This supports the idea that existing artifacts (like database schemas and legacy documents) are intentionally avoided to prevent contamination of the ideal business model.

2. Josuttis, N. (2007). SOA in Practice: The Art of Distributed System Design. O'Reilly Media.

Chapter 3, Section: "Top-Down or Bottom-Up?": This section discusses the trade-offs between analysis approaches. It notes that a pure top-down approach "starts from scratch by analyzing the business," which implies that existing technical artifacts like database schemas are not the primary input. This aligns with the reasoning that such sources would not be useful for defining the ideal business logic from a business-first perspective.

Scroll to Top