Define & Compare Flowcharts of Each Method Tom Delong.

Slides:



Advertisements
Similar presentations
Building a Cradle-to-Grave Approach with Your Design Documentation and Data Denise D. Dion, EduQuest, Inc. and Gina To, Breathe Technologies, Inc.
Advertisements

Session No. 4 Implementing the State’s Safety Programme Implementing Service Providers SMS
PRINCIPLES OF A CALIBRATION MANAGEMENT SYSTEM
System Integration Verification and Validation
1 sqa13b IEEE Standard for SQAP u IEEE Std –Standard for Software Quality Assurance Plans –12 pages u IEEE Guide for Software Quality Assurance.
Integrated Messaging and Process Analysis Control Techniques  SEA Inc. Proprietary Data – Please Protect Accordingly 6100 Uptown Blvd., NE, Suite 700,
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Overview of Key Rule Features
Overview Lesson 10,11 - Software Quality Assurance
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
Configuration Management
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Hazard Analysis and Critical Control Points
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Effective Methods for Software and Systems Integration
S/W Project Management
Introduction to Software Quality Assurance (SQA)
Typical Software Documents with an emphasis on writing proposals.
Software Engineering Term Paper
SMS Operation.  Internal safety (SMS) audits are used to ensure that the structure of an SMS is sound.  It is also a formal process to ensure continuous.
Standard WBS Version 1.0 WBS2-3.pptPage 1 Standard Work Breakdown Structure Legend = Decomposes to lower level WBS elements 4.0 Implementation 4.0 Implementation.
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
Management & Development of Complex Projects Course Code - 706
How Systems are Developed The Commercial Life Cycle Model Common form of the Software Life Cycle Used through the commercial, industrial, institutional.
S Q A.
Software Project Management
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Project Life Cycle.
Project Plan. Project Plan Components Project Overview – Description and Strategy Business Case Summary Key Deliverables and Scope Critical Success Factors.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Certificate IV in Project Management Qualification Code BSB41507 Unit.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Best Practices: Job Briefings. Practice Statement Provides a uniform methodology and outlines key components of job briefings.
Over View of CENELC Standards for Signalling Applications
The Goal: To Climb Above The Competition Copyright 2005: I Lead Projects, L.L.C. Course Description Project Process Workplates Project Process Workplates.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Week 4 Certificate IV in Project Management Qualification Code BSB41507.
Revision N° 11ICAO Safety Management Systems (SMS) Course01/01/08 Module N° 9 – SMS operation.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
Configuration Control (Aliases: change control, change management )
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Risk Management in Software Development Projects Roberto Torres Ph.D. 11/6/01.
An Integrated Model-Based Approach to System Safety and Aircraft System Architecture Development Eric Villhauer – Systems Engineer Brian Jenkins – System.
BSBPMG502A Manage Project Scope Manage Project Scope Project Scope Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit.
Camera PDR/CD1 Planning 19 September 2008
Project Quality Management
2012 Spring Simulation Interoperability Workshop
ISA 201 Intermediate Information Systems Acquisition
Data Architecture World Class Operations - Impact Workshop.
DT249/4 Information Systems Engineering Lecture 0
IEEE Std 1074: Standard for Software Lifecycle
Session 5b Dr. Dan C. Surber, ESEP
Software Independent Verification and Validation (IV&V)
Software Life Cycle Risk Management
Engineering Processes
HART Technologies Process Overview
Engineering Processes
PSS verification and validation
Presentation transcript:

Define & Compare Flowcharts of Each Method Tom Delong

3 » ANSI Process » MIL-STD-882 Process » Safety Cases » SAE ARP 4761 Process » Reports Overview of Methods

4 ANSI Process Residual Risk Review & Acceptance Assess Mishap Risk Understanding Risk Options Identify Mitigation Measures Reduce Risk to Acceptable Level Verify Risk Reduction Iterative Risk Reduction Changes Understanding Risk Drivers Risk Assessment Risk Reduction Understanding Hazards Recognize & Document Hazards Tasks Schedule Team Tools Document the System Safety Approach Program Initiation Hazard Identification Risk Acceptance Hazard Tracking Continuous T Maturing Design Life Cycle Monitoring

5 ANSI Process

6 MIL-STD-882 Process Element 1: Document the System Safety Approach Element 2: Identify and Document Hazards Element 3: Assess and Document Risk Element 4: Identify and Document Risk Mitigation Measures Element 5: Reduce Risk Element 6: Verify, Validate, and Document Risk Reduction Element 7: Accept Risk and Document Element 8: Manage Life-Cycle Risk

7 Safety Cases

8 A Simple Goal Structure

9 SAE ARP 4761 Process Determine Impact of S/W Design Define Initial System Safety Design Requirements SIL Testing Ground Testing Flight Testing Determine severity of failure conditions on the A/C or aircrew Determine S/W Levels A/B/C/D/E Allocate S/W functions to appropriate CSCIs CSCs, CSUs Software Requirements and Definition System Safety Engineering IAW ARP 4761 Software Coding And Unit Testing PDRCDR SOFTWARE DESIGN Analyze System Hazards Refine Hazard Mitigations and Identify Derived Safety Reqmts INTEGRATION TESING/ QUALIFICATION TESTING Determine S/W Safety Involvement Determine S/W Level Define S/W Safety Critical Requirements Determine S/W Safety Hazard Mitigations Define S/W Safety Verification Requirements Ensure Compliance with Safety-Critical Requirements Conduct S/W Safety Analyses Per 1228 DO-178B Software Design Assurance SSPP per “882” PSSA SSA Software Safety IAW IEEE STD 1228 Perform Test Safety Analysis & Develop S-C Test Requirements (FMETs/FTs/CWAs) Integration Specs & SRSs TDOCs FHA

10 Safety Cases

11 » Following are key elements of most standards:  Scope  System Description  System Hazards  Safety Requirements  Risk Assessment  Hazard Control / Risk Reduction Measures  Safety Analysis / Test  Safety Management System  Development Process Justification  Conclusions Typical Safety Case Contents

12 Safety Assessment Report Purpose » Historical record » Comprehensive evaluation of risk  60 days prior to test  60 days prior to fielding  New phase of contract or completion » Sent to DTIC & MANPRINT Database » Provides manufacturer’s statement of risk control with justification Contents » Introduction » System description » System operations » System safety engineering » Conclusions (signed statement) » References