Information Technology Reference
In-Depth Information
automatically. Using AOP techniques will make the system more modular, and devel-
opers only design the aspect without considering other aspects or the core component.
Real-time feature is the most important aspect of the real-time systems, which de-
termines the performance of the systems. So we describe the real-time feature as an
independent aspect according to the AOP techniques, and design a time model to
realize and manage the time aspect in order to make the real-time systems easier to
design and develop and guarantee the time constraints.
The design and analysis of various types of systems, like real-time systems or
communication protocols, require insight in not only the functional, but also in the
real-time and performance aspects of applications involved. Research in formal meth-
ods has recognized the need for the additional support of quantitative aspects, and
various initiatives have been taken to accomplish such support. In this paper, we pro-
vide some ideas for the aspect-oriented formal specification of real-time systems and
three well-known case studies to validate aspect-oriented formal specification.
2 Aspect-Oriented Formal Specification
The primary goal of a software development methodology is to facilitate the creation,
communication, verification and tracing of requirements, design, and implementation.
To be truly effective, a modern methodology must also automatically produce imple-
mentations from designs, test cases from requirement specifications, analyses of
designs and reusable component libraries. Our experience in the development of mul-
timedia systems and research into software development methodologies have led us to
conclude that existing public-domain methodologies do not permit us to achieve these
goals. Most often software development methods offer excellent solutions to specific,
partial aspects of system development, providing only little of help for other aspects.
Classical methods for specifying and analyzing real-time systems typically focus on a
limited subset of system characteristics. RTSA, for example, focuses primarily on the
functionality and state-oriented behavior of real-time systems. STATEMATE pro-
vides three different graphic or diagrammatic languages for three different aspects.
Module charts represent the structural aspect of the system, activity charts represent
functional aspect of system, and state charts represent the behavior aspect of the sys-
tem. At the other extreme, formal specification and verification methods strive for
foolproof or error-free designs. They can be used to specifying and analyzing some
properties such timing constraints. Thus integration of different specification methods
is desired:
Integration of the methods used to specify systems requirements.
Integration of tools that support these methods.
And integration of the multiple specification fragments produced by applying these
methods and tools.
In our opinion, an acceptable real-time system design methodology must synthe-
size the different aspects of systems, use a number of different methods and tools,
consist of an orderly series of steps to assure that all aspects of the requirement and all
the design aspects have been considered. The real-time system design methodology
should address these problems:
Search WWH ::
Custom Search