Software Evaluation Process

Introduction

This work represents work in progress, which will evolve as input and feedback from developer and user communities is gathered.

The primary motivation behind the OMII-UK Evaluation Process is to determine the level of maturity for selected software that is submitted to OMII-UK, and how it can be improved. Such software may be delivered as part of an OMII-UK Commissioned Software Project or from other sources.

Overview

This is achieved through two methods: tutorial-based evaluation and criteria-based assessment.

• Tutorial-based Evaluation: this provides a pragmatic evaluation of the software intended for those assessing its practicality and technical suitability for use.

• Criteria-based Assessment: this is a quantitative assessment of the software intended for those wanting to rapidly assess properties of the software in terms of sustainability and maintenance, functional characteristics and usability.

These methodologies are managed by a lightweight, tailored PRINCE2 project management method, with the aim to adopt those PRINCE2 processes, activities and deliverables that provide a suitable framework for managing evaluation activities.

Documents

The Best Practice: Software Release Recommendations document covers recommendations for releasing software based on OMII-UK Best Practices.

The Software Evaluation Process document covers the Evaluation Process.