Which statement best describes the relationship between top down and bottom-up service identification in Service-Oriented Integration?

Bottom-up service Identification analyzes existing systems to Identify SOA Services. Top-down
service identification analyzes business processes to identify SOA services.
Which statement best describes the relationship between top down and bottom-up service

identification in Service-Oriented Integration?

Bottom-up service Identification analyzes existing systems to Identify SOA Services. Top-down
service identification analyzes business processes to identify SOA services.
Which statement best describes the relationship between top down and bottom-up service

identification in Service-Oriented Integration?

A.
Only a bottom up approach shouldbe used because the goal of SOIis to provide SOA Services
exposing existing systems.

B.
Only a top-down approach should be used because the goal of SOI is composite application
assembly.

C.
A bottom-up approach should be used to identify which SOA Services are built; then a topdown approach should be used to determine which SOA Services are used by each composite
application.

D.
A top-down approach should be used to determine the needed SOA Services; then a bottom-up
approach should be used to determine how existing source systems can meet the requirements
top-down approach should be used by business, and a bottom-up approach should be used by
IT.Theoverlap between the SOA Services Identified by the two methods are the ones that should

Explanation:

Note: There are three schools of thought around “how to build an Enterprise Service Oriented
Architecture.” They are:
* Top down – central group decides everything and the dev teams adopt them.
* Bottom up – central group provides a directory and dev teams make whatever services they
want. Dev teams go to the directory to find services they can use.
* Middle out – central group provides key elements of the interface, including numbering schemes,
message exchange patterns, standard communication mechanisms, and monitoring infrastructure,
and encourages the dev teams to use it to build services that can be shared.



Leave a Reply 0

Your email address will not be published. Required fields are marked *