Softwaretechnik at Universität Mannheim | Flashcards & Summaries

Select your language

Suggested languages for you:
Log In Start studying!

Lernmaterialien für Softwaretechnik an der Universität Mannheim

Greife auf kostenlose Karteikarten, Zusammenfassungen, Übungsaufgaben und Altklausuren für deinen Softwaretechnik Kurs an der Universität Mannheim zu.

TESTE DEIN WISSEN

Architectural Centralized Control Flow  Model

Lösung anzeigen
TESTE DEIN WISSEN

a dedicated control sub-system takes responsibility for managing the execution of other sub-systems, two principal models –

  • call-return model
    • top-down subroutine model where control starts at the top of a subroutine hierarchy and moves downwards 
  • manager model
    • one system component controls the stopping, starting and coordination of other system processes
Lösung ausblenden
TESTE DEIN WISSEN

Thin and Fat Client Deployment Models

Lösung anzeigen
TESTE DEIN WISSEN

Thin-client model:

  • application processing and data management carried out on server
  • used when legacy systems are migrated to client-server architectures
  • network load


Fat-client model

  • the server is only responsible for data management
  • most suitable for new C/S systems where the capabilities of the client system are known in advance
Lösung ausblenden
TESTE DEIN WISSEN

Pros and Cons of Patterns

Lösung anzeigen
TESTE DEIN WISSEN

Benefits:

  • easier to reuse successful designs
  • help in building reusable design
  • improve system documentation and understandability

Costs:

  • lower system's efficiency (speed)
  • require more classes
  • require more run-time objects
  • complexity!!
Lösung ausblenden
TESTE DEIN WISSEN

Typical Contents of CM Plan

Lösung anzeigen
TESTE DEIN WISSEN
  • types of documents to be managed
  • who takes responsibility
  • policies for change control
  • tools used to assist CM process
  • CM database
Lösung ausblenden
TESTE DEIN WISSEN

Prime Path Coverage (PPC)

Lösung anzeigen
TESTE DEIN WISSEN

TR contains each prime path in G

Lösung ausblenden
TESTE DEIN WISSEN

Costs of Testing

Lösung anzeigen
TESTE DEIN WISSEN

Half of a software company's development budget is spent on testing.


But the cost of Not testing is more expensive.

Lösung ausblenden
TESTE DEIN WISSEN

Strategy: Object Behavioral

Lösung anzeigen
TESTE DEIN WISSEN

Intent 

  •  Strategy lets the algorithm vary independently from clients that use it 

 Applicability 

  •  many related classes differ only in their behaviour, i.e. different variants of an algorithm are required 
  •  a class defines many behaviours, and these appear as multiple conditional statements in its operations. 
    •  related branches can be moved into their own strategy class 
  •  an algorithm uses data that clients should not know about 
    •  the strategy pattern can be used to avoid exposing complex, algorithm-specific data structures 

Consequences 

  •  no conditional statements for selecting behaviour 
  •  clients must be aware of different strategies 
  •  increased number of objects 
  • communication overheads 


Lösung ausblenden
TESTE DEIN WISSEN

Goals of system's architecture

Lösung anzeigen
TESTE DEIN WISSEN
  • Performance
    • localise operations in large-grained components to minimise sub- system communication
  • Security

    • use a layered architecture with critical assets in inner layers

  • Safety

    • isolate safety-critical components

  • Availability

    • include redundant components in the architecture

  • Maintainability

    • usefine-grained, self-contained component

  • Scalability

    • consider concurrency effects in case you need to distribute the system

Lösung ausblenden
TESTE DEIN WISSEN

Contract Creation Guidelines

Lösung anzeigen
TESTE DEIN WISSEN
  1. Identify system operations from the SSDs
  2. For complex system operations or which are not clear in the use case, construct a contract
  3. To describe the postconditions, use the following categories
    1. instance creation and deletion
    2. attribute modification
    3. associations formed and broken
Lösung ausblenden
TESTE DEIN WISSEN

Good architecture strives to achieve..

Lösung anzeigen
TESTE DEIN WISSEN
  • cohesive responsibilities
  • separation of concerns
  • protected variations
Lösung ausblenden
TESTE DEIN WISSEN

Fully Dressed Use Case Sections

Lösung anzeigen
TESTE DEIN WISSEN
  • Primary Actor
  • (Stakeholders & Interests)
  • Preconditions
  • Post conditions
  • Main Success Scenario
  • Extensions
  • (Special Requirements)
  • (Open Issues)
Lösung ausblenden
TESTE DEIN WISSEN

Domain Models

Lösung anzeigen
TESTE DEIN WISSEN

The fundamental idea in object-oriented analysis is to decompose a domain of interest 

  • into individual conceptual classes or objects
    • or just things that we are aware of 
  • in order to be able to “rebuild” the real world in the object-oriented software system later 
    •  aim for a “low representational gap”


A domain model is a visual representation of conceptual classes or real world objects in the domain of interest 

  •  it does not describe software classes or objects 
    • but provides inspiration for designing software objects later 
  •  domain models are also know as 
    • conceptual models 
    •  domain object models 
    •  analysis object models
Lösung ausblenden
  • 133057 Karteikarten
  • 1737 Studierende
  • 36 Lernmaterialien

Beispielhafte Karteikarten für deinen Softwaretechnik Kurs an der Universität Mannheim - von Kommilitonen auf StudySmarter erstellt!

Q:

Architectural Centralized Control Flow  Model

A:

a dedicated control sub-system takes responsibility for managing the execution of other sub-systems, two principal models –

  • call-return model
    • top-down subroutine model where control starts at the top of a subroutine hierarchy and moves downwards 
  • manager model
    • one system component controls the stopping, starting and coordination of other system processes
Q:

Thin and Fat Client Deployment Models

A:

Thin-client model:

  • application processing and data management carried out on server
  • used when legacy systems are migrated to client-server architectures
  • network load


Fat-client model

  • the server is only responsible for data management
  • most suitable for new C/S systems where the capabilities of the client system are known in advance
Q:

Pros and Cons of Patterns

A:

Benefits:

  • easier to reuse successful designs
  • help in building reusable design
  • improve system documentation and understandability

Costs:

  • lower system's efficiency (speed)
  • require more classes
  • require more run-time objects
  • complexity!!
Q:

Typical Contents of CM Plan

A:
  • types of documents to be managed
  • who takes responsibility
  • policies for change control
  • tools used to assist CM process
  • CM database
Q:

Prime Path Coverage (PPC)

A:

TR contains each prime path in G

Mehr Karteikarten anzeigen
Q:

Costs of Testing

A:

Half of a software company's development budget is spent on testing.


But the cost of Not testing is more expensive.

Q:

Strategy: Object Behavioral

A:

Intent 

  •  Strategy lets the algorithm vary independently from clients that use it 

 Applicability 

  •  many related classes differ only in their behaviour, i.e. different variants of an algorithm are required 
  •  a class defines many behaviours, and these appear as multiple conditional statements in its operations. 
    •  related branches can be moved into their own strategy class 
  •  an algorithm uses data that clients should not know about 
    •  the strategy pattern can be used to avoid exposing complex, algorithm-specific data structures 

Consequences 

  •  no conditional statements for selecting behaviour 
  •  clients must be aware of different strategies 
  •  increased number of objects 
  • communication overheads 


Q:

Goals of system's architecture

A:
  • Performance
    • localise operations in large-grained components to minimise sub- system communication
  • Security

    • use a layered architecture with critical assets in inner layers

  • Safety

    • isolate safety-critical components

  • Availability

    • include redundant components in the architecture

  • Maintainability

    • usefine-grained, self-contained component

  • Scalability

    • consider concurrency effects in case you need to distribute the system

Q:

Contract Creation Guidelines

A:
  1. Identify system operations from the SSDs
  2. For complex system operations or which are not clear in the use case, construct a contract
  3. To describe the postconditions, use the following categories
    1. instance creation and deletion
    2. attribute modification
    3. associations formed and broken
Q:

Good architecture strives to achieve..

A:
  • cohesive responsibilities
  • separation of concerns
  • protected variations
Q:

Fully Dressed Use Case Sections

A:
  • Primary Actor
  • (Stakeholders & Interests)
  • Preconditions
  • Post conditions
  • Main Success Scenario
  • Extensions
  • (Special Requirements)
  • (Open Issues)
Q:

Domain Models

A:

The fundamental idea in object-oriented analysis is to decompose a domain of interest 

  • into individual conceptual classes or objects
    • or just things that we are aware of 
  • in order to be able to “rebuild” the real world in the object-oriented software system later 
    •  aim for a “low representational gap”


A domain model is a visual representation of conceptual classes or real world objects in the domain of interest 

  •  it does not describe software classes or objects 
    • but provides inspiration for designing software objects later 
  •  domain models are also know as 
    • conceptual models 
    •  domain object models 
    •  analysis object models
Softwaretechnik

Erstelle und finde Lernmaterialien auf StudySmarter.

Greife kostenlos auf tausende geteilte Karteikarten, Zusammenfassungen, Altklausuren und mehr zu.

Jetzt loslegen

Das sind die beliebtesten StudySmarter Kurse für deinen Studiengang Softwaretechnik an der Universität Mannheim

Für deinen Studiengang Softwaretechnik an der Universität Mannheim gibt es bereits viele Kurse, die von deinen Kommilitonen auf StudySmarter erstellt wurden. Karteikarten, Zusammenfassungen, Altklausuren, Übungsaufgaben und mehr warten auf dich!

Mehr Karteikarten anzeigen

Das sind die beliebtesten Softwaretechnik Kurse im gesamten StudySmarter Universum

Softwaretechnik II

Karlsruher Institut für Technologie

Zum Kurs
Softwaretechnik

LMU München

Zum Kurs
Softwaretechnik 1

Hochschule Reutlingen

Zum Kurs
Softwaretechnik 2

Hochschule Hamm-Lippstadt

Zum Kurs

Die all-in-one Lernapp für Studierende

Greife auf Millionen geteilter Lernmaterialien der StudySmarter Community zu
Kostenlos anmelden Softwaretechnik
Erstelle Karteikarten und Zusammenfassungen mit den StudySmarter Tools
Kostenlos loslegen Softwaretechnik