fulfils all requirements of the SIG/TÜViT Evaluation Criteria



Similar documents
fulfils all requirements of the SIG/TÜViT Evaluation Criteria

fulfils all requirements for very high protection of the criteria catalogue The appendix is part of the certificate and consists of 4 pages.

How To Certify A Security Area Datacenter For A Trustworthy Site Infrastructure

fufils all requirements for high protection of the criteria catalogue The appendix is part of the certificate and consists of 4 pages.

fulfils all requirements for extended protection of the criteria catalogue The appendix is part of the certificate and consists of 4 pages.

to confirm that its document management- and archiving solution fulfils all applicable audit criteria for document management solutions

fulfils all requirements defined in the technical specification The appendix to the certificate is part of the certificate and consists of 6 pages.

fulfils all requirements defined in the technical specification The appendix to the certificate is part of the certificate and consists of 6 pages.

fulfils all requirements for medium protection of the criteria catalogue The appendix is part of the certificate and consists of 4 pages.

Measuring Software Product Quality

Spoof Detection and the Common Criteria

Open Source Tools. The Magazine for Professional Testers. December 2010

Only a matter of power supply and air conditioning? Joachim Faulhaber TÜV Informationstechnik GmbH

Weak Spots in Enterprise Mobility Management Dennis Schröder

Requirements engineering

The «SQALE» Analysis Model An analysis model compliant with the representation condition for assessing the Quality of Software Source Code

SERG. Test Code Quality and Its Relation to Issue Handling Performance

FMEDA and Proven-in-use Assessment. Pepperl+Fuchs GmbH Mannheim Germany

Oracle RAC Services Appendix

Getting software security Right

Characteristics of Computational Intelligence (Quantitative Approach)

The Role of Information Technology Studies in Software Product Quality Improvement

> We make. your business move. Innovative e-business solutions for banks and corporates

QUALITY MODEL BASED ON COTS QUALITY ATTRIBUTES

Auditor view about ETSI and WebTrust criteria. Christoph SUTTER

ISO/IEC 9126 in practice: what do we need to know?

Press release. Qurius trading update Q3-2007

Supplier Guidance Accounts Payable - Summarized

Requirements engineering and quality attributes

SPPA-D3000 Plant Monitor Technical Description

A Business Process Driven Approach for Generating Software Modules

Innovative cable technologies Business Unit Telecommunication Systems

ISCC 103 Quality Management. Quality Management ISCC V 2.3-EU

High Availability of the Polarion Server

Certification Report. NXP Secure Smart Card Controller P40C012/040/072 VD

ISO 9001:2015 Overview of the Revised International Standard

Free/Libre and Open Source Software: Survey and Study FLOSS

2. Scope 2.1 This policy covers all the activities and processes of the University that uses personal information in whatever format.

smart grids forum Intelligent power grids: How to build in Safety and Security Conference March 21 22, 2013 in Munich, Germany

Achieving ISO 9001 Certification for an XP Company


Achtung, Folientest, nicht für den Produktiveinsatz geeignet. DMT Online Condition Monitoring Systems MineSafe, PlantSafe, WindSafe

Common Criteria V3.1. Evaluation of IT products and IT systems

ONTOLOGY BASED FEEDBACK GENERATION IN DESIGN- ORIENTED E-LEARNING SYSTEMS

Zero Downtime In Multi tenant Software as a Service Systems

sample exam Microsoft Operations Framework edition September 2008 content 2 introduction 3 sample exam 13 answer key 28 evaluation MOFF.

How To Know If You Can Get Open Source Software To Work For A Corporation

How To Validate An Isos 9126 Quality Model

GUIDELINES FOR THE ENGAGEMENT OF EXTERNAL CONSULTANTS/PROFESSIONAL SERVICES AT MEMORIAL UNIVERSITY

OUTSOURCING AND SERVICE AUDITOR S REPORTS

File:Quality-Management Manual-V2

Monitoring the Quality of Outsourced Software

CERTIFICATE. InfraServ GmbH & Co. Knapsack KG Industriestraße Hürth Germany ISO 9001:2008

On the Quality of Quality Models MASTER THESIS. J.H. Hegeman

FRENCH RADIOSOUNDING AUTOMATION EXPERIMENTS ABSTRACT

Managing Successful Offshore QA Delivery

International Marketing

Document Code Title Editors Version Date. Version 2.0 Certification - Workflow Description. T Liebich, K Hausknecht, AEC3

Introduction. Initiative

Java: Learning to Program with Robots. Chapter 11: Building Quality Software

What Is the Value of Your Software?

Custom Development Methodology Appendix

Usability metrics for software components

The solution GBOS, together with the specialist CeGIT knowhow, ensures that integration projects are

SDNL137 Computation of nonlinear modes of a tube curved with two non-linearities of type Summarized annular

Annex 26 GUIDELINES FOR COMPLETING THE PROJECT DESIGN DOCUMENT FORM FOR CARBON CAPTURE AND STORAGE CDM PROJECT ACTIVITES. (Version 01.

Testability of Dependency injection

VoIP Example 2 (Basic Calling Method)

DRAFT APPLICATION FORMAT FOR ELECTRICITY CONNECTION

Subnetting Examples. There are three types of subnetting examples I will show in this document:

Project Portfolio Management Cloud Service

Péter Hegedűs, István Siket MTA-SZTE Research Group on Artificial Intelligence, Szeged, Hungary

Supporting Document Guidance. Security Architecture requirements (ADV_ARC) for smart cards and similar devices. April Version 2.

Best Practice Application Lifecycle Workflow

Prefiled pursuant to Article III, Section 2(A)(4)(b)(i) of the Constitution of Louisiana.

Verification Report Level III

Environmental Protection Agency Clean Water and Drinking Water State Revolving Funds ARRA Program Audit

Transcription:

The certification body of TÜV Informationstechnik GmbH hereby awards this certificate to the company ProRail Moreelsepark 3 3511 EP Utrecht, The Netherlands to confirm that its software product OOGST Diensten Rijden met RouteLint, 1.0.2.1 fulfils all requirements of the SIG/TÜViT Evaluation Criteria Trusted Product Maintainability V1.0 Level: (4 stars) of Software Improvement Group and TÜV Informationstechnik GmbH. The requirements are summarized in the appendix to the certificate. The appendix is part of the certificate and consists of 4 pages. The certificate is valid only in conjunction with the corresponding evaluation report until 2011-05-31. Maintainability TPM6403.09 11 Certificate Registration No.: TUVIT-TPM6403.09 Essen, 2009-05-28 Dr. Christoph Sutter Head of Certification Body TÜV Informationstechnik GmbH Langemarckstr. 20 45141 Essen, Germany www.certuvit.de Software Improvement Group Amsterdam, The Netherlands www.sig.eu

Appendix to the certificate TUVIT-TPM6403.09 page 1 of 4 Evaluation Report Evaluation Report C2009-001 OOGST Diensten Rijden met RouteLint of the Software Product: OOGST Diensten Rijden met RouteLint of ProRail, Version 1.0 as of 2009-05-26, Software Improvement Group. Notes and requirements stated in the evaluation report have to be followed. Evaluation Criteria SIG/TÜViT Evaluation Criteria Trusted Product Maintainability, Version 1.0, Software Improvement Group (SIG) and TÜV Informationstechnik GmbH (TÜViT). Requirements for the Issuance of the Quality Mark The rating at the level of the main quality characteristic of maintainability is 3 stars or more. The rating at the level of each sub-characteristic is 2 stars or more. The software product description requirements must be fulfilled. Target of Evaluation Software product OOGST Diensten Rijden met RouteLint of ProRail, Version 1.0.2.1 Software product description for OOGST Diensten Rijden met RouteLint of ProRail, Version 1.0.2.1

Appendix to the certificate TUVIT-TPM6403.09 page 2 of 4 Evaluation Result The overall quality level of maintainability for the evaluated product is 4 out of 5 possible stars ( ) according to the evaluation criteria. This rating was derived from the ratings of the quality subcharacteristics of maintainability calculated from the measurement of the source code properties. Results and interdependencies between sub-characteristics and product properties are summarised in the following table. Details can be found in the evaluation report. Product Property Quality Sub- Characteristic Volume Duplication Unit Size Unit Complexity Unit Interfacing Inward Coupling Result Analysability X X X Changeability X X X Stability X X Testability X X Summary of the SIG/TÜViT Evaluation Criteria The SIG/TÜViT Evaluation Criteria Trusted Product Maintainability specify five increasing quality levels of the software product characteristic maintainability and its sub-characteristics analysability, changeability, stability, and testability. The different levels are represented by one ( ) to five ( ) stars.

Appendix to the certificate TUVIT-TPM6403.09 page 3 of 4 The quality levels are derived from the software product properties measured by source code analysis. These product properties are volume, duplication, unit complexity, unit size, unit interfacing and inward coupling (see table above). To obtain the rating, the measurements of the product properties are calibrated against a benchmark repository containing a large number of comparable software products. The relative number of products in the repository to which a given number of stars is assigned for a specific property shall follow the distribution: : 5 % of the products : 5 % of the products The best 5 % of the products of the repository in terms of a given property receive five stars; the next 30 % of the products four stars and so on. The last 5 % of the products finally receive one single star. A certificate can be issued for software products having successfully passed the evaluation and reaching an overall level of at least three stars for the characteristic maintainability and a minimum of two stars for each sub-characteristic.

Appendix to the certificate TUVIT-TPM6403.09 page 4 of 4 Furthermore the software product description must fulfil the following requirements: The description identifies the product boundaries and its overall function. The description identifies all top-level components of the product. The description of the top-level components is such that any software artefact within the evaluation scope belongs to exactly one top-level component. The description identifies the role of each top-level component in the product. The description contains top-level components of appropriate number and size to facilitate maintenance of the product. The description shall give a global overview of the software product architecture.