Integrated Messaging and Process Analysis Control Techniques  SEA Inc. Proprietary Data – Please Protect Accordingly 6100 Uptown Blvd., NE, Suite 700,

Slides:



Advertisements
Similar presentations
Steven F. Mattern Science and Engineering Associates, Inc. (505)
Advertisements

Integra Consult A/S Safety Assessment. Integra Consult A/S SAFETY ASSESSMENT Objective Objective –Demonstrate that an acceptable level of safety will.
Testing and Quality Assurance
S Y S T E M S E N G I N E E R I N G.
Software Quality Assurance Plan
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Define & Compare Flowcharts of Each Method Tom Delong.
1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
Integration of Quality Into Accident Investigation Processes ASQ Columbia Basin Section 614 John Cornelison January 2008.
Overview Lesson 10,11 - Software Quality Assurance
Pratt & Whitney National Workshop on Aviation Software Systems for the Second Century of Flight: Design for Certifiably Dependable Systems October 5-6,
1 SYSTEM and MODULE DESIGN Elements and Definitions.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Hazards Analysis & Risks Assessment By Sebastien A. Daleyden Vincent M. Goussen.
1 CSc Senior Project Software Testing. 2 Preface “The amount of required study of testing techniques is trivial – a few hours over the course of.
Systems Engineering Approach to MPS Risk Management Kelly Mahoney Presented at the Workshop for Machine Protection in Linear Accelerators.
Other Planning Processes: Final Planning Touches
What is Business Analysis Planning & Monitoring?
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Software Project Management
Software Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
Introduction to Software Quality Assurance (SQA)
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Copyright 2005 Welcome to The Great Lakes TL 9000 SIG TL 9000 Requirements Release 3.0 to Release 4.0 Differences Bob Clancy Vice President, BIZPHYX,
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.
Software Project Management Introduction to Project Management.
An EDI Testing Strategy Rosemary B. Abell Director, National HIPAA Practice Keane, Inc. HIPAA Summit IV April 24-26, 2002.
Software Quality Assurance Activities
Risk Management - the process of identifying and controlling hazards to protect the force.  It’s five steps represent a logical thought process from.
Michael Dermody September 2010  Capability Maturity Model Integration ◦ Is a Trademark owned by the Software Engineering Institute (SEI) of Carnegie.
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
Chapter 9 Testing the System Shari L. Pfleeger Joann M. Atlee
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Lach1MAPLD 2005/241 Accessible Formal Verification for Safety-Critical FPGA Design John Lach, Scott Bingham, Carl Elks, Travis Lenhart Charles L. Brown.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
SOFTWARE PROJECT MANAGEMENT
Software Safety Case Why, what and how… Jon Arvid Børretzen.
Over View of CENELC Standards for Signalling Applications
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
Software Engineering Lecture # 1.
Lach1MAPLD 2005/241-W Accessible Formal Verification for Safety-Critical FPGA Design BOF-W Presentation John Lach, Scott Bingham, Carl Elks, Travis Lenhart.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Alex Ezrakhovich Process Approach for an Integrated Management System Change driven.
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
Failure Modes, Effects and Criticality Analysis
Project Scope Management Pantelis Ipsilandis- Dimitrios Tselios.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
1 ME Spring 2015 Systems Engineering, Part II Session 8 5 February 2015 Mr. Larry Hopp, CPL © Copyright 2013.
An Integrated Model-Based Approach to System Safety and Aircraft System Architecture Development Eric Villhauer – Systems Engineer Brian Jenkins – System.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Software Development and Safety Critical Decisions
OH&S Plant Obligations make
Software and Systems Integration
PSS verification and validation
Hazards Analysis & Risks Assessment
A New Concept for Laboratory Quality Management Systems
Review and comparison of the modeling approaches and risk analysis methods for complex ship system. Author: Sunil Basnet.
Presentation transcript:

Integrated Messaging and Process Analysis Control Techniques  SEA Inc. Proprietary Data – Please Protect Accordingly 6100 Uptown Blvd., NE, Suite 700, Albuquerque, New Mexico (505) Page One IMPACT ™ Toolset Functional and Graphical Interface Model Bringing CONTEXT to and With Hardware, Software, and the Human Element Systems Engineering Safety Engineering Software Engineering Specialty Engineering Software Test Software Design Software Safety System Safety Systems Integration Hazard Identification Hazard Causal Factors Hazard Mitigation Fault Tree Analysis Residual Risk Safety Reporting Functional Definition Requirements Allocation Control Requirements System Modeling Interface Analysis System Integration Human Factors Training Reliability/Availability and Maintainability Integrated Logistics Safety-Critical SW SW Causal Factors SW Safety Requirements Hazard Mitigation Interface w/Hardware Interface w/Human Requirements Allocation Implementation Model Fault Detection Fault Handling SW & HW Integration User Interface Analysis Test Rqmt Allocation Test Case Generation Test Acceptance Criteria Test Readiness Report INFLUENCING DESIGN PROVING DESIGN Science & Engineering Associates, Inc.

SEA Inc. Proprietary Data – Please Protect Accordingly PROCESS-BASED TOOL SET PROCESS-BASED TOOL SET ANALYSES PLACES SOFTWARE, HARDWARE AND PERSONNEL ACTION WITHIN THE CONTEXT OF MAJOR SYSTEM FUNCTIONS ANALYSES PLACES SOFTWARE, HARDWARE AND PERSONNEL ACTION WITHIN THE CONTEXT OF MAJOR SYSTEM FUNCTIONS IMPACT ™ Allows Hardware & Software Designers to See the “Big Picture” Reduces the Amount of Reverse Engineering to “Make It Work” Testing is More a “Proving Process” Than a “Fixing Process” Timelines & Milestones Are Met With Fewer Surprises Customers Have More Confidence in the Contractor as it offers Tangible Evidence of Progress Shows “Actual Design” as opposed to “Perceived Design” Graphically Integrating Hardware, Software And Human Interaction in the Performance of System Functions 6100 Uptown Blvd., NE, Suite 700, Albuquerque, New Mexico (505) Integrated Messaging and Process Analysis Control Techniques  Page Two CONTACT SEA, Inc. Albuquerque Division Steve Mattern or Greg Elcock (505) Science & Engineering Associates, Inc.

Integrated Messaging and Process Analysis Control Techniques  SEA Inc. Proprietary Data – Please Protect Accordingly 6100 Uptown Blvd., NE, Suite 700, Albuquerque, New Mexico (505) Page Three IMPACT Software Safety Process The integration of the “Software Assurance” of RTCA/DO 178B and “Software Safety” of Mil-Std 882 ensures a total integration of system safety engineering, system engineering and software development methodologies for a safer system. The process as defined below produces the necessary output products to support system certification and safety requirements criteria. System Functional Analysis Analysis is accomplished to determine system functionality and the ramifications of “loss of functionality”. This activity is accomplished in conjunction with systems engineering and can be used to supplement interface and integration activities. The primary purpose is to identify the Safety-Critical Functions (SCF) of the system and categorize them in accordance with DO-178B safety level criteria. The SCF’s is then tied to the software functionality to determine which CSCI’s or CSU’s will be determined to have significant safety impact. This allows functionality to be allocated to the appropriate safety levels within the software design architecture. System Hazards Analysis The Functional Hazard Analysis is a natural springboard into the safety activities required by Mil-Std 882. The most important step in the process is the in-depth analysis to identify failure modes or pathways to the identified hazards of the system. This analysis includes the identification of each hardware, software, and human interaction on the failure pathways. Identification of Software Safety Requirements The in-depth hazard causal analysis defines the interaction of hardware, software, and the human as contributors to potential mishaps. The results of this analysis is a more refined list of hazard mitigation requirements for hardware and software design, safety and redundant systems, fault detection, tolerance, and recovery, and procedures and training. The safety engineering team then ensures that the domain experts (designers) successfully implement the defined hazard mitigation requirements. This is accomplished through a variety of analysis, inspection, and test activities. IMPACT ™ Science & Engineering Associates, Inc.