Scribd
Upload
14 views17 pages

Lesson 1.4.2

Uploaded by

rivera.aramis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
14 views17 pages

Lesson 1.4.2

Uploaded by

rivera.aramis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

COMPLEX MODELS: STRUCTURAL,

BEHAVIORAL

Course: Software Design and Construction – COEN 3410


Professor: Jaime Yeckle Sanchez
Lesson: 1.4.2
Objectives

■ Use structural and behavioral models in model-driven engineering.


Structural Models

■ Structural models of software display the organization of a system in terms of


the components that make up that system and their relationships.
■ Structural models may be static models, which show the structure of the system
design, or dynamic models, which show the organization of the system when it
is executing.
■ You create structural models of a system when you are discussing and designing
the system architecture.
Class Diagrams

■ Class diagrams are used when developing an object-oriented system model to


show the classes in a system and the associations between these classes.
■ An object class can be thought of as a general definition of one kind of system
object.
■ An association is a link between classes that indicates that there is some
relationship between these classes.
■ When you are developing models during the early stages of the software
engineering process, objects represent something in the real world, such as a
patient, a prescription, doctor, etc.
The Consultation Class

Figure: Images May Be Subject to Copyright.


Classes and Associations in the MHC-PMS

Figure: Images May Be Subject to Copyright.


Generalization

■ Generalization is an everyday technique that we use to manage complexity.


■ Rather than learn the detailed characteristics of every entity that we
experience, we place these entities in more general classes (animals, cars,
houses, etc.) and learn the characteristics of these classes.
■ This allows us to infer that different members of these classes have some
common characteristics e.g. squirrels and rats are rodents.
■ In a generalization, the attributes and operations associated with higher-level
classes are also associated with the lower-level classes.
■ The lower-level classes are subclasses inherit the attributes and operations
from their superclasses. These lower-level classes then add more specific
attributes and operations.
A Generalization Hierarchy

Figure: Images May Be Subject to Copyright.

Figure: Images May Be Subject to Copyright.


Behavioral Models

■ Behavioral models are models of the dynamic behavior of a system as it


is executing. They show what happens or what is supposed to happen
when a system responds to a stimulus from its environment.
■ You can think of these stimuli as being of two types:
– Data Some data arrives that has to be processed by the system.
– Events Some event happens that triggers system processing. Events may have
associated data, although this is not always the case.
Data-Driven Modeling

■ Many business systems are data-processing systems that are primarily driven
by data. They are controlled by the data input to the system, with relatively
little external event processing.
■ Data-driven models show the sequence of actions involved in processing
input data and generating an associated output.
■ They are particularly useful during the analysis of requirements as they can
be used to show end-to-end processing in a system.
Event-Driven Modeling

■ Real-time systems are often event-driven, with minimal data processing. For
example, a landline phone switching system responds to events such as
‘receiver off hook’ by generating a dial tone.
■ Event-driven modeling shows how a system responds to external and internal
events.
■ It is based on the assumption that a system has a finite number of states and
that events (stimuli) may cause a transition from one state to another.
State Machine Models

■ These model the behaviour of the system in response to external and internal
events.
■ They show the system’s responses to stimuli so are often used for modelling
real-time systems.
■ State machine models show system states as nodes and events as arcs between
these nodes. When an event occurs, the system moves from one state to
another.
■ State charts are an integral part of the UML and are used to represent state
machine models.
State Diagram of a Microwave Oven

Figure: Images May Be Subject to Copyright.


Model-Driven Engineering

■ Model-driven engineering (MDE) is an approach to software development


where models rather than programs are the principal outputs of the
development process.
■ The programs that execute on a hardware/software platform are then
generated automatically from the models.
■ Proponents of MDE argue that this raises the level of abstraction in software
engineering so that engineers no longer have to be concerned with
programming language details or the specifics of execution platforms.
Types of Model

■ A computation independent model (CIM)


– These model the important domain abstractions used in a system. CIMs are sometimes
called domain models.
■ A platform independent model (PIM)
– These model the operation of the system without reference to its implementation. The
PIM is usually described using UML models that show the static system structure and how
it responds to external and internal events.
■ Platform specific models (PSM)
– These are transformations of the platform-independent model with a separate PSM for
each application platform. In principle, there may be layers of PSM, with each layer adding
some platform-specific detail.
Agile Methods and MDA

■ The developers of MDA claim that it is intended to support an iterative


approach to development and so can be used within agile methods.
■ The notion of extensive up-front modeling contradicts the fundamental ideas
in the agile manifesto and I suspect that few agile developers feel comfortable
with model-driven engineering.
■ If transformations can be completely automated and a complete program
generated from a PIM, then, in principle, MDA could be used in an agile
development process as no separate coding would be required.
References

■ Sommerville, I. (2011). Software Engineering (9th Ed.). United States: Pearson


Education Limited.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy