These disciplines contribute the most to the formation of a virtual world that
mimics the service ecosystem that we are about to construct.
PHYSICAL ENVIRONMENT. Service-oriented modeling activities can always be repeated to perfect
the resulting artifacts that the modeling disciplines require for delivery. This perpetual process
is called iteration. Iterating through the various disciplines should promote one major modeling
agenda: to transform services from their intangible state to concrete entities. There are two major
physical artifacts that make up a physical environment:
1. Deployable service-oriented software assets that should be integrated with a production
environment. (These tangible entities are called solution services.)
2. A physical architecture that emerges from our logical architecture. This concrete architecture
depicts an integrated and configurable production environment that typically consists
of infrastructure, networks, management facilities such as monitoring and security, and,
of course, solution services.
SUMMARY
The service-oriented modeling driving principles are virtualization, metamorphosis, and literate
modeling.
Enterprise concepts??”foundation software (such as middleware and language platforms),
legacy software (such as applications and services), repositories, and utility software??”are all
conceived as organizational service-oriented software assets.
Pages:
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77