Core Data Requirements

The intention of defining a core data-set is to assist contributors to the ISBSG repository, by nominating those data items which as a set should minimise the collection effort and be sufficient to be useful to the ISBSG. Any additions to this core data-set that can be collected are encouraged since they will increase the value of the contribution to the ISBSG repository and thereby increase the value of results that ISBSG can return.

The core data-set is a blend of “content” and “control” data, some categorise the project and some provide information on the likely quality of the project data. If you only submit the core data this should be sufficient information to assess the quality of the data and also sufficient to enhance the value of the ISBSG analysis.

As a general rule, the value which a contributor will receive from submitting a project to the ISBSG Repository will be directly related to the amount of data which can be provided. Full data submissions will enable the submitter to better compare their projects to others in the repository as well as providing better value to the organisation when developing in-house project estimates in the future. The purpose of this document is to indicate which data fields are the most important, so that submitters may be guided when designing their internal collection processes and submitting projects.

A. CORE DATA REQUIREMENTS

The minimum project data required for current analysis, is indicated below. In the case that a project received by the ISBSG is missing some of this data, an attempt is normally made by the ISBSG registrar to contact the submitter to allow completion of the data. The core data set is likely to be readily available for projects which have just completed, or where historical data is being complied for a group of projects for submission to the ISBSG Repository.

Core Data-set:

Project/Product Attributes:
    • Development Type
    • Development Platform
    • Target Platform (or indication that same as for development)
    Note: Much of the 'Project/Product Attributes' data requested will be readily available and should be submitted

    Project Work Effort:
     

    • Work Effort Total
    • Time Recording Method
    • Indication of whether all Work Effort is included or not
    • Confidence Rating (& reason for rating)


    Project Size:
     

    • Function Point Total (or means to derive it)
    • FPA Counting Standard


B. SECOND LEVEL DATA REQUIREMENTS

In addition to the Core Data Requirements, many of the following questions are used to make an assessment of the validity of the collected data. Where the validity of the data is rated as 'poor' due to either insufficient data or poor confidence in the data, the particular project will still be entered into the Repository but will be excluded from any formal ISBSG analysis. Whereas the following data is likely to be available for projects just completed, it may not be available for historical projects:
 

Project/Product Attributes:
    • Project Elapsed & Inactive Time
    • Project Implementation Date


    Project Work Effort:
     

    • Reason for Confidence Rating
    • Other Comments on Work Effort Data

      •  
    Project Size:
     
    • Numbers of Inputs, Outputs, Enquiries, Files and Interfaces
    • FPA Training Received
    • Clarification of FPA Counting Standards
    • Counting Techniques
    • Project Team Involvement
    • Review of Project Count
    • Documentation Used
    • Quality of Documentation
    • Availability of Screen / Report / File Layouts
    • Project Phase When Counted


The effect of using the Core Data Requirements for submissions to ISBSG Repository

Project data is the life-blood of the International Software Benchmarking Standards Group. The greater the number of current projects, the greater relevance analysis of the ISBSG data has to current IT development. During 1999, the ISBSG published the “Minimum Data Requirements” for project data submitted for inclusion in the Repository. This was in response to comments by several people and organisations, that the full ISBSG Data Collection Package contained many detailed questions, some of which were not easily answered and may act as a disincentive to submission. This data-set is now called: “Core Data Requirements”.

Our analysis of the contents of submissions over time suggests that a significant number of projects have been submitted with fewer data items i.e. nearer to the core data-set.
This means that using Data Disk Release 6 for a broad view of project data will return a greater number of projects. Whereas some detailed queries may return at best fewer recent projects, or possibly, too few projects for a statistically meaningful result.

However, the opportunity exists for a submitter to add data to a project at any time after a submission has been made. This means that a submitter can initially try out the submission process using the core data-set and then, having become familiar with the process and gained an understanding of the data fields, further data can be added. This can be done by resubmitting the project to ISBSG via the Registrar at admin@isbsg.org or to the ISBSG postal address. Submitters may have noticed that where their project data is ‘light’ in detail or has been rated less than ‘A’, the ISBSG asks for specific additional data at the time that the Productivity Benchmark Report is returned. This is indeed a request for more information so that the project may be up-graded.
It is to be hoped that knowledge of the core data-set will encourage more organisations to submit projects to ISBSG. At the same time, project data with more than the core data set of questions answered is most desirable to ensure the full usefulness of ISBSG data.  

 

© The International Software Benchmarking Standards Group Limited (ACN 081 497 636)