APP DEV: System Modeling

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/61

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 2:21 PM on 9/4/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

62 Terms

1
New cards

System modeling

is the process of developing abstract

models of a system, with each model presenting a

different view or perspective of that system.

2
New cards

System modeling

representing a

system using some kind of graphical notation, which is

now almost always based on notations in the Unified

Modeling Language (UML).

3
New cards

System modelling

helps the analyst to understand the

functionality of the system and models are used to

communicate with customers.

4
New cards

Models of the existing system

are used during requirements

engineering. They help clarify what the existing system does

and can be used as a basis for discussing its strengths and

weaknesses. These then lead to requirements for the new

system.

5
New cards

An external perspective

where you model the context or

environment of the system.

6
New cards

An interaction perspective

where you model the

interactions between a system and its environment, or

between the components of a system.

7
New cards

A structural perspective

where you model the

organization of a system or the structure of the data that

is processed by the system.

8
New cards

A behavioral perspective

where you model the dynamic

behavior of the system and how it responds to events.

9
New cards

Activity diagrams

which show the activities involved in a

process or in data processing .

10
New cards

Use case diagrams

which show the interactions

between a system and its environment.

11
New cards

Sequence diagrams

which show interactions between

actors and the system and between system components.

12
New cards

Class diagrams

which show the object classes in the

system and the associations between these classes.

13
New cards

State diagrams

which show how the system reacts to

internal and external events.

14
New cards

True

Incomplete and incorrect models are OK as their role is to

support discussion.

T/F

15
New cards

False

Models should be an accurate representation of the system but

needs to be complete.

T/F

16
New cards

True

Models have to be both correct and complete.

T/F

17
New cards

Context models

are used to illustrate the operational

context of a system - they show what lies outside the

system boundaries.

18
New cards

System boundaries

are established to define what is

inside and what is outside the system.

19
New cards

True

Context models simply show the other systems in the

environment, not how the system being developed is

used in that environment.

T/F

20
New cards

Process models

reveal how the system being developed

is used in broader business processes.

21
New cards

TRUE

Modeling user interaction is important as it helps to

identify user requirements.

T/F

22
New cards

False

Modeling system-to-system interaction can not highlights the

communication problems that may arise.

23
New cards

Modeling component interaction

helps us understand if a

proposed system structure is likely to deliver the required

system performance and dependability.

24
New cards


25
New cards

Use case diagrams and sequence diagrams

_____ and _____ may be

used for interaction modeling.

26
New cards

use case

represents a discrete task that involves

external interaction with a system.

27
New cards

Use Case Modeling

Represented diagramatically to provide an overview of

the use case and in a more detailed textual form.

28
New cards

Sequence diagrams

are part of the UML and are used to

model the interactions between the actors and the

objects within a system.

29
New cards

A sequence diagram

shows the sequence of interactions

that take place during a particular use case or use case

instance.

30
New cards

Structural models of software

display the organization of

a system in terms of the components that make up that

system and their relationships.

31
New cards

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.

32
New cards

Class diagrams

are used when developing an

object-oriented system model to show the classes in a

system and the associations between these classes.

33
New cards

An association

is a link between classes that indicates

that there is some relationship between these classes.

34
New cards

Generalization

is an everyday technique that we use to

manage complexity.

35
New cards

Generalization

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.

36
New cards

generalization

In object-oriented languages, such as Java, ____ is

implemented using the class inheritance mechanisms built into

the language.

37
New cards

In a generalization

the attributes and operations associated with

higher-level classes are also associated with the lower-level

classes.

38
New cards

An aggregation model

shows how classes that are

collections are composed of other classes.

39
New cards

Aggregation models

are similar to the part-of relationship

in semantic data models.

40
New cards

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.

41
New cards

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

42
New cards

Data-driven models

show the sequence of actions

involved in processing input data and generating an

associated output.

43
New cards

Data-driven models

They are particularly useful during the analysis of

requirements as they can be used to show end-to-end

processing in a system.

44
New cards

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.

45
New cards

Event-driven modeling

shows how a system responds to

external and internal events.

46
New cards

Event Driven Modeling

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.

47
New cards

State machine models

These model the behaviour of the system in response to

external and internal events.

48
New cards

State machine models

They show the system’s responses to stimuli so are

often used for modelling real-time systems.

49
New cards

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.

50
New cards

Model-driven engineering (MDE)

is an approach to

software development where models rather than

programs are the principal outputs of the development

process.

51
New cards

Model-driven engineering (MDE)

The programs that execute on a hardware/software

platform are then generated automatically from the

models.

52
New cards

model-driven engineering

Pros

Allows systems to be considered at higher levels of abstraction

Generating code automatically means that it is cheaper to adapt

systems to new platforms.

53
New cards

model-driven engineering

Cons

Models for abstraction and not necessarily right for

implementation.

Savings from generating code may be outweighed by the costs

of developing translators for new platforms.

54
New cards

Model-driven architecture (MDA)

was the precursor of

more general model-driven engineering

55
New cards

Model-driven architecture MDA

is a model-focused approach to software design

and implementation that uses a subset of UML models to

describe a system.

56
New cards

Model-driven architecture MDA

Models at different levels of abstraction are created.

From a high-level, platform independent model, it is

possible, in principle, to generate a working program

without manual intervention.

57
New cards

A computation independent model (CIM)

These model the important domain abstractions used in a

system. CIMs are sometimes called domain models.

58
New cards

A platform independent model (PIM)

These model the operation of the system without reference to its

implementation. The ___ is usually described using UML models

that show the static system structure and how it responds to

external and internal events.

59
New cards

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.

60
New cards

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.

61
New cards

Executable UML or xUML.

The fundamental notion behind model-driven

engineering is that completely automated transformation

of models to code should be possible.

This is possible using a subset of UML 2, called

_____

62
New cards