Plans for LSE-130 through CD-2 Gregory Dubois-Felsmann SLAC National Accelerator Laboratory.

Slides:



Advertisements
Similar presentations
Overcoming Customer Constraints on Requirements Documents Presented by: Robert Smole Presented by: Robert Smole November 5, 2008 Sub-Optimization of Systems.
Advertisements

TIME MANAGEMENT 641 Topic 03 Activity Sequencing.
IX- CONSTRUCTION PLANNING
Configuration Management
Thad Henry Configuration and Data Management. Purpose: To propose a strategy for assessing the development and effectiveness of configuration management.
Systems Engineering Breakouts George Angeli. Tuesday 11am Current Commissioning Plans – Chuck Claver Revised commissioning timeline Development plans.
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
WBS & AO Controls Jason Chin, Don Gavel, Erik Johansson, Mark Reinig Design Meeting (Team meeting #10) Sept 17 th, 2007.
1 Introduction to System Engineering G. Nacouzi ME 155B.
1 April 2010 TX SET Timeline Project Conceptualization 11 weeks Market Requirements 12 weeks ERCOT Requirements 12 weeks Conceptual Design 6 weeks Detail.
CS Integration Management (Part 6) Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor Bilkent University,
Project Management Session 7
SE 555 – Software Requirements & Specifications Introduction
Project Plan Development
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
LSU 10/09/2007System Design1 Project Management Unit #2.
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
Introduction to Computer Technology
Project Life Cycle Introduction and Overview © Ed Green Penn State University All Rights Reserved.
Measuring What Matters November 7 th Agenda Review and update of tasks and timeline Review and update of tasks and timeline Role of RTF Role of.
ITER In-Vessel Coils (IVC) Interim Design Review PDR Checklist Items C Neumeyer July 28, 2010 July 26-28, 20101ITER_D_3MAZCX.
©2008 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected under all copyright laws as they currently exist.
Verification and Validation on LSST Brian Selvy LSST All-Hands Meeting Bremerton August 17, 2015.
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
Using Business Scenarios for Active Loss Prevention Terry Blevins t
MICE Collaboration Meeting Frascati 26 – 29 June 2005 Work Group report On Design & Safety Review.
Engineering Design Introduction to Mechanical Engineering
EddiCam: The Eddington Photometric Camera EddiCam Definition Phase Kick-Off Meeting J. Miguel Mas-Hesse Vienna, 17th Sept., 2001.
26 June 2008 DG REGIO Evaluation Network Meeting Ex-post Evaluation of Cohesion Policy Programmes co-financed by the European Fund for Regional.
LCFOA Meeting at SLAC Linear Collider Forum of the Americas 1 LINEAR COLLIDER FORUM OF THE AMERICAS CONVENTIONAL FACILITIES OVERVIEW Victor R. Kuchler.
Lecture 7: Requirements Engineering
CLIC Implementation Studies Ph. Lebrun & J. Osborne CERN CLIC Collaboration Meeting addressing the Work Packages CERN, 3-4 November 2011.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Develop Project Charter
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Conceptual Design Requirements for FIRE John A. Schmidt FIRE PVR March 31, 2004.
1 Using Common Criteria Protection Profiles. 2 o A statement of user need –What the user wants to accomplish –A primary audience: mission/business owner.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
Board Incentive, Director Experience, and Outcomes of Joint Venture Investment Jung-Ho Lai National Taipei College of Business I-Ju Chen Yuan-Ze University.
Project X RD&D Plan Beam Transfer Line and Recycler Injection David Johnson AAC Meeting February 3, 2009.
Software Engineering REQUIREMENT ENGINEERING. Software Engineering Phases.
Smart Home Technologies
1 Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde.
Software Requirements Specification Document (SRS)
September 10, FY 2003 Plans Bob Simmons. September 10, Introduction Overview of Project and Engineering Plans Project Plans Engineering Plans.
NCSX Interface Control Management Plan and Implementing Procedure 003 Peer Review December 19, 2002.
23-Nov-1999STScI Projects Monthly Status Review1 of 8 SpaceTelescopeScienceInstitute COS Status Report for period December, 1998 to November, 1999 Tony.
Upgrade PO M. Tyndel, MIWG Review plans p1 Nov 1 st, CERN Module integration Review – Decision process  Information will be gathered for each concept.
1 Requirements Analysis Lecture # Recap of Requirements Elicitation - 1 Requirements elicitation deals with discovering requirements for a software.
Content Lessons from writing proposals and work on PTDR How can this meeting help to remedy problems SCT AOB.
LIU Configuration Management EDMS Documentation, Layout and ECRs This presentation follows the LIU-PSB specific presentation done on 9 th October 2014.
Commissioning Planning
Camera PDR/CD1 Planning 19 September 2008
Verification Matrix Process
Software Project Configuration Management
Agenda ComCam planning and scheduling (James & Jacques) CCS & CCS-TCS Interface (Tony) Software to use ComCam Software to get data out of ComCam (Mike)
CS4311 Spring 2011 Process Improvement Dr
Engineering Design Process
CS 425/625 Software Engineering Software Evolution
DOE: Transition from MIE to Early Operations Kevin Reil LSST Camera Commissioning Lead LSST Commissioning Plan Review January 24-26, 2017.
10 Stages Of the Engineering Design Process
CLINICAL INFORMATION SYSTEM
Software & Hardware for Wavefront Estimation Pipeline Development Te-Wei Tsai Software Engineer Joint Technical Meeting March 6, 2017.
EMIS 7307 Chapter 6.
Click to add title Planning for LSST Verification George Angeli LSST All Hands Meeting Tucson August 15, 2016.
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
Instrument Overview Larry Springer HMI Program Manager
Project Management Unit #2
Presentation transcript:

Plans for LSE-130 through CD-2 Gregory Dubois-Felsmann SLAC National Accelerator Laboratory

Role of the LSE-130 ISD LSE-69 is the main Interface Control Document (ICD) between the Camera and Data Management. It depends on two subsidiary documents: – LSE-68 defines the details of the Camera data acquisition interface – LSE-130 defines details of data transfers needed by DM, other than the actual image data LSE-69 defines categories of Camera-to-DM transfers of “support data” – for which LSE-130 will supply the lists of data items: – Design, Assembly, and Laboratory Test Data – CA-DM-CON-ICD-0001 – Camera Conditions Data (i.e., telemetry) – CA-DM-CON-ICD-0002 – Camera Configuration Data (the data used by the OCS configure command) – CA-DM-CON-ICD-0005 The spirit of LSE-130 has been that it should define the data that DM can reasonably anticipate requiring for the pipelines and data quality assessment – and that prudent engineering requires for cross-checks on critical effects – It is desirable to have alternatives to “blind fits” to camera effects in on-sky data

Scope concerns Because this definition for LSE-130 has some inherent elasticity (“prudent engineering”) there are some concerns about deriving Camera-level project scope (i.e., inputs to the CD-2 baseline) from requirements implicit in the data enumerated in LSE-130 The nature of much of the data being discussed is that it helps DM optimize its performance on the Camera we actually receive It is very difficult to work backward from the SRD performance requirements to unchallengeable statements that DM must have data item X with quality Y or fail – especially since we don’t know in detail yet what the actual Camera’s idiosyncrasies will be Some judgment is required and some detailed sensor effects studies may be characterized as science-optimization work to be done under the DESC We should try to keep these management-level decisions out of this session

History of LSE Joint Technical Meeting – Interactive brainstorming of a list of data needed by DM – Meant to be a “Phase 1” list – defining the types of data required but not providing quantitative specifications on precision, spatial granularity, etc. November 2013 – June 2014 – Some refinement by DM – Review by the Camera of the meaning of each item and whether it was consistent with established scope for the Camera’s construction, documentation, and test plans Now – Move to more quantitative definitions – Revise document structure to reflect explicit reliance on documented Camera test plans (replacing some of the previous lists of items) – Capture as input to CD-2 (note earlier Director’s Review) – Future changes with scope implications will need full CCB impact review

LSE-130 draft structure 1.Introduction 2.Camera to DM 1.Design, Assembly, and Laboratory Test Data 1.Component identities 2.Focal place electronic layout 3.Camera geometry 4.Physical sensor characteristics 5.Optical modeling 6.Thermal modeling 7.Documentation 2.Conditions Data 3.Configuration Data 4.General specifications 3.DM to Camera (incomplete)

Plans for LSE-130 Move the full current “list of items” to a DM-level document (handle LDM-272 has been reserved) Modify LSE-130, primarily in sections and 2.1.5, to refer to existing (and upcoming) Camera test plans – E.g., Sensor Electro-optical Test Plan, LCA Mark up LDM-272 to show the requirement/ICD/other document that confirms that each required data item will be available