This website has been translated by machine translation software and has not been subsequently revised by translators. Further information at: link. Hide
the accesskey _ mod _ content
-

Quality Plan, standardisation and normalisation of the ministry of Culture

  • Short Name:
    CalidadMCU
    Summary:
    Launches the proposal to create a department of quality, standardization and standardization to manage the control and normalization in the procedures for continuous improvement of informatics dependent on the SGTSI of the ministry of Culture.
    Target audience:
    Any Public Administration
    Agencies Responsible:
    Ministry of culture and sport
    Branch of culture and Sport
    Division of information technologies
    Contact:

     

    Sergio Carabanchel Sánchez

    Head of service of systems

    General office information technologies and systems (SGTSI)

    Culture ministry

    91 701 70 25 - sergio.carabanchel@mcu.es

    Type of Solution:
    Good Practice
    Status of the Solution:
    Production
    Organic Area:
    State
    Technical Area:
    Management of services and systems, standardisation and regulation
    Functional Area:
    Government and the public Sector
    License:
    Not implemented
    Interoperability level:
    Legal

    Description

    Purpose:

    The objectives that arise with the following plan of implantation are as follows:

    • Mejorar la calidad final de los productos software desarrollados en el Ministerio de Cultura.
    • Disponer de un repositorio centralizado de archivos fuentes y documentación de los productos software del ministerio.
    • Enter and implement procedures of version control and own configuration of the software engineering in the ministry of culture.
    • Correct planning and structuring updates in production systems
    • Mantener y gestionar un repositorio del conocimiento en el Ministerio de Cultura donde ubicar toda l información de los proyectos mantenidos por la SGTSI de forma centralizada

    Objective:

    The objectives that arise with the following plan of implantation are as follows:

    • Mejorar la calidad final de los productos software desarrollados en el Ministerio de Cultura.
    • Disponer de un repositorio centralizado de archivos fuentes y documentación de los productos software del ministerio.
    • Introducir y aplicar procedimientos de control de versiones y configuración propios de la ingeniería de software en  el Ministerio de Cultura.
    • Correct planning and structuring updates in production systems
    • Mantener y gestionar un repositorio del conocimiento en el Ministerio de Cultura donde ubicar toda l información de los proyectos mantenidos por la SGTSI de forma centralizada

    Description:

    Para la implantación de una nueva área de calidad se requiere un esfuerzo considerable por parte de todos los factores implicados en el proceso. Se propone la división del esfuerzo en las siguientes fases:

    PHASE I

    • Calendars will be established to update systems in production
    • Manual models available for development and quality.

    PHASE II

    • Integration of the quality throughout the life cycle of the project
    • Total versioned software products in production systems
    • Models of unit tests and integration.

    PHASE III

    • Centralized Project Manager
    • Centralized Wiki with all available information of software project
    • Error Control through tools centralized
    • Dispose of a database of knowledge of all projects MCU software

    Requirements:

    As the plan of quality is implemented by stages, each of them will require different resources and tools.

    PHASE I

    • Calendar of implantations in production
    • Version control tool. Recommendation of Subversion
    • Templates documentaries. User Manual, administration and the architecture systems
    • Methodological guide that facilitates the implantation of systems
    • Centralized desk manager. We Recommend a Wiki, versatile, agile and fast.
    • Management tool for centralized incidences. GLPI

    PHASE II

    • Templates for documentary evidence plans
    • Packaging tools software

    PHASE III

    • Does not require special requirements.

    For all phases tools are needed evidence control systems: Apache JMeter, WebLOAD, Badboy and Quest PerformaSure.

    Has been used tenología Open Source for documentation, incident management, documentation.

    • Wiki DekiWiki . Una herramienta muy flexible para almacenar toda la BBDD de conocimientos. Es muy ágil para documentar de manera colaborativa, permitiendo mucho ahorro de tiempo en la generación documental.
    • . GLPI Management tool to store the incidences knowledge relating to the end user experience and the development team.
    • Subversion. Tool of version control software and documentation of all projects
      information systems.
    • Tools of evidence. For testing of warm service have been used the following tools:
      • Jmeter Apache
      • Quest Performasure
      • WebLOAD
      • Findbugs
      • Badboy
    • Bugzilla . Herramienta de gestión de correcciones en los equipos de desarrollo para administrar y controlar los diferentes versiones correctivas de los productos.

    Results:

    The introduction in three phases of an area of quality in the software will considerably improve the management and administration of the processes of software engineering increasing finally performance and control of the activity. Through the inclusion of processes of quality throughout the life cycle of software allows final efforts to its launch and their exploitation better security and efficiency and lower effects and discontinuity of service resulting in welfare of different departments involved in SGTSI and service to the citizen.

    A continuación se resúmen las tres fases de las que consta el Plan de Calidad:

    Phase I

    La fase I de implantación del área de calidad centra sus esfuerzos en preparar el terreno para la generalización de los procedimientos de calidad de los servicios. Se darán a conocer modelos de manual imprescindibles para la puesta en marcha del servicio y se establecerá un calendario fijo de actualizaciones o puesta en marcha. Las acciones a realizar en esta fase son:

    • Calendar of updates
    • Evidence and documentation
    • Version Control
    • Methodology and resources
    • Training of quality team

    Phase II

    En esta segunda fase se profundiza en la integración de la calidad añadiendo control de pruebas unitarias y de integración así como repositorios de “releases” o empaquetados finales para la puesta en marcha de los productos software en producción.
     

    • Evidence and documentation
    • Se realizaran pruebas unitarias y de integración supervisadas por el departamento de calidad. 
    • Version Control
       

    Phase III

    The last phase allows the implantation total area of quality through a complete centralisation of information on each project and the standardization of the management of the configuration and versions.
     

    • Construction of a knowledge base
    • Version Control

    Advantages:

    The advantages of the implantation of a plan of quality and normalization in the ministry of culture have been many.

    • Continuous improvement in the planning of the entire life cycle of projects software with all resources involved, allowing a correct estimate of the times of analysis and development in preproduction implantation of the computer system.
    • Creation of a knowledge base of all projects of area computing, allowing you to have all the manuals and information of installation and commissioning, record of incidences which allow a management and administration of independent system based on knowledge centralized.
    • Standardisation and normalisation of all processes of work in the field of software improves the transfer of knowledge, administration, management and maintenance of applications.
    • La planificación del control de versiones de sistemas software permite administrar los tiempos de trabajo de cada persona implicada en cada proyecto de forma mas eficaz, con una calendarización de las subidas a producción y una planificación de cada servicio informático.
    • You get more time to the development of new features and improvements of software platforms, reducing the time spent on corrective maintenance of the application., detecting errors in its phase of preproduction and tests.

     

    Subscriptions

    In this area you can register to receive notification of changes that occur in news, documents or forums associated with the settlement or the active semantic.

    The fields with an asterisk * are required. It must mark at least one of the subscription rushes (News, documents or forums) and indicate the email in the text field indicated for the high or low of subscription.

    Enter the email with which you want to receive notifications of the solution or the active semantic.

    *

    You can consult the data protection policy of PAe and CTT in its legal notice

    Enter the email to unsubscribe from the unsubscribe.
General access point
General access point
Maintainer