Databases Reference
In-Depth Information
from third generation to fourth generation and the success of reusable
object libraries accompanying object-oriented languages like C
and Java
confirmed CASE tools as an advanced technology that cannot be bypassed in
the development of modern information systems.
Current CASE tools have sparse functionalities, cover different phases
in a projects life cycle, and are based on different formal specification mod-
els. This makes a comparison difficult. There is no standard architecture for a
CASE tool, only products that address specific activities in software engineer-
ing. The project actors see CASE tools from their individual perspectives and
from their own roles in the software project. Many classifications of CASE
tools have been proposed; they are either based on the projects life cycle
(analysis, design, implementation, validation, maintenance, administration,
etc.), on the level of abstraction (upper CASEs, middle CASEs, and lower
CASEs), or on the degree of automation (manual tools; semiautomated, or
interactive, tools; fully automated tools). Programming experts focus on
process modeling, formal verification of program behavior, and code genera-
tion. Database experts focus on conceptual data modeling, physical DB
design, and integrity constraints validation. Project managers focus on data
dictionaries, report generation, and assessment techniques.
The daisy in Figure 13.1 gives a flavor of an ideal integrated CASE
toolset. The figure highlights a set of functionalities provided by CASE tools
independently of any specific methodology and classification. One can imag-
ine as many CASE environments as combinations of petals in the daisy.
Among CASE tools we can distinguish those related to project manage-
ment and control, those related to DB modeling, those related to process
modeling, and those related to IS administration and maintenance. The
baseline of these tools is the knowledge repository that groups all the meta-
data concerning the application domain, the products and the processes of
the project, and the generic reusable components. The cornerstone of the
toolset is the fundamental inference and reasoning mechanisms that can be
used by various tools. Graphical interfaces constitute a convenient way to
synthesize specifications and to give a rapid understanding of the semantics
of the system under construction.
++
13.1.1
Functional Classification of CASE Tools
The functional classification of tools given in Table 13.1 is not exhaustive,
but it gives a good view of the diversity of CASE tools that support software
engineering projects.
