Evaluación De EME

EME, como cualquier otro equipo de desarrollo de software, puede ser evaluado según el modelo Capability Maturity Model desarrollado por el Ministerio de Defensa de EEUU que establece una serie de claves que se deben cumplir para alcanzar cada uno de los cinco niveles.

Los requisitos que deben cumplirse para alcanzar el nivel 2 son:

The Key Process Areas for Level 2: Repeatable

Requirements Management

Goal 1 System requirements allocated to software are controlled to establish a baseline for software engineering and management use.
Goal 2 Software plans, products and activities are kept consistent with the system requirements allocated to software.

Software Project Planning

Goal 1 Software estimates are documented for use in planning and tracking the software project.
Goal 2 Software project activities and commitments are planned and documented.
Goal 3 Affected groups and individuals agree to their commitments related to the software project.

Software Project Tracking and Oversight

Goal 1 Actual results and performances are tracked against the software plans.
Goal 2 Corrective actions are taken and managed to closure when actual results and performance deviate significantly form the software plans.
Goal 3 Changes to software commitments are agreed to by the affected groups and individuals.

Software Subcontract Management

Goal 1 The prime contractor selects qualified software subcontractors.
Goal 2 The prime contractor and the software subcontractor agree to their commitments to each other.
Goal 3 The prime contractor and the software subcontractor maintain ongoing communications.
Goal 4 The prime contractor tracks the software subcontractor’s actual results and performance against its commitments.

Software Quality Assurance

Goal 1 Software quality activities are planned.
Goal 2 Adherence of software products and activities to the applicable standards, procedures and requirements is verified objectively.
Goal 3 Affected groups and individuals are informed of software quality assurance activities and results.
Goal 4 Noncompliance issues that cannot be resolved within the software project are addressed by senior management.

Software Configuration Management

Goal 1 Software configuration management activities are planned.
Goal 2 Selected software work products are identified, controlled and available.
Goal 3 Changes to identified software work products are controlled.
Goal 4 Affected groups and individuals are informed of the status and content of software baselines.

Nuestro informe es:

REQUISITOS

Goal 1 Los requisitos se contemplan en los Casos de Uso que suelen estar actualizados aunque creemos que no son suficientes.
Goal 2 El software realizado se adapta a los Casos de Uso.

PLANIFICACIÓN PROYECTO

Goal 1 La especificación está siendo usada para la planificación.
Goal 2 Las actividades están planificadas a base de los planes de iteración.
Goal 3 Los grupos aceptan y se responsabilizan de sus partes.

SEGUIMIENTO DEL SOFTWARE

Goal 1 Se va comparando los avances de software con lo planificado.
Goal 2 Cuando no se cumplen los objetivos tomamos medidas amplianzo plazos, añadiendo personal…
Goal 3 Los cambios en las tareas son aceptados por los miembros.

SUBCONTRATAS

No existen.

CALIDAD SOFTWARE

Goal 1 Tenemos planificación para control de calidad.
Goal 2 Se comprueba objetivamente (por otro grupo) a la finalización de cada iteración.
Goal 3 Se informa a los grupos afectados por control de calidad medianet Wiki o hablando con ellos directamente.
Goal 4 No hay problemas relaciones con el control de calidad que no se hayan podido resolver a nivel de proyecto

GESTIÓN DE LA CONFIGURACIÓN DEL SOFTWARE

Todo va medianamente.
No ha habido cambios sustanciales respecto a la configuración inicial.