"Object-oriented Modeling

and Design of Distributed

Multimedia Applications"

Beatingo, Dave Bryan J.

Calle, Reycart C.
Distributed Multimedia Applications
DMAs (Distributed Multimedia Applications) are a type of software that
takes advantage of technological advancements in a variety of areas,
such as networking and image and other media processing, to provide
end-users with highly interactive, real-time access to remote resources
and/or distributed collaborative processing.
The Development of Distributed Multimedia Applications applies two
modeling methodologies, one based on the UML modeling language
and the other on the TRIO formal specification language.

UML offers a diverse range of diagram types for describing static and
dynamic elements of a system under development, as well as modeling
user requirements, system components, their relationships, and internal
behavior.

TRIO is a formal language for specifying OO real-time software

systems. In TRIO, a system specification is divided into two parts:
graphical and textual. Classes, their interfaces, and the links between
them are represented using graphical notation.
Modeling with UML
• The first step in the OO development is to describe user requirements;
these are captured in UML by means of use cases diagrams. This use
cases are obviously related to system functionalities.
• The next step is to identify problem domain objects. These are
captured in the UML class diagram.
• The design phase, the problem domain object model is refined in
several ways. In the development of DMAs, it is at this stage that
concerns such as how to operate media and network hardware come
into play.
• The refining of the object model continues in the direction of system
component identification. Objects that have a high degree of cohesion
are clustered together, indicating subsystems with distinct borders. This
is captured in the UML component diagram.
• After identifying system objects and components, the design moves
on to defining the behavior of the objects.
• The internal behavior of each object in the system is defined as part of
the OO design process. UML provides state diagrams for this purpose.
• These State diagrams are useful for describing the dynamics of a single (non-
trivial) item across multiple use cases.
• Sample use cases.
Modeling with TRIO
• TRIO class diagram structure is almost identical to UML
• The number of connections in the TRIO class diagram is naturally
greater than the number of arrows.
Example.
DiVA TRIO class diagram
Modelling with TRIO

TRIO is a formal language for specifying OO real-time software

systems. In TRIO, a system specification is divided into two parts:
graphical and textual. Classes, their interfaces, and the links between
them are represented using graphical notation.

• TRIO allows the designer to formally express both the structural and
real-time features of the system to be developed, integrating sound
OO abstraction strategies like information hiding, inheritance, and
genericity with the clarity of logic requirements.
• TRIO combines graphical and textual descriptions; the latter specify
behavioral properties as logic formulas