A service is a software solution
embodiment that is created in pursuit of resolving a business or a technological problem but is
also a piece of implementation that must coexist with other software assets. This journey, which
commences at the first appearance of an organizational concern, is shaped by service-oriented
modeling disciplines, and concludes as a physical solution, is the crux of the service-oriented life
cycle.
But how can service-oriented modeling activities influence the course of service evolution?
Do services have their own life span? Do they really live and perish? Do we understand how
a service evolves during its lifetime? These questions and others are widely debated in today??™s
service-oriented architecture (SOA) industry, which is still struggling to define services, clarify
their behaviors, and identify what is required for their survival. Before we move on to the technical
aspects of the service life span, we should understand why life cycles are such compelling
frameworks for driving service development.
There is nothing ???cyclical??? about the service life cycle, and as much as we would like them
to, services do not live forever. While services continue to evolve and provide value to their consumers
and greatly contribute to businesses in production environments, they are always subject
to perfection and enhancements. This usually requires a second look under the hood to determine
whether a service should be ferried back to the drawing board for redesign, re-architecture, and
reconstruction initiatives.
Pages:
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79