A STRATEGIC ENDEAVOR GUIDED BY MODELING DISCIPLINES. Creating a miniature mockup
of a final software product and its supporting environment can obviously reduce investment risk
by ensuring the success of the impending software construction initiative. This can be achieved
Service-Oriented Modeling: What Is It About? 3
by employing analysis, design, and architectural disciplines that are driven by a modeling strategy
that fosters asset reusability, a high return on investment, and a persuasive value proposition for
the organization.
Service-oriented modeling disciplines enable us to focus on modeling strategies rather
than being concerned with source code and detailed programming algorithms. By employing this
modeling paradigm we raise the bar from the granular constructs of our applications, yet we must
accommodate the language requirements of the underpinning platforms. We focus on identifying
high-level business and technological asset reusability and consolidation opportunities, but we
must also foster the reuse of software building blocks such as components and libraries. We
rigorously search for interoperability solutions that can bridge heterogeneous technological environments,
but we also concentrate on integration and message exchange implementation detail.
A LEARNING AND VALIDATION PROCESS. By producing a small version of the final artifact
we are also engaging in a learning and verification process.
Pages:
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27