Software Process Training
|
|
|
- Josephine Bailey
- 8 years ago
- Views:
Transcription
1 Dr. Ernest Wallmüller Wolfgang Höh Rule 17 Verification and Validation Qualität & Informatik Copyright Qualität & Informatik 2005
2 It is recoded that anything has started with an error... There is a rumor saying that all began with an error in a program Copyright Qualität & Informatik / 2
3 Verification & Validation! Verification! Purpose: Ensure that selected work products meet their specified requirements.! Validation! Purpose: Demonstrate that a product or product component fulfills its intended use when placed in its intended environment. Copyright Qualität & Informatik / 3
4 Industry Standard Cost Ratio to Fix a Defect COST $ Defects cost less to fix when detected earlier in the process 1 DEFEC Requirements Design Implementation Test Release Data from Gilb, T. and Graham, D. Software Inspection. Addison-Wesley, TIME Copyright Qualität & Informatik / 4
5 Early Defect Detection Shortens the Schedule RESOURCES $ Without Early Defect Detection With Early Defect Detection Requirements Design Implementation Test Release SCHEDULE Adapted from Fagan, M. Advances in Software Inspections, IEEE Transactions on SW Engineering, July 1986 Copyright Qualität & Informatik / 5
6 The Error Train The Error Summation Effect Requirements Definition Design Implementation Test and Integration correct Requirements correct Design correct Programs correct Behavior wrong Requirements Design Errors Program Errors corrected Errors introduced Errors Caused Errors by Requirement and Design Known, not corrected Errors unknown Errors Source: Mizomo, NEC, 1999 Copyright Qualität & Informatik / 6
7 Cost of Error Corrections X 1 3-6X 10X 15-40X 30-70X Requirem. Design Coding Dev.Test Accept.Test Production Source: Boehm The sooner an error can be found, the cheaper it can be corrected! Copyright Qualität & Informatik / 7
8 Context & Alternative solutions Requirements Product components Product components, work products, verification and validation reports Customer needs Product Customer Copyright Qualität & Informatik / 8
9 SW Development Overview: Rule 17 () Phase A Phase B Phase C Phase D Phase E Phase F P- Review 2 URS Handover of URS to PL-DP P- Review 3 Start Development KICK OFF SRS P- Review 4 (SRS- Review) DDS- Review Draft Architectural Design Complete Software Design Design- Review SDD- Review SW-Design Approval 17_ Impl. and Module Test Integration and Integration Test α n- Version Check Completeness of Deployments System Test Function Test Applic. Test P- Review 5 M Tryout Representative βa, β B, β C,.. GPM: Beta Version Release Review β1, β 2, β 3,.. Type Approval P- Review 6 Final Version Copyright Qualität & Informatik / 9
10 - Policy / Scope / Purpose! Policy According to the Standard Software Development and the Quality-, Environmental-, and Safety Manual (chapter 7) the policy establishes the following: Verification of the product and intermediate work products against all selected requirements, including customer, product, and productcomponent requirements. Demonstrate that a product or product component fulfills its intended use when placed in its intended environment.! Scope All SW producing units in AVL SBU MES.! Purpose The purpose of verification and validation is to help the development organization build quality into the software. The software verification and validation processes determine if development products of a given activity conform to the requirements of that activity, and if the software satisfies the intended use and user needs. The strategy is to minimize deficiencies and to find them as early as possible in the software development life cycle. Copyright Qualität & Informatik / 10
11 Exercise: Familiarization! Method: Plenum! Timing: 10! Form: Brainstorming and discussion! Documents: none! Deliverable: Documentation on flipchart (Trainer)! Questions: I. What are you experiences with Verification & Validation? II. What worked well in the past? III. What did not work so well? Copyright Qualität & Informatik / 11
12 Exercise: Roles, Activities, Work Products! Method: Individual! Timing: 15! Form: Individual elaboration! Documents: Rule 17; form: next foil! Deliverable: Filled in form Question: I. Based on your experience, the prior discussion and the process definition list the involved roles, the performed activities, and the produced work products. Copyright Qualität & Informatik / 12
13 Roles, Activities, Work Products Roles Activities Work Products Copyright Qualität & Informatik / 13
14 Roles, Activities, Work Products Roles PL-DP SPL IVV ST IE QA SQE GPM Activities Prepare for verification Prepare & conduct peer reviews Analyze Peer reviews Perform Verification, Analyze Verification Results and Identify Corrective Action Select Products for Validation and establish Validation Procedure with Environment Establish Validation Procedures and Criteria Perform Validation and Analyze Validation Results Work Products Project Work Product plan Master Test Plan Verification and Validation Plan (V&V Plan) Metrics chart and report List of findings Records in defect tracking tool Technical Performance Chart URS Review Protocol SRS Review Protocol Technical discussion protocol Change Request Report Feature Presentation Design Review Protocol (3 to 6) Acceptance Test Protocol TryOut Record Copyright Qualität & Informatik / 14
15 with Practices: VER Prepare for Verification Prepare and conduct reviews Analyze reviews Verify Selected Work Products Copyright Qualität & Informatik / 15
16 with Practices: VAL Select Products for Validation and establish Validation Procedure with Environment Establish Validation Procedures and Criteria Validate Product or Product Components Copyright Qualität & Informatik / 16
17 Tasks: Verification Practice Task Work Products Prepare for Verification Prepare and conduct reviews Analyze reviews Perf. Verification, Analyze Verification Results & Identify Corrective Action Fill records in Project Work Product Plan Create Master Test Plan Create V&V Plan (chapter verification) Plan peer reviews according to V&V Plan Conduct peer reviews Analyze peer reviews Perform verification Analyze verification results (defects) Verification results (list of findings) Record Test-results Create technical perf. charts Project Work Product plan Master Test Plan Verification and Validation Plan (V&V Plan) Review Work Product Review Protocol Metrics chart and report Project Work Product Plan updated Defect Tracking Tool List of findings Test Manager update (IBM/Rational Test Manager or RequisitePro) Defect Tracking Tool Copyright Qualität & Informatik / 17
18 Tasks: Validation Practice Task Work Products Select Products for Validation & establish Validation Proc. with Environment Establish Validation Procedures and Criteria Perform Validation and Analyze Validation Results Creation of V&V Plan (chapter validation) Establish validation procedures and criteria Generate and analyze work products according V&V Plan (URS-, SRS-, Review Protocol) Generate and analyze work products according V&V Plan (Technical discussion protocol) Generate and analyze work products according V&V Plan (Change Request Report, Feature presentation, Design Reviews) Generate and analyze work products according V&V Plan (Acceptance Test report) Generate and analyze work products according V&V Plan (TryOut Record) Master Test Plan Project Work Product Plan updated Master Test Plan updated (criteria list) URS Review Protocol SRS Review Protocol Technical discussion protocol Change Request Report Feature Presentation Design Review Protocol (3 to 6) Acceptance Test Protocol TryOut Record Copyright Qualität & Informatik / 18
19 Testing and Effort Test management Test controlling Test planning Test case deriving Test data definition Test procedure and test environment Test execution Test analysis and reporting Test preparation Closure 65 % 32 % Copyright Qualität & Informatik / 19
20 Testing as a Managed Quality Manager Test Manager User Tester / Techn. Tester System specialist / Build Manager Test documentation Test planning Q Planning Test control Test environment Installation/Operation/ Deinstallation Test monitoring Operational Testing Preparation Execution Analysis Test management Technical Testing Test system Design, set up and maintenance Acceptance / Release Increment x + 1 Increment x Test closure Copyright Qualität & Informatik / 20
21 Risk based Testing Focus on areas with high bug density! Focus an bug costing a lot! Focus on modules that are often used! Low of8 High of1 of2 of7 Low Impact of3 of5 of6 of4 of10 of9 High Probability Risk based Testing Ståle Amland 5 th International Conference EuroSTAR '99, Copyright Qualität & Informatik / 21
22 Non-Risk Based Requirement 1 Requirement 2 Requirement 3 Requirement 4 Requirement 5 Requirement 6 Requirement 7 Environments and Data Scenarios Copyright Qualität & Informatik / 22
23 Risk Based High Project Objective Risk Low Low Moderate Approach Minimal Approach Rigorous / Early Approach Technical / Development Risk High Copyright Qualität & Informatik / 23
24 Quality Attributes of ISO 9126 Test of Installation Installation procedure Re Installation test De Installation test Test of relocation Disc test Test of fall back Usability Check Programming Guidelines GUI Style Guides Architecture check Verifiability Stability Test of performance Load test Stress test Mass test test of resources Adaptability Analysability Modifiability Install ability Consumption behavior Conformity Portability Test compatibility SW-SW SW-HW HW-HW End user access changeability Efficiency Time response Correctness Functionality Reliablity Useability Operability Adequacy Legality Learnability Test of usability Exchangeability Interoperability Comprehensibility Security Functional Tests Component test Function test Application test Verbundtest URL /Link Test Maturity Fault tolerance Recoverability Test new system components Software Hardware Middleware Operating system Database Check IT security Test of security access Penetration test Virus-/Trojan check Browser parameters Data security Security guidelines Test of robustness Test of user bug Test technical exceptional situations Restart /Recovery test Availability tests Test serviceability Problem Management (Service Center) Operations Management Performance Management Configurations Management Change Management (Service Center) Copyright Qualität & Informatik / 24
25 Exercise: Task Description! Method: Group work! Timing: 20 group work, 15 presentation & discussion (comparative discussion of group results)! Form: Group elaboration! Documents: Rule 17:! Deliverable: Task description on flipchart! Question: I. Describe the selected task VER_T02: Create Master Testplan using the presented description technique ("next foil). Copyright Qualität & Informatik / 25
26 Task Description Technique Input ID Task Name Description Roles Tools Method/Technique Output Copyright Qualität & Informatik / 26
27 Task Details Create Master Testplan Input Project Work Product Plan V&V Plan List of available verification techniques ID VER_T02 Roles SPL IVV Task Name Create Master Testplan Description All Work Product must have the attribute set to yes or no Define test-strategy, test environment Reference other relevant documents Define required skills incl. its capacity assign resources reference project milestones Resp. for task VER_T02 Tools Template: Template_VER_Master Testplan.dot Method/Technique List of available verification techniques Output V&V Plan updated Master Testplan Project Work Product Plan updated Copyright Qualität & Informatik / 27
28 Rule 17: Work Products and Templates WP Id Type Description Task Id Resp. Link to Template VER_W01 M Project Workproduct plan VER_T01 PL-DP Template Project_WorkProduct_Plan.xlt VER_W02 M Master Testplan VER_T02 SPL IVV Template_VER_Master_Testplan.dot VER_W03 M Verification and Validation Plan (V & V SPL VER_T03 Plan) IVV Template_VV_plan.dot VER_W05 O Metrics chart and report VER_T06 QA n.a. VER_W06 M List of findings VER_T09 QA Template Walkthrough_and_Review_ Protocol.dot VER_W07 M Records in defect tracking tool VER_T08 SPL IVV n.a. VER_W08 O Technical Performance Chart VER_T11 SPL IVV n.a. VAL _W01 M V&V Plan VAL_T01 SPL Template_VV_plan.dot IVV VAL _W02 M URS Review Protocol VAL_T02 QA Template Walkthrough_and_Review_ Protocol.dot or Template URS_SRS_Review.dot VAL _W03 M SRS Review Protocol VAL_T02 QA Template Walkthrough_and_Review_ Protocol.dot or Template URS_SRS_Review.dot VAL _W04 O Technical discussion protocol VAL_T03 SPL IVV Template Walkthrough_and_Review_ Protocol.dot VAL _W05 O Change Request Report VAL_T04 PL-DP n.a. VAL _W06 O Feature Presentation VAL_T04 PL-DP n.a. VAL _W07 M Design Review Protocol (3 to 6) VAL_T04 PL-DP Template FB-MES SQ- R23_Pdr*.dot VAL _W08 M Acceptance Test Protocol VAL_T05 SPL IVV Template Acceptance_Test_Protocol. dot VAL_W09 M TryOut Record VAL_T06 GPM Template_VAL_FB-MES SZT-R01_ TA- Certificate.dot Copyright Qualität & Informatik / 28
29 Rule 17: Concluding Discussion What was important for you concerning this Rule? Copyright Qualität & Informatik / 29
30 Any Questions Copyright Qualität & Informatik / 30
Software Process Training
Dr. Ernest Wallmüller Wolfgang Höh Rule 8 Configuration Management Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Software Configuration Management (S) The process of identifying,
Software Process Training
Rule 15 Technical Solution Dr. Ernest Wallmüller Wolfgang Höh Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Context & Alternative solutions Requirements Product components Product
Software Process Training
Dr. Ernest Wallmüller Wolfgang Höh Rule 24 Review & Walkthrough Guideline Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Purpose of Reviews! To improve the quality of the item under
Software Process Training
Dr. Ernest Wallmüller Wolfgang Höh Rule 6 Development Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Context Ver Product & product component requirements Alternative solutions Product
Software Process Training
Dr. Ernest Wallmüller Wolfgang Höh Rule 10 Rule 10 Supplier Agreement Management Supplier Agreement Management Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Context QA Corrective
Software Process Training
Rule 5 Project Planning Dr. Ernest Wallmüller Wolfgang Höh Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Context QA Corrective action Supplier agreement Supplier Replan Status,
Software Process Training
Dr. Ernest Wallmüller Wolfgang Höh Rule 16 Integrated Project Management Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Context QA Management process areas Engineering & Support
Software Process Training
Dr. Ernest Wallmüller Wolfgang Höh Rule 9 and Product Quality Assurance Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 - What does it mean? Nonconformance? Copyright Qualität & Informatik
Software Process Training
Rule 14 Risk Management Dr. Ernest Wallmüller Wolfgang Höh Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Why Risk Management? NASA took consequences from the Columbia Disaster :
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
Software Process Training
Module Dr. Ernest Wallmüller Wolfgang Höh Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Agenda 13:00 Opening Paulweber 13:05 Short, Wallmüller, Höh, All agenda and overview of training
Software Testing Interview Questions
Software Testing Interview Questions 1. What s the Software Testing? A set of activities conducted with the intent of finding errors in software. 2.What is Acceptance Testing? Testing conducted to enable
Levels of Software Testing. Functional Testing
Levels of Software Testing There are different levels during the process of Testing. In this chapter a brief description is provided about these levels. Levels of testing include the different methodologies
Software Quality Assurance Software Inspections and Reviews
Software Quality Assurance Software Inspections and Reviews Contents Definitions Why software inspections? Requirements for inspections Inspection team Inspection phases 2 Definitions Manual quality assurance
Software Engineering Compiled By: Roshani Ghimire Page 1
Unit 7: Metric for Process and Product 7.1 Software Measurement Measurement is the process by which numbers or symbols are assigned to the attributes of entities in the real world in such a way as to define
Procedure for Assessment of System and Software
Doc. No: STQC IT/ Assessment/ 01, Version 1.0 Procedure for Assessment of System and Software May, 2014 STQC - IT Services STQC Directorate, Department of Electronics and Information Technology, Ministry
Project QA and Collaboration Plan for <project name>
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete 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
Software Testing. Knowledge Base. Rajat Kumar Bal. Introduction
Software Testing Rajat Kumar Bal Introduction In India itself, Software industry growth has been phenomenal. IT field has enormously grown in the past 50 years. IT industry in India is expected to touch
Group18-CUCE2012. Mr. Mobile Project. Software Testing Plan (STP) Version: 4.0. CM Identifier: G18_SE004
Group18-CUCE2012 Mr. Mobile Project Software Testing Plan (STP) Version: 4.0 CM Identifier: G18_SE004 26 April 2010 Revision History Prepared/ Modified by Ahmed Adel Ahmed Abdullah, Ahmed Hafez and Sheriff
IT Project: System Implementation Project Template Description
2929 Campus Drive Suite 250 IT Project: System Implementation Project Template Description Table of Contents Introduction... 2 Project Phases... 3 Initiation & Requirements Gathering Milestone... 3 Initiation
SOFTWARE QUALITY MODELS: A COMPARATIVE STUDY
SOFTWARE QUALITY MODELS: A COMPARATIVE STUDY Mrs. Manisha L. Waghmode Assistant Professor Bharati Vidyapeeth Deemed University, Institute of Management and Rural Development Administration, Sangli Dr.
Software Project Management Plan (SPMP)
Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.
VAIL-Plant Asset Integrity Management System. Software Development Process
VAIL-Plant Asset Integrity Management System Software Development Process Document Number: VAIL/SDP/2008/008 Engineering For a Safer World P u b l i c Approved by : Ijaz Ul Karim Rao Revision: 0 Page:2-of-15
Oracle Insurance Policy Administration System Quality Assurance Testing Methodology. An Oracle White Paper August 2008
Oracle Insurance Policy Administration System Quality Assurance Testing Methodology An Oracle White Paper August 2008 Oracle Insurance Policy Administration System Quality Assurance Testing Methodology
Lecture 8 About Quality and Quality Management Systems
Lecture 8 About Quality and Quality Management Systems Kari Systä 10.03.2014 10.03.2014 TIE-21100/21106; K.Systä 1 Content of today s lecture Two weeks ago we discussed about testing and inspections, that
Service Delivery Module
Service Delivery Module Software Development Methodology -India follows international industry standards and has adopted the standard methodology in our Software Development Life Cycle (SDLC). It is a
Basic Testing Concepts and Terminology
T-76.5613 Software Testing and Quality Assurance Lecture 2, 13.9.2006 Basic Testing Concepts and Terminology Juha Itkonen SoberIT Contents Realities and principles of Testing terminology and basic concepts
Design Document Version 0.0
Software Development Templates Design Document Version 0.0 Description of Project DOCUMENT NO: VERSION: CONTACT: EMAIL: Ivan Walsh DATE: 4/13/2004 Distribution is subject to copyright. Design Document
Software Engineering: Analysis and Design - CSE3308
CSE3308/DMS/2004/25 Monash University - School of Computer Science and Software Engineering Software Engineering: Analysis and Design - CSE3308 Software Quality CSE3308 - Software Engineering: Analysis
International Software & Systems Engineering. Standards. Jim Moore The MITRE Corporation Chair, US TAG to ISO/IEC JTC1/SC7 James.W.Moore@ieee.
This presentation represents the opinion of the author and does not present positions of The MITRE Corporation or of the U.S. Department of Defense. Prepared for the 4th Annual PSM Users Group Conference
Independent Test and Evaluation
Independent Test and Evaluation ProPath Office of Information and Technology Table of Contents Independent Test and Evaluation Process Maps... 1 Process: Independent Test and Evaluation... 3 Independent
What do you think? Definitions of Quality
What do you think? What is your definition of Quality? Would you recognise good quality bad quality Does quality simple apply to a products or does it apply to services as well? Does any company epitomise
Testing Introduction. IEEE Definitions
Testing Introduction IEEE Definitions Software testing is the process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs) and to evaluate the
What is a life cycle model?
What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each
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
Chap 1. Software Quality Management
Chap 1. Software Quality Management Part 1.1 Quality Assurance and Standards Part 1.2 Software Review and Inspection Part 1.3 Software Measurement and Metrics 1 Part 1.1 Quality Assurance and Standards
The Role of Information Technology Studies in Software Product Quality Improvement
The Role of Information Technology Studies in Software Product Quality Improvement RUDITE CEVERE, Dr.sc.comp., Professor Faculty of Information Technologies SANDRA SPROGE, Dr.sc.ing., Head of Department
(Refer Slide Time: 01:52)
Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This
Essentials of the Quality Assurance Practice Principles of Testing Test Documentation Techniques. Target Audience: Prerequisites:
Curriculum Certified Software Tester (CST) Common Body of Knowledge Control Procedures Problem Resolution Reports Requirements Test Builds Test Cases Test Execution Test Plans Test Planning Testing Concepts
1. Software Engineering Overview
1. Overview 1. Overview...1 1.1 Total programme structure...1 1.2 Topics covered in module...2 1.3 Examples of SW eng. practice in some industrial sectors...4 1.3.1 European Space Agency (ESA), software
How CMMI contributes to Software Testing
How CMMI contributes to Software Testing Dr. Uwe Hehn method park Software AG Uwe.Hehn@methodpark.de Contents 1. Motivation for S/W Quality Models 2. Why Testers should have some knowledge of Quality Models
Software Project Audit Process
Software Project Audit Process Version 1.2 Information and Communication Technology Agency of Sri Lanka July 2013 Copyright 2011 ICTA Software Project Audit Process-v-1.2 Revision History Date Version
ISO/IEC 9126-1 Software Product Quality Model
Why do current systems fail? Standish Group found that 51% of projects failed 31% were partially successful Main causes were poor user requirements: 13.1% Incomplete requirements 12.4% Lack of user involvement
<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
SOFTWARE QUALITY & SYSTEMS ENGINEERING PROGRAM. Quality Assurance Checklist
SOFTWARE QUALITY & SYSTEMS ENGINEERING PROGRAM Quality Assurance Checklist The following checklist is intended to provide system owners, project managers, and other information systems development and
Quality Management. Lecture 12 Software quality management
Quality Management Lecture 12 Software quality management doc.dr.sc. Marko Jurčević prof.dr.sc. Roman Malarić University of Zagreb Faculty of Electrical Engineering and Computing Department of Fundamentals
SOFTWARE ASSURANCE STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8739.8 w/change 1 Space Administration July 28, 2004 SOFTWARE ASSURANCE STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-2201-93 DATED NOVEMBER
Lecture Softwareengineering-Vertiefung
Lecture Softwareengineering-Vertiefung 1 Introduction Summer term 2014 TU Chemnitz Department of Computer Science Dr. Dirk Müller Overview Introduction Organizational issues Process of software inspection,
CDC UNIFIED PROCESS JOB AID
CDC UNIFIED PROCESS JOB AID Independent Verification & Validation Activities Document Purpose This Job Aid is a brief document listing the items to be noted, checked, remembered, and delivered when completing
Building Reusable Testing Assets for a Product Line
Building Reusable Testing Assets for a Product Line John D. McGregor Visiting Scientist - SEI Senior Partner - Korson-McGregor Associate Professor - Clemson University johnmc@cs.clemson.edu Qualifications
CS 451 Software Engineering Winter 2009
CS 451 Software Engineering Winter 2009 Yuanfang Cai Room 104, University Crossings 215.895.0298 yfcai@cs.drexel.edu 1 Testing Process Testing Testing only reveals the presence of defects Does not identify
Software Testing Lifecycle
STLC-Software Testing Life Cycle SDLC Software Testing Lifecycle Software Testing Life Cycle (STLC) defines the steps/ stages/ phases in testing of software. However, there is no fixed standard STLC in
The document you download is the copyright of ISO, and may not be stored, reproduced, transferred or resold by any means, except as follows.
Licence Agreement You are about to download material which is subject to strict copyright conditions. Please read these terms and conditions carefully. By accepting them, you are entering into a binding
Product Name Manufacturer Manufacturer Part No Description Unit of Measure State Price
Product Name Manufacturer Manufacturer Part No Description Unit of Measure State Price Consultant/Planner Distinctive Business Solutions DBS-CP-10 Project Manager Distinctive Business Solutions DBS-PM-10
1. Introduction. Annex 7 Software Project Audit Process
Annex 7 Software Project Audit Process 1. Introduction 1.1 Purpose Purpose of this document is to describe the Software Project Audit Process which capable of capturing different different activities take
Application of software product quality international standards through software development life cycle
Central Page 284 of 296 Application of software product quality international standards through software development life cycle Mladen Hosni, Valentina Kirinić Faculty of Organization and Informatics University
Independent Verification and Validation of SAPHIRE 8 Software Project Plan
INL/EXT-09-17022 Rev. 2 Independent Verification and Validation of SAPHIRE 8 Software Project Plan March 2010 The INL is a U.S. Department of Energy National Laboratory operated by Battelle Energy Alliance
Automated Office Systems Support Quality Assurance Plan. A Model DRAFT. December 1996
Quality Assurance Plan A Model DRAFT United States Department of Energy Office of Nonproliferation and National Security Title Page Document Name: Publication Date: Draft, ontract Number: Project Number:
Time Monitoring Tool Software Development Plan. Version <1.1>
Time Monitoring Tool Software Development Plan Version Revision History Date Version Description Author 10/01/01 1.0 First Draft Sabrina Laflamme 12/01/01 1.1 Completion of Document John Lemon Page
Prof. Paolo Nesi. Lab: DISIT, Sistemi Distribuiti e Tecnologie Internet
1 Sistemi Distribuiti Corso di Laurea in Ingegneria Prof. Paolo Nesi PARTI: 3 Ciclo di Vita, management, assessment Department of Systems and Informatics University of Florence Via S. Marta 3, 50139, Firenze,
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
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
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
Process Models and Metrics
Process Models and Metrics PROCESS MODELS AND METRICS These models and metrics capture information about the processes being performed We can model and measure the definition of the process process performers
Project Risk Management: IV&V as Insurance for Project Success
Project Risk Management: IV&V as Insurance for Project Success Introduction Software development projects can be expensive and risky: Ever more complex mission-critical requirements lead to increasingly
Testing Metrics. Introduction
Introduction Why Measure? What to Measure? It is often said that if something cannot be measured, it cannot be managed or improved. There is immense value in measurement, but you should always make sure
HOW TO CREATE USEFUL SOFTWARE PROCESS DOCUMENTATION ABSTRACT
HOW TO CREATE USEFUL SOFTWARE PROCESS DOCUMENTATION Linda Westfall The Westfall Team lwestfall@westfallteam.com 3000 Custer Road, Suite 270, PMB 383 Plano, TX 75075 ABSTRACT Whether our organization is
Test Automation Process
A white Success The performance testing helped the client identify and resolve performance bottlenecks which otherwise crippled the business. The ability to support 500 concurrent users Test Automation
Abstract. 1 Introduction
Amir Tomer Amir Tomer is the Director of Systems and Software Engineering Processes at RAFAEL Ltd., Israel,with whom he has been since 1982,holding a variety of systems and software engineering positions,both
Software Testing Tutorial
Software Testing Tutorial SOFTWARE TESTING TUTORIAL Simply Easy Learning by tutorialspoint.com tutorialspoint.com i C O P Y R I G H T & D I S C L A I M E R N O T I C E All the content and graphics on this
Managing Small Software Projects - An Integrated Guide Based on PMBOK, RUP, and CMMI
Managing Small Software Projects - An Integrated Guide Based on PMBOK, RUP, and CMMI César Cid Contreras M.Sc. Prof. Dr. Henrik Janzen Published at the South Westphalia University of Applied Sciences,
Project Plan for <project name>
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and
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.
Mike Peters Senior Test Consultant/Delivery Manager mike.peters@logicacmg.com. LogicaCMG 2006. All rights reserved
LogicaCMG & Testing: TestFrame & RRBT Mike Peters Senior Test Consultant/Delivery Manager mike.peters@logicacmg.com LogicaCMG 2006. All rights reserved About LogicaCMG > 40,000 employees worldwide 41 countries
Software Engineering Question Bank
Software Engineering Question Bank 1) What is Software Development Life Cycle? (SDLC) System Development Life Cycle (SDLC) is the overall process of developing information systems through a multi-step
Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.
INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing
CMMI KEY PROCESS AREAS
CMMI KEY PROCESS AREAS http://www.tutorialspoint.com/cmmi/cmmi-process-areas.htm Copyright tutorialspoint.com A Process Area is a cluster of related practices in an area that, when implemented collectively,
Software Configuration Management Plan
For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.
Draft Requirements Management Plan
BAO111: Core Competencies for the Business Analyst Draft Requirements Management Plan 1.0 INTRODUCTION 1.1 Purpose This document outlines requirements roles and responsibilities, presents a stakeholder
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
SOFTWARE QUALITY IN 2002: A SURVEY OF THE STATE OF THE ART
Software Productivity Research an Artemis company SOFTWARE QUALITY IN 2002: A SURVEY OF THE STATE OF THE ART Capers Jones, Chief Scientist Emeritus Six Lincoln Knoll Lane Burlington, Massachusetts 01803
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
Syllabus. REQB Certified Professional for Requirements Engineering. Foundation Level
Syllabus REQB Certified Professional for Requirements Engineering Version 2.1 2014 The copyright to this edition of the syllabus in all languages is held by the Global Association for Software Quality,
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
Introduction to Software Engineering
CS1Ah Lecture Note 7 Introduction to Software Engineering In this note we provide an overview of Software Engineering. The presentation in this lecture is intended to map out much of what we will study
ISO 9001/TL 9000 and CMMI Comparison
ISO 9001/TL 9000 and CMMI Comparison www.questforum.org Copyright QuEST Forum 2007 1 Purpose This summary is intended to give those familiar with CMMI a general sense of the additional requirements contained
Project Lifecycle Management (PLM)
Project Lifecycle Management (PLM) Process or Tool? Why PLM? Project Definition Project Management NEW REQUEST/ INITIATIVES SUPPORT (Quick fixes) PROJECT (Start Finish) ONGOING WORK (Continuous) ENHANCEMENTS
Configuration Management Practices
Safety Critical Software Management Practices Linda Westfall Westfall Team, Inc. International Conference on Software Quality ICSQ 2011 Copyright 1999-2010 Westfall Team, Inc. All Rights Reserved. Management
Latest Trends in Testing. Ajay K Chhokra
Latest Trends in Testing Ajay K Chhokra Introduction Software Testing is the last phase in software development lifecycle which has high impact on the quality of the final product delivered to the customer.
CMMI: Specific Goals and Practices
Software Engineering for Outsourced & Offshore Development CMMI: Specific Goals and Practices PeterKolb Software Engineering CMMI Process Areas for R&D Projects Slide 2 Content Management in Projects Project
UNIT-II Part-A Questions
UNIT-I 1. What is quality? 2. Define software quality? 3. What are the views of quality? 4. Give the definitions of quality? 5. What is quality as per ISO? 6. What are the reasons for software becomes
PM Planning Configuration Management
: a Project Support Function As stated throughout the Project Planning section, there are fundamental components that are started during the pre-performance stage of the project management life cycle in
Appendix H Software Development Plan Template
Appendix H Software Development Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms
Manual Testing Online Training Concepts : Software Testing Manual Module 1: Testing fundamentals. Introduction:
Manual Testing Online Training Concepts : Software Testing Manual Module 1: Testing fundamentals Introduction: Why explicitly the s/w companies are recruited the test engineers: Who can do this Testing:
Software Testing. System, Acceptance and Regression Testing
Software Testing System, Acceptance and Regression Testing Objectives Distinguish system and acceptance testing o How and why they differ from each other and from unit and integration testing Understand
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
Preventive Approach for Web Applications Security Testing OWASP 10/30/2009. The OWASP Foundation http://www.owasp.org
Preventive Approach for Web Applications Security Testing 10/30/2009 Luiz Otávio Duarte Ferrucio de Franco Rosa Walcir M. Cardoso Jr. Renato Archer Information Technology Center Brazilian Ministry of Science
Software Quality Testing Course Material
Prepared by Vipul Jain Software Quality Testing Course Material Course content is designed and will be taught in such a manner in order to make a person job ready in around 10-12 weeks. Classroom sessions
Software Development: The Waterfall Model
Steven Zeil June 7, 2013 Contents 1 Software Development Process Models 2 1.1 Components of the Waterfall Model................................. 2 1.1.1 What is a requirement?. 2 1.1.2 Testing..........