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:

    Los objetivos que se plantean con el siguiente plan de implantación son los siguientes: 

    • Mejorar la calidad final de los productos software desarrollados en el Ministerio de Cultura.
    • Having a centralized repository sources files and documentation of software products of the ministry.
    • 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
    • Maintain and manage a repository of knowledge in the ministry of culture where to locate any l project information maintained by the SGTSI centrally

    Objective:

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

    • Improve the quality end products developed software in the ministry of culture.
    • Having a centralized repository sources files and documentation of software products of the ministry.
    • 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
    • Maintain and manage a repository of knowledge in the ministry of culture where to locate any l project information maintained by the SGTSI centrally

    Description:

    For the introduction of a new area of quality requires considerable effort on the part of all the factors involved in the process. Proposes the division of effort in the following phases:

    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:

    Como el plan de calidad se implementa por fases, en cada una de ellas se requieren diferentes recursos y herramientas.

    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. A very flexible tool to store the whole BBDD knowledge. It is very Agile to document collaboratively, allowing much time saving in the generation documentary.
    • GLPI . Herramienta de gestión de incidencias para almacenar el conocimiento relacionado con la experiencia del usuario final y los equipos de desarrollo.
    • Subversion . Herramienta de control de versiones software y documentación de todos los proyectos de
      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:

    La implantación en tres fases de un área de calidad en el software permitirá mejorar considerablemente la gestión y administración de los procesos de ingeniería del software aumentando finalmente el rendimiento y el control de la actividad. Mediante la inclusión de procesos de calidad en todo el ciclo de vida del software se permite que los esfuerzos finales para su puesta en marcha y su explotación obtengan mayor garantía y eficacia y menor grado de incidencias y discontinuidad del servicio redundando en bienestar de los diferentes departamentos implicados en la SGTSI y en el servicio al ciudadano.

    Overview below are the three phases of the composed the Plan of Quality:

    Phase I

    Phase I of implantation of the area of quality focuses its efforts in preparing the ground for the generalization procedures for quality of services. Will be announced manual models essential for the launch of the service and establish a fixed schedule of updates or launch. Actions to perform at this stage are:

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

    Phase II

    In this second phase elaborates on the integration of the quality adding control of unit tests and integration as well as “ repositories packaged releases ” or end for the launch of products software in production.
     

    • Evidence and documentation
    • Es realitzaran unit tests and integration supervised by the department of quality.
    • 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:

    Las ventajas de la implantación de un plan de calidad y normalización en el Ministerio de Cultura han sido muchas.

    • 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.

    Introduzca el email con el que desea recibir las notificaciones de la solución o del activo semántico.

    *

    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