But the tone is always the
same. What ??™ s the reason? Very simple: progress.
We have reached a point where what ??™ s needed are complex and distributed
systems, but where conventional development methods are not yet ready to make
such systems available fast enough and at acceptable cost.
We cannot expect to develop increasingly progressive, larger, and better systems
while continue using the same tools. Our approach, the modeling languages
we use, and the development environments have to be part of this progress and
evolve in line with it.
Introduction 1
CHAPTER
1 If you can??™t please write to me and ask me: twe@system-modeling.com.
2 CHAPTER 1 Introduction
In software development, e.g., this evolution can be seen quite clearly.
Development tools have known increasingly larger components (from 0/1 to
classes/objects) from the times we used punch cards, and then Assembler, and
then procedural programming languages, and eventually object-oriented languages,
thus facilitating the description of complex systems. The evolution to the
next generation has already begun: The graphical Unifi ed Modeling Language
( UML ) has become increasingly popular for developing software systems, and it
is being used to solve more and more tasks that had been previously done with
conventional programming languages ( Figure 1.
Pages:
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40