Space Engineering 2 © Dr. X Wu, 2012

Slides:



Advertisements
Similar presentations
Unit 3, Chapter 9, Lesson 9: Space Systems Engineering 1 The Systems-engineering Process Trading Requirements We use the requirements loopa necessary and.
Advertisements

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.
Basic Overview of Project Management and Life Cycle ACES Presentation T. Gregory Guzik January 21, 2003.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Understanding the Systems Engineering Process
Stepan Potiyenko ISS Sr.SW Developer.
14/06/20151 MORE Requirements seen from ESA Pedro Pablos 1 st MORE Team Meeting 27 Febrero 2007.
Introduction to Software Engineering Dr. Basem Alkazemi
Development and Use of Architectures in System Engineering Rosalind Lewis USC-CSSE Workshop October 2007 © 2007 The Aerospace Corporation Motivated by.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Overview of Software Requirements
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
Systems Engineering Management
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.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Page - 1 Rocketdyne Propulsion & Power Role of EASY5 in Integrated Product Development Frank Gombos Boeing Canoga Park, CA.
Engineering Systems of.
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Systems Engineering for Space Vehicles Bryan Palaszewski with the Digital Learning Network NASA Glenn Research Center Cleveland, OH.
Effective Methods for Software and Systems Integration
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
Overview of the Database Development Process
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
NASA’s Goddard Space Flight Center LRO Integration and Test Joanne Baker GSFC Code 568 August 16-17, 2005.
USAFA Department of Astronautics I n t e g r i t y - S e r v i c e - E x c e l l e n c e Astro 331 Electrical Power Subsystem—Intro Lesson 19 Spring 2005.
Tielong Zhang On behalf of the CGS Team in the Institute of Geology and Geophysics, Chinese Academy of Science Spacecraft System and Payload China Geomagnetism.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Software System Engineering: A tutorial
ITEC 3220M Using and Designing Database Systems
Principles of Engineering System Design Dr T Asokan
Command and Data Handling (C&DH)
Space Engineering 2 © Dr. X Wu, Space Engineering 2 Lecture 1.
1 DORS PROPRIETARY–SENSITIVE INFORMATION Welcome to DORS Many high volume restaurants during peak periods can experience a significant increase in inaccurate.
Lecture 7: Requirements Engineering
Preparing for a Wind Lidar Venture Class Mission Discussion at Lidar Working Group Meeting Bar Harbor, ME August 24 – 26, 2010 Dr. Wayman Baker 1.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
1 | 2010 Lecture 1: Systems – what and why?. Covered in this lecture Systems and systems thinking Why we use Systems Engineering Systems from “cradle.
Request for Proposal (RFP)
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
Process: A Generic View
1 Mission Discussion & Project Reviews 祝飛鴻 10/14/93.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
NASA/Air Force Cost Model presented by Keith Smith Science Applications International Corporation 2002 SCEA National Conference June
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Smart Home Technologies
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
Software Engineering Lecture 10: System Engineering.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
EDGE™ Preliminary Project Plan P09102 – METEOR Stage Separation System JJ Guerrette (ME)
Supportability Design Considerations
OVERVIEW Impact of Modelling and simulation in Mechatronics system
HCI in the software process
Peer Review Agenda (Suggested).
Request for Proposal (RFP)
HCI in the software process
Human Computer Interaction Lecture 14 HCI in Software Process
System architecture, Def.
Presentation transcript:

Space Engineering 2 © Dr. X Wu, 2012 Lecture 3 Space Engineering 2 © Dr. X Wu, 2012

Group Presentations Week 5: mission design (5%) Week 13: spacecraft bus subsystem design (5%)

Space Engineering 2 © Dr. X Wu, 2008 Outline Introduction Systems Engineering Spacecraft Environment Spacecraft Bus Subsystems Space Engineering 2 © Dr. X Wu, 2008

Space Engineering 2 © Dr. X Wu, 2008 What is a Space System Ground Spaceflight Operations Payload Operations Payload Data Processing Space Orbits Spacecraft Launch Launch Vehicle Integration Launch Operations Space Engineering 2 © Dr. X Wu, 2008

Spacecraft Subsystems Space Segment Payload Bus Structure Mechanisms Attitude and orbit control Thermal Propulsion Power Telemetry and command Data handling Space Engineering 2 © Dr. X Wu, 2008

Space Mission Elements

Space Engineering 2 © Dr. X Wu, 2008 Systems Engineering A logical process for system development Functional & physical decomposition of system into logical parts Involves development of system requirements: System Analysis Requirements Development Interface Requirements Requirements Validation Test & Demonstration Simulation Analysis Physical/functional configuration audits Integration & Test Planning “Cradle to Grave” lifecycle planning Treaty provisions and DoD regulations require disposal of satellites at the end of life. 7 Space Engineering 2 © Dr. X Wu, 2008

Roles of Systems Engineering Develop the system architecture Develop and maintain the requirements Analyze and characterize the system design Manage technical resources and performance Develop and maintain interfaces Verify and validate the system Identify, assess, manage and mitigate risks during design, development and implementation Organize technical peer reviews 8 Space Engineering 2 © Dr. X Wu, 2008

Spacecraft Systems Engineering Process in SMAD Analyze the mission Mission objectives Estimation of needs, requirements, and constraints Characterize the mission Alternative mission concepts Alternative mission architecture System drivers Characterizing the mission architecture Evaluate the mission Identification of critical requirements Mission utility Mission concept selection Define requirements Space Engineering 2 © Dr. X Wu, 2008

Objectives, Requirements and Constraints Mission objectives Primary objectives: the broad goals that the system must achieve to be productive Secondary objectives: for political, social, or cultural purposes Requirements and constrains Functional requirements define how well the system must perform to meet its objectives Operational requirements determines how the system operates and how users interact with it Constraints limit cost, schedule and implementation techniques 10 Space Engineering 2 © Dr. X Wu, 2008

Space Engineering 2 © Dr. X Wu, 2008 Mission Concepts Data Delivery – how mission and housekeeping data are obtained, distributed and used Space vs. ground Central vs. distributed processing Level of autonomy Communications Architecture – how the subsystems talk to each other and the ground station Intra-satellite link Inter-satellite link Down/Up link Tasking, Scheduling, and Control – how the system decides what to do in the lifetime Spacecraft autonomy Mission lifetime – the overall time from planning, building, deployment, operations, replacement, and end-of-life Mission Concept Selection Go/no-go decision on proceeding with the mission Selection of the mission concept Detailed engineering decisions 11 Space Engineering 2 © Dr. X Wu, 2008

Identifying Alternative Mission Architecture Identify the mission elements subject to trade Identify the main options for each tradable elements Construct a trade tree of available options Prune the trade tree by eliminating unrealistic combinations Look for other alternatives which could substantially influence how we do the mission 12 Space Engineering 2 © Dr. X Wu, 2008

Identifying System Drivers Identify the area of interest Identify parameters which measure the area of interest Develop first-order algorithms like time delay, resolution… Examine the factors Look for ‘hidden drivers’ Develop a more accurate algorithm to estimate the parameters 13 Space Engineering 2 © Dr. X Wu, 2008

Characterizing the Mission Architecture Define the preliminary mission concept Define the subject characteristics Determine the orbit or constellation characteristics Determine payload size and performance Select the mission operations approach Design the spacecraft bus Select a launch and orbit transfer system Determine deployment, logistics, and end-of-life strategies Provide costing support Document and iterate 14 Space Engineering 2 © Dr. X Wu, 2008

Critical Requirements What if affects Coverage or response time Number of satellites, altitude, inclination, communications architecture, payload field of view, scheduling, staffing Resolution Instrument size, altitude, attitude control Sensitivity Payload size, complexity; processing, and thermal control; altitude Mapping Accuracy Attitude control, orbit and attitude knowledge, mechanical alignments, payload precision, processing Transmit power Payload size and power, altitude, inter-satellite distance On-orbit lifetime Redundancy, weight, power and propulsion budgets, component selection Survivability Altitude, weight, power, component selection, design of space and ground system, number of satellites, number of ground stations, communications architecture Space Engineering 2 © Dr. X Wu, 2008

Space Engineering 2 © Dr. X Wu, 2008 Mission Utility Provide quantitative information for decision making Provide feedback on the system design Mission simulation Commercial mission analysis and mission utility tools Space Engineering 2 © Dr. X Wu, 2008

Mission Concept Selection Overall mission objectives Technical feasibility Level of risk Schedule and budget Preliminary results

Requirements Specification Purpose The contract between the builder and the user Define capabilities, without necessarily defining implementation Define constraints Characteristics Unambiguous Complete Consistent Verifiable and testable Limit bias towards a particular implementation Space Engineering 2 © Dr. X Wu, 2008

Content of Requirements Document Define context of the system How will the system be used? Who/What is involved Functional requirements What is the system supposed to do? Performance specs Definitions/glossary Non functional requirements Space Engineering 2 © Dr. X Wu, 2008

Non-functional Requirements 20 Space Engineering 2 © Dr. X Wu, 2008

Space Engineering 2 © Dr. X Wu, 2008 System Resources System level Mass Power Energy Volume Communication Subsystem level CPU utilization On-board storage Switch (power feed) availability Data interface availability Fuel capacity Space Engineering 2 © Dr. X Wu, 2008

System Development Process ‘Breadboard’ system Concept development and proof of concept Prototype First draft of complete system Implements all requirements Engineering model Complete system without final flight configuration Plug and play with flight model Flight model The final product Space-ready product, implements all requirements Space Engineering 2 © Dr. X Wu, 2008

Space Engineering 2 © Dr. X Wu, 2008 Design Review Preliminary Design Review (PDR) Architecture and interface specifications Software design Development, integration, verification test plans Breadboard Critical Design Review (CDR) System Architecture Design Elements Mechanical Design Elements Electrical Design Elements Software Design Elements Integration Plan Verification and Test Plan Project Management Plan Space Engineering 2 © Dr. X Wu, 2008

Spacecraft Integration and Test Methodical process for test of spacecraft to validate requirements at all levels Sequence: Perform component or unit level tests Integrate components/units into subsystems Perform subsystem tests Integrate subsystems into spacecraft Perform spacecraft level test Integrate spacecraft into system Perform system test when practical Space Engineering 2 © Dr. X Wu, 2008

System Integration and Test Types: Functional testing Do subsystems work together? “Fit” check payload fairing, adapter Environmental testing Thermal vacuum, shock and vibration testing Combined functional and environmental testing Usually spacecraft level thermal vacuum involved integrated functional testing Final System demo: Do all segments work together, mainly ground and space Payload or system characterization Performance can be altered by the space environment Often performed in thermal vacuum chamber Can Use a combination of “hardware in loop” and simulation: Ground Testing Systems like propulsion and attitude control cannot be operated safely on the ground May use “stimulators” for sensors like sun & earth sensor, or star tracker. Space Engineering 2 © Dr. X Wu, 2008

Design Verification and Qualification Testing Validate design precepts and models Examine system limitations Build & Test, Build & Test… Qualification: Determine system suitability for mission Provides tool for customer to measure success of the enterprise Allows time for fixes to meet requirements – may involve warranty period Space Engineering 2 © Dr. X Wu, 2008

Space Engineering 2 © Dr. X Wu, 2008 Types of Design Tests Functional “Life” Testing (could involve structural, thermal, illumination, power cycling, radiation exposure etc.) Component to System Level Often performed in between other forms of test Structural Static Tests Dynamic Tests Thermal Thermal cycling Thermal vacuum Space Engineering 2 © Dr. X Wu, 2008

Space Engineering 2 © Dr. X Wu, 2008 Conclusion Spacecraft systems engineering envisioning, designing, building, operating, and funding space systems. Life cycle of a project From mission concept to orbit Supporting documentation Requirements specification Design documents Interface control documents Space Engineering 2 © Dr. X Wu, 2008