By Usabilidad de rup gy juniorflgtiS gexa6pR 03, 2010 8 pagos INGENIERÍA DE SOFTWARE Rational Unified Process RUP Rubby Casallas Departamento de Sistemas y Computación Facultad de Ingeniería Universidad de los Andes Referencias 2 http://vww. rational. c http://www-306. ibm. Unified Process: An I Wesley Professional; Agenda org oduct rup/ The Rational chten. Addison 0) Introducción Principio 1: Iterativo e incremental Disciplinas y Actividades Principio 2: Guiado por los casos de uso Principio 3: Centrado en la arquitectura Introducción: Principios 4 CONSTRUCCION TRANSICION Cuatro grandes fases.
Al final del ciclo debe haber un producto funcionando que satisface un conjunto de casos de uso Propósito de las fases 10 INICIO Definir los objetivos del ciclo ELABORACION Definir la arquitectura del producto Desarrollar el producto Liberar el producto Definir la arquitectura del Implementation Se hace un plan de fases Se identifican los principales casos de uso Se identifican los riesgos Test Deploy Iteraciones en la fase de Elaboración Business Modeling Requirements Analysis & Design Implementation Test Deploy Se hace un plan de proyecto Se completan los casos de uso Se liminan los riesgos Iteraciones en la fase de Construcción 18 Implementation Test Se elabora un producto totalmente operativo y eficiente Se escribe el manual de usuario Deploy Iteraciones en la fase de Transición 19 Se implanta el producto en el sitio del cliente Se entrena a los usuarios. 31_1f8 http://www- 128. ibm. co m/develo pe rwo rks/rationa ry/5383 -html Ejemplo de un flujo de trabajo detallado 26 Tomado de: http://www-128. ibm. com/developerworks/rational ‘library/5383. tml 27 Artefactos Roles Tareas 28 Analyst n Business Process Analyst Business Designer Business-Model Reviewer C] Requirements Reviewer C] System Analyst C] Use-Case Specifier Cl User-lnterface Designer Developer C] Architect Ü Architecture Reviewer C] Capsule Designer Code Reviewer n Database Designer Cl Design Reviewer C Designer C] Implementer C] Integrator Roles (cont. ) 29 de Uso 36 Roles y Casos de Uso 37 Rastreabilidad de los Casos de Uso 38 «trace» Caso de Uso Realización de Diseño Realización de Análisis «trace» Pruebas Unitarias pruebas Funcionales x Caso de Prueba [The Unified Software Development Process. l. Jacobson, G. Booch and J. Rumbaugh.
Addison-Wesley] 39 Introducción Principio 1: Iterativo e incremental C] Disciplinas y Actividades C Principio 2: Guiado por los Artifacts Produced* Business Modeling 47 (Business Understanding) 1. 2. For initial iteration, ELICIT Business Rules, Business Needs, Business Understanding ; for all subsequent x iterations DETAIL Business Rules, Needs, Understanding For initial iteration, IDENTIFY all significant Business Use-Cases, Specifications, Models, Rules, Vision, and Architecture; for all subsequent x iterations DETAIL Business Use-Cases, Specifications, Models, Rules, Vision, Architecture Target Organizational Assessment Document, Business Glossary
Document, Business Rules Document, Business UseCase Model, Business Vision, Object Model, Business Architecture Document, Supplementary Business Specification, Business Glossary Requirements (User/System Requirements Gathering) For initial iteration, ELICIT Requirements (Requests), & Rules; for all subsequent x iterations DETAIL Requirements (Requests), & Rules. For initial iteration, IDENTIFY all significant Use-Cases and classify by risk; for all subsequent x iterations DETAIL Use-Cases (high risk Usecases first), Specifications, Models, Realizations to match all Iower-level Analysis Classes and Analysis Diagrams nd higherlevel Business Rules, & Requests. PRIORITIZE or REPRIORITIZE USE-CASES by RISK.
Stakeholder Requests Requirements Management Plan, Supplementary Specification, Use-Case Specification, Use- Case Model, Glossary, So Storyboard, Use-Case Pack ments Specification, s, User Interface Packages, Charts, Realizations, Definitions, & Analysis Models to match all Iower-level Design Class Diagrams and higherlevel Use-Case Models. For initial iteration, CREATE Sequence Diagrams, Analysls Classes, Analysis packages, Charts, Realizations, Definitions, & Analysis Models; for all subsequent iterations DETAL Sequence Diagrams, Classes, Packages, Charts, Realizations, Definitions, & Models to match all Iower- level Design Class Diagrams and higherlevel Use-Case Models. For initial iteration, CREATE Design Classes & Class Diagrams; for all subsequent x iterations ns DETAIL Design Classes & Class Diagrams to match all higher-level Analysis Classes, Diagrams, & Models. For initial iteration, CREATE Data Models; for all subsequent x iterations DETAL Data Models.
Communication Diagrams, Object Diagrams, Sequence Diagrams, State Charts, Activity Diagrams, Package Diagrams, Class Diagrams, Software Architecture Document, Deployment Model, Analysis Model, Design Model, Proof-ofConcept Prototype, UseCase Realizations, Design Packages, Subsystem Design Packages, Design Classes, Unit Test Classes, Analysis Classes, Data Models, Data Definitions Process Disciplines Steps Human Actions 49 Implementation (Process Modeling) 10. Test Log, Test Guidelines, Test Classes, Test Components, Test Interface Specification, Test Automation Architecture, Test Environment Configuration Deployment 50 (Environmental Modeling) 12. 13.
For initial iteration, CREATE Deployment Diagrams, Builds, Instructions, Plans, Notes, Releases; for all subsequent x iterations DETAIL Deployment Diagrams, guilds, Instructions, Plans, Notes, Releases. For initial iteration, CREATE Component Diagrams, Builds, Instructions, Plans, Notes, Releases; for all subsequent x iterations DETAIL Component Diagrams, Bullds, Instructions, Plans, Notes, Releases. Deployment Diagrams, Alpha Software Build Releases, Beta Software Build Releases, Versioned Software Build Releases, Release Notes, Deployment Plan, Bill of Materials, Installation Instructions, End-User Support Material, Training Materials, Artwork process Disciplines 81_1f8
