HIS Source Code Metrics
|
|
- Annabel Higgins
- 2 years ago
- Views:
Transcription
1 HIS Source Code Metrics Stand: Version: Autor: Kuder, Helmar Mitarbeit: Audi BMW Group DaimlerChrysler Porsche Volkswagen Albrecht Korn, Erwin Haunschild Dr. Bernhard Kalusche Helmar Kuder, Martin Huber, Andreas Krüger, Dr. Eric Sax (MBtech GmbH) Dr. Rüdiger Dorn, Jesper Hansson Herbert Tschinkel, Jörg Kluge HIS-SC-Metriken.1.3.1_e.doc S. 1 / 8
2 Inhaltverzeichnis 1 BACKGROUND General Reference Documents Glossary OUTLINE Metric Groups Variation of Metrics METRICS MEASUREMENT Metrics with limits Metrics without limits... 8 History Version Date Change First Official Version Range Reference to the Document, "HIS requirements for Software Test" New Glossary Implementation of Tables 3-1 and 3-2, spelling corrections, limit value for ap-cg-cycle, 'Binding' Metrics without limits Update comments for metrics CALLING, stability index Si, NOMV, NOMVPR and ap_cg_cycle Adding titel for ap_cg_cycle: number of recursions HIS-SC-Metriken.1.3.1_e.doc Version: S. 2 / 8
3 1 Background 1.1 General HIS (Hersteller initiative Software - Manufacturer's software initiative) five working groups from the Automotive manufacturer's Audi, BMW Group, DaimlerChrysler, Porsche and Volkswagen whose goal is the production of agreed standards within the areas of Standard software modules for networks, Development of process maturity, Software test, Software tools and Programming of ECU's. Software Metrics are the basis for efficient project and quality management. With software Metrics statements can be made about the quality of the software product and the software development process. In this document HIS specifies a fundamental set of Metrics to be used in the evaluation of software. 1.2 Reference Documents Table 1-1 Reference Documents Document HIS Subset MISRA C ISO/IEC 9899:1999 Definition Cyclomatic Complexity Title General Subset of the MlSRA C Guidelines Dated: ; Version: Programming languages - C Stand: 1999 Complexity Metric (Arthur H. Watson, Thomas J. McCabe; Computer Systems Laboratory; National Institute of Standards and Technology; Gaithersburg, MD ; United States of Americe) Date: August Glossary Metric A measure (Metric) is the objective allocation of a value to an entity, in order to characterise a specific feature. (Source: German-language group of users for software Metrics and expenditure estimates Statement An action that can be implemented on an individual basis. (Source [ISO/IEC 9899:1999]; Kapitel 6.8: A statement specifies an action to be performed. ) HIS-SC-Metriken.1.3.1_e.doc Version: S. 3 / 8
4 2 Outline 2.1 Metric Groups The fixed Metrics are raised on the basis of a "compilable unit"' 1. A Metric Statement should be raised for each function. 2.2 Variation of Metrics The software supplier is responsible for the documentation of the measured values in accordance with the software Metrics defined in this document. A fundamental distinction exists between Metrics which only need to be documented (table 3-2 Metrics without boundary limits) and in Metrics (table 3-1 Metrics with boundary limits), with which a violation of the boundary limit will lead to further action. All metrics have to be reported, all violations of the agreed boundary limits at the function level have to be justified. Correction of violations of the boundary limits of the metrics is user-specific (e.g. Functional Software, Operating System) and OEM-Specific. Each OEM could specify, for example, outside of the definitions in Table 3-l, which we'll call the "Green range", wider ranges within which he accepts the software subject to rework, the "Yellow range " or completely rejects it, the "Red range 'I. 1 Different Analysis tools define "compilable unit" to be "total software " even if the external interfaces refer to the opposite (partial extent), i.e. Limit values can differ dependent on whether "total software "or "partial extent " is being referenced. HIS-SC-Metriken.1.3.1_e.doc Version: S. 4 / 8
5 3 Metrics Measurement 3.1 Metrics with limits Table 3-1 Metrics with limits Metric Description Comment Range Comment Density COMF Relationship of the number of comments (outside of and within fubctions) to the number of statements Comprehensibility, clarity in the code. With violation documentation to decide on the acceptance or rejection. According to its definition the value cannot be > 1 For example Logiscope: COMF = (BCOM + BCOB) / STMT > 0,2 For example QA-C: COMF = (STM28 / STM22) paths PATH non cyclic remark paths (i.e. minimum number of necessary cases of test) Measurement for the reduction of PATH:Allocation into several functions, Display in sub-functions. For example Logiscope: ct_path, PATH 1-80 For example QA-C: STPTH Go to Statements GOTO Go to Statements This drastically increases the number of paths and thus reduces testability For example Logiscope: ct_goto, GOTO 0 For example QA-C: STGTO Cyclomatic Complexity v(g) In accordance with the Cyclomatic Number [Definition Cyclomatic Complexity ] Measurement for the decrease in v(g): Allocation across several functions with paging into and out of sub-functions. For example Logiscope: ct_vg, VG, ct_cyclo For example CodeSurfer: vg 1-10 For example QA-C: STCYC Calling Functions CALLING By how many subfunctions is this function called? The range 1 to 5 only makes sense when the entire system is analysed. With subsystems and libraries 0 to 5 is permissible. For the complete system there is the exception of main(), since this will only be called by the Start-up-Code. For example Logiscope: dc_calling, NBCALLING 0-5 For example QA-C: STM29 called functions CALLS How many different functions does this function call? Calling the same subfunction counts only once. Examine width of nesting For example Logiscope: dc_calls, DRCT_CALLS For example QA-C: STCAL 0-7 HIS-SC-Metriken.1.3.1_e.doc Version: S. 5 / 8
6 Metric Description Comment Range Complexity of the function, need for stack Function Parameters PARAM How complex is the function interface? Structures and Arrays hide the complexity in the same way. For example Logiscope: ic_param 0-5 For example QA-C: STPAR Instructions per function STMT How complex is the function? Empty functions fall through For example Logiscope: lc_stat, STMT For example QA-C: STST call Levels LEVEL Depth of nesting of a function. Maximum nesting levels within a function + 1 For example Logiscope: LEVL 0-4 For example QA-C: STMIF return points RETURN return points within a function Complexify of a function, Maintainability of a function, When does a function return. 0 = a function without a specific return statement 0-1 For example Logiscope: RETU For example QA-C: STM19 To be collected at a function level or at the total software level. The stability index S i The stability index supplies a measure of the number of the changes (changes, deletions, additions) between two versions of a piece of software. Stability Index Si = (STMT - (S change + S new + S del ))/STMT The value is per definition <= 1. The lower this value of this metric the more changes the new software version contains. If no changes had been made overall then the value of this metric would be 1. As might be expected the stability index for two early successive versions of a piece of software will be rather low and should always then continue to rise for the later versions. 0-1 For example Logiscope: not supported For example QA-C: not supported HIS-SC-Metriken.1.3.1_e.doc Version: S. 6 / 8
7 Metric Description Comment Range Language scope VOCF The language scope is an indicator of the cost of maintaining/changing functions. VOCF = (N1 + N2) / (nl + n2), where nl = different operators N1 = Sum of all Operators n2 = different Operands N2 = Sum of all Operands Higher value = similar or duplicated code portions; Calls inlout of sub-functions need to be considered For example Logiscope: VOCF For example QA-C: Ermittelbar aus STOPN (n2), STOPT (n1), STM21 (N1), STM22 (N2) 1-4 NOMV NOMVPR recursions ap_cg_cycle Total number of the violations of the Rules of the [HIS Subset MISRA C 1.0.2]. NOMV = MISRA HIS Subset violations violations of each rule of the [HIS Subset MISRA C 1.0.2], Classified according to the rules. NOMVRP = MISRA violations per rule Call graph recursions Compliance of HIS rules within the Software production process For example Logiscope: nicht vorhanden For example QA-C: can be determined over Compliance Report. Compliance of HIS rules within the software production process. Should also contain a rule to identify,,dead Code For example Logiscope: nicht vorhanden For example QA-C: can be determined over Compliance Report. Recursions over one or more functions. For example Logiscope: ap_cg_cycle, GA_CYCLE For example QA-C: STNRA HIS-SC-Metriken.1.3.1_e.doc Version: S. 7 / 8
8 3.2 Metrics without limits The Metrics specified in the following table represent pure measured values which must still be documented in every case. Table 3-2 Metrics without limits Metric Description Comment Range S change STMT(changed) The number of statements in a piece of software which have changed between the previous and the current version of the software. Evaluation of the extent of change since the last official software release. This value is needed for the calculation of the stability index of Si. For example Logiscope: not supported For example QA-C: not supported S del STMT(deleted) The number of statements in a piece of software which have been deleted between the previous and the current version of the software. Evaluation of the extent of change since the last official software release. This value is needed for the calculation of the stability index of Si. For example Logiscope: not supported For example QA-C: not supported S new STMT(new) The number of statements in a piece of software which have added between the previous and the current version of the software. Evaluation of the extent of change since the last official software release. This value is needed for the calculation of the stability index of Si. For example Logiscope: not supported For example QA-C: not supported HIS-SC-Metriken.1.3.1_e.doc Version: S. 8 / 8
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
Herstellerinitiative Software (OEM Initiative Software)
Herstellerinitiative Software (OEM Initiative Software) Dr. Michael Daginnus Volkswagen AG Wolfsburg Dr. Dieter Marx Porsche AG Weissach Dr. Ralf Belschner Daimler AG Sindelfingen Kai Barbehön BMW AG München
FUNCTION POINT ANALYSIS: Sizing The Software Deliverable. BEYOND FUNCTION POINTS So you ve got the count, Now what?
FUNCTION POINT ANALYSIS: Sizing The Software Deliverable BEYOND FUNCTION POINTS So you ve got the count, Now what? 2008 Course Objectives The primary webinar objectives are to: Review function point methodology
Software Metrics. Lord Kelvin, a physicist. George Miller, a psychologist
Software Metrics 1. Lord Kelvin, a physicist 2. George Miller, a psychologist Software Metrics Product vs. process Most metrics are indirect: No way to measure property directly or Final product does not
The «SQALE» Analysis Model An analysis model compliant with the representation condition for assessing the Quality of Software Source Code
The «SQALE» Analysis Model An analysis model compliant with the representation condition for assessing the Quality of Software Source Code Jean-Louis Letouzey DNV IT Global Services Arcueil, France jean-louis.letouzey@dnv.com
Glossary of Object Oriented Terms
Appendix E Glossary of Object Oriented Terms abstract class: A class primarily intended to define an instance, but can not be instantiated without additional methods. abstract data type: An abstraction
Quality Analysis with Metrics
Rational software Quality Analysis with Metrics Ameeta Roy Tech Lead IBM, India/South Asia Why do we care about Quality? Software may start small and simple, but it quickly becomes complex as more features
for Source Code MathWorks Automotive Conference June 23 rd 2010 A project with Renault, PSA, Valeo, Delphi, MathWorks Presenters: Thierry Cambois -
Software Quality Objectives for Source Code A project with Renault, PSA, Valeo, Delphi, MathWorks MathWorks Automotive Conference June 23 rd 2010 Presenters: Thierry Cambois - Cost Patrick Munier - MathWorks
APPROACHES TO SOFTWARE TESTING PROGRAM VERIFICATION AND VALIDATION
1 APPROACHES TO SOFTWARE TESTING PROGRAM VERIFICATION AND VALIDATION Validation: Are we building the right product? Does program meet expectations of user? Verification: Are we building the product right?
Unit 11: Software Metrics
Unit 11: Software Metrics Objective Ð To describe the current state-of-the-art in the measurement of software products and process. Why Measure? "When you can measure what you are speaking about and express
ISO 26262 Introduction
ISO 26262 Introduction Prof. Christian Madritsch 2012 Table of Contents Structure of ISO 26262 Management of Functional Safety Product Development System Level Product Development Hardware Level Product
Die wichtigsten Use Cases für MISRA, HIS, SQO, IEC, ISO und Co. - Warum Polyspace DIE Embedded Code-Verifikationslösung ist.
Die wichtigsten Use Cases für MISRA, HIS, SQO, IEC, ISO und Co. - Warum Polyspace DIE Embedded Code-Verifikationslösung ist. Christian Guß Application Engineer The MathWorks GmbH 2015 The MathWorks, Inc.
Mining Metrics to Predict Component Failures
Mining Metrics to Predict Component Failures Nachiappan Nagappan, Microsoft Research Thomas Ball, Microsoft Research Andreas Zeller, Saarland University Overview Introduction Hypothesis and high level
Reducing Technical Debt Using Maintainability Index
Reducing Technical Debt Using Maintainability Index Too much debt can be bad for business. We are all familiar with the negative repercussions that financial debt can cause. Technical debt, and the cost
Baseline Code Analysis Using McCabe IQ
White Paper Table of Contents What is Baseline Code Analysis?.....2 Importance of Baseline Code Analysis...2 The Objectives of Baseline Code Analysis...4 Best Practices for Baseline Code Analysis...4 Challenges
Non-committal VDA recommendation regarding standards The Verband der Automobilindustrie (Automotive Industry Association - VDA) proposes that its memb
Verband der Automobilindustrie Quality Management in the Automobile Industry Joint Quality Management in the Supply Chain Product creation, product manufacture and product delivery Minimizing risks in
Automotive CAE Integration.
WHITEPAPER Automotive CAE Integration.. 2010 AUDI AG BMW AG Daimler AG Dr. Ing. h. c. F. Porsche AG Volkswagen AG PROSTEP AG Automotive CAE Integration Addendum to Automotive CAE Integration: Requirements
Programming by Contract vs. Defensive Programming: A Comparison of Run-time Performance and Complexity
Department of Computer Science Roger Andersson Patrick Jungner Programming by Contract vs. Defensive Programming: A Comparison of Run-time Performance and Complexity Master s Thesis 2003:03 Programming
Definitions. Software Metrics. Why Measure Software? Example Metrics. Software Engineering. Determine quality of the current product or process
Definitions Software Metrics Software Engineering Measure - quantitative indication of extent, amount, dimension, capacity, or size of some attribute of a product or process. Number of errors Metric -
Measurement of Software Complexity. Testwell CMTJava. with Testwell CMT++ en_software_complexity_metrics
Measurement of Software Complexity with Testwell CMT++ Testwell CMTJava www.verifysoft.com en_software_complexity_metrics 20121025 Code Complexity Measurements Code Complexity Measurement Tools Testwell
Improving Quality with Software Metrics
61-04-59 Improving Quality with Software Metrics Ian S. Hayes TO SUCCESSFULLY MANAGE INFORMATION SYSTEMS in the cost-conscious 1990s and beyond, IS managers must become more effective in delivering their
Database design 1 The Database Design Process: Before you build the tables and other objects that will make up your system, it is important to take time to design it. A good design is the keystone to creating
Module 10. Coding and Testing. Version 2 CSE IIT, Kharagpur
Module 10 Coding and Testing Lesson 26 Debugging, Integration and System Testing Specific Instructional Objectives At the end of this lesson the student would be able to: Explain why debugging is needed.
A New Cognitive Approach to Measure the Complexity of Software s
, pp.185-198 http://dx.doi.org/10.14257/ijseia.2014.8.7,15 A New Cognitive Approach to Measure the Complexity of Software s Amit Kumar Jakhar and Kumar Rajnish Department of Computer Science and Engineering,
Software Requirements Metrics
Software Requirements Metrics Fairly primitive and predictive power limited. Function Points Count number of inputs and output, user interactions, external interfaces, files used. Assess each for complexity
Software Requirements 1
Software Requirements 1 Requirements are descriptions of the services that a software system must provide and the constraints under which it must operate Requirements can range from high-level abstract
Analysis and Evaluation of Quality Metrics in Software Engineering
Analysis and Evaluation of Quality Metrics in Software Engineering Zuhab Gafoor Dand 1, Prof. Hemlata Vasishtha 2 School of Science & Technology, Department of Computer Science, Shri Venkateshwara University,
Regulation No. 55 Mechanical Couplings Coupling Balls and Towing Brackets
Regulation No. 55 Mechanical Couplings Coupling Balls and Towing Brackets S. Weiland Institute Structural Durability and System Reliability Geneva - GRRF January 31 st, 2006 Regulation No. 55 Mechanical
Complexity Analysis of Simulink Models to improve the Quality of Outsourcing in an Automotive Company. Jeevan Prabhu August 2010
Complexity Analysis of Simulink Models to improve the Quality of Outsourcing in an Automotive Company Jeevan Prabhu August 2010 ABSTRACT Usage of software in automobiles is increasing rapidly and since
Volume I, Section 4 Table of Contents
Volume I, Section 4 Table of Contents 4 Software Standards...4-1 4.1 Scope...4-1 4.1.1 Software Sources...4-2 4.1.2 Location and Control of Software and Hardware on Which it Operates...4-2 4.1.3 Exclusions...4-3
ISSN Online-document, issued 10/2011 English version, issued 2012/03 Copyright 2011 by Verband der Automobilindustrie e. V. (VDA) Qualitäts
Verband der Automobilindustrie Joint Quality Management In the Supply Chain Marketing and Service Field failure analysis Audit standard 1 st edition, October 2011 ISSN 0943-9412 Online-document, issued
How They Do It in Switzerland Outsource the Code, Insource the Quality
McCabe IQ Analyzes and Visualizes Software Quality in Critical International Financial Systems Introduction This paper examines how a major Swiss financial services company analyzes and monitors the quality
C++ INTERVIEW QUESTIONS
C++ INTERVIEW QUESTIONS http://www.tutorialspoint.com/cplusplus/cpp_interview_questions.htm Copyright tutorialspoint.com Dear readers, these C++ Interview Questions have been designed specially to get
The more intelligent solution for greater transparency SIMATIC Plant Intelligence. simatic
The more intelligent solution for greater transparency SIMATIC Plant Intelligence simatic PLANT INTELLIGENCE 1 SIMATIC Plant Intelligence greater transparency from the machine to the enterprise level Increasing
Krishna Institute of Engineering & Technology, Ghaziabad Department of Computer Application MCA-213 : DATA STRUCTURES USING C
Tutorial#1 Q 1:- Explain the terms data, elementary item, entity, primary key, domain, attribute and information? Also give examples in support of your answer? Q 2:- What is a Data Type? Differentiate
Chap 4. Using Metrics To Manage Software Risks
Chap 4. Using Metrics To Manage Software Risks. Introduction 2. Software Measurement Concepts 3. Case Study: Measuring Maintainability 4. Metrics and Quality . Introduction Definition Measurement is the
Static analysis on integration level
Static analysis on integration level Heiko Frey Robert Bosch GmbH, P.O. Box 1661, D-71226 Leonberg, E-mail: heiko.frey@de.bosch.com. Abstract Static analysis on integration level is a method of checking
Test automation: Open source compared to commercial software
Test automation: Open source compared to commercial software Hall 1 Booth 1145 Folie 1 Agenda 1. ISTEC company profile 2. Software Quality Assurance Our services 3. Customer scenario 4. Customer requirements
Tool Support for Inspecting the Code Quality of HPC Applications
Tool Support for Inspecting the Code Quality of HPC Applications Thomas Panas Dan Quinlan Richard Vuduc Center for Applied Scientific Computing Lawrence Livermore National Laboratory P.O. Box 808, L-550
Software Quality Assurance Software Measurement
Software Quality Assurance Software Measurement Contents Motivation Measure types Requirements Evaluation and calibration of measures Measure scales Data Acquisition for Measuring Important measures Case
The SQALE Quality and Analysis Models for Assessing the Quality of Ada Source Code
The SQALE Quality and Analysis Models for Assessing the Quality of Ada Source Code Thierry Coq 1 and Jean-Pierre Rosen 2 1 DNV France, Paris, France thierry.coq@dnv.com, http://www.dnv.com 2 Adalog, Issy-les-Moulineaux,
EVALUATING METRICS AT CLASS AND METHOD LEVEL FOR JAVA PROGRAMS USING KNOWLEDGE BASED SYSTEMS
EVALUATING METRICS AT CLASS AND METHOD LEVEL FOR JAVA PROGRAMS USING KNOWLEDGE BASED SYSTEMS Umamaheswari E. 1, N. Bhalaji 2 and D. K. Ghosh 3 1 SCSE, VIT Chennai Campus, Chennai, India 2 SSN College of
TEST METRICS AND KPI S
WHITE PAPER TEST METRICS AND KPI S Abstract This document serves as a guideline for understanding metrics and the Key performance indicators for a testing project. Metrics are parameters or measures of
Development of AUTOSAR Software Components within Model-Based Design
2008-01-0383 Development of AUTOSAR Software Components within Model-Based Design Copyright 2008 The MathWorks, Inc. Guido Sandmann Automotive Marketing Manager, EMEA The MathWorks Richard Thompson Senior
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
Requirements Management Best Practices
Requirements Management Best Practices Sponsored by: Karl Wiegers Principal Consultant, Process Impact www.processimpact.com Sponsor: RequirementOne Free 30 day trial Sign up by 31 st May and benefit from
Development Effort & Duration
Practical Software Project Estimation: A Toolkit for Estimating Software Development Effort & Duration International Software Benchmarking Standards Group Compiled and edited by Peter R. Hill Mc Grauu
Cost-Benefit Analysis of the Quality Measurement System of EB tresos
Cost-Benefit Analysis of the Quality Measurement System of EB tresos Jörg Eibisch, Bernd Hardung, Susanne Hartkopf, Alexander Much Elektrobit Automotive GmbH Am Wolfsmantel 46 91058 Erlangen, Germany Abstract
Managing Software Quality
Managing Software Quality Main Issues Quality cannot be added as an afterthought Metrics for measuring quality are necessary Quality can mean different things Quality needs to be implemented both in the
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
Manufacturing View. User View. Product View. User View Models. Product View Models
Why SQA Activities Pay Off? Software Quality & Metrics Sources: 1. Roger S. Pressman, Software Engineering A Practitioner s Approach, 5 th Edition, ISBN 0-07- 365578-3, McGraw-Hill, 2001 (Chapters 8 &
TurboNest. What s New. Version 11.0. Released April 2014. Copyright 2014 Hypertherm, Inc. All rights reserved.
TurboNest Version 11.0 2015 What s New Released April 2014 What s New in TurboNest 2015 (v11.0) 1 New Features and Enhancements The following enhancements are available in the TurboNest 11.0 release: Ribbon
The Configuration Management process area involves the following:
CONFIGURATION MANAGEMENT A Support Process Area at Maturity Level 2 Purpose The purpose of is to establish and maintain the integrity of work products using configuration identification, configuration
we keep you ahead consulting Product Lifecycle Management.
we keep you ahead consulting Product Lifecycle Management. Precisely and efficiently manage the lifecycle of your products along the entire value chain. Your driver for profitable growth. For a product
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
Rise-Based Peer Reviews Linda Westfall The Westfall Team
Rise-Based Peer Reviews Linda Westfall The Westfall Team lwestfall@westfallteam.com www.westfallteam.com Abstract While the benefits of formal inspections are well documented, in reality, many projects
Using Entity-Relationship Diagrams To Count Data Functions Ian Brown, CFPS Booz Allen Hamilton 8283 Greensboro Dr. McLean, VA 22102 USA
Using Entity-Relationship Diagrams To Count Data Functions Ian Brown, CFPS Booz Allen Hamilton 8283 Greensboro Dr. McLean, VA 22102 USA Contents What Is an Entity-Relationship (E-R) Diagram? E-R Vocabulary
Introduction to Computers and Programming. Testing
Introduction to Computers and Programming Prof. I. K. Lundqvist Lecture 13 April 16 2004 Testing Goals of Testing Classification Test Coverage Test Technique Blackbox vs Whitebox Real bugs and software
Maintenance Cost Estimation
MEST Maintenance Cost Estimation 1 Classifying Maintenance Activities 12 Adjusting System Size through Complexity 2 Product Versions = Maintenance Projects 13 Adjusting System Size through Quality 3 Types
Test Framework Introduction & Overview of the Test Framework
Test Framework Introduction & Overview of the Test Framework Author(s): imbus AG MoReq2 test development team Date: 18/04/2008 Version: 1.0 Status: Customer: Approved Serco Consulting imbus AG v1.0 April
CSTE Mock Test - Part III Questions Along with Answers
Note: This material is for Evaluators reference only. Caters to answers of CSTE Mock Test - Part III paper. 1. Independence is important in testing is mostly due to the fact that (Ans: C) a. Developers
METHODOLOGIES AND TOOLS FOR THE SOFTWARE QUALITY ASSURANCE COURSE *
METHODOLOGIES AND TOOLS FOR THE SOFTWARE QUALITY ASSURANCE COURSE * Vladimir V. Riabov Department of Mathematics and Computer Science Rivier College Nashua, NH, 03060 603 897-8613 vriabov@rivier.edu ABSTRACT
Making Visio Diagrams Come Alive with Data
Making Visio Diagrams Come Alive with Data An Information Commons Workshop Making Visio Diagrams Come Alive with Data Page Workshop Why Add Data to A Diagram? Here are comparisons of a flow chart with
ECE 495 Project 3: Shocker Actuator Subsystem and Website Design. Group 1: One Awesome Engineering
ECE 495 Project 3: Shocker Actuator Subsystem and Website Design Group 1: One Awesome Engineering Luquita Edwards Evan Whetsell Sunny Verma Thomas Ryan Willis Long I. Executive Summary The main goal behind
Open Source Tools. The Magazine for Professional Testers. December 2010
12 December 2010 ISSN 1866-5705 www.testingexperience.com free digital version print version 8,00 printed in Germany Open Source Tools diego cervo - Fotolia.com karaboux - Fotolia.com Take a daily photo
CS Homework 8 p. 1. CS Homework 8. To become more familiar with some additional software metrics (besides just lines of code, LOC).
CS 435 - Homework 8 p. 1 Deadline: Due by 11:59 pm on Thursday, April 11, 2013 How to submit: CS 435 - Homework 8 Submit your files for this homework using ~st10/435submit on nrs-labs, with a homework
Functional Safety, Automotive SPICE and Agile Methodology Automotive SPIN Italia 8 th Automotive Software Workshop 17.
Functional Safety, Automotive SPICE and Agile Methodology Automotive SPIN Italia 8 th Automotive Software Workshop 17. February 2011 Markus Müller KUGLER MAAG CIE GmbH Leibnizstr. 11, 70806 Kornwestheim
CRM Auditor Configuration and User Guide Microsoft Dynamics CRM 4.0. CRM Addins Productivity Solutions for Microsoft Dynamics CRM
CRM Auditor Configuration and User Guide Microsoft Dynamics CRM 4.0 CRM Addins info@crmaddins.co.uk Table of Contents Introduction... 3 Document Overview.... 3 Version Compatibility.... 3 CRM Auditor for
1 External Model Access
1 External Model Access Function List The EMA package contains the following functions. Ema_Init() on page MFA-1-110 Ema_Model_Attr_Add() on page MFA-1-114 Ema_Model_Attr_Get() on page MFA-1-115 Ema_Model_Attr_Nth()
Software Development for Multiple OEMs Using Tool Configured Middleware for CAN Communication
01PC-422 Software Development for Multiple OEMs Using Tool Configured Middleware for CAN Communication Pascal Jost IAS, University of Stuttgart, Germany Stephan Hoffmann Vector CANtech Inc., USA Copyright
Software Security Analysis: Control Flow Security Analysis with McCabe IQ
Software Security Analysis: Control Flow Security Analysis with McCabe IQ Applying a Path-based Method to Vulnerability Assessment of the Microsoft SDL Banned Function Calls Introduction When considering
A methodology for measuring software development productivity using Eclipse IDE
Proceedings of the 9 th International Conference on Applied Informatics Eger, Hungary, January 29 February 1, 2014. Vol. 2. pp. 255 262 doi: 10.14794/ICAI.9.2014.2.255 A methodology for measuring software
CALL CENTER REPORTS GUIDE
CALL CENTER REPORTS GUIDE RELEASE 18.0 DOCUMENT VERSION 2 BroadWorks Guide Copyright Notice Copyright 2011 BroadSoft, Inc. All rights reserved. Any technical documentation that is made available by BroadSoft,
LMS User Manual LMS Grade Book NUST LMS lms.team@nust.edu.pk
LMS User Manual LMS Grade Book NUST LMS lms.team@nust.edu.pk Setting up LMS Grade book Setting up LMS gradebook involves followings main steps: 1. Create gradebook categories 2. Add grade items in grade
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
Software Testing & Analysis (F22ST3): Static Analysis Techniques 2. Andrew Ireland
Software Testing & Analysis (F22ST3) Static Analysis Techniques Andrew Ireland School of Mathematical and Computer Science Heriot-Watt University Edinburgh Software Testing & Analysis (F22ST3): Static
Software Engineering & Architecture
Software Engineering & Architecture 11. QUALITY METRICS AND VISUALIZATION Martin Kropp University of Applied Sciences Northwestern Switzerland Institute for Mobile and Distributed Systems References Some
The automotive industry is making great efforts to improve. Uniform standards in software development are an important
Process Improvements in Software Development Optimizing software quality with SPICE The automotive industry is making great efforts to improve software quality. In this context the Embedded Software Components
DATA ITEM DESCRIPTION
DATA ITEM DESCRIPTION Form Approved OMB NO.0704-0188 Public reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions,
Software Metrics in Static Program Analysis
www.redlizards.com Software Metrics in Static Program Analysis ICFEM, 11/18/2010 Andreas Vogelsang 1, Ansgar Fehnker 2, Ralf Huuck 2, Wolfgang Reif 3 1 Technical University of Munich 2 NICTA, Sydney 3
Does the Act of Refactoring Really Make Code Simpler? A Preliminary Study
Does the Act of Refactoring Really Make Code Simpler? A Preliminary Study Francisco Zigmund Sokol 1, Mauricio Finavaro Aniche 1, Marco Aurélio Gerosa 1 1 Department of Computer Science University of São
Creditor Invoice Entry User Guide
Creditor Invoice Entry User Guide Created in version 2009.4.0.117 1/5 Table of Contents Creditor Invoice Entry... 2 Creditor Invoice Entry Path: Creditors Creditor Invoice Entry When an invoice has been
Adaptive Enterprise Solutions
Reporting User Guide Adaptive Enterprise Solutions 8401 Colesville Road Suite 450 Silver Spring, MD 20910 800.237.9785 Toll Free 301.589.3434 Voice 301.589.9254 Fax www.adsystech.com Version 5 THIS USER
is Research Assistant at the Laboratory for Machine Tools and Production Engineering (WZL) at RWTH Aachen
Research A s s e m b ly T e c h n o l o g y authors Dipl.-Ing. Jan Eilers is Research Assistant at the Laboratory for Machine Tools and Production Engineering (WZL) at RWTH Aachen University (Germany).
Q Clause. Page 1 of 6 TITLE: Configuration Control, Engineering Changes - Class S1 and S2
Page 1 of 6 1. Purpose: This states the requirements for preparation and submission of proposed engineering changes to the items procured by this order and to the applicable engineering drawings and specifications.
The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision of resources to support service requirements.
CAPACITY AND AVAILABILITY MANAGEMENT A Project Management Process Area at Maturity Level 3 Purpose The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision
ITIL QUALIFICATION SCHEME & ROLE-BASED TRAINING MATRIX WHITE PAPER
& ROLE-BASED TRAINING MATRIX WHITE PAPER PRESENTED BY: PUBLISHED: MAY 1, 2014 VERSION: 4 LISA SCHWARTZ AND DONNA KNAPP, ITSM ACADEMY SECTION PAGE Overview 2 Path to ITIL Expert Certification 3-5 Complementary
Exploring the Quality of Free/Open Source Software: a Case Study on an ERP/CRM System
640 Exploring the Quality of Free/Open Source Software: a Case Study on an ERP/CRM System Ioannis Samoladas, Stamatia Bibi, Ioannis Stamelos and Georgios L. Bleris Department of Informatics, Aristotle
Internet connection (high speed recommended) Microsoft Excel (installed locally) Adobe Reader 8.1 or later (installed locally)
ecellerate Purchase Order Management This manual provides a general overview of the IES ecellerate Purchase Order module. The Purchase Order module is designed to receive electronic Purchase Orders in
Supplier Engagement Guidance
Supplier Engagement Guidance This document provides guidance on engaging with suppliers to collect greenhouse gas (GHG) data when developing scope 3 GHG inventories following the GHG Protocol Corporate
IRCA Briefing note ISO/IEC 20000-1: 2011
IRCA Briefing note ISO/IEC 20000-1: 2011 How to apply for and maintain Training Organization Approval and Training Course Certification IRCA 3000 Contents Introduction 3 Summary of the changes within ISO/IEC
Different Approaches to White Box Testing Technique for Finding Errors
Different Approaches to White Box Testing Technique for Finding Errors Mohd. Ehmer Khan Department of Information Technology Al Musanna College of Technology, Sultanate of Oman ehmerkhan@gmail.com Abstract
IB-ARM Version 4.5 Portfolio Dashboard Screen Captures
IB-ARM Version 4.5 Portfolio Dashboard Screen Captures Information Balance, Inc. Screen shots are based on Version 4.5.0, Copyright 2013 Information Balance, Inc. Analyst Workbench The Portfolio Summary
Do you know? "7 Practices" for a Reliable Requirements Management. by Software Process Engineering Inc. translated by Sparx Systems Japan Co., Ltd.
Do you know? "7 Practices" for a Reliable Requirements Management by Software Process Engineering Inc. translated by Sparx Systems Japan Co., Ltd. In this white paper, we focus on the "Requirements Management,"
TL 9000 Requirements Handbook, Release 5.5. Changes from Release 5.0
TL 9000 Requirements Handbook, Release 5.5 Changes from Release 5.0 1 Change Process 2 Handbook Production Process IG Q Sub-teams IGQ Work Group Member Companies Input Rejected proposal can be reworked
Advanced Topics in Computer Science: Testing. Path Testing. Luke Gregory Professor H. Schligloff and Dr. M. Roggenbach.
Advanced Topics in Computer Science: Testing Path Testing Luke Gregory 321512 Professor H. Schligloff and Dr. M. Roggenbach Abstract Testing is a vital component of software engineering. As complex programs
Simulation in design of high performance machine tools
P. Wagner, Gebr. HELLER Maschinenfabrik GmbH 1. Introduktion Machine tools have been constructed and used for industrial applications for more than 100 years. Today, almost 100 large-sized companies and
Do students like tool usage in a Software Engineering course?
Do students like tool usage in a Software Engineering course? Michael Ritzschke, Olga Schiemangk, Klaus Bothe 9th Workshop Software Engineering Education and Reverse Engineering Neum, Bosnia and Herzegowina,
Control and Indicating Equipment
VdS Guidelines for Fire Detection and Fire Alarm Systems VdS 2540en Control and Indicating Equipment Requirements and Test Methods VdS 2540en : 2010-12 (02) Publishing house: VdS Schadenverhütung GmbH
MORE CONTROL LESS RISK
MORE CONTROL LESS RISK IDENTIFYING, ANALYZING AND CONTROLLING ACCESS RISK WITH THE GARANCY ACCESS INTELLIGENCE MANAGER White Paper VERSION 1.0 STEFANIE PFAU, THOMAS GROSSE OSTERHUES 2013 Beta Systems Software