Especificación y Descripción de Liberación. Líneas Base.

Slides:



Advertisements
Presentaciones similares
Ciclo de vida de desarrollo de software
Advertisements

PRELIMINAR CONCURRENTE RETROALIMENTACION
Ingeniería de Software II
Guía metodológica para la gestión de proyectos de software en PyMEs que no son fábricas de software por medio de Metodologías ágiles.
Taller de Desarrollo de Proyectos II (75.47) Presentación Inicial ERNESTO GIMENO PABLO BESADA SANTIAGO PETERSEN PATRICIO FAGALDE
Temario El Ciclo de Vida de los Proyectos
Taller de Gestión de Software
Proyecto de Ingeniería de Software 2008
Sistema de Gestión de la Calidad
Evaluación de Productos
6.3 Formalización y cierre del proyecto.
Conclusiones Fase de Construcción Grupo 1.  Objetivos de la Fase  Cumplimientos  Conclusiones Puntos a tratar:
Trabajo Práctico Taller de Desarrollo de Proyectos 2 Septiembre 2009.
Gestión de la Configuración (SCM)
PROCESO DE DESARROLLO. Introducción Mediante esta presentación se pretende describir el proceso de desarrollo del TALLER I.
DESAGREGACION PRELIMINAR DE SUB COMPETENCIAS
Leonora Sistemas S.A. Sistema de Planificación y Control de Ventas (SIPCOV)‏ Patricia Albornoz Labrín.
REQUIREMENTS MANAGEMENT
Conclusiones de Fase de Construcción Grupo 2 – Año 2006.
PLANEACION DEL SISTEMA
Ing. Alexandra García Ing. Patricia Nogales. OBJETIVOS: General Específicos.
El Proceso de Software es la única manera de desarrollar sistemas de calidad. F. o V. Justifica tu respuesta. Que tiene que ver la globalización.
Fundamentos de Ingeniería de Software Facultad de Ingenieria Universidad Distrital Francisco José de Caldas ESPECIFICACIÓN Y MANEJO DE LOS REQUERIMIENTOS.
IIS Evaluación de productos, procesos, recursos Mejorando las predicciones (¿o estimaciones?)
REQUERIMIENTOS DE SOFTWARE
Gestión del cambio.
Unidad VI Documentación
Contexto Proyecto consolidado dentro de la línea de investigación de Sistemas de Información en el Dpto. de Ingeniería en Sistemas de Información de la.
Evaluación de sistemas de cómputo Edna Martha Miranda Chavez Sergio Fuenlabrada Velázquez Sep 2010 BENCH MARK para compra de software de base, herramientas,
Análisis de Sistemas.
Ingeniería de Software: Metodologías Agustín J. González ElO329: Diseño y Programación Orientados a Objeto Adaptado de:
Análisis y diseño detallado de aplicaciones informáticas de gestión
Gestión de la Configuración
¿Cómo nos ayuda GeneXus a mejorar la calidad en el proceso de desarrollo de Software? Ing. Rosario Estévez Ing. Rafael Mon
INGENIERÍA DE SOFTWARE
Ximena Romano – Doris Correa
Fin Fase Elaboración Presentación al director del proyecto Agenda –Objetivos –Cumplimientos –Conclusiones Presentación al director del proyecto Agenda.
GESTION DE LA CONFIGURACION DEL SOFTWARE (GCS/SCM)
PLANEACION DEL SISTEMA
Proyecto de Ingeniería de Software Grupo Nº 9 - GXPost (Desarrollo con GeneXus 8.0) Evaluación de la Fase Construcción (Jueves 4 de Noviembre de.
Evaluación interna Nivel superior (NS)
El rol de SQA en PIS.
Guía metodológica para la gestión de proyectos de software en PyMEs que no son fábricas de software por medio de metodologías ágiles Tatiana Alejandra.
ASIGNACIÓN DE ROLES.
GESTION DE PROYECTOS INFORMATICOS Clase I I I
Grupo 10 – 2008 Proyecto de Ingeniería de Software
La necesidad de sistematizar las experiencias de su trabajo es un aspecto frecuentemente mencionado por muchas personas que trabajan en el campo de desarrollo.
Guía metodológica para la gestión de proyectos de software en PyMEs que no son fábricas de software por medio de metodologías ágiles Tatiana Alejandra.
Roles de Open UP.
MODELAMIENTO VISUAL Y UML
Introducción al proceso de verificación y validación.
MANUAL ESPECIFICO DE FUNCIONES Y DE COMPETENCIAS LABORALES
Estructurar tus ideas para hacerlas realidad
Ciclo de Vida del Software
Ingeniería en Informática F UNDAMENTOS DE C OMPUTACIÓN B ACHILLERATO EN I NGENIERÍA I NFORMÁTICA L IC. C ARLOS H. G UTIÉRREZ L EÓN.
ANGIE PAOLA SOLANO CASTIBLANCO DAR SOPORTE A LOS PROCESOS NORMAS ISO DOC. JOHANA LÓPEZ CHAVEZ SENA 2010.
Evaluación interna Nivel superior (NS)
Proyecto de Ingeniería de Software 2008 Proyecto TITA Soft. Grupo 02.
Introducción a la Administración de Proyectos
6.3 FORMALIZACIÓN Y CIERRE DEL PROYECTO.. PROCESO DE CIERRE DE PROYECTO O FASE  La fase de cierre se inicia cuando se completa la ejecución del proyecto.
EI, Profesor Ramón Castro Liceaga IV. AREAS DE EVALUACIÓN DE LA AUDITORIA EN INFORMÁTICA. UNIVERSIDAD LATINA (UNILA)
PROCESO DE DESARROLLO. Introducción Mediante esta presentación se pretende describir el proceso de desarrollo del TALLER I.
Identificación de entradas, salidas y herramientas de procesos de gestión del PMI Jairo A. Orozco L.
Vigencia de retención: 1 año Modelo de Madurez de la Capacidad Integrado - CMMI Reporte de Seguimiento 14/Sep/2015 al 25/Sep/15 Versión: 1.0 Liberación:
Modelo de procesos de software
TEAM SOFTWARE PROCESS CICLO 1. El software propuesto por el equipo de Ingenium para cumplir con las necesidades planteadas, modela los un conjunto de.
Vigencia de retención: 1 año Modelo de Madurez de la Capacidad Integrado - CMMI Reporte de Seguimiento [Periodo del Reporte] Versión: 1.0 Liberación: 09/03/2015.
UNIVERSIDAD NACIONAL DE CHIMBORAZO Integrante: Jorge Klinger José Chapalbay Fausto Morocha TEMA: GESTIÓN DE LA CALIDAD DEL PROYECTO.
Entregables del Proyecto
Gestión del Alcance del Proyecto
Transcripción de la presentación:

Especificación y Descripción de Liberación. Líneas Base. Fundamentals of CC/UCM for Windows Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Especificación y Descripción de Liberación. Líneas Base. Herramientas para sobrevivir a una iteración A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline. Taller de Gestión de Software 2003  Module 8 – Rebasing Your Work Area

Fundamentals of CC/UCM for Windows Agenda Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Introducción Especificación de la Liberación Descripción de la Liberación Líneas Base A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Fundamentals of CC/UCM for Windows Introducción Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Planifiquemos la iteración… PLAN DE DESARROLLO DE SOFTWARE Como sabemos si terminamos? Y yo que tengo que hacer? PLAN DE VERIFICACION AGENDA DE ENTREGABLES Que es lo que tenemos que implementar? PLAN DE ITERACION Gran cantidad de documentos! Que queremos lograr? A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline. DOCUMENTO DE REQUERIMIENTOS PLAN DE SQA Como vamos a testear?  Module 8 – Rebasing Your Work Area

Especificación de Liberación Fundamentals of CC/UCM for Windows Especificación de Liberación Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Una alternativa… Concentrémonos en la iteración Como sabemos si terminamos? Y yo que tengo que hacer? Que es lo que tenemos que implementar? Especificación de Liberación Que queremos lograr? A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline. Como vamos a testear?  Module 8 – Rebasing Your Work Area

Especificación de Liberación Fundamentals of CC/UCM for Windows Especificación de Liberación Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Es un plan de iteración “concentrado” Tiene solamente: Código y artefactos a liberar Objetivos, como alcanzarlos y medirlos Plan de demostración Procedimientos de demostración A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Especificación de Liberación Fundamentals of CC/UCM for Windows Especificación de Liberación Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Contenido de la Liberación Es la descripción de los productos que se desarrollarán en la iteración Casos de Uso Artefactos A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Especificación de Liberación Objetivos de la Liberación Objetivos ¿Para qué sirve realizar esta Liberación? Criterios a cumplir ¿Qué debe cumplir la Liberación para evaluarla como “buena” Plan de cumplimiento Son las tareas para lograr el cumplimiento de los criterios

Especificación de Liberación Plan de demostración Agenda de actividades Son las tareas que demostrarán que se cumplieron los criterios planteados Responsabilidades del equipo Responsables por el contenido y por las actividades de demostración

Especificación de Liberación Casos de uso a demostrar (Escenarios) Procedimiento de demostración Son las actividades que se van a realizar para demostrar que lo que se propuso para esta Iteración realmente se hizo Trazabilidad con requerimientos Que requerimientos funcionales y no funcionales se cubrirán con la Liberación

Descripción de la liberación Fundamentals of CC/UCM for Windows Descripción de la liberación Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Y al final de la liberación? Comparamos lo que logramos con la especificación. Descripción de la Liberación Especificación de Liberación ITERACION A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Descripción de la liberación Fundamentals of CC/UCM for Windows Descripción de la liberación Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Describe el resultado de la iteración Contiene: Que liberamos y en que línea base Restricciones o limitaciones Resultados de la evaluación Acciones a tomar Que aprendimos A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Descripción de la liberación Contexto Contenido de la Liberación Línea base liberada Métricas de la Liberación

Descripción de la liberación Notas de la liberación Restricciones o limitaciones específicas de la Liberación

Descripción de la liberación Resultados de la Evaluación Justificación para los criterios cumplidos Resultados de los procedimientos de evaluación. Acciones para los criterios no satisfechos Recomendaciones para la próxima liberación Hechos observados en el desarrollo a tener en cuenta para el futuro

Descripción de la liberación Asuntos Destacables Acciones a tomar Soluciones a problemas, detalles faltantes, etc. Se recomienda utilizar una tabla similar a la descrita para las acciones para los criterios no satisfechos.] Resumen de lecciones aprendidas Para tomar en cuenta para próximos desarrollos y Especificaciones de Liberación

Fundamentals of CC/UCM for Windows Líneas Base Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Línea Base: Colección etiquetada de componentes de software y documentación bajo control de configuración que son tratados como una sola unidad (W. Royce) Actualizados, mantenidos, y testeados en conjunto. Se recomienda crear una al final de cada iteración A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Fundamentals of CC/UCM for Windows Líneas Base Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Elemento Línea Base 1 3 2 1 2 3 Versión A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Fundamentals of CC/UCM for Windows Líneas Base Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Ventajas: Una línea base provee un punto estable en que apoyarse. La línea base generada en la iteración anterior es el punto de partida para la iteración actual. Una línea base permite volver hacia atrás en los cambios, en caso que estos sean inestables. Permite reproducir errores, ya que se puede recrear la configuración de una liberación A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Líneas Base : Ideas avanzadas Fundamentals of CC/UCM for Windows Líneas Base : Ideas avanzadas Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) En todo momento existe una línea base recomendada del proyecto. Es la “mejor” de todas La que se usa como base para futuros desarrollos. Las líneas bases pueden llegar a tener estado o “Nivel de promoción” indicando la madurez alcanzada. Construida, Testeada, Liberada, Rechazada, etc. A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Línea Base recomendada Fundamentals of CC/UCM for Windows Línea Base recomendada Objective Explain the concept of a recommended baseline. Key points The recommended baseline is a collection of baselines across all of the components associated with the project. Recommended baselines are project-specific. They are used internally by UCM when a developer: Joins a project Rebases to a recommended baseline. When developers join a project, their development work areas are initialized with the recommended baselines. Developers periodically rebase their development stream with the recommended baseline of the integration stream, synchronizing their development stream with the project’s current baseline. The more often you create baselines, the tighter control you have over the project. As a rule of thumb, you should make a baseline for each full system build or test. Slide animation (Automatic) 1 1 1 1 2 3 Línea base obsoleta 2 2 2 The recommended baseline is the set of baselines the project manager wants the project team to use to rebase their development streams. The project's recommended baseline consists of the newest baseline from each component that is at or over the project's minimum recommended promotion level. The recommended baseline is used by default when developers join or rebase a project. A developer can also choose to rebase to an older baseline. Note: In a typical baseline, the version of one or more elements often does not change. 3 3 3 5 4 4 4 Línea base recomendada 4 4 5  5 5 Module 8 – Rebasing Your Work Area

Fundamentals of CC/UCM for Windows Niveles de Promoción Objective Explain the concept of baseline promotion levels. Key points The promotion level attribute indicates the baseline's stability, test completion, or other quality factor or measurement. Each project has a minimum recommended promotion level. The project manager can select a default promotion level for all of the projects in a PVOB. Slide animation (Automatic) Testeada BL1 Rechazada BL2 Promotion level is a property of a UCM baseline that can be used to indicate the quality or degree of stability of the activities and versions represented by that baseline. Each baseline has a promotion level. When a baseline is created, its promotion level is set to the initial promotion level of the PVOB. After a baseline is created, it is normally built, tested, and perhaps released or rejected. The baseline’s promotion level can be changed to mark these phases. The diagram shows that over time different levels were applied with different quality ratings. Each project has a minimum recommended promotion level. Baselines at or above the minimum recommended promotion level can become the recommended baseline. By default, the minimum promotion level is INITIAL. INITIAL means that each new baseline automatically becomes recommended. If more than one baseline qualifies, the newest baseline is used. Construida BL3  Module 8 – Rebasing Your Work Area

Fundamentals of CC/UCM for Windows Conclusiones Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Especificación de la liberación Permite concentrarse durante la iteración en un solo documento Es un referente para todos los actores Descripción de la liberación Presenta los resultados de la iteración con respecto a lo planteado en la especificación de liberación. Línea base Es una “fotografía” de los artefactos de desarrollo A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area

Fundamentals of CC/UCM for Windows tgsoft01@fing.edu.uy Objective Define the term baseline. Key points A baseline collects versions that should be associated with each other into one identifiable set. UCM baselines are applied across an entire UCM component. This slide shows a baseline marking a set of versions that should be used together. Point out the relationship between version and element. The project manager sets initial baselines. The integrator creates and promotes baselines in the integration stream. Baselines will be covered in more detail in the Managing Project Baselines module of this course. Slide animation (Automatic) Gracias tgsoft01@fing.edu.uy A UCM baseline is a set of selected versions of each element (and their associated activities) within one or more components. Typically created by the project manager or integrator, baselines are stable configurations that serve as: Starting points for creating development streams. Reference and synchronization points during the development effort. For example: At the start of a debugging project, a baseline is created to identify the set of versions that will require debugging. Later in the project, the baseline might identify those versions that successfully passed the testing phase or those that successfully compiled. In the car and truck factory mentioned in Module 1, the baseline would consist of all the individual parts of the car. In the graphic above, each element is represented as a series of numbered circles. Each circle represents a version within the element. The baseline is depicted by the line connecting the appropriate versions. UCM baselines enable you to: Reproduce an earlier release of a software project. Infer an association among the complete set of files related to a project (such as source files, product requirements documents, documentation plans, functional and design specifications, and test plans). Determine the design decisions driving each activity. Note: If a new baseline is created for a UCM project that contains more than one component, new baselines are also created for those components that were modified since the last baseline.  Module 8 – Rebasing Your Work Area