ARO Workshop Wendy Roll - May 2004 Topic 4: Effects of software certification on the current balance between software/system modeling, analysis and testing.

Slides:



Advertisements
Similar presentations
Jeremy S. Bradbury, James R. Cordy, Juergen Dingel, Michel Wermelinger
Advertisements

Technology Drivers Traditional HPC application drivers – OS noise, resource monitoring and management, memory footprint – Complexity of resources to be.
Topic 1: Emerging paradigms for improvements of software reliability Outbrief summary.
Software Engineering 1. Software development – the grand view 2. Requirements engineering.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Dynamic Service Composition with QoS Assurance Feb , 2009 Jing Dong UTD Farokh Bastani UTD I-Ling Yen UTD.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Software Testing and Quality Assurance: Introduction and Terminology
Equipment Capability Customer DAES Analysis-Experimentation-Simulation 1 DARP Workshop System of Systems Safety Cases Parallel Session 18 th & 19 th April.
1 The Problem o Fluid software cannot be trusted to behave as advertised unknown origin (must be assumed to be malicious) known origin (can be erroneous.
Developed by Reneta Barneva, SUNY Fredonia The Process.
Certified Business Process Professional (CBPP®)
Matthew J Mattia CSC  Cumbersome Code  Consistent/Predictable design (GUEPs #5, CD’s #10)  Display “proper” amount of information  Including.
Chapter : Software Process
Verification technique on SA applications using Incremental Model Checking 컴퓨터학과 신영주.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Integrated Social and Quality of Service Trust Management of Mobile Groups in Ad Hoc Networks Ing-Ray Chen, Jia Guo, Fenye Bao, Jin-Hee Cho Communications.
Test Organization and Management
Chapter 2 The process Process, Methods, and Tools
Assurance techniques for code generators Ewen Denney USRA/RIACS, NASA Ames Bernd Fischer ECS, U Southampton.
RUP Implementation and Testing
An Introduction to Software Architecture
Integrating SSA&I projects into the Future Internet activities Fundamental Limitations of the current.
Computer Science Open Research Questions Adversary models –Define/Formalize adversary models Need to incorporate characteristics of new technologies and.
Lecture 1 Introduction to Software Engineering
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Event Management & ITIL V3
Proof Carrying Code Zhiwei Lin. Outline Proof-Carrying Code The Design and Implementation of a Certifying Compiler A Proof – Carrying Code Architecture.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Johann Schumann and Pramod Gupta NASA Ames Research Center Bayesian Verification & Validation tools.
Verification and Validation in the Context of Domain-Specific Modelling Janne Merilinna.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Service Oriented Architectures Presentation By: Clifton Sweeney November 3 rd 2008.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
J1879 Robustness Validation Hand Book A Joint SAE, ZVEI, JSAE, AEC Automotive Electronics Robustness Validation Plan The current qualification and verification.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
Develop a Safety Assurance approach for Complex Systems (Problem Definition) Supervisors: Tim Kelly, Rob Alexander Chris Leong HISE Group Giving a Presentation.
Investigating Survivability Strategies for Ultra-Large Scale (ULS) Systems Vanderbilt University Nashville, Tennessee Institute for Software Integrated.
Safety Critical Systems 5 Testing T Safety Critical Systems.
Systems Analysis and Design in a Changing World, Fourth Edition
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Notes by Ben Boerkoel, Kent ISD, based on a training by Beth Steenwyk.
Developed by Reneta Barneva, SUNY Fredonia The Process.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
High Confidence Software and Systems HCMDSS Workshop Brad Martin June 2, 2005.
From Information Assurance to Trusted Systems – A Strategic Shift Patricia A. Muoio Chief, NSA Trusted Systems Research (formerly known as National Information.
An EDI Testing Strategy Rosemary B. Abell Director, National HIPAA Practice Keane, Inc. HIPAA Summit V October 30 – November 1, 2002.
Hosted by: Institute for Software Integrated Systems (ISIS) Vanderbilt University Software Reliability for FCS Discussion Format May 18-19, 2004 ARO Workshop.
Computer Science and Engineering 1 Mobile Computing and Security.
ARO Workshop Wendy Roll - May 2004 Topic 4: Effects of software certification on the current balance between software/system modeling, analysis and testing.
Chapter 19: Building Systems with Assurance Dr. Wayne Summers Department of Computer Science Columbus State University
Outsourcing, subcontracting and COTS Tor Stålhane.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Winter 2007SEG2101 Chapter 121 Chapter 12 Verification and Validation.
Center for Devices and Radiological Health U. S. Department of Health and Human Services Paul L. Jones Senior Systems / Software Engineer Division of Electronics.
UNIT 7 MONITORING AND EVALUATION  Monitoring and evaluation is the process of examining progress against institution’s goals or plan.  The term SM &
TTCN-3 Testing and Test Control Notation Version 3.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
Basic Concepts of Software Architecture. What is Software Architecture? Definition: – A software system’s architecture is the set of principal design.
Building PetaScale Applications and Tools on the TeraGrid Workshop December 11-12, 2007 Scott Lathrop and Sergiu Sanielevici.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
Air Force Institute of Technology
Role of the Systems Analyst
Verification and Validation Unit Testing
Dr. Molly Secor-Turner, PhD, RN, FSAHM Associate Professor
Presentation transcript:

ARO Workshop Wendy Roll - May 2004 Topic 4: Effects of software certification on the current balance between software/system modeling, analysis and testing

ARO Workshop Wendy Roll - May Context  Traditional approach for certified software development has been to implement the system and then perform rigorous testing and analysis (post-creation) – Safety critical systems are designed to reduce this testing/analysis burden  Newer model-based approaches are intended to reduce errors and support analysis (pre-creation), but…  Certification processes require the same degree of confidence in all evidence used therein – E.g., when less direct methods are to be used for certification:  Any models, modeling tools, analysis tools, etc, must be certified to the same level as the underlying system, and  Fidelity of any system representations must be similarly certified for all applicable aspects (e.g. functionality, timing, concurrency)  Area for future research – For dynamic/distributed/large-scale needs of FCS, certification will have to be reevaluated  Research into different SoS certification definition and implementation  Research into the development of software that can meet the newly defined criteria Certify?

ARO Workshop Wendy Roll - May Question 1  …What techniques are available which compellingly reduce the aggregate certification effort?  Possible areas for future research – Automated test  Generation – Including status and health monitoring collection to create inputs for test  Running - with limited configurations – COTS/Reuse  Focus on barriers to trust/assurance efforts from commercial marketplace (e.g. new business models, incentives) – Languages/Patterns that only allow safe design and/or complete analysis (E.g. SCADE/Luster)

ARO Workshop Wendy Roll - May Question 2  …What unique approaches, if any, can more efficiently certify tools and representations than the system itself?  Areas for future research – Using extensive modeling and simulation to address safety  What is the “language” for this model?  How can this be made cost efficient?  How does the model become trusted? – Certification of a process along with tool use

ARO Workshop Wendy Roll - May Question 3  …What aspects are most amenable to these approaches and techniques? – Can techniques address unique challenges resulting from mobile ad hoc networking or other system of system dynamics?  Areas for future research – How do we handle certified software that must have a dependency on an unreliable assets (network, nodes, other software components)?  New strategies to address the issue of “communication towers” being mobile, mortal soldiers - Proactive approach - Using alternate situation monitoring sources to determine failure - using the network to your advantage – Limit dynamism, but support some dynamism  Set of static choices  Assure no harm is done  Certify adaptation mechanisms – Association of certification/reliability needs with acceptable implementations  Includes characterizing those implementations

ARO Workshop Wendy Roll - May Question 4  …Are these approaches and techniques scalable to the size of FCS?  Areas of future research (might be in the context of other research areas listed) – Amount of software – Certification of individual systems does not guarantee safety of SoS – Certification of complete set of dynamic behaviors – How will solutions fit into existing development models (waterfall, spiral…) – Current certification process only addresses a subset of these issues