LAT System Verification Issues

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Software Quality Assurance Plan
Foundational Objects. Areas of coverage Technical objects Foundational objects Lessons learned from review of Use Case content Simple Study Simple Questionnaire.
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
Software Quality Assurance Plan
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 5 Architecture-Driven Component Development.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Software Quality Metrics
GLAST LAT ProjectLAT Engineering Meeting, April 1, 2003 GLAST Large Area Telescope: Performance & Safety Assurance Darren S. Marsh Stanford Linear Accelerator.
Configuration management. Reasons for software configuration management  it facilitates the ability to communicate  status of documents, coding, changes.
Software Configuration Management (SCM)
AUDITING INFORMATION TECHNOLOGY USING COMPUTER ASSISTED AUDIT TOOLS AND TECHNIQUES.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
GLAST LAT ProjectMay 25, 2006: Pre-Environmental Test Review LAT Test Verification Process Presentation 4 of 12 GLAST Large Area Telescope Gamma-ray Large.
GLAST LAT Project28 March 2005 LAT System EngineeringLAT Test Planning Meeting GLAST LAT GLAST LAT System Engineering Gamma-ray Large Area Space Telescope.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
Configuration Management
Software Configuration Management
Software Engineering Institute Capability Maturity Model (CMM)
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Introduction to Software Quality Assurance (SQA)
MICROSOFT ACCESS 2007 BTA – Spring What is Access?  Microsoft Access is a database management system…this means that it contains database information.
Software Configuration Management (SCM)
Software System Engineering: A tutorial
1 Configuration Management “The Cookbook Approach”
Packaging & Distribution Project Summary Report Project Name: Brief Project Description: The Packaging and Distribution Project can deal with three different.
Software Process Models
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
GLAST LAT ProjectCDR/CD3 Review May 12-16, 2003 Document: LAT-PR-01967Section XX 1 GLAST Large Area Telescope: LAT System Engineering WBS Dick Horn.
What is a schema ? Schema is a collection of Database Objects. Schema Objects are logical structures created by users to contain, or reference, their data.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
NCSX Systems Engineering Management Plan Peer Review Bob Simmons May 15, 2003.
MTF – Manufacturing and Test Folder Large Scale Deployment of MTF Sonia Mallón Amérigo Elena Manola-Poggioli on behalf of the EDMS Team, TS-CSE.
System Test Planning SYSTTPLAN 1 Location of Test Planning Responsibilities for Test Planning Results of Test Planning Structure of a Test Plan Test Definitions.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
GLAST LAT ProjectFace to Face, 14 April 2004 LAT System Engineering 1 GLAST Large Area Telescope: EGSE and Interface Verification Pat Hascall SLAC System.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Software Engineering Lecture 9: Configuration Management.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Infrastructure Technology and Outsourcing MphasiS Internal SPEED ITO QMS V What’s Changing? September June 2016 Process Definition and Improvement.
16 Copyright © 2004, Oracle. All rights reserved. Testing the Migrated Oracle Database.
DCIT Document Hierarchy End-to-End Procedures and operational system features effecting multiple organizations Systems Integration Document Detailed system.
SACM Vulnerability Assessment Scenario IETF 95 04/05/2016.
CIS 375 Bruce R. Maxim UM-Dearborn
Session 10 Dr. Dan C. Surber, ESEP
REGIONAL USERS GROUP MEETING
Accelerator Readiness Review October 31, 2006
Project Planning: Scope and the Work Breakdown Structure
Configuration Management
How Systems are Developed
Chapter 11: Software Configuration Management
Configuration Management
Packaging & Distribution Project Summary Report
Session 5b Dr. Dan C. Surber, ESEP
Development Projects / Analysis Projects / On-site Service Projects
Software and System Delivery
GLAST Large Area Telescope
Electrical Ground Support Equipment Verification Test Support
Thermal Vacuum Test: Plans and Procedures
LECTURE 34: Database Introduction
Chapter 11: Software Configuration Management
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
PART06 Hands-on Training Identifying Test Scenarios and Test Cases.
First Article Inspection
LECTURE 33: Database Introduction
DOE Review of the LCLS Project October 2006
GLAST Large Area Telescope:
Chapter 4: Software Process Models
Presentation transcript:

LAT System Verification Issues Tom Leisgang 3/19/02

Verification Issues Source Documents LAT Requirements (LIIb) Subsystem Requirements, LIII, LIV Subsystem Test Plans “433” Documents IRD’s MAR Specs Ops 3/19/02

Requirements Verification Study Period Development Period Verification Period Operations Period Technical Aspects of a Commercial Project Cycle Users Needs RR User Product VR Product Requirements Decomposition Definition VR VR Product Verification RR Integration & Verification RR VR Product Specifications Segment Verification RR VR Configuration Item Verification Product Design Documents Configuration Items DR DR RR Design-to Documentation Build-to Documentation 3/19/02 Time & Maturity

Verification Tool Application Performance Assurance T E S & I N G R A O P L Sys. Req’t V E R I F C A T O N M X Sys. Verif. P R O D U C T V A L I N F U N C T I O A L R E Q ‘ Sub- Sys. Req’t Sub- Sys. Verif. Dsgn Req’t Dsgn Verif. Requirements Tracking Tools - DOORS 3/19/02

DOORS Tool Utilization Collect Requirements from “Master” Documents Collect Verifications from Test Plans Link from Requirement to Test Procedure Provide summary outputs Flat File Hardcopy Build Requirements Verification database Track from Requirement to test procedure 3/19/02

DOORS Output Fields Requirements Documents 3/19/02 Field Name Description Req# Numerical sequence designator of requirement Doc Para Paragraph in the specification referencing the identified Requirement Version The version number of the released spec from which the requirements have been obtained Category Performance category (Science Performance, Trigger etc) Topic Specific requirement topic Metric Measurement / verification attribute Constraints Conditions which must be met to validate verification VM Verification Method Req text Full text of the requirement within DOORS from the referenced document. In-links In-Bound requirement links Out-links Out-Bound requirement links Doc# Specification document number from Cyberdocs. SS Subsystem Identification. Lev Specification Hierarchy Level. 3/19/02

Sample Tracker Rqts 3/19/02

DOORS Test Plan Output Fields Test Plans Test Plan Fields Comment Test # Test number referenced from Test Plan Doc # Document # of test plan from Cyberdocs. Doc Para Paragraph number of test in test plan Version The version number of the released test plan Verification Method (VM) Type of test which is being performed Topic Test performance subject Config Configuration of unit under test Prerequisite Conditions or tests which must occur prior to performing this test Assy Level Level of assembly of the device under test Test text Full text of DOORS Object. Test Proc # Reference to test procedure which will perform the test Rqt. Verified In-bound links from originating requirement Test Proc link. Out-bound links Test Procedure Paragraph number 3/19/02

Sample Test Plan Links 3/19/02

Tkr Rqts w/ no test identified 3/19/02

LAT Requirements Summary 3/19/02

Requirements Open Issues No requirements docs for Thermal Number of Released Documents Test Plans Released Requirements Verification Matrices 3/19/02