Model-Based Testing of Spacecraft Flight Software
|
|
|
- Myron Neal
- 9 years ago
- Views:
Transcription
1 Model-Based Testing of Spacecraft Flight Software Maria Hernek Virtual 12/09/2013
2 Objective/Outline Objective: To present the result and achievements of ESA study Model Based Testing of flight SW and discuss strengths and weaknesses of the method Outline: ESA ISVV process short intro of applicable parts Background of ESA study Method and approach Test object Implementation Conclusion Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 2
3 Independent Software Verification & Validation (ISVV) by ESA 1. ISVV is required for Mission and Safety Critical software, (ECSS-E-40/ECSS-Q-80) 2. ISVV tasks are additional and complementary to the nominal SW supplier s verification and validations tasks 3. ISVV tasks cover verification and validation of software requirements, design, code and tests (typically starting at SW-SRR and finishing before the SW-QR) 4. ISVV supplier is required to be an organization independent of the software supplier as well as the prime/system integrator (full technical, managerial, and financial independence) 5. Most ESA projects implement the ISVV process as an industrial contract placed by the Prime contractor Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 3
4 ESA ISVV Process overview 6 activities/stages: Management (MAN), Verification (IVE) and Validation (IVA) Activities are composed of TASKS, and these are further split into SUBTASKS 1. Management (MAN.PM and MAN.VV) is concerned with issues such as ISVV objectives and scope, planning, roles, responsibilities, budget, communication, competence, confidentiality, schedule and ISVV level definition (to limit the scope of ISVV) 2. Technical Specification Analysis (IVE.TA) is verification of the software requirements 3. Design Analysis (IVE.DA) is verification of the SW Architectural Design and the Software Detailed Design 4. Code Analysis (IVE.CA) is verification of the SW source code 5. Validation (IVA) is testing of the SW to demonstrate that the implementation meets the technical specification MAN. Management MAN.PM.ISVV Process Management MAN.VV.ISVV level definition IVE. Independent Verification IVE.TA.Technical Specification Analysis IVE.DA.Design Analysis IVE.CA.Code Analysis IVA. Independent Validation IVA.Validation Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 4
5 ESA ISVV Process overview Example of a Task/Subtask description Activity: Technical Specification Analysis Task: SW Requirements Verification Subtasks: T1.S1, T1.S2 T1.S11 Start/End Events Inputs/Outputs Methods are identified for each subtask Some numbers: IVE.TA 1 task 11 subtasks IVE.DA 3 tasks 15/12/5 subtasks IVE.CA 3 tasks 10/5/3 subtasks IVA 3 tasks 3/3/3 subtasks Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 5
6 ESA ISVV Process overview IVE: Technical Specification Analysis TA.T1: Software Requirements Verification Subtasks: To verify Software Requirements external consistency with the system requirements Interface Requirements external consistency with the system requirements software requirements correctness consistent documentation of the software requirements software requirements completeness dependability and safety requirements readability of the software requirements timing and sizing budgets of the software requirements Identify test areas and test cases for Independent Validation that software requirements are testable software requirements conformance with applicable standards System Requirements Requirements allocated to Software (SRR) allocated to SW Requirements Specification (PDR) SW - SW-HW Interface Requirements Requirements (SRR) Interfaces Control Document (PDR) Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 6
7 ESA ISVV Process overview IVA: Independent Validation IVA: Independent Validation Subtasks: Identification of Test Cases Construction of Test procedures Execution of Test Procedures Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 7
8 Background o o Software Verification & Validation important phase Software Validation phase critical path o Software Validation labor intensive o Software versioning impact on Validation regression need Test lib Requirements o Source of problem Validation? and/or Specification? Test log SimOps TestScript Java, php python o o More automation possible? Specification incomplete, incorrect SCOS TC TM SVF SVF-Software Validation Facility SCOS - SpaceCraft Operations System SimOps Simulator Operations Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 8
9 Method and Approach o Sequence-Based Specification (SBS) combined with o Statistical-Based Testing (SBT) Sequence-Based Specification develop Black Box specification depends solely on external stimuli and responses Statistical-Based Testing Test values randomly generated using a probabilistic profile System boundary External Stimuli Black Box spec Responses Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 9
10 Approach Test lib Requirements Test log SimOps TestScript Java, php python TC SCOS SVF TM Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 10
11 Test Object Spacecraft Flight Software Earth observation mission Main functions: Thermal control Power control and distribution unit management Attitude and Orbit Control System and mode management Telemetry memory management Mass memory and formatting unit management Functions suited for SBS Modeled State machine based Complex combination of input sequences Possible to identify stimuli, predicate and responses On-Board time management Remote interface unit management Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 11 Predicate represent a stimuli which can be expressed in form of regular expression rule
12 Test Object Requirements metrics 500 FSW requirements 350 Irrelevant Relevant but too simple for SBS Relevant and worth doing 225 Relevant but only for stimuli response Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 12 Relevant and selected
13 Sequence-Based Specification, steps Model system s state transition and responses according to all possible sequences of system inputs Requirements Tool support for all steps Sequence-based Specification Mealy Machine Annotated Mealy Machine Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 13 Test Model
14 Sequence-Based Specification, steps Requirements Sequence-based Specification Mealy Machine Identify boundaries Define interfaces Identify stimuli Identify responses Enumerate sequences of stimuli Identify canonical sequences Define state variables Annotated Mealy Machine Test Model Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 14
15 Statistical Based Testing, steps Test Model Tool support: JUMBL CONVAC-TC Abstract Test Cases Generate abstract test cases covering transitions of Mealy Machine Mapping abstract stimuli to test scripts Concrete libraries Test Cases What parameter and values of stimuli? What parameter and values of predicate? Where to read responses and expected values. Code Test Oracle Test Results Compare results with Oracle Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 15
16 Test generation Test case criteria: cover every arc of Mealy Machine (every state is covered) weighted arcs used reflecting frequency, importance, risk of the likelihood of arc to happen Patch coverage, typically infinite number of paths but basis path coverage can be achieved Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 16
17 Tool support 1. SBS Super a. Protoseq with some additions, dedicated build: Extended predicate support 2. JUMBL More responses supported Support dynamic sequence adjustment Forward traceability Interface smoothly with JUMBL Protoseq considered but not used a. By Software Quality Research Laboratory, SQRL 1 b. Generate abstract tests, a path in a usage model 3. CONVAC TC a. Custom made tool b. Converts abstracts test cases to executable Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 17 1 University of Tennessee
18 Implementation, characteristics Function Thermal cntrl Number of stimuli Max length of seq Number of predicates Response type Simple 19 Power cntrl Simple 4 AOCS mode mng Simple 21 MMM Complex 9 MMFU mng Complex 5 OBT mng Complex 6 Num of states Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 18
19 SBS, Effectiveness Function hrs spent SBS models hrs spent refining model Thermal cntrl 18 (60) 16 Power cntrl 18 (60) 28 AOCS mode mng 15 (51) 16 MMM 25 (86) 35 OBT 12 (42) 35 MMFU mng 8 10 Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 19 Explain stimuli, predicate and responses, revising model
20 Discrepancies found applying SBS Problem Major Minor Comment Inconsistency Completeness Testability Understandability Sum Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 20
21 Conclusions + Method will discover issues related to completeness and consistency of requirements + Testability is addressed: identify stimuli and means to generate it + Traceability forward and backward is supported - Data management requirement are difficult to address - Implementation details are not addressed (black box) In the current version time dependent functions are not modeled Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 21
22 Thanks for your attention! For more information, please contact: Maria Hernek, European Space Agency Model-Based Testing Maria Hernek Virtual 12/09/2013 TEC-SWS Slide 22
UIDE FOR NDEPENDENT OFTWARE ERIFICATION ALIDATION
UIDE FOR NDEPENDENT OFTWARE ERIFICATION ALIDATION prepared by/préparé par ESA property. reference/réference ESA ISVV Guide issue/édition 2 revision/révision 0 date of issue/date d édition December 29,
SCADE Suite in Space Applications
SCADE Suite in Space Applications at EADS David Lesens 09/10/2008 Overview Introduction Historical use of SCADE at EADS Astrium ST Why using SCADE? The Automatic Transfer Vehicle (ATV) M51 and Vega R&T
System Engineering Data Repository
System Data Repository 09:00 data in the MBSE life-cycle 09:20 EGS-CC in the system context 09:40 Conceptual Modelling and ECSS 10:00 ecascade 10:20 A snapshot of systems engineering data management in
An Introduction to the ECSS Software Standards
An Introduction to the ECSS Software Standards Abstract This introduces the background, context, and rationale for the creation of the ECSS standards system presented in this course. Addresses the concept
DANSE Software Quality Assurance
DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee Department of Computer Science DANSE Objectives Extensible open source framework Modular interoperability
LISA Pathfinder SUMMARY
Page 2 of 36 SUMMARY This document defines the Independent Software Verification and Validation requirements for the Implementation Phase of the LISA Pathfinder project. Page 3 of 36 TABLE OF CONTENTS
FSW QA Testing Levels Definitions
FSW QA Testing Levels Definitions 1. Overview This document is used to help determine the amount and quality of testing (or its scope) that is planned for or has been performed on a project. This analysis
USE OF PYTHON AS A SATELLITE OPERATIONS AND TESTING AUTOMATION LANGUAGE
USE OF PYTHON AS A SATELLITE OPERATIONS AND TESTING AUTOMATION LANGUAGE Gonzalo Garcia VP of Operations, USA Property of GMV All rights reserved INTRODUCTION Property of GMV All rights reserved INTRODUCTION
Operability in the SAVOIR Context
SAVOIR Avionics Reference Architecture Operability in the SAVOIR Context Avionics, Data Control & Software Systems Workshop 23/10/2012 Implementing Operability The CCN Standoff & the SOIRD SOIRD & Standarisation
Automated Model Based Testing for an Web Applications
Automated Model Based Testing for an Web Applications Agasarpa Mounica, Lokanadham Naidu Vadlamudi Abstract- As the development of web applications plays a major role in our day-to-day life. Modeling the
An Increase in Software Testing Robustness: Enhancing the Software Development Standard for Space Systems
An Increase in Software Robustness: Enhancing the Software Development Standard for Space Systems Karen Owens and Suellen Eslinger Software Engineering Subdivision 15 th Ground System Architectures Workshop
Space product assurance
Space product assurance Software dependability and safety ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Handbook is one document of the series of
Mission Operation Ground. Assurance @ ESA. Mario Merri GSAW, Los Angeles, USA 2 Mar 2011 ESA UNCLASSIFIED
Mission Operation Ground Software Systems Product Assurance @ ESA Mario Merri GSAW, Los Angeles, USA 2 Mar 2011 The European Cooperation for Space Standardisation (ECSS) Established: in 1993 Goal: coherent,
The Project Management Plan will be used to guide, communicate and coordinate project efforts.
F.1 General Implementation Contractor Deliverables include critical system planning and development components. Sufficient deliverables have been identified at key steps in the project to guide the project
Database Administration for Spacecraft Operations The Integral Experience
r bulletin 103 august 2000 Database Administration for Spacecraft Operations The Integral Experience J. Houser & M Pecchioli Mission Operations Department, ESA Directorate of Technical and Operational
ECSS-E-ST-40C 6 March 2009. Space engineering. Software. ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands
ECSS-E-ST-40C Space engineering Software ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS Standards intended to
Introduction to Automated Testing
Introduction to Automated Testing What is Software testing? Examination of a software unit, several integrated software units or an entire software package by running it. execution based on test cases
Space engineering. System engineering. ECSS-E-10 C Draft 1
Space engineering System engineering This ECSS document is a draft standard distributed for Public Review. It is therefore subject to change without any notice and may not be referred to as an ECSS Standard
RAMS Software Techniques in European Space Projects
RAMS Software Techniques in European Space Projects An Industrial View J.M. Carranza COMPASS Workshop - York, 29/03/09 Contents Context and organisation of ESA projects Evolution of RAMS Techniques in
Introduction of ISO/DIS 26262 (ISO 26262) Parts of ISO 26262 ASIL Levels Part 6 : Product Development Software Level
ISO 26262 the Emerging Automotive Safety Standard Agenda Introduction of ISO/DIS 26262 (ISO 26262) Parts of ISO 26262 ASIL Levels Part 4 : Product Development System Level Part 6 : Product Development
CSTE Mock Test - Part I - Questions Along with Answers
Note: This material is for Evaluators reference only. Caters to answers of CSTE Mock Test - Part I paper. 1. A branch is (Ans: d) a. An unconditional transfer of control from any statement to any other
Assurance Cases and Test Design Analysis
Assurance Cases and Test Design Analysis Flight Software Workshop November 7-9, 2012 Khalid Lateef Ph.D. Outline Scope Test Design challenges Assurance cases Example of test design IV&V for an automobile
Model-Based Quality Assurance of The SMB2 Protocol Documentation
Model-Based Quality Assurance of The SMB2 Protocol Documentation Wolfgang Grieskamp Architect, Protocol Engineering Team, Microsoft Corporation Microsoft Part of the company s interoperability initiative
Establishing an Environment for Continuous Integration and Test of Flight Software
Establishing an Environment for Continuous Integration and Test of Flight Software Robert Klar, Christopher Mangels, and Randal Harmon Southwest Research Institute Integration and Test Integration and
Software Test Plan (STP) Template
(STP) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project. This
ESA s Data Management System for the Russian Segment of the International Space Station
iss data management system ESA s Data Management System for the Russian Segment of the International Space Station J. Graf, C. Reimers & A. Errington ESA Directorate of Manned Spaceflight and Microgravity,
SAFE SOFTWARE FOR SPACE APPLICATIONS: BUILDING ON THE DO-178 EXPERIENCE. Cheryl A. Dorsey Digital Flight / Solutions cadorsey@df-solutions.
SAFE SOFTWARE FOR SPACE APPLICATIONS: BUILDING ON THE DO-178 EXPERIENCE Cheryl A. Dorsey Digital Flight / Solutions [email protected] DIGITAL FLIGHT / SOLUTIONS Presentation Outline DO-178 Overview
Software Verification for Space Applications Part 2. Autonomous Systems. G. Brat USRA/RIACS
Software Verification for Space Applications Part 2. Autonomous Systems G. Brat USRA/RIACS Main Objectives Implement a sustained and affordable human and robotic program to explore the solar system and
NODIS Library Program Formulation(7000s) Search
NODIS Library Program Formulation(7000s) Search NASA Procedural Requirements This Document Is Uncontrolled When Printed. Check the NASA Online Directives Information System (NODIS) Library to verify that
Metrics in Software Test Planning and Test Design Processes
Master Thesis Software Engineering Thesis no: MSE-2007:02 January 2007 Metrics in Software Test Planning and Test Design Processes Wasif Afzal School of Engineering Blekinge Institute of Technology Box
SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
USE OF SCILAB FOR SPACE MISSION ANALYSIS AND FLIGHT DYNAMICS ACTIVITIES
USE OF SCILAB FOR SPACE MISSION ANALYSIS AND FLIGHT DYNAMICS ACTIVITIES Thierry Martin CNES Scilabtec 09 Use of Scilab for space mission analysis Page 1 Use of Scilab in CNES Scilab is now widely used
4 Applying DO-178B for safe airborne software
Applying DO-178B for safe airborne software 81 4 Applying DO-178B for safe airborne software Published as E. Kesseler, E. van de Sluis, Reliability, maintainability and safety applied to a real world avionics
Life Cycle Quality Gates
1 Operations Release Life Cycle Quality Gates 8 Post Implement Validation 6 Implement Build Product Test Quality Assurance 2 Versions 3 4 5 Patches 7 Design 1 10 9 Requirements Requirements Sources: Executive
Space Project Management
EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space Project Management Project Phasing and Planning Secretariat ESA ESTEC Requirements & Standards Division Noordwijk, The Netherlands Published by: Price:
Example Software Development Process.
Example Software Development Process. The example software development process is shown in Figure A. The boxes represent the software development process kernels. The Software Unit Testing, Software Component
ATV Data Link Simulator: A Development based on a CCSDS Layers Framework
SpaceOps 2010 ConferenceDelivering on the DreamHosted by NASA Mars 25-30 April 2010, Huntsville, Alabama AIAA 2010-2089 ATV Data Link Simulator: A Development based on a CCSDS
Thanks to SECNOLOGY s wide range and easy to use technology, it doesn t take long for clients to benefit from the vast range of functionality.
The Big Data Mining Company BETTER VISILITY FOR BETTER CONTROL AND BETTER MANAGEMENT 100 Examples on customer use cases Thanks to SECNOLOGY s wide range and easy to use technology, it doesn t take long
Certification of a Scade 6 compiler
Certification of a Scade 6 compiler F-X Fornari Esterel Technologies 1 Introduction Topic : What does mean developping a certified software? In particular, using embedded sofware development rules! What
How To Write Software
1 Medical Device Software - Software Life Cycle Processes IEC 62304 2 Credits John F. Murray Software Compliance Expert U.S. Food and Drug Administration Marcie R. Williams Medical Device Fellow Ph.D.
VDM vs. Programming Language Extensions or their Integration
VDM vs. Programming Language Extensions or their Integration Alexander A. Koptelov and Alexander K. Petrenko Institute for System Programming of Russian Academy of Sciences (ISPRAS), B. Communisticheskaya,
AUTOMATED TESTING and SPI. Brian Lynch
AUTOMATED TESTING and SPI Brian Lynch 1 Introduction The following document explains the purpose and benefits for having an Automation Test Team, the strategy/approach taken by an Automation Test Team
Formal Software Testing. Terri Grenda, CSTE IV&V Testing Solutions, LLC www.ivvts.com
Formal Software Testing Terri Grenda, CSTE IV&V Testing Solutions, LLC www.ivvts.com Scope of Testing Find defects early Remove defects prior to production Identify Risks Unbiased opinion When Should Testing
SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT
SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT Mar 31, 2014 Japan Aerospace Exploration Agency This is an English translation of JERG-2-610. Whenever there is anything ambiguous in this document, the original
CS 451 Software Engineering Winter 2009
CS 451 Software Engineering Winter 2009 Yuanfang Cai Room 104, University Crossings 215.895.0298 [email protected] 1 Testing Process Testing Testing only reveals the presence of defects Does not identify
Fundamentals of Measurements
Objective Software Project Measurements Slide 1 Fundamentals of Measurements Educational Objective: To review the fundamentals of software measurement, to illustrate that measurement plays a central role
ENEA: THE PROVEN LEADER IN SAFETY CRITICAL AVIONICS SYSTEMS
ENEA: THE PROVEN LEADER IN SAFETY CRITICAL AVIONICS SYSTEMS [email protected]. www.enea.com For over 40 years, we have been one of the fastest growing avionics consulting companies in the world. Today our
Appendix F Wyle Laboratories Test Plan and Test Report
Appendix F Wyle Laboratories Test Plan and Test Report Revisions REVISION Original REPORT NO. Test Plan DATE April 14, 2011 REV DATE PAGE OR PARAGRAPH AFFECTED DESCRIPTION OF CHANGES --- 4-14-11 Entire
Model-based Testing: Next Generation Functional Software Testing
Model-based Testing: Next Generation Functional Software Testing By Dr. Bruno Legeard Model-based testing (MBT) is an increasingly widely-used technique for automating the generation and execution of tests.
Model-Based Testing of Web Applications using NModel
Model-Based Testing of Web Applications using NModel Juhan Ernits 1, Rivo Roo 2, Jonathan Jacky 3, and Margus Veanes 4 1 University of Birmingham, UK [email protected] 2 Reach-U Ltd,Tartu, Estonia
How CMMI contributes to Software Testing
How CMMI contributes to Software Testing Dr. Uwe Hehn method park Software AG [email protected] Contents 1. Motivation for S/W Quality Models 2. Why Testers should have some knowledge of Quality Models
Application Modelling
Seminar on Model-Based Testing as a Service Application Modelling Author: Antti Heimola Date: Dec-4, 2008 Time: Thu Dec- 4, 2008 Location: Tampere: TUT/Department of Software Systems, Tietotalo, class
Standard Glossary of Terms Used in Software Testing. Version 3.01
Standard Glossary of Terms Used in Software Testing Version 3.01 Terms Used in the Expert Level Test Automation - Engineer Syllabus International Software Testing Qualifications Board Copyright International
4. Test Design Techniques
4. Test Design Techniques Hans Schaefer [email protected] http://www.softwaretesting.no/ 2006-2010 Hans Schaefer Slide 1 Contents 1. How to find test conditions and design test cases 2. Overview of
Goddard Procedures and Guidelines
Goddard Procedures and Guidelines DIRECTIVE NO. APPROVED BY Signature: Original signed by NAME: A. V. Diaz TITLE: Director Responsible Office: Title: Code 300 / Office of Systems Safety and Mission Assurance,
End User Guide The guide for email/ftp account owner
End User Guide The guide for email/ftp account owner ServerDirector Version 3.7 Table Of Contents Introduction...1 Logging In...1 Logging Out...3 Installing SSL License...3 System Requirements...4 Navigating...4
Dependable (Safe/Reliable) Systems. ARO Reliability Workshop Software Intensive Systems
Dependable (Safe/Reliable) Systems Composing, Analyzing and Validating s to Assess / Develop / Validate Methods and Supporting Tools for the Creation of Dependable Systems ARO Reliability Workshop Intensive
8. Master Test Plan (MTP)
8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across
Software Engineering. Software Testing. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering Software Testing Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To discuss the distinctions between validation testing and defect t testing To describe the
Software testing. Objectives
Software testing cmsc435-1 Objectives To discuss the distinctions between validation testing and defect testing To describe the principles of system and component testing To describe strategies for generating
1.2 Tools support for management of testing & tests
1.2 Tools support for management of testing & tests Tools: Requirements management tools store requirements check for consistency and undefined (missing) requirements allow prioritization enable individual
Model Based Software Development for DDG 1000 Advanced Gun System
BAE Systems Land & Armaments Model Based Software Development for DDG 1000 Advanced Gun System Dirk Jungquist BAE Systems Land & Armaments 2012 Distribution Statement A: Approved for public release; distribution
Belatrix Software Factory Sample Automated Load/Stress Testing Success Cases
Belatrix Software Factory Sample Automated Load/Stress Testing Success Cases Introduction. In this white paper we will discuss different cases where the Belatrix Quality Assurance team has implemented
TDRS / MUST. and. what it might do for you
TDRS / MUST and what it might do for you Dr. Marcus G. F. Kirsch XMM-Newton Deputy Spacecraft Operations Manager with Inputs from José-Antonio Martínez nez-heras, Black Hat S.L., Spain European Space Agency
Chapter 17 Software Testing Strategies Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For
Automated Software Testing Economics: A White Paper
Automated Software Testing Economics: A White Paper Contents Automated Software Testing Economics 1 Automated Software Testing Case Study 2 Benefits of Automated Software Testing 4 About Master Key Consulting
Intro to scientific programming (with Python) Pietro Berkes, Brandeis University
Intro to scientific programming (with Python) Pietro Berkes, Brandeis University Next 4 lessons: Outline Scientific programming: best practices Classical learning (Hoepfield network) Probabilistic learning
System Build 2 Test Plan
System Build 2 Test Plan Version 1.0 System Build 2 Test Plan Author s Signature Your signature indicates that this document has been prepared with input from content experts and is in compliance with
Formal models of bank cards for free
Formal models of bank cards for free Fides Aarts, Joeri de Ruiter and Erik Poll Digital Security, Radboud University Nijmegen Introduction Active learning on bank cards Learn state machines of implementations
REDUCING THE COST OF GROUND SYSTEM DEVELOPMENT AND MISSION OPERATIONS USING AUTOMATED XML TECHNOLOGIES. Jesse Wright Jet Propulsion Laboratory,
REDUCING THE COST OF GROUND SYSTEM DEVELOPMENT AND MISSION OPERATIONS USING AUTOMATED XML TECHNOLOGIES Colette Wilklow MS 301-240, Pasadena, CA phone + 1 818 354-4674 fax + 1 818 393-4100 email: [email protected]
3SL. Requirements Definition and Management Using Cradle
3SL Requirements Definition and Management Using Cradle November 2014 1 1 Introduction This white paper describes Requirements Definition and Management activities for system/product development and modification
A Practical Guide to implementing Agile QA process on Scrum Projects
Agile QA A Practical Guide to implementing Agile QA process on Scrum Projects Syed Rayhan Co-founder, Code71, Inc. Contact: [email protected] Blog: http://blog.syedrayhan.com Company: http://www.code71.com
Aligning IT investment and Business
IBM Software Group Aligning IT investment and Business The role of requirements management, portfolio management and enterprise architecture Productivity, Governance, Innovation Dr Tariq Aslam 2009 IBM
Requirements engineering
Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and
Virtual Integration and Consistent Testing of Advanced Driver Assistance Functions
Stuttgart, Testing Expo 2012 Virtual Integration and Consistent Testing of Advanced Driver Assistance Functions 2012-06-12 Jürgen Schüling Agenda Introduction and Motivation State of the Art Hardware in
Model based testing tools. Olli Pekka Puolitaival
Model based testing tools Olli Pekka Puolitaival Index 1. Software testing evolution 2. model based testing (MBT): main idea 3. MBT: step by step 4. MBT: tools 5. Questions Software testing evolution model
Introducing ECSS Software-Engineering Standards within ESA
r bulletin 111 august 2002 Introducing ECSS Software-Engineering Standards within ESA Practical approaches for space- and ground-segment software M. Jones & E. Gomez Ground Segment Engineering Department
ISTQB Certified Tester. Foundation Level. Sample Exam 1
ISTQB Certified Tester Foundation Level Version 2015 American Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged. #1 When test cases are designed
AndroLIFT: A Tool for Android Application Life Cycles
AndroLIFT: A Tool for Android Application Life Cycles Dominik Franke, Tobias Royé, and Stefan Kowalewski Embedded Software Laboratory Ahornstraße 55, 52074 Aachen, Germany { franke, roye, kowalewski}@embedded.rwth-aachen.de
From Use Cases to Test Cases. Step-by-step approach to ensure the quality of specifications and to derive test cases based on a use case model
HOOD Group 2007 www.hood-group.com From Use Cases to Test Cases Step-by-step approach to ensure the quality of specifications and to derive test cases based on a use case model Speaker HOOD Group Experts
<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
Is the Cost of Reliability, Maintainability, and Availability Affordable for Software Intensive Systems?
Is the Cost of Reliability, Maintainability, and Availability Affordable for Software Intensive Systems? Presented to IEEE Software Technology Conference Long Beach, CA Myron Hecht April, 2014 1 The Aerospace
Presentation: 1.1 Introduction to Software Testing
Software Testing M1: Introduction to Software Testing 1.1 What is Software Testing? 1.2 Need for Software Testing 1.3 Testing Fundamentals M2: Introduction to Testing Techniques 2.1 Static Testing 2.2
PHASE 6: DEVELOPMENT PHASE
PHASE 6: DEVELOPMENT PHASE The Phase features a key step in the project: system construction. The previous phases lay the foundation for system development; the following phases ensure that the product
MNLARS Project Audit Checklist
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
Regression Testing Based on Comparing Fault Detection by multi criteria before prioritization and after prioritization
Regression Testing Based on Comparing Fault Detection by multi criteria before prioritization and after prioritization KanwalpreetKaur #, Satwinder Singh * #Research Scholar, Dept of Computer Science and