Swt2 Flashcards
3 factors effecting software architecture
organization
reuse
requirements
architecture style
architecture pattern
reference architecture
solution principle
solution to a recurring problem
defines domain concepts components and subsystems
clean architecture
Entity
| Use Cases
| Controllers
| External Interfaces
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
1 entity
2 use case
3 external interface
4 entity
5 controller
6 external interface
7 controller
8 controller
observer pattern
3 layers of enterprise applications
presentation layer
domain layer
data source layer
software component
contractually specified unit of software system
no need to know internals to adapt
provides interface
hide implementation details
explicit dependencies (required interfaces)
how to connect components
combine suitable provided with required
static or dynamic compositons
explicit connector between components to adapt communication
components infrastructure
components
repository
component framework
supporting tool
platform
5 aspects vorgehensmodelle
activities, roles, products, techniques, tools
activities
1 UP
2 XP
3 Scrum
1 Inception, Elaboration, Construction, Transition
2 Spike, Release planning, Iteration acceptance, Tests small release
3 Sprint planning, Daily scrum, Spring review, Retrospective, PB refinement
Roles
1 UP
2 XP
3 Scrum
1 Project Manager, Architect, Process Engineer
2 no fixed rules, product owner, customer, developer
3 Product owner, Scrum master, Team
Products
1 UP
2 XP
3 Scrum
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
SaaS main characteristics
Network-based access
managed from central locations
one-to-many model
Centralized feature updating
SaaS examples
Salesforce.com
IBM SmartCloud Solutions
Cloud types
Private: Customer and provider belong to the same organization
Public: Customer and provider belong to the different organizations
Hybrid: private + public
Cloud computing characteristics
On-demand self-Service
Broad Network Access
Measured Service
Resource Pooling
Rapid Elasticity
Cloud computing deployment models
public
private
hybrid
Cloud computing delivery models
SaaS
PaaS
IaaS
Hypervisor
app1 / app2 / app3
bins-libs / bins-libs / bins-libs
guest os / guest os 2 / guest os 3
Hypervisor
Host operating system
Hardware
Containerization
app1 / app2 / app3 conta
bins-libs / bins-libs / bins-libs iner
Docker engine run
operating system time
Hardware
Advantages of Virtualization
Improved energy efficiency
Availability
Quality of Service
Overbooking of resources
Logical view on resource pools improves management
Almost no performance penalty
Content of Container Images
Image Manifest
File System layers
Image Index
Container config
Dimensions of Dependability
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:
Redundancy systems without Fail Safe
Homogeneous Redundancy
Heterogeneous Redundancy
Triple Modular Redundancy
Redundancy systems with Fail Safe
Protected Single Channel Pattern
Monitor-Actuator Pattern
Sanity Check Pattern
Watchdog Pattern
Safety Executive Pattern
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
Five data source architectural patterns
Basic pattern: Record Set
Table Data Gateway
Active Record
Row Data Gateway
Data Mapper
Internals of microservices
Resources
service layer
domain
repositories
data mappers
gateways
http clients
Interactions Between Domains
Shared Kernel
Consumer/Supplier Development Team
Conformist
Anticorruption Layer
Open Host Service
Published Language
Service Deployment Models
Private cloud
Public cloud
Hybrid cloud
Community cloud
Major Roles Scrum
Product Owner
Scrum Master
Team
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
Service Delivery Models examples
SaaS: salesforce.com
Paas: Windows Azure
IaaS: Amazon Web Services
Best practices Rational Unified Process
develop software iteratively
manage requirements
use component-based architectures
model software visually
verify software quality
control changes to software
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
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
Meetings in scrum
Sprint Meeting
Sprint Review
Daily Scrum
Sprint Retrospective
5 data source architectural patterns
Record Sets
Active Record
Data Mapper
Table Data Gateway
Row Data Gateway
7 bestandteile Microservice architecture
Resources
Service Layer
Domain
Gateways
Http Client
Repositories
Data mapper
4 factors effecting performance
Implementation
Execution Environment
Usage
External Services
4 facette of requirement classification of glinz
Kind
Representation
Satisfication
Role
Cloud architecture principles
Decentralization
Asynchrony
Autonomy
Local responsibility
Controlled concurrency
Failure tolerant
Controlled parallelism
Conway’s Law
Organisationen, welche Systeme designen sind auf Designerstellungen, welche
Kopien der Kommunikationsstruktur dieser Organisation sind, beschränkt
