Evidence-based Development coupling structured argumentation with requirements development.
|
|
- Doris Norris
- 5 years ago
- Views:
Transcription
1 Evidence-based Development coupling structured argumentation with requirements development integrate 2012
2 based on paper Paper: EVIDENCE-BASED DEVELOPMENT COUPLING STRUCTURED ARGUMENTATION WITH REQUIREMENTS DEVELOPMENT IET Safety Edinburgh, September 2012 Experience: application in large UK defence and civil nuclear projects
3 agenda requirements in brief overview a shift in thinking reviewing traceability traceability, rationale and evidence Evidence-based Development conclusion
4 requirements in brief manage requirements in layers Subsystem integrate 2014
5 requirements in brief manage requirements in layers express requirements as traceable statements in appropriate language Subsystem integrate 2014
6 requirements in brief manage requirements in layers express requirements as traceable statements in appropriate language systematically decompose requirements through the layers and record the relationships Subsystem integrate 2014
7 manage requirements in layers express requirements as traceable statements in appropriate language systematically decompose requirements through the layers and record the relationships requirements in brief record the rationale for the decomposition compliance information Subsystem integrate 2014
8 demonstrate compliance requirements in brief Standards and Regulations Standards and Regulations Standards and Regulations Subsystem integrate 2014
9 plan tests against requirements requirements in brief Standards and Regulations Standards and Regulations Standards and Regulations Subsystem verifies verifies verifies Validation, Verification, Test and Inspection Plan integrate 2014
10 requirements in brief collect results/evidence against test plans Standards and Regulations Standards and Regulations Standards and Regulations Subsystem verifies verifies Validation, Verification, Test and Inspection Plan EVIDENCE verifies integrate 2014
11 manage change through impact analysis requirements in brief Standards and Regulations Standards and Regulations Standards and Regulations Subsystem verifies verifies Validation, Verification, Test and Inspection Plan EVIDENCE verifies integrate 2014
12 assurance case for requirement verifies verifies EVIDENCE verifies integrate 2014
13 assurance-based development or evidence-based development Standards and Regulations Standards and Regulations Standards and Regulations Subsystem verifies verifies Validation, Verification, Test and Inspection Plan EVIDENCE verifies integrate 2014
14 a shift in thinking Stakeholder Subsystem Subsystem integrate 2014
15 a shift in thinking Stakeholder from reviewing requirements in isolation: review one requirements document at a time Subsystem Subsystem integrate 2014
16 integrate 2014 Stakeholder Subsystem Subsystem a shift in thinking from reviewing requirements in isolation: review one requirements document at a time to reviewing in context: review relationship between requirements at multiple levels because most of the meaning is captured in the relationships, not just in the requirements
17 traceability documenting how high-level requirements are transformed into low-level requirements understanding how requirements are satisfied, validated and verified explaining compliance against regulations connecting evidence to design integrate
18 tracing: satisfaction relationship User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode.. The HCI will present a button for each of the possible operating modes. The HCI will indicate which of the operating modes are reachable by valid transition from the current mode. The HCI will indicate which is the current operating mode. The HCI will switch operating modes when a button for a new reachable mode is pressed.
19 User Requirement satisfaction argument The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Why do you believe that this traceability is sufficient and necessary?. The HCI will present a button for each of the possible operating modes. The HCI will indicate which of the operating modes are reachable by valid transition from the current mode. The HCI will indicate which is the current operating mode. The HCI will switch operating modes when a button for a new reachable mode is pressed.
20 User Requirement satisfaction argument The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Satisfaction Argument???? Prototyping shows that the user experience is improved by showing all possible states, indicating the current state and indicating the next possible states, so long as there are no more. than 15 possible states. The HCI will present a button for each of the possible operating modes. The HCI will indicate which of the operating modes are reachable by valid transition from the current mode. The HCI will indicate which is the current operating mode. The HCI will switch operating modes when a button for a new reachable mode is pressed.
21 structured argumentation User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Assume that there are fewer than 15 states Satisfaction Argument???? Prototyping shows that the user experience is improved by showing all possible states, indicating the current state and indicating the next possible states, so long as there are no more. than 15 possible states. HCI prototype ref H56a v1 The HCI will present a button for each of the possible operating modes. The HCI will indicate which of the operating modes are reachable by valid transition from the current mode. The HCI will indicate which is the current operating mode. The HCI will switch operating modes when a button for a new reachable mode is pressed.
22 Goal Structuring Notation? User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Assume that there are fewer than 15 states Satisfaction Argument???? Prototyping shows that the user experience is improved by showing all possible states, indicating the current state and indicating the next possible states, so long as there are no more. than 15 possible states. HCI prototype ref H56a v1 The HCI will present a button for each of the possible operating modes. The HCI will indicate which of the operating modes are reachable by valid transition from the current mode. The HCI will indicate which is the current operating mode. The HCI will switch operating modes when a button for a new reachable mode is pressed.
23 claim / argument / evidence User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Assume that there are fewer than 15 states Satisfaction Argument???? Prototyping shows that the user experience is improved by showing all possible states, you indicating believe the current state and indicating the next possible states, so long as there are no more. than 15 possible states. the claim The HCI will present a button for each of the possible operating modes. argument: explains why The HCI will indicate which of the operating modes are reachable by valid transition from the current mode. HCI prototype ref H56a v1 analysis models experiments prototypes The HCI will indicate which is the current operating mode. The HCI will switch operating modes when a button for a new reachable mode is pressed.
24 tracing: verification relationship User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode.. Acceptance Test Put the facility into a valid operating state, and attempt to select a new valid operating state. Acceptance Test Put the facility into a valid operating state, and attempt to select a new invalid operating state.
25 verification argument Acceptance Test User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Verification Argument This requirement is verified by considering a positive and a negative attempt at updating software. Put the facility into a valid operating state, and attempt to select a new valid operating state. Acceptance Test Put the facility into a valid operating state, and attempt to select a new invalid operating state.
26 structured argumentation User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Verification Argument This requirement is verified by considering a positive and a negative attempt at updating software models similarities experience argument: explains why you believe the claim. Acceptance Test Put the facility into a valid operating state, and attempt to select a new valid operating state. Acceptance Test Put the facility into a valid operating state, and attempt to select a new invalid operating state.
27 structured argumentation User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. Verification Argument This requirement is verified by considering a positive and a negative attempt at updating software Acceptance Test Put the facility into a valid operating state, and attempt to select a new valid operating state. Acceptance Test Put the facility into a valid operating state, and attempt to select a new invalid operating state. argument: explains why you believe the claim Test Argument This test objectives was fulfilled because. test results
28 Evidence-based Development What is it? framework for collecting evidence for the correctness of a system as you design the system uses requirements traceability as the structure for establishing arguments and supporting evidence extends the structured argument paradigm to cover all kinds of requirement not just safety gives ownership of assurance to every engineer
29 objectives of EbD connect the assurance case connected to the design the assurance case should not be an after-thought develop the assurance case early in time to influence the design in time to save costly rework late in the day apply a uniform approach to all aspects of assurance address all kinds of requirements: function, performance, ease-of-use, reliability, safety,... have a single point of reference for structured argumentation
30 relationships in the W model Statement of need Operational use Stakeholder requirements validates Acceptance test plan fulfils Acceptance test results requirements test plan test results Subsystem requirements Integration test plan Integration test results requirements test plan test results
31 progressive assurance Statement of need Operational use Stakeholder requirements Acceptance test plan Acceptance test results requirements test plan test results Subsystem requirements Integration test plan Integration test results requirements test plan test results
32 single requirement assurance case
33 testing mantra test early, test often because the sooner you find defects, the cheaper it is to fix
34 testing (V&V) covers early: design analysis design modelling design reviews middle: component tests factory tests integration tests late: systems tests operational tests acceptance tests all of these actions collect evidence for the correctness of the design w.r.t. requirements (verification)
35 V&V as request for evidence User Requirement The operator shall be able to select a new operating mode only if it represents a valid transition from the current operating mode. V&V Methods Evidence This requirement is verified by Analysis Analogy Inspection results results results early supports design intent Satisfaction Argument This requirement is met by... The HCI will present a button for each of the possible operating modes. The HCI will indicate which of the operating modes are reachable... Test Demonstration results results late supports design fulfilment
36 progressive assurance Statement of need Operational use Stakeholder requirements Acceptance test plan Acceptance test results requirements test plan test results Subsystem requirements Integration test plan Integration test results requirements test plan test results
37 progressive provision of evidence Statement of need Operational use Stakeholder requirements validates Acceptance test plan Operational product requirements test plan Subsystem requirements Integration test plan Subsystems requirements test plan s Analysis results Analysis results test results Integration test results test results Acceptance test results
38 the principles of EbD seem sound in practice, a cultural shift is required have to communicate benefits more effectively mentoring in how to write arguments engineers have new emphasis on owning V&V effective tool support is vital in visualising data focussed views of local argument structures navigation of large-scale argument structures going forward we will: start earlier know better how to write arguments place more emphasis on mentoring summary
39 using structured arguments within requirements development seems sound in practice, a cultural shift is required have to communicate benefits more effectively mentoring in how to write arguments engineers have new emphasis on owning V&V effective tool support is vital in visualising data focussed views of local argument structures navigation of large-scale argument structures next time we will: start earlier know better how to write arguments place even more emphasis on mentoring summary
Computer Science and Software Engineering University of Wisconsin - Platteville 9-Software Testing, Verification and Validation
Computer Science and Software Engineering University of Wisconsin - Platteville 9-Software Testing, Verification and Validation Yan Shi SE 2730 Lecture Notes Verification and Validation Verification: Are
More informationDeriving safety requirements according to ISO for complex systems: How to avoid getting lost?
Deriving safety requirements according to ISO 26262 for complex systems: How to avoid getting lost? Thomas Frese, Ford-Werke GmbH, Köln; Denis Hatebur, ITESYS GmbH, Dortmund; Hans-Jörg Aryus, SystemA GmbH,
More informationSimulink Verification and Validation
Simulink Verification and Validation Mark Walker MathWorks 7 th October 2014 2014 The MathWorks, Inc. 1 V Diagrams 3 When to Stop? A perfectly tested design would never be released Time spent on V&V is
More informationProcess for the Evaluation and Acceptance of Building Products in the USA
Process for the Evaluation and Acceptance of Building Products in the USA Rick Okawa, P.E. Deputy Vice President of Global Services and Business Development An Integrated Building System Product Certification
More informationA Model-Based Reference Workflow for the Development of Safety-Related Software
A Model-Based Reference Workflow for the Development of Safety-Related Software 2010-01-2338 Published 10/19/2010 Michael Beine dspace GmbH Dirk Fleischer dspace Inc. Copyright 2010 SAE International ABSTRACT
More informationChapter 8. Achmad Benny Mutiara
Chapter 8 SOFTWARE-TESTING STRATEGIES Achmad Benny Mutiara amutiara@staff.gunadarma.ac.id 8.1 STATIC-TESTING STRATEGIES Static testing is the systematic examination of a program structure for the purpose
More informationQuality Management System (QMS)
Chapter 12: Introduction: TOTAL QUALITY MANAGEMENT - II Quality Management System (QMS) Dr. Shyamal Gomes American National Standard Institute (ANSI) and American Society for Quality Control (ASQC) define
More informationUK EPR GDA PROJECT. Name/Initials Date 30/06/2011 Name/Initials Date 30/06/2011. Resolution Plan Revision History
RP unique number: GI-UKEPR-CI-01-RP 0 30/06/2011 1 of 19 Approved for EDF by: A. PETIT Approved for AREVA by: C. WOOLDRIDGE Name/Initials Date 30/06/2011 Name/Initials Date 30/06/2011 Resolution Plan History
More informationStandard Glossary of Terms used in Software Testing. Version 3.2. Foundation Extension - Usability Terms
Standard Glossary of Terms used in Software Testing Version 3.2 Foundation Extension - Usability Terms International Software Testing Qualifications Board Copyright Notice This document may be copied in
More informationTESTING SOFTWARE QUALITY CHARACTERISTICS
TESTING SOFTWARE QUALITY CHARACTERISTICS Zigmars Gailans TAPOST 2017 Agenda Introduction Quality Functionality Usability Accessibility https://kahoot.it Kahoot app 2 3 What is Quality? The standard of
More informationVerification and Validation in a Regulated Software Environment
Verification and Validation in a Regulated Software Environment 1 William J. Bryan Corporate Quality Manager ANSYS, Inc. Webster Verify to establish the truth, accuracy, or reality of Validate to support
More informationSafety Argument based on GSN for Automotive Control Systems. Yutaka Matsubara Nagoya University
1 Safety Argument based on GSN for Automotive Control Systems Yutaka Matsubara Nagoya University yutaka@ertl.jp 02.26.2014 2 Agenda 1. Safety argument in ISO26262 2. Requirements related to safety argument
More informationELECTRIC POWER SYSTEM
FUNDAMENTAL CHANGES TO THE ELECTRIC POWER SYSTEM POST-2018 BY MARK SIIRA, ComRent International This article gives a glimpse of some significant changes that will occur in electric power system testing
More informationASSURANCE CONTINUITY: CCRA REQUIREMENTS
ASSURANCE CONTINUITY: CCRA REQUIREMENTS VERSION 2.1 JUNE 2012 1 INTRODUCTION...3 1.1 SCOPE...3 1.2 APPROACH...3 1.3 CONTENTS...3 2 TECHNICAL CONCEPTS...4 2.1 ASSURANCE CONTINUITY PURPOSE...4 2.2 TERMINOLOGY...4
More informationUsing the Scaling Equations to Define Experimental Matrices for Software Validation
Using the Scaling Equations to Define Experimental Matrices for Software Validation Richard R. Schultz, Edwin Harvego, Brian G. Woods, and Yassin Hassan V&V30 Standards Committee Presentation Content Description
More informationSoftware Verification and Validation (VIMMD052) Introduction. Istvan Majzik Budapest University of Technology and Economics
Software Verification and Validation (VIMMD052) Introduction Istvan Majzik majzik@mit.bme.hu Budapest University of Technology and Economics Dept. of Measurement and Information s Budapest University of
More informationLecture 5: Requirements Specifications
Lecture 5: Requirements Specifications Why we need to write specifications Purpose and audience Choosing an appropriate size and formality Desiderata for Specifications Properties of good specifications
More informationFundamentals to Creating Architectures using ISO/IEC/IEEE Standards
Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards What to Architect? How to Architect? IEEE Goals and Objectives Chartered by IEEE Software Engineering Standards Committee to: Define
More informationISO27001:2013 The New Standard Revised Edition
ECSC UNRESTRICTED ISO27001:2013 The New Standard Revised Edition +44 (0) 1274 736223 consulting@ecsc.co.uk www.ecsc.co.uk A Blue Paper from Page 1 of 14 Version 1_00 Date: 27 January 2014 For more information
More informationREQUIREMENTS ENGINEERING LECTURE 2017/2018. Dr. Jörg Dörr. Conceptual Modelling. Fraunhofer IESE
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Dr. Jörg Dörr Conceptual Modelling AGENDA Analysis & Specification with Conceptual Models 2 Requirements Specification ANALYSIS & SPECIFICATION WITH CONCEPTUAL
More informationUnit 1 Introduction to Software Engineering
Unit 1 Introduction to Software Engineering João M. Fernandes Universidade do Minho Portugal Contents 1. Software Engineering 2. Software Requirements 3. Software Design 2/50 Software Engineering Engineering
More informationQUALITY ASSURANCE POLICY. Quality Assurance Policy. September 2016 Version 2.0 Policy authorised by Responsible Officer
Quality Assurance Policy September 2016 Version 2.0 Policy authorised by Responsible Officer 1 Table of Contents 1.0 Introduction...3 2.0 Scope of policy...3 3.0 Policy statement...3 4.0 Quality assurance
More informationThe data quality trends report
Report The 2015 email data quality trends report How organizations today are managing and using email Table of contents: Summary...1 Research methodology...1 Key findings...2 Email collection and database
More informationThis PDF was generated from the Evaluate section of
Toolkit home What is inclusive design? Why do inclusive design? How to design inclusively Overview Map of key activities Manage This PDF was generated from the Evaluate section of www.inclusivedesigntoolkit.com
More informationFIRE SAFETY GUIDELINES
FSG 1:2013 FIRE SAFETY AND SHELTER DEPARTMENT SINGAPORE CIVIL DEFENCE FORCE FIRE SAFETY GUIDELINES FSG 1:2013 CERTIFICATION OF REGULATED FIRE SAFETY PRODUCTS & MATERIALS (REVISED PROCEDURES) Effective
More informationRequirement Validation Model for Virtual Distributed System
Requirement Validation Model for Virtual Distributed System Tayyaba Kiran 1, Saima Farhan1, Huma Tauseef 1 and Muhammad Abuzar Fahiem 1 1 Department of Computer Science, Lahore College for Women University,
More informationModel-Based Design for High Integrity Software Development Mike Anthony Senior Application Engineer The MathWorks, Inc.
Model-Based Design for High Integrity Software Development Mike Anthony Senior Application Engineer The MathWorks, Inc. Tucson, AZ USA 2009 The MathWorks, Inc. Model-Based Design for High Integrity Software
More informationBy V-cubed Solutions, Inc. Page1. All rights reserved by V-cubed Solutions, Inc.
By V-cubed Solutions, Inc. Page1 Purpose of Document This document will demonstrate the efficacy of CODESCROLL CODE INSPECTOR, CONTROLLER TESTER, and QUALITYSCROLL COVER, which has been developed by V-cubed
More informationConcepts of Usability. Usability Testing. Usability concept ISO/IS What is context? What is context? What is usability? How to measure it?
Concepts of Usability Usability Testing What is usability? How to measure it? Fang Chen ISO/IS 9241 Usability concept The extent to which a product can be used by specified users to achieve specified goals
More informationA Software Safety Argument Pattern Catalogue
A Software Safety Argument Pattern Catalogue R. Hawkins and T. Kelly {richard.hawkins\tim.kelly}@york.ac.uk Department of Computer Science The University of York Abstract This document presents a catalogue
More informationCoding Standards in FACE Conformance. John Thomas, Chris Edwards, and Shan Bhattacharya
Coding Standards in FACE Conformance John Thomas, Chris Edwards, and Shan Bhattacharya LDRA Overview Provider of Software Quality, Compliance Management & Testing Solutions Established 1975 ISO 9001 certified
More informationTheme 2 Program Design and Testing
Theme 2 Program Design and Testing Systematic Testing 1 Learning Objectives to present a few systematic testing techniques that increase the chance of finding defects while keeping the number of test cases
More informationSoftware Engineering Testing and Debugging Testing
Software Engineering Testing and Debugging Testing Prof. Dr. Peter Thiemann Universitt Freiburg 08.06.2011 Recap Testing detect the presence of bugs by observing failures Debugging find the bug causing
More informationHuman Computer Interaction Lecture 14. HCI in Software Process. HCI in the software process
Human Computer Interaction Lecture 14 HCI in Software Process HCI in the software process Software engineering and the design process for interactive systems Usability engineering Iterative design and
More informationPart 5. Verification and Validation
Software Engineering Part 5. Verification and Validation - Verification and Validation - Software Testing Ver. 1.7 This lecture note is based on materials from Ian Sommerville 2006. Anyone can use this
More informationTest and Evaluation of Autonomous Systems in a Model Based Engineering Context
Test and Evaluation of Autonomous Systems in a Model Based Engineering Context Raytheon Michael Nolan USAF AFRL Aaron Fifarek Jonathan Hoffman 3 March 2016 Copyright 2016. Unpublished Work. Raytheon Company.
More informationCoding Standards in FACE Conformance. John Thomas, Chris Edwards, and Shan Bhattacharya
Coding Standards in FACE Conformance John Thomas, Chris Edwards, and Shan Bhattacharya LDRA Overview Provider of Software Quality, Compliance Management & Testing Solutions Established 1975 ISO 9001 certified
More informationHCI in the software process
chapter 6 HCI in the software process HCI in the software process Software engineering and the process for interactive systems Usability engineering Iterative and prototyping Design rationale the software
More informationHCI in the software. chapter 6. HCI in the software process. The waterfall model. the software lifecycle
HCI in the software process chapter 6 HCI in the software process Software engineering and the process for interactive systems Usability engineering Iterative and prototyping Design rationale the software
More informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS SOFTWARE ENGINEERING
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS 6403 - SOFTWARE ENGINEERING QUESTION BANK TWO MARKS UNIT I SOFTWARE PROCESS AND PROJECT MANAGEMENT 1. What is software engineering? Software engineering
More informationHuman Computer Interaction Lecture 06 [ HCI in Software Process ] HCI in the software process
Human Computer Interaction Lecture 06 [ HCI in Software Process ] Imran Ihsan Assistant Professor www.imranihsan.com aucs.imranihsan.com HCI06 - HCI in Software Process 1 HCI in the software process Software
More informationGuidelines for deployment of MathWorks R2010a toolset within a DO-178B-compliant process
Guidelines for deployment of MathWorks R2010a toolset within a DO-178B-compliant process UK MathWorks Aerospace & Defence Industry Working Group Guidelines for deployment of MathWorks R2010a toolset within
More informationQA Best Practices: A training that cultivates skills for delivering quality systems
QA Best Practices: A training that cultivates skills for delivering quality systems Dixie Neilson QA Supervisor Lynn Worm QA Supervisor Maheen Imam QA Analyst Information Technology for Minnesota Government
More informationGUIDANCE ON THE SECURITY ASSESSMENT OF GENERIC NEW NUCLEAR REACTOR DESIGNS
Title of document ONR GUIDE GUIDANCE ON THE SECURITY ASSESSMENT OF GENERIC NEW NUCLEAR REACTOR DESIGNS Document Type: Unique Document ID and Revision No: Nuclear Security Technical Assessment Guide Revision
More informationSoftware Engineering - I
Software Engineering - I An Introduction to Software Construction Techniques for Industrial Strength Software Chapter 3 Requirement Engineering Copy Rights Virtual University of Pakistan 1 Requirement
More information2/18/2009. Introducing Interactive Systems Design and Evaluation: Usability and Users First. Outlines. What is an interactive system
Introducing Interactive Systems Design and Evaluation: Usability and Users First Ahmed Seffah Human-Centered Software Engineering Group Department of Computer Science and Software Engineering Concordia
More informationRole and Representation of System Requirements in Systems Engineering Using Cradle
Cradle-7 From concept to creation... 3SL Role and Representation of System Requirements in Systems Engineering Using Cradle RA008/01 July 2016 July 2016 3SL. All rights reserved. Cradle is a registered
More informationAADL Requirements Annex Review
Dominique Blouin Lab-STICC Université de Bretagne-Occidentale Université de Bretagne-Sud Bretagne, France 1 AADL Standards Meeting, April 23 th, 2013 Agenda Comments from Annex Document Review Motivations
More informationVerification of the Requirements Specification
Software Verification and Validation (VIMMD052) Verification of the Requirements Specification Istvan Majzik majzik@mit.bme.hu Budapest University of Technology and Economics Dept. of Measurement and Information
More informationPERSPECTIVE. End-to-end test automation A behaviordriven and tool-agnostic approach. Abstract
PERSPECTIVE End-to-end test automation A behaviordriven and tool-agnostic approach Anand Avinash Tambey Product Technical Architect, Infosys Abstract In today s fast changing world, IT is under constant
More informationSE 2730 Final Review
SE 2730 Final Review 1. Introduction 1) What is software: programs, associated documentations and data 2) Three types of software products: generic, custom, semi-custom Why is semi-custom product more
More informationUser Centered Design (UCD)
User Centered Design (UCD) User Centered Design (UCD) introduction defining UCD usability characteristics of UCD UCD activities Introduction The primary aim of the process of design and implementation
More informationAerospace Software Engineering
16.35 Aerospace Software Engineering Verification & Validation Prof. Kristina Lundqvist Dept. of Aero/Astro, MIT Would You...... trust a completely-automated nuclear power plant?... trust a completely-automated
More informationBlack-box Testing Techniques
T-76.5613 Software Testing and Quality Assurance Lecture 4, 20.9.2006 Black-box Testing Techniques SoberIT Black-box test case design techniques Basic techniques Equivalence partitioning Boundary value
More informationCoding and Unit Testing! The Coding Phase! Coding vs. Code! Coding! Overall Coding Language Trends!
Requirements Spec. Design Coding and Unit Testing Characteristics of System to be built must match required characteristics (high level) Architecture consistent views Software Engineering Computer Science
More informationVerification and Validation. Assuring that a software system meets a user s needs. Verification vs Validation. The V & V Process
Verification and Validation Assuring that a software system meets a user s needs Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 19,20 Slide 1
More informationSoftware Architectures. Lecture 6 (part 1)
Software Architectures Lecture 6 (part 1) 2 Roadmap of the course What is software architecture? Designing Software Architecture Requirements: quality attributes or qualities How to achieve requirements
More informationMARPA DOCUMENT MARPA Revision 1.1
MARPA 1100 - Page 1 MARPA DOCUMENT MARPA 1100 Revision 1.1 STREAMLINE PROGRAM FOR PMA APPLICATIONS OF NON-SAFETY-SIGNIFICANT ARTICLES SUBMITTED BY EXPERIENCED APPLICANTS WITH A QUALIFYING PERFORMANCE RECORD
More informationTesting! Prof. Leon Osterweil! CS 520/620! Spring 2013!
Testing Prof. Leon Osterweil CS 520/620 Spring 2013 Relations and Analysis A software product consists of A collection of (types of) artifacts Related to each other by myriad Relations The relations are
More informationACCREDITATION COMMISSION FOR CONFORMITY ASSESSMENT BODIES
ACCREDITATION COMMISSION FOR CONFORMITY ASSESSMENT BODIES ACCREDITATION SCHEME MANUAL Document Title: Document Number: Various Accreditation Schemes ACCAB-ASM-7.0 CONTROLLED COPY Revision Number Revision
More informationRECOMMENDATION FOR USE
Page 1 of 6 TITLE CONTENT OF THE TECHNICAL FILE ORIGINATOR NB-RAIL STRATEGY SG SUBJECT RELATED TO Directives 2008/57/EC, 2009/131/EC, 2011/18/EU, Recommendation 2011/217/EU, Decision 2010/713/EU and all
More informationNACC2016, June 5-7, 2016, San Antonio, TX
Verification, Validation, and Control of Automated Calculational Applications Subject to ASME NQA-1 Quality Assurance Requirements Katie Phillips, Jaime Rickert, Charles A. Waggoner Institute for Clean
More informationSoftware Testing Interview Question and Answer
Software Testing Interview Question and Answer What is Software Testing? A process of analyzing a software item to detect the differences between existing and required conditions (i.e., defects) and to
More informationQuality Assurance Procedure Use of Accreditation Body & FP Certification FZE Marks, Logos and Symbols
Index 1.0 Purpose 2.0 Scope 3.0 References 4.0 Definitions 5.0 Responsibilities 6.0 Procedure 7.0 Records FP Certification Template Rev 002 1.0 Purpose 1.1 This procedure describes the applicable, rules
More informationAutomating Best Practices to Improve Design Quality
Automating Best Practices to Improve Design Quality 임베디드 SW 개발에서의품질확보방안 이제훈차장 2015 The MathWorks, Inc. 1 Key Takeaways Author, manage requirements in Simulink Early verification to find defects sooner
More informationPrototype Report. Farm Worker Safety Application. Team 09. Life Cycle Planner Developer. Developer. Quality Focal Point. Developer.
Prototype Report Farm Worker Safety Application Team 09 TEAM MEMBER NAME Juan Andrade Theerapat Chawannakul Fereshteh Khorzani Vahagen Sinanian Basir Navab Basir Navab David Tasky ROLES Project Manager
More informationComply DAu Requirement engineering og projektstyring
Comply Serve @ DAu Requirement engineering og projektstyring Delivering Progressive Assurance with ComplyPro 10 th March 2016 Agenda Assurance - a key industry issue Project failure is expensive! Comply
More informationUNIT II Requirements Analysis and Specification & Software Design
UNIT II Requirements Analysis and Specification & Software Design Requirements Analysis and Specification Many projects fail: because they start implementing the system: without determining whether they
More informationTesting is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not.
i About the Tutorial Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not. Testing is executing a system in order
More informationECE-492 SENIOR ADVANCED DESIGN PROJECT
ECE-492 SENIOR ADVANCED DESIGN PROJECT Meeting #4 1 ECE-492 Meeting#4 HW1: Teams show us your Requirements Specification? HW2: Teams show us your Conceptual Design? 2 ENGINEERING DESIGN MAKES A DIFFERENCE
More informationStandard Glossary of Terms used in Software Testing. Version 3.2. Advanced Test Automation - Engineer Terms
Standard Glossary of Terms used in Software Testing Version 3.2 International Software Testing Qualifications Board Copyright Notice This document may be copied in its entirety, or extracts made, if the
More informationLecture 5 Safety Analysis FHA, HAZOP
Lecture 5 Safety Analysis FHA, HAZOP Introduction While designing a safety-critical system usually several safety analysis techniques are applied The idea is to achieve completeness of safety requirements,
More informationCERTIFICATION RULES - PORTABLE FIRE EXTINGUISHERS
Accredited product certification CERTIFICATION RULES - PORTABLE FIRE EXTINGUISHERS Revisions in this document: Rev. no. Date Description of revision 3 2015-08-25 4.8 Added information regarding certificate
More informationEngineering Design Notes I Introduction. EE 498/499 Capstone Design Classes Klipsch School of Electrical & Computer Engineering
Engineering Design Notes I Introduction EE 498/499 Capstone Design Classes Klipsch School of Electrical & Computer Engineering Topics Overview Analysis vs. Design Design Stages Systems Engineering Integration
More informationRequirements Reuse: Fantasy or Feasible?
Requirements Reuse: Fantasy or Feasible? Sponsored by: Karl Wiegers Principal Consultant, Process Impact www.processimpact.com Source Book Software Requirements, 3 rd Edition by Karl Wiegers and Joy Beatty
More informationThe requirements engineering process
3 rd Stage Lecture time: 8:30-12:30 AM Instructor: Ali Kadhum AL-Quraby Lecture No. : 5 Subject: Software Engineering Class room no.: Department of computer science Process activities The four basic process
More informationAutomating Best Practices to Improve Design Quality
Automating Best Practices to Improve Design Quality Adam Whitmill, Senior Application Engineer 2015 The MathWorks, Inc. 1 Growing Complexity of Embedded Systems Emergency Braking Body Control Module Voice
More informationScenario-Based Analysis. Scenario-Based Analysis (example) Form analysis
Scenario-Based Analysis Scenario-Based Analysis (example) Provides a more user-oriented view perspective on the design and development of an interactive system. The defining property of a scenario is that
More informationRequirements-driven Verification Methodology for Standards Compliance Serrie-justine Chapman (TVS)
Requirements-driven Verification Methodology for Standards Compliance Serrie-justine Chapman (TVS) in collaboration with Test and Verification Solutions Ltd Infineon Technologies UK ARTEMIS CRYSTAL project
More informationA SEMI-FORMAL METHOD TO VERIFY CORRECTNESS OF FUNCTIONAL REQUIREMENTS SPECIFICATIONS OF COMPLEX EMBEDDED SYSTEM
A SEMI-FORMAL METHOD TO VERIFY CORRECTNESS OF FUNCTIONAL REQUIREMENTS SPECIFICATIONS OF Nihal Kececi Department of Computer Science Université du Québec à Montréal Software Engineering Management Research
More informationOn the Purpose of Object-Oriented Analysis
September 29 On the Purpose of Object-Oriented Analysis The What and How of what Geir Høydalsvik & Guttorm Sindre. The Norwegian Institute of Technology A critical look at: What is this about? The relationship
More informationNIST Risk Assessment for Part 11 Compliance: Evaluation of a GXP Case Study
NIST Risk Assessment for Part 11 Compliance: Evaluation of a GXP Case Study Monica Fanjoy* 109 Fairground Road, Holly Springs, NC 27540, USA Summary Current guidance for compliance with 21 Code of Federal
More informationMeDUSA Method for Designing UML2-based Embedded System Software Architectures
MeDUSA Method for Designing UML2-based Embedded System Software Architectures Alexander Nyßen 1, Horst Lichter 1, Jan Suchotzki 2, Lukas Kurmann 3 1 Introduction MeDUSA (Method for Designing UML2-based
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2015/2016 Eddy Groen Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects of
More informationFinal Project Report
16.04.02 Final Project Report Document information Project Title HP Tool Repository of SESAR standard HP methods and tools Project Number 16.04.02 Project Manager DFS Deliverable Name 16.04.02 Final Project
More informationNetwork Certification Body
Network Certification Body Scheme rules for assessment of railway projects to requirements of the Railways Interoperability Regulations as a Notified and Designated Body 1 NCB_MS_56_Notified and Introduction
More informationFieldbus transmitter must also be calibrated Mr. Juha Salimaki
Fieldbus transmitter must also be calibrated Mr. Juha Salimaki Area Sales Manager, Country Manager - India Beamex Oy, Finland Contents 1. What is calibration 2. Why calibrate 3. The operation of fieldbus
More informationNUCLEAR DIRECTORATE GENERIC DESIGN ASSESSMENT NEW CIVIL REACTOR BUILD
Health and Safety Executive NUCLEAR DIRECTORATE GENERIC DESIGN ASSESSMENT NEW CIVIL REACTOR BUILD STEP 3 SECURITY ASSESSMENT OF THE WESTINGHOUSE AP1000 DIVISION 5 ASSESSMENT REPORT NO. AR 09/042-P HSE
More informationFOUR INDEPENDENT TOOLS TO MANAGE COMPLEXITY INHERENT TO DEVELOPING STATE OF THE ART SYSTEMS. DEVELOPER SPECIFIER TESTER
TELECOM AVIONIC SPACE AUTOMOTIVE SEMICONDUCTOR IOT MEDICAL SPECIFIER DEVELOPER FOUR INDEPENDENT TOOLS TO MANAGE COMPLEXITY INHERENT TO DEVELOPING STATE OF THE ART SYSTEMS. TESTER PragmaDev Studio is a
More informationSoftware architecture in ASPICE and Even-André Karlsson
Software architecture in ASPICE and 26262 Even-André Karlsson Agenda Overall comparison (3 min) Why is the architecture documentation difficult? (2 min) ASPICE requirements (8 min) 26262 requirements (12
More informationTechniques for the unambiguous specification of software
Formal Techniques for the unambiguous of software Objectives To explain why formal techniques help discover problems in system requirements To describe the use of algebraic techniques for interface To
More informationSkill Category 6 - Summary Walkthroughs, Checkpoint Reviews and Inspections
Skill Category 6 - Summary Walkthroughs, Checkpoint Reviews and Inspections The following topics will be discussed in this Skill Category: Purpose of Reviews Review Types Prerequisites to Reviews Conducting
More informationWHITE PAPER. 10 Reasons to Use Static Analysis for Embedded Software Development
WHITE PAPER 10 Reasons to Use Static Analysis for Embedded Software Development Overview Software is in everything. And in many embedded systems like flight control, medical devices, and powertrains, quality
More informationXIV. The Requirements Specification Document (RSD)
XIV. The Requirements Specification Document (RSD) What is a RSD? What to include/not include in a RSD? Attributes of a Well-Written RSD Organization of a RSD Sample Table of Contents An Example 2002 John
More informationPRC Coordination of Protection Systems for Performance During Faults
PRC-027-1 Coordination of Protection Systems for Performance During Faults A. Introduction 1. Title: Coordination of Protection Systems for Performance During Faults 2. Number: PRC-027-1 3. Purpose: To
More informationSoftware Engineering (CSC 4350/6350) Rao Casturi
Software Engineering (CSC 4350/6350) Rao Casturi Testing Software Engineering -CSC4350/6350 - Rao Casturi 2 Testing What is testing? Process of finding the divergence between the expected behavior of the
More informationSystem Design and Modular Programming
CS3 Programming Methodology Lecture Note D1, 2 November 2000 System Design and Modular Programming System design involves meeting competing requirements and satisfying constraints on the system and the
More informationPROTERRA CERTIFICATION PROTOCOL V2.2
PROTERRA CERTIFICATION PROTOCOL V2.2 TABLE OF CONTENTS 1. Introduction 2. Scope of this document 3. Definitions and Abbreviations 4. Approval procedure for Certification Bodies 5. Certification Requirements
More informationVerification and Validation. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1
Verification and Validation 1 Objectives To introduce software verification and validation and to discuss the distinction between them To describe the program inspection process and its role in V & V To
More informationDATA ITEM DESCRIPTION
helping projects succeed... DATA ITEM DESCRIPTION 1. TITLE VERIFICATION REQUIREMENTS SPECIFICATION (VRS) 2. Identification Number PPA-003914-7 17 August 2017 3. DESCRIPTION/PURPOSE OF THE VRS 3.1 The Verification
More information