Exam 2 Flashcards

(38 cards)

1
Q

Activity diagrams

A

which show the activities involved in a process or in data processing .

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Use case diagrams

A

which show the interactions between a system and its environment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Sequence diagrams

A

which show interactions between actors and the system and between system components.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Class diagrams

A

which show the object classes in the system and the associations between these classes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

State diagrams

A

which show how the system reacts to internal and external events.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

External Entity

A

Square shape: An element that inputs data into a system and/or retrieves data from the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Process

A

Circle: Circle represent a process. In context diagram there is only 1 process that represents the entire system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Flow Line

A

shows the movement of data from one entity/process to another

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Interaction Models

A

-Use case modeling:model interactions between a system and external agents
-Sequence Diagrams: model interactions between system components

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Use Case Model Symbols

A

System: Rectangle
Use Case: Circle
Actor: Person
Line: Relationships

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

«Include»

A

Points to Included Use case, always happens

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

«Extend»

A

Points to Base Use case, sometimes happens but not required

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Inheritance

A

Open arrow Ex. Customer with children New Customer and Returning Customer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Structural Models

A

Class Diagrams

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Class Diagram

A

Box With the following:
Class Name/
Attributes (like int char etc)/
Operations/Methods (void operation(), int operation_c(int), etc)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Class Diagram Symbols

A

Public(+)
Private(-)
Protected(#)

17
Q

Relationships

A

Open arrow: Inheritance
Straight Line: Association
Aggregation: open diamond

18
Q

Behavioral Model

A

Data-driven modeling
-Activity diagrams
Event-driven modeling
-State machine

19
Q

Data-Driven Model figures

A

Box: shows input/outputs from objects.
Oval box: shows activities

20
Q

Model-driven Engineering

A

is an approach to software development where models rather than programs are the principal outputs of the development process.

21
Q

Types of models in Model-driven architecture (MDA)

A

-A computation-independent model (CIM)
-A platform-independent model (PIM)
-Platform-specific models (PSM)

22
Q

Cons to MDA

A

-There is limited tool availability and organizations may require tool adaptation and customization to their environment
-Companies do not want to develop or maintain their own tools or to rely on small software companies, who may go out of business
-Without these specialist tools, model-based development requires additional manual coding which reduces the cost-effectiveness of this approach.

23
Q

Importance of Architecture

A

Architecture is a critical link between requirements and the software that will be built.

24
Q

Box Architecture

A

Each box in the diagram represents a component. Boxes within boxes indicate that the component has been decomposed into subcomponents.

25
Advantages of explicit architecture
-Stakeholder communication -System analysis -Large-scale reuse
26
Performance
Architecture should be designed to localize operations and minimize communications. You can also use large rather than fine-grain components to minimize communication delays
27
Security
Use a layered architecture with critical assets protected in the innermost layers.
28
Safety
Localize safety-critical features in a small number of sub-systems. Prevent middleware attacks.
29
Availability
Include redundant components and mechanisms for fault tolerance. (Fault-tolerant architecture)
30
Maintainability
Use fine-grain, self-contained components that may readily be changed.
31
Layered Architecture
System functionality is organized into separate layers, and each layer only relies on the facilities and services offered by the layer immediately beneath it.
32
Repository architecture
Repository style describes how a set of interacting components can share data.
33
The Client–server pattern
In a client–server architecture, the functionality of the system is organized into services, with each service delivered from a separate server. Clients are users of these services and access servers to make use of them.
34
The pipe and filter pattern
The processing of the data in a system is organized so that each processing component (filter) is discrete and carries out one type of data transformation. The data flows (as in a water pipe) from one component to another for processing.
35
Data processing applications
Data-driven applications that process data in batches without explicit user intervention during the processing. Ex: billing system
36
Transaction processing applications
Data-centred applications that process user requests and update information in a system database. Ex: Online shopping, banking, hotel reservation systems
37
Event processing systems
Applications where system actions depend on interpreting events from the system’s environment. Ex: video games, vending machines
38
Language processing systems
Applications where the users’ intentions are specified in a formal language that is processed and interpreted by the system. Ex: compiler, google assistant, web search engines