Karteikarten
Softwaretechnik 2
Karten in diesem Stapel (31)
- 1Brooks LawAdding manpower to a late software project makes it later
- 2Boehms first LawErrors are more frequent during requirements and design
- 3Dijkstras LawTesting shows the presence, not absence of bugs.
- 4Lehmans 2 laws1: A used system will be changed.
2: An evolving system increases in complexity unless something is done to reduce it. - 5Parnas LawInformation Hiding, only what is hidden can be changed without risk.
- 6SOLIDSingle Responsibility Principle
Open Closed Principle
Liskov Substitution Principle
Interface Segregation Principle
Dependency Inversion Principle - 7Software development process modelsWaterfall
V Model
Spiral Model
Unified Process - 8Stages WaterfallPlanung, Definition, Entwurf, Implementierung, Testen, Einsatz
- 9Stages V-ModelRequirements Def
Coarse Grained Design
Detailed Design
Implementation
Unit Tests
Integration Tests
System Tests
Acceptance Tests - 10Spiral Model QuatersObjective Setting
Risk assessment and reduction
Implementation and validation
Planning - 11Unified Process DisciplinesBusiness Modelling, Requirements, Design, Implementation, Test, Deployment
Configuration & Change management, Project management, Environment - 12Unified Process PhasesInception: Vision, Business case
Elaboration: Risky implementation, req discovery
Construction
Transition: beta tests, deployment - 13Agile approachesXP, Scrum
- 14Agile principlesIndividuals and Interactions over Processes and tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to change over following a plan - 15Scrum: Roles, Meetings and ArtifactsRoles: PO, Scrum Master, Team
Meetings: Planning, Daily, Review, Retrospective
Artifacts: Product Backlog, Sprint backlog, Sprint featureincrement - 16Requirement classificationConcern based: functional, quality, constraint
Representation: operational, quantitative, qualitative, declarative
Satisfaction: hard, soft
Role: prescriptive, normative, assumptive - 17Specific ConcernsFunctional: Functionality and Behaviour, data, stimuli, reactions
Quality: Performance, Reliability, Usability, Security, Availability, portability, Maintainability
Contraint: Physical, Legal, Cultural, Environmental, Design&Implementation Interface - 18GRAS PatternsTODO
- 19View points in palladio{Structural, Behavioural, Deployment}
view points. - 20EA Patterns - Domain Logic PatternsTransaction Script
Domain model
Table Module - 21EA Patterns - Data Source PatternsRecord Map
Data Table Gateway
Active Record
Row Data Gateway
Identity Map
Data Mapper - 22EA Patterns - OO-REL PatternsSingle Table Inheritance
Class Table Inheritance
Concrete Table Inheritance - 23Clean ArchitectureTODO
- 24Cloud services: - Characteristics - Delivery Models - Deployment modelsCharacteristics: Elastic scalability, On-demand self-service, ubiquituous network access, resource pooling, measured service
Delivery models: SaaS, PaaS, IaaS
Deployment models: Public, private, hybrid - 25Architecture principlesTODO
- 26Conways LawAny organizaton that designs a system will produce a design whose structure is a copy of the organizations communication structure.
- 27Features of ModelsRepresentational feature
Reduction feature
Pragmatic feature (not directly associatable to originals) - 28A metamodel must coverAbstract/concrete Syntax
Static/dynamic Semantics - 29Dimensions of DependabilityAvailability
Reliability
Safety
Security
Resilience - 30RT PatternsChannel
Monitor-Actuator
Sanity Check
Watchdog
Safety Executive - 31RT Priority LevelsInterrupt level prio: Process requires fast response
Clock level prio: Periodic processes
Informationen
- Beschreibung
- Karteikarten am Softwaretechnik 2, erstellt von Lukas Bach am 09/03/2019.
- Erstellt von
- Lukas Bach
- Aufrufe
- 3
- Bewertung