23 September 20031 Level C CMU using Reusable ATN Software Example considerations from re-use of the ATNSI RRI.

Slides:



Advertisements
Similar presentations
ATML Readiness For Use Phase II. Phase II Readiness For Use The ATML: Phase II will build on the Core phases, adding additional ATML components and features.
Advertisements

AIRWORTHINESS ASPECTS OF AIRCRAFT LEASING
A I R T R A F F I C O R G A N I Z A T I O N Future Communications Study Technology Assessment Team: Suggested Phase III Activities Presented at ICAO ACP.
Configuration Management
ATN 99 Service Technique de la Navigation Aérienne 1 ATN Activities & Plans ATN in FRANCE FOR SAFETY REASONS MAIN FUTURE DATA/LINK ATSC WILL BE ATN.
Medical Device Software Development
ACI/GM/3011/1.0 ACI's Portable ATN Software Products & Services Technology for next-generation aviation data communication… Presented by Forrest Colliver.
The Future of PETAL Technology
Transition from Q1- 8th to Q1- 9th edition
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
18-19 September 2001ATN2001 (London)1 A Commitment to ATN Implementing Aeronautical Data Link Today Presented by Kevin Wohlers ACI Program Manager.
ATN 2002 London September 2002 Presented by Aloke Roy Authors: Christophe Hamel Tom Judd Ketan Nguyen Bryan Rowe Kevin Wohlers ATN AIRBORNE IMPLEMENTATION.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
1 Software Requirements Specification Lecture 14.
Industrial Avionics Working Group 18/04/07 Defining the Safety Case Architecture IAWG Modular Certification.
Health and Safety Risk Assessment (RA) End presentation Risk Assessment (RA)
CSC230 Software Design (Engineering)
The ATN Avionics Vendors View. ATN2001 Sept 2001; p.2 PETAL-II Avionics.
[ §4 : 1 ] 4. Requirements Processes II Overview 4.1Fundamentals 4.2Elicitation 4.3Specification 4.4Verification 4.5Validation Software Requirements Specification.
Project Execution & Termination Life Cycle Execution Presented by: Basker George.
CSSE 375 Software Construction and Evolution: Configuration Management
Effective Methods for Software and Systems Integration
SQA Architecture Software Quality By: MSMZ.
 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Quality and Innovation in Product and Process Design.
Chapter 2 The process Process, Methods, and Tools
Safety-Critical Systems 6 Certification
IPv6 integration with the ATN Tony Whyman Helios Information Services Ltd.
PART ONE The Product and the Process Chapter 2 The Process  Software Engineering: A Layered Technology a “quality” focus process model methods tools.
ETICS2 All Hands Meeting VEGA GmbH INFSOM-RI Uwe Mueller-Wilm Palermo, Oct ETICS Service Management Framework Business Objectives and “Best.
26-27 September 2000ATN2000 (London)1 Certifiable Software for the ATN Making ATN a reality…now… Presented by Forrest Colliver ACI General Manager.
How To Build a Testing Project 1 Onyx Gabriel Rodriguez.
SOFTWARE REUSABILITY AJAYINDER SINGH CSC What is Software Reuse Software reuse is the process of implementing or updating software systems using.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Safety Management Systems (SMS) Course Module N° 1 – SMS course introduction.
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
COSC 4303 Software Engineering Introduction and Initial Planning of Group Projects Fall 2007.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
Federal Aviation Administration Data Communications Program FAA Prototype & Validation Activities Presented to:Data Comm Implementation Team By:Craig Morris.
© 2015 Wind River. All Rights Reserved. Integrating FACE™ Aligned Componentry Larry Kinnan Principal Technologist, Wind River.
ESW 7 – NENA Standards Roger Hixson - NENA We are mid-way through documentation development for NG9-1-1, with a number of documents published and more.
Software Engineering Lecture 10: System Engineering.
I. UML Tool review (Rhapsody) and II. Requirement and TEST in UML modeling May 31th 2005 KIM, YUN GOO Lab Seminar.
의료용 S/W 기술문서 심사 방법 원 찬 요 유엘 코리아 발표자 소개 년 2 월 한양대 전자공 졸업 ~ : ㈜ 금성사 ( 현 LG 전자 ) 연구원 ~ : ㈜ 메디슨 규격팀 팀장
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
 System Requirement Specification and System Planning.
I&C Lab Seminar Procedure for the Software Requirements Specification for Safety Critical Systems Seo Ryong Koo Korea Advanced Institute Science.
Medical Device Software Development
AMHS (ATS Message Handling System)
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
Presented by Thales Avionics ATN 2003 London, UK September 2003
Chapter ? Quality Assessment
IEEE Std 1074: Standard for Software Lifecycle
Software Requirements
Unit Test: Functions, Procedures, Classes, and Methods as Units
Subject Name: Embedded system Design Subject Code: 10EC74
GLAST Large Area Telescope
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
QGen and TQL-1 Qualification
QGen and TQL Qualification
.NET vs. J2EE Architecture
AIS Manual (Doc 8126) Air Navigation Procedures for AIM Seminar
PPT and video are due no later than March 1, 2019
Rust for Flight Software
Presentation transcript:

23 September Level C CMU using Reusable ATN Software Example considerations from re-use of the ATNSI RRI

23 September Key RSC Considerations for Reuse Planning Definition of Requirements produced by the project High and Low Level (for Level C) Software Requirements How to tie integrator system to these requirements Traceability of requirements/test within RSC Tools Used and Qualified (if done so) Software Lifecycle Documentation (or availability to Certification Authorities) Portable Test Procedures Complete Description of External Interfaces Information for Porting the RSC

23 September Requirements  ATNSI RRI High Level Requirements Software Requirements from ATNSI FRS, 9705 SARPS, ATNSI PICS Performance Requirements  ATNSI RRI Low Level Requirements Software Design Document  Traceability From High to Low Level Requirements From Low Level Requirements to Code From Low Level Requirements to Test Cases A priori RSC system requirements are unknown unless the operating system and host architecture are assumed

23 September Planning For RSC Use CMU Development Plans SDP SCMPSQAPSVPPSAC SDP SCMPSQAPSVPPSAC RSC Development Plans Relationship of CMU to RSC Plans must be shown

23 September Tying an RSC into the CMU CMU System Requirements ATNSI FRS9705 SARPSATNSI PICS CMU ATN STACK Requirements RRI SwRS RRI SDD Other CMU Requirements RRI CodeRRI Low Level Tests CMU SRS

23 September Porting CLNP ULS TPS SNDCF PLP LMSLMS SESSES DSI DLPI LMI RSCs must have well-defined interfaces - validation of all inputs at the boundaries are required depending upon placement of partitions - timing requirements for I/O signals must be enforced by the system RSC tests are ported and rerun on the system System Environment Exchange (SEE) IDRP

23 September ATN Application CLNP CMCPDLC Crew Interface Fault Handler CM ASECPDLC ASE ULS TPS SNDCF PLP LMSLMS SESSES ATN Stack Start- up AVLC SN-SME ACI Developed VME IDRP

23 September Level C ATN Development for CMU Honeywell plans to partition CPDLC + ATN Stack away from the ACARS implementation Honeywell Functional Hazard Assessment not yet complete ED 120 is not yet published, important information in Annex A HMI Requirements which address issues from hazard assessment are to be worked with the customer Not needed until 2007, but beginning work now

23 September Level C Certification - Best Case Partition CLNP CMCPDLC Crew Interface Fault Handler CM ASECPDLC ASE ULS TPS + TP4 SNDCF PLP LMSLMS SESSES ATN Stack Start- up AVLC SN-SME VME Existing ACARS Williamsburg v3 Level C IDRP

23 September Level C Certification - Next Most Likely Partitioning CLNP CMCPDLC Crew Interface Fault Handler CM ASECPDLC ASE ULS TPS + TP4 SNDCF PLP LMSLMS SESSES ATN Stack Start- up AVLC SN-SME VME Existing ACARS Williamsburg v3 Level C IDRP

23 September CMU ATN Status CMU Development in progress VME/AVLC layers formal code complete SN-SME requirements written RRI ABIS Stack being ported to the CMU operating system This will be the 6th Port of the RRI Reviewing HMI and safety requirements CMF function in Mark III (ACARS + ATN) will be ported CMU Mark II EPIC VIA