1 ME 59700 Spring 2013 Introduction to Systems Engineering Session 3 Dr. Dan C. Surber, ESEP © Copyright 2013.

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

10 Golden Questions for Concept Exploration & Development Dr. Dan C. Surber (317)
Simulating Ground Support Capability for NASAs Reusable Launch Vehicle Program Kathryn E. Caggiano Peter L. Jackson John A. Muckstadt Cornell University.
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
S Y S T E M S E N G I N E E R I N G.
Software Quality Assurance Plan
Aerospace Systems Engineering
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
SYSTEMS ENGINEERING APPROACH TO SYSTEM REALISATION P. Srikumar.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
CS 545 Software Systems Design Project Presentation Format Lecture Created by Dan Benson Computer Science Lectures © D. Benson, 2002.
Development and Use of Architectures in System Engineering Rosalind Lewis USC-CSSE Workshop October 2007 © 2007 The Aerospace Corporation Motivated by.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001.
Engineering Systems of.
The program work breakdown structure (WBS) establishes the essential
The ESS vacuum team has overall responsibility for all technical vacuum systems used on the: Accelerator, Target and Neutron Scattering Instruments and.
Effective Methods for Software and Systems Integration
Work Breakdown Structure
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Chapter 7: The 30 elements of systems engineering
CASE Tool Evolution Computer-aided documentation Computer- aided diagramming Analysis and design tools Automated design analysis Automated.
Space Engineering 2 © Dr. X Wu, 2012
CPIS 357 Software Quality & Testing
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
Space Engineering 2 © Dr. X Wu, Space Engineering 2 Lecture 1.
Space Systems Engineering: Functional Analysis Module Functional Analysis Module Space Systems Engineering, version 1.0.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Hampton Black – 11/5/12 MARS ONE. WHAT IS MARS ONE? Mars One is a private, apolitical organization whose intent is to establish a colony on Mars by 2023.
Systems Engineering Conceptual System Design. Systems Engineering and Analysis, B.S. Blanchard and W. J. Fabrycky, 3 rd edition, Prentice-Hall, 1998.
The Architecture of Systems. System Architecture Every human-made and natural system is characterized by a structure and framework that supports and/or.
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
Software Engineering Lecture 10: System Engineering.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
Chapter 3 Conceptual System Design
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
1 ME Fall 2014 Introduction to Systems Engineering Session 1 Dr. Dan C. Surber, ESEP © Copyright 2013.
SYSE 802 John D. McGregor Module 0 Session 3 Systems Engineering QuickView.
1 ME Spring 2015 Systems Engineering, Part II Session 8 5 February 2015 Mr. Larry Hopp, CPL © Copyright 2013.
ME Summer 2013 Systems Engineering, Part II Session July 2013 Mr. Larry Hopp, CPL.
EDGE™ Preliminary Project Plan P09102 – METEOR Stage Separation System JJ Guerrette (ME)
Installation and Commisioning SE view point Romuald Duperrier ESS SE manager.
ME Fall 2014 Introduction to Systems Engineering Session 6 Dr. Dan C. Surber, ESEP © Copyright 2013.
Breakdown Work Structure Applying Management Tools to a Project.
1 ME Fall 2014 Introduction to Systems Engineering Session 4 Dr. Dan C. Surber, ESEP © Copyright 2013.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Session 10 Dr. Dan C. Surber, ESEP
Session 2 Dr. Dan C. Surber, ESEP
Introduction to Project Management
Information Systems Development
An Overview of Requirements Engineering Tools and Methodologies*
Session 9 Dr. Dan C. Surber, ESEP
CINEMA System Engineering
Technical Resource Allocations
Developing Information Systems
Session 5b Dr. Dan C. Surber, ESEP
Overview of System Engineering
Enabling System Elements
Design and Implementation
CS 8532: Advanced Software Engineering
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
PSS verification and validation
Verification Concepts for SysmL v2
System architecture, Def.
Jeff Dutton/NASA COR August 26, 2019
Presentation transcript:

1 ME Spring 2013 Introduction to Systems Engineering Session 3 Dr. Dan C. Surber, ESEP © Copyright 2013

2 Lecture Topics Concept Exploration Types of Requirements Wasson’s SOI construct

3 Concept Exploration CONTEXT Diagram (your SOI related to all others) Concept of Operations & Support (CONOPS) –Missions –timelines System Architecture Elements (SA) –Hardware items –Software items –Technical data –Tools –Support equipment & Special Test Equipment (STE) –Facilities (mfg., testing, assembly, depot) –Training –People Four (4) types of system requirements –Performance -- Interface –Environment -- Design Constraint Product Breakdown Structure (PBS) Technology Readiness Level (1-9) Your System Environ- ments Data Senders Data Receivers Threats

4 SoS, SOI, MS, & SS SoS - Systems that interact with each, but were not all intentionally designed to work together, may exhibit unexpected behaviors upon interaction. Interoperability – the capacity for two or more systems to exchange inputs & outputs across an interface without adversely affecting operational effectiveness and suitability System of Interest (SOI) Mission System (MS) Support System (SS) Mission System performs the functions that yield results that are operationally suitable and effective for the User’s Need. Support System performs the functions that enable the Mission System to complete its operations and execute the mission life cycles defined by the User’s Need.

5 The “Vee” Diagram Concept Development Preliminary Design Detailed Design Build & Test Integration Qualification Testing System Validation Test & Evaluation Master Plan Subsystem Test Plan Product & Component Test Plans Credit to: Forsberg & Moor; Ben Blanchard & Wolter Fabrycky; J.O. Grady

6 Mission Event Timelines Understand the mission events performed by the Mission System –Operational suitability –Operational effectiveness Understand how the Support System prepares the Mission System for its next mission cycle Identify Target Determine Target Range & Speed Establish Target Aim Point Commence Reload Confirm Weapon Guidance Launch Weapon What if the weapon requires man-in-the-loop guidance commands until impact?

7 Example System Context Diagram Concept of Operations & Support 4 Types of System Requirements –Performance –Environmental –Interface –Design Constraint Product Breakdown Structure System Architecture

8 System Context for ISS System Of Interest (SOI) International Space Station Natural Environment Induced Environment Man-made Environment Threat Environment Other Systems Micro meteorites Space Debris A-Sat Weapon ammonia coolant leaks lost tools and parts leaking fuel from robot resupply RF energy from Shuttle radar laser landing/alignment signals UHF comms from ISS comms vacuum of space solar winds & flares hot & cold extremes robotic resupply vehicles NASA TDRSS comm satellites

9 Types of System Requirements PERFORMANCE – station shall remain on orbit for at least 10 years. INTERFACE – station shall interface with US Space shuttle and Russian resupply vessels. ENVIRONMENT – station shall survive micro meteorite impacts without loss of pressurization or power for the life of its time on orbit. DESIGN CONSTRAINT – station shall accommodate 99 percentile males and 1 st percentil females. TECHNICAL PERFORMANCE MEASURES ACQUISITION & TECHNICAL –KEY PERFORMANCE PARAMETERS (KPP) MEASURES OF EFFECTIVENESS (MOE) –MEASURES OF PERFORMANCE (MOP) »DATA ELEMENTS –THRESHOLD CRITERIA –OBJECTIVE CRITERIA Provide a manned station for long term on orbit research operations.

10 Mission Analysis & CONOPS Understand the primary mission(s) of the SOI –Scenarios within each mission profile –Understand the division between MS & SS Construct Mission Even Timelines Use System Context to discover relationships between SOI, MS, SS and external elements –Environments (natural, induced, man-made) –Interfacing systems –Design constraints –THREATS (natural, man-made) Feed Requirements Analysis –Performance -- Environmental –Interface (external) -- Design Constraint Preliminary System Architecture

11 Mission Event Timelines Understand the mission events performed by the Mission System –Operational suitability –Operational effectiveness Understand how the Support System prepares the Mission System for its next mission cycle Orbit the station core Orbit & attach truss with solar panels Orbit air lock module Add on-orbit spares Add science modules & air locks Add remaining truss & solar panels On-orbit assembly of the ISS MS = on-orbit modules SS = space shuttle, robot resupply, ground control

12 Concept of Operations & Support MSN SYS WHO WHAT WHERE WHEN HOW WHY SPT SYS WHO WHAT WHERE WHEN HOW WHY MISSION TYPES LEVELS OF MAINTENANCE TRAINING K S A EXISTING SPEC CODES OBSOLETE SEPC CODES NEW SPEC CODES

13 Further Concept Exploration Functional Analysis & Decomposition –Functional Block Diagrams –Functional Flow Block Diagrams –Architecture Analysis/Block Diagram Allocation of Performance Requirements to lower tier FUNCTIONS Schematic Block Diagram of Concept –Intra-faces & Inter-faces –Allocation of other requirements to SBD elements Product Breakdown Structure System Architecture Block Diagram

14 Product Breakdown Structure Decomposes the system into its configuration item groupings (by function, by supplier, or by template from a standard) Use at least a 3-tier construct –System –Product –Component Most systems have more tiers (5, 7 or 9)

15 PBS Breakdown System of Interest ISS SoS Support System ISS Supt Sys Mission System ISS US Space Shuttle NASA Msn Control Unity ModuleZarya Module 12 other Modules Subsystems Astronaut Tng Facility