Verification Joel Kastner. HAWC/DCS Verification Describe observing sequence for a test target Generate simulated data Process through HAWC and DCS pipelines.

Slides:



Advertisements
Similar presentations
1 Universities Space Research Association User Tools for Cycle 1 Phase II: SOFIA Spot R. Y. Shuping DCS Development Lead L. Lin DCS Engineer J. Rho Associate.
Advertisements

Chapter 12 Prototyping and Testing Design of Biomedical Devices and Systems By Paul H. King Richard C. Fries.
ICT Class System Life Cycle.  Large systems development projects may involve dozens of people working over several months or even years, so they cannot.
Lecture # 2 : Process Models
CEN nd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Process Models.
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
System Construction and Implementation Objectives:
Commentary on Validating Resource Usage in Least Commitment Planning Authors: Nazma Ferdous and Mark Giuliano Commentary by Rob Sherwood October 2006.
ProActive Task Manager Component for SEGL Parameter Sweeping Natalia Currle-Linde and Wasseim Alzouabi High Performance Computing Center Stuttgart (HLRS),
Part 2d: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding.
SOFIA Stratospheric Observatory for Infrared Astronomy DCS PDR at RIT3/7/2000 DCS Preliminary Design Review Sean C. Casey USRA Senior Scientist Lead Scientist.
SOFIA DCS History and Overview Ian Gatley. SOFIA March DCS Preliminary Design Review2 The South Pole CARA Project: A DCS demonstration A data.
DCS Architecture Bob Krzaczek. Key Design Requirement Distilled from the DCS Mission statement and the results of the Conceptual Design Review (June 1999):
Behavioral Design Outline –Design Specification –Behavioral Design –Behavioral Specification –Hardware Description Languages –Behavioral Simulation –Behavioral.
Simulation.
1 SWE Introduction to Software Engineering Lecture 5.
1 Simulation Modeling and Analysis Verification and Validation.
Section 15-1GLAST Ground System Design Review August 18&19, 2004 ISOC Organization ISOC Manager R Cameron Commanding, H&S Timeline Planning Command Generation.
Slide 1 Sterling Software Peter Sharer Sterling Software.
Examples of DCS Interaction with an FSI Bob Krzaczek.
Chapter 9 Database Design
L ECTURE 2 S OFTWARE P ROCESSES 1. O BJECTIVES To describe outline process models for requirements engineering, software development, testing and evolution.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Codex Guidelines for the Application of HACCP
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Testing. Definition From the dictionary- the means by which the presence, quality, or genuineness of anything is determined; a means of trial. For software.
DCS Overview MCS/DCS Technical Interchange Meeting August, 2000.
SSSC 02/18/2010 P. Marcum Science Utilization Policies SOFIA SCIENCE UTILIZATION POLICIES Pamela M. Marcum SOFIA Project Scientist SSSC Feb 19, 2010.
Example  Software for a virtual library (borrowing books using the Internet) Internt terminal DB.
Creating a Shared Vision Model. What is a Shared Vision Model? A “Shared Vision” model is a collective view of a water resources system developed by managers.
Generic Instrument Processing Facility Interface Specifications A. BuongiornoFrascati 12 /10/2012 ESA EOP-GS 1.
Lecture 3 Software Engineering Models (Cont.)
Advanced Higher Computing SOFTWARE DEVELOPMENT PROCESS.
Lecture 7: Requirements Engineering
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Integrated Data Cycle Systems Harvey E. Rhody Chester F. Carlson Center for Imaging Science.
Mark Dixon 1 Tech – Introduction. Mark Dixon 2 Module Aims give you experience of: –The Software Development Lifecycle Analyse (of Problem / Application.
Midterm Presentation Capstone Team#1, Spring 2011 Irshad Ahmad KhanBalaji Srinivasan Ramakrishna AtluruVideesh Gogineni Instructor: Dr. Kwok-Bun Yue Mentor:
SSC SI Data Processing Pipeline Plans Tom Stephens USRA Information Systems Development Manager SSSC Meeting – Sept 29, 2009.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Worldwide Protein Data Bank Common D&A Project Sequence Processing Modular Demo May 6, 2010 Project Deliverable.
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Bina Nusantara 19 C H A P T E R SYSTEM CONSTRUCTION AND IMPLEMENTATION.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
1 SUZAKU HUG 12-13April, 2006 Suzaku archive Lorella Angelini/HEASARC.
1 Universities Space Research Association Science Instrument Pipeline Requirements SSSC 2009 September 29 Erick Young Director SOFIA Science Mission Operat.
T Project Review Muuntaja I1 Iteration
Paul Alexander1 DS3 Deliverable Status 4 th SKADS Workshop, Lisbon, 2-3 October 2008 DS3 Deliverables Review.
Module 3: Problem Solving: Look for a pattern Guess and check.
1 Process activities. 2 Software specification Software design and implementation Software validation Software evolution.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
Calibration meeting summary
How Systems are Developed
I&T&C Organization Chart
Software Verification and Validation
Software Process Activities.
Software Requirements
An Introduction to Visual Basic .NET and Program Design
Model-Driven Analysis Frameworks for Embedded Systems
Lecture 09:Software Testing
The Hazard Analysis Critical Control Point
The Hazard Analysis Critical Control Point
Click to add title Planning for LSST Verification George Angeli LSST All Hands Meeting Tucson August 15, 2016.
Systems Construction and Implementation
System Construction and Implementation
Systems Construction and Implementation
VOEvent client software
Presentation transcript:

Verification Joel Kastner

HAWC/DCS Verification Describe observing sequence for a test target Generate simulated data Process through HAWC and DCS pipelines Generate archive product Compare results with known test target

AIRES/DCS Verification AIRES has an established test plan AIRES is providing algorithms and tests to DCS Implement tests in DCS environment Ensure that both approaches yield same result

DCS Extensibility Tests The South Pole experiment resembles FORCAST and FLITECAM We plan to reuse existing modules from the South Pole experiment and compare results with FSI team algorithms This tests the applicability of the DCS methods to future instruments

DCS/MCS Interface Tests When MCS prototype is available, DCS will subscribe to it and test interfaces

Compliance with GI Needs Astronomers write scenarios Mark Morris authored prototypes, distributed at Conceptual Design Review DCS team converts scenarios to tasks Team is knowledgeable about astronomy and software development Team presents verification review Verify compliance

DCS Design Verification through Use Case Analysis Narrative Scenario Use Cases DCS Design

Verification Plan Need a method to verify that DCS has met its requirements “Use Case Analysis” provides such a method By constructing use case scenarios we can test the DCS & verify that it has met its requirements

DCS Design Verification through Use Case Analysis Scenario s Validation Matrix DCS Design Pseudo Data “Match?” 4