Read the summary and the most important questions on Systems Engineering

• Systems Engineering V1

  This is a preview. There are 4 more flashcards available for chapter 19/04/2016
  Show more cards here

• Sketch the triangle of aspects on life cycles.

  System integrity requires that these three aspects are in balance and given equal emphasis at all decision gate reviews.

• Exercise 1

  This is a preview. There are 4 more flashcards available for chapter 26/04/2016
  Show more cards here

• Sketch the extended V-Model for the Lawnmower.

  Conceptualize, elicit requirements 
  
  prototype, produce, sale

• What is a Use-Case? Sketch am example.

  A use case contents a number of procedures, which show how the system is used and which situations/messages it needs to deal with.

• Systems Engineering V2&3

  This is a preview. There are 3 more flashcards available for chapter 03/05/2016
  Show more cards here

• What is a Blackbox, Whitebox and Greybox?

  A Blackbox does only look at the in- and output. The rerelation of both can only be described stochastically.
  
  In a Whitebox the system will be shown, with all causes and effects in between the input and output. (Mathecally possible)
  -> high complexity
  
  The Greybox is a Blackbox with a subsystem seen like a Whitebox.

• What kind of different system views are there?

  Depending on the approach the views can be divided
  
  In the engineering process different departments have different views on a developed product

• What is a 'Life cylce' (always for Soi). Name difference between technical and economical view on life cycles.

  
  Economical view starts with product launch, systems engineering starts from the very first idea. 
  
  

  • every system has a life-cycle, even if it is not formally defined
  • life cycle refers to the System-of-interest
  • life cycle is structured in stages
  • every stage of a life-cycle ends up with a decision gate
  • the Systems Engineer is responsible for the individual planning of the system life-cycle (tailoring process)
  • Systems Engineering processes on the beginning of the life-cycle, but keeps track for the whole life-cycle

• How do identify a System of System over a System of interests?

  • Operational independence of constituent systems
  • Managerial independence of constituent systems
  • Geographical distribution
  • Emergent behavior
  • Evolutionary development processes

  
  By working together the systems generate greater benefits than by the use of every system on its own

• Exercise 2

  This is a preview. There are 2 more flashcards available for chapter 17/05/2016
  Show more cards here

• Sketch a Risk Management concept (Level of risks)

  
  

  • The likelihood that undesirable event will occur
    
  • The undesirable consequence of the event if it does occur
    
  • The only way to remove the presence of risk is to set goals very low, to stretch the schedule, and to supply unlimited funds.

  
  
            -> It will never happen in the real world.

• Name the three basic risk categories (and draw a model of their correlation, also take the programmatic risk into account).

  
  Technical risk:
  

  • technical requirement not be achieved
    

  
  
  Cost risk: 
  

  • Budget to be exceeded
    

  
  
  Schedule risk: 
  

  • fail to meet schedule milestones – cascading effect
    

  
  
  Programmatic risk: 
  

  • Events beyond the control of the project manager
    

• Systems Engineering V4

  This is a preview. There are 14 more flashcards available for chapter 31/05/2016
  Show more cards here

• What is the difference between a requirement and a need?

  Requirement: 
  

  • formal structured
  • can be: verified & validated
  • several requirements can satisfy a single need

  Need:
  

  • required results
  • desired by stakeholders
  • base of requirements 

  Example:
  
  The car should be colorful -> need
  The color is 00FF00 -> requirement
  
  We need a big display with the possibility to touch
  The display has to react in less than 0,25s 
  
  => Needs have to be translated into technical requirements!