Swt2 Flashcards

1
Q

3 factors effecting software architecture

A

organization
reuse
requirements

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

architecture style
architecture pattern
reference architecture

A

solution principle
solution to a recurring problem
defines domain concepts components and subsystems

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

clean architecture

A

Entity
| Use Cases
| Controllers
| External Interfaces

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

1 taxation library
2 pay taxes
3 rest api
4 taxpayer class
5 mvc gui
6 sql db
7 o/r mapper
8 query translator

A

1 entity
2 use case
3 external interface
4 entity
5 controller
6 external interface
7 controller
8 controller

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

observer pattern

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

3 layers of enterprise applications

A

presentation layer
domain layer
data source layer

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

software component

A

contractually specified unit of software system
no need to know internals to adapt
provides interface
hide implementation details
explicit dependencies (required interfaces)

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

how to connect components

A

combine suitable provided with required
static or dynamic compositons
explicit connector between components to adapt communication

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

components infrastructure

A

components
repository
component framework
supporting tool
platform

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

5 aspects vorgehensmodelle

A

activities, roles, products, techniques, tools

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

activities
1 UP
2 XP
3 Scrum

A

1 Inception, Elaboration, Construction, Transition
2 Spike, Release planning, Iteration acceptance, Tests small release
3 Sprint planning, Daily scrum, Spring review, Retrospective, PB refinement

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

Roles
1 UP
2 XP
3 Scrum

A

1 Project Manager, Architect, Process Engineer
2 no fixed rules, product owner, customer, developer
3 Product owner, Scrum master, Team

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

Products
1 UP
2 XP
3 Scrum

A

1 Domain models, documentation, source code, executables
2 user stories, iteration plan, release plan, tasks, tests, code
3 vision, product backlog, sprint goal, tasks, sprint backlog, release plan, product increment

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

SaaS main characteristics

A

Network-based access
managed from central locations
one-to-many model
Centralized feature updating

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

SaaS examples

A

Salesforce.com
IBM SmartCloud Solutions

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

Cloud types

A

Private: Customer and provider belong to the same organization
Public: Customer and provider belong to the different organizations
Hybrid: private + public

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

Cloud computing characteristics

A

On-demand self-Service
Broad Network Access
Measured Service
Resource Pooling
Rapid Elasticity

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

Cloud computing deployment models

A

public
private
hybrid

19
Q

Cloud computing delivery models

A

SaaS
PaaS
IaaS

20
Q

Hypervisor

A

app1 / app2 / app3
bins-libs / bins-libs / bins-libs
guest os / guest os 2 / guest os 3
Hypervisor
Host operating system
Hardware

21
Q

Containerization

A

app1 / app2 / app3 conta
bins-libs / bins-libs / bins-libs iner
Docker engine run
operating system time
Hardware

22
Q

Advantages of Virtualization

A

Improved energy efficiency
Availability
Quality of Service
Overbooking of resources
Logical view on resource pools improves management
Almost no performance penalty

23
Q

Content of Container Images

A

Image Manifest
File System layers
Image Index
Container config

24
Q

Dimensions of Dependability

A

Availability: ability to deliver services when requested
Reliability: The ability of the system to deliver services as specified
Security: protect itself against deliberate or accidental intrusion
Safety: The ability of the system to operate without catastrophic failure
Resilience: recover from damaging events:

24
Redundancy systems without Fail Safe
Homogeneous Redundancy Heterogeneous Redundancy Triple Modular Redundancy
25
Redundancy systems with Fail Safe
Protected Single Channel Pattern Monitor-Actuator Pattern Sanity Check Pattern Watchdog Pattern Safety Executive Pattern
26
Secure Software Principles
Secure the weakest link Practice defence in depth: layer by layer Fail securely Secure by default principle of the least privilege No security through obscurity Minimize attack surface Privileged Core Input Validation and Output Encoding Don‘t Mix Data and Code
27
Five data source architectural patterns
Basic pattern: Record Set Table Data Gateway Active Record Row Data Gateway Data Mapper
28
Internals of microservices
Resources service layer domain repositories data mappers gateways http clients
29
Interactions Between Domains
Shared Kernel Consumer/Supplier Development Team Conformist Anticorruption Layer Open Host Service Published Language
30
Service Deployment Models
Private cloud Public cloud Hybrid cloud Community cloud
30
Major Roles Scrum
Product Owner Scrum Master Team
31
Microservice Characteristics
Componentization via services Organized around business capabilities Products not projects Smart endpoints and dumb pipes Decentralized governance Decentralized data management Infrastructure automation Design for failure Evolutionary design
32
Service Delivery Models examples
SaaS: salesforce.com Paas: Windows Azure IaaS: Amazon Web Services
33
Best practices Rational Unified Process
develop software iteratively manage requirements use component-based architectures model software visually verify software quality control changes to software
34
Agile methods advantages
Agile projects do not assume a stable world Disciplined Process Shifts responsibility to each team member Fast feedback on customer satisfaction and product quality essential
34
Agile methods advantages
Agile projects do not assume a stable world Disciplined Process Shifts responsibility to each team member Fast feedback on customer satisfaction and product quality essential
35
Meetings in scrum
Sprint Meeting Sprint Review Daily Scrum Sprint Retrospective
36
5 data source architectural patterns
Record Sets Active Record Data Mapper Table Data Gateway Row Data Gateway
37
7 bestandteile Microservice architecture
Resources Service Layer Domain Gateways Http Client Repositories Data mapper
38
4 factors effecting performance
Implementation Execution Environment Usage External Services
39
4 facette of requirement classification of glinz
Kind Representation Satisfication Role
39
Cloud architecture principles
Decentralization Asynchrony Autonomy Local responsibility Controlled concurrency Failure tolerant Controlled parallelism
40
Conway’s Law
Organisationen, welche Systeme designen sind auf Designerstellungen, welche Kopien der Kommunikationsstruktur dieser Organisation sind, beschränkt