A service-oriented ecosystem is established in which services, consumers,
and their empowering platforms can coexist, collaborate, and interface to provide viable business
and technology solutions. Yes, we are engaged in an architectural endeavor that simulates a
deployment environment, a production landscape that fosters our business model and strategies.
We no longer address internal service structures, we merely tackle interaction and collaboration
challenges between packaged solutions. This process offers two major architecture modeling disciplines,
as depicted in Exhibit 1.14: the conceptual and the logical. For additional information,
refer to Chapters 15 and 16, which provide in-depth service architecture modeling mechanisms
and best practices.
Conceptual Architecture Modeling. The underlying physical construct of an architectural blueprint
must be a sound technological environment that complies with architecture strategies, best
practices, and standards. But even before the tangible aspects of a proposed architecture can be
addressed, a strategy and a general direction must be devised that provide guidance for future
technological implementation. The service-oriented conceptual architecture process is designed to
undertake such tasks. This activity can assist in the discovery of the main architecture concepts
that can drive future development and production projects.
The architecture abstraction discovery process can even start at the inception phase of a
given project and continue throughout the development life cycle.
Pages:
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62