Lecture 5 Recap Quiz - System Design 2

Lecture 5 Recap Quiz - System Design 2

University

5 Qs

quiz-placeholder

Similar activities

G04 System Design I

G04 System Design I

University

3 Qs

Overview of Java Web Development

Overview of Java Web Development

University

10 Qs

SD- Arquitectura de Software y Patrón MVC

SD- Arquitectura de Software y Patrón MVC

University

10 Qs

LPIII - Evaluación diagnóstica 1

LPIII - Evaluación diagnóstica 1

University

10 Qs

FSW:CH07.T01 -  Design Pattern

FSW:CH07.T01 - Design Pattern

University - Professional Development

9 Qs

G05 System Design II

G05 System Design II

University

5 Qs

Parallel & Distributed Database

Parallel & Distributed Database

University

10 Qs

Model View Controller (MVC)

Model View Controller (MVC)

University

10 Qs

Lecture 5 Recap Quiz - System Design 2

Lecture 5 Recap Quiz - System Design 2

Assessment

Quiz

Computers

University

Hard

Created by

Denitsa Assova

Used 1+ times

FREE Resource

5 questions

Show all answers

1.

MULTIPLE CHOICE QUESTION

45 sec • 1 pt

MVC:

The view subsystem sends updates to the controller subsystem and model subsystem

The difference between 3 tier architectural style and MVC is that MVC is hierarchical

Decouples data access and presentation, allowing multiple synchronized views of the same model

2.

MULTIPLE CHOICE QUESTION

45 sec • 1 pt

Concurrency:

A race condition is a design

flaw where the output of a process depends on the specific sequence of other events

Logical concurrency is when threads are provided by hardware

Addresses the non functional requirements flexibility and maintainability as tasks are assigned to separate threads

3.

MULTIPLE CHOICE QUESTION

45 sec • 1 pt

HW/SW Mapping:

Addresses the question how UML models can be realised in code

Control objects are mapped to processors, entity objects to memory and boundary objects to IO devices

The difficulty of HW/SW mapping is determining the cost of the HW needed to realise the system

4.

MULTIPLE CHOICE QUESTION

45 sec • 1 pt

Access Control:

During system design we model access rights by associating use cases with the actors

Access right is the row in the access matrix and it models all possible actors that interact with the system

Capability associates a (class, operations) pair with an actor

5.

MULTIPLE CHOICE QUESTION

45 sec • 1 pt

Software Control:

Centralised design leads to additional communication overhead

Centralised control can be modelled using the Fork diagram

Event-driven centralised control is when control resides within the program code