This transformation process is the essence of the metamorphosis paradigm driven by
service-oriented modeling disciplines that ensure software elasticity, and ultimately, business
agility.
But the transformation process does not stop with the deployment of services to production.
Imagine how frequently a valuable application is involved in multiple project iterations that lead
to software upgrades. Think about the myriad instances of a service finding its way back to the
drawing board to be redesigned and then ferried back to the production environment again. This
is typical of the software development life cycle, during which software products are upgraded,
enhanced, and redistributed.
LITERATE MODELING. Should a programming language offer a simple syntax that is easy to
understand, and is intuitive and readable? Or should it offer formal grammar, rules, and symbols
that only developers can handle? Should a programming language be based on machine-readable
source code that is easy to debug and optimize? Or should it be considered a scientific artifact,
a mathematical formula that only experts on the subject can deliver?
This long-running debate is believed to have begun in the early 1980s and encompasses two
major approaches to software development that have major ramifications for the service-oriented
modeling paradigm. The first was introduced by Donald Knuth??™s theory of ???literate programming???
in which he argues: ???I believe that the time is ripe for significantly better documentation of
programs, and that we can best achieve this by considering programs to be works of literature.
Pages:
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32