Summary: System Engineering

Read the summary and the most important questions on System Engineering

• System Engineering week 1

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

• What’s the role of anindustrial engineer?

  
  - Proces improvement
  
  
  - Problem analysis
  
  
  - Proces and product design

• What is systems engineering?

  
  “An interdisciplinary approach toevolveandverifyanintegratedandoptimallybalanced set of product andprocess designs thatsatisfy user needsandprovide information for management decision making.”
  
  So: a method to design a system taking into account all stages of the life cycle

• What is the INCOSE definition of systems engineering?

  Systems engineering is an interdisciplinary approach and means to enable the realization of successful systems. It focus on defining customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem. Systems Engineering integrates all the disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation. Systems Engineering considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs.

• Current and growing focus for System engineering

  
  - Changes in market
  - International tenders
  - European law
  - Open contracting
  - Shift from technical specification to functional specification
  - Shift of risk and responsibilities 

• Design and construct a complex system

  
  Project:
  - Unique 1 off solution
  - Start and end date
  - Scope, time, money

• Project management vs systems engineering

  Overlap van planning, risk management, configuration management, data management, assessment, decision analyse

• Life cycle phases

  
  - Tender phase
  - Design phase
  - Building, construction,
  - Testing
  - Use and Maintenance
  - Demolition

• Stakeholder management in Project management

  Parties with an interest in the execution and outcome of a project. They would include business streams affected by or dependent on the outcome (Prince2).
  
  
  Stakeholders are persons or organizations(e.g., customers, sponsors, the performing organization, or the public), who are actively involved in the project or whose interests may be positively or negatively affected by the performance or completion of the project.
  
  (PMI).
  
  
  Any individual, group or organization that can affect, be affected by, or perceiveitselfto be affected by, a programme
  
  (MSP).

• SBS: System Breakdown Structure(‘Objectenboom’)

  
  - ‘Architecture’ of subsystems (also includes interfaces)
  - Decomposition
  - Subsystems also known as objects
  - Objects and how they relate
  - First insight to interfaces

• Difficulties/ cave at in requirements formulation

  
  - Requirements creep/ volatility
  - Not verifiable/ testable
  - Unable to prioritize
  - Pre-defined solution
  - Incomplete
  - Stakeholders not sufficiently involved