L5 - Design Goals Flashcards Preview

EIST (IN0006) > L5 - Design Goals > Flashcards

Flashcards in L5 - Design Goals Deck (24):
1

Concurrent Threads can lead to ...

race conditions

2

Façade Pattern

Provides unified interface for a subsystem + consists of a set of public operations + makes use easier

3

Deployment Diagram

illustrates distribution of components on concurrent processes at runtime

4

Access Control Matrix

Models access of actors on classes: actors (rows) + classes (columns) + entry (access right)

5

Global Resource Handling

Describes access rights for different actors. Tool: Access Control Matrix

6

Concurrency

Addresses nonfunctional requirements (e.g.: performance/latency) + can lead to starvation/deadlocks/fairness

7

Hardware/Software Mapping

Mapping object model on hardware & software

8

Boundary Conditions

Initialization + Termination + Failure

9

Remote Proxy

Caching of information. Proxy object as local representative for an object in different address space. No frequent information change.

10

Persistent Data Management

Data is persistent if the values of their attributes live beyond execution (file system: many readers/1 writer OR database: concurrent writers and readers)

11

Global Access Table

Represents non-empty cell by triple (actor; class; operation): LeagueOwner; Arena; view()

12

Physical Concurrency

Threads provided by hardware (multiprocessors/multicores)

13

Thread Of Control

Path through a set of state diagrams where only a single object is active at any time

14

Centralized Software Control

Fork Sequence Diagram: Procedure-Driven (control in code) OR Event-Driven (control in dispatcher) OR 'Spider' (1 control object)

15

By what is a class/a class attribute and an instance of a class modeled when mapped to a database?

table (class) - column (class attribute) - row (instance of class)

16

Logical Concurrency

Threads provided by software

17

Capability

Associates pair (class; operation) with an actor: Arena; view() with LeagueOwner

18

Component Diagram

illustrates dependencies between components at design time/compilation/run time

19

Decentralized Software Control

Stair Sequence Diagram: Independent Objects (distributed control means better performance but outspread responsibility)

20

Good System Design foresees ______________.

... fatal failures and deals with them.

21

Virtual Proxy

Real object too expensive to create/download and doesn't get accessed often.

22

Protection Proxy

Access Control. Provides protection for the real object. Different actors with different viewing rights.

23

Access Control

Associates list of pairs (actor; operation) with class: Player; play() with Match

24

Software Control

implicit (rule-based & logic programming) + explicit (centralized & decentralized)