RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW

OVERVIEW INTRODUCTION TO RUP FULL LIFECYCLE APPROACH NINE DISCIPLINES OF RATIONAL EIGHT PRINCIPLES OF RATIONAL THREE CONTENT ELEMENTS OF RATIONAL RUP VS. SCRUM AND EXTREME PROGRAMMING AGILE UNIFIED PROCESS BEST PRACTICES Unified Process Test-Driven Development (TDD) Unified Modeling Language (UML)

INTRODUCTION ITERATIVE AND INCREMENTAL RATIONAL SOFTWARE CORPORATION IN LATE 1990S COVERS BUSINESS MODELING TO CODING PRACTICES USES MODELING CONSTRUCTS OF UML FOR ARCHITECTURE PROVIDES PROCESS AND PROCESS FRAMEWORK FOR SOFTWARE DEVELOPMENT

FULL LIFECYCLE APPROACH LIFECYCLE PHASES SIMILAR TO WATERFALL 1. INCEPTION 2. ELABORATION 3. CONSTRUCTION 4. TRANSITION ITERATIVE DEVELOPMENT WITHIN EACH PHASE INCREMENTAL BUILDS ITERATION TO ITERATION Inception Validate costs and budget Create business cases Develop use cases and plan Elaboration Mitigate key risks; revise business case Create architectural foundation – executable Use-case model 80% complete Construction Build the system Develop components First external release Transition Deploy to production Communicate use to end-user Conduct beat-testing Lifecycle Objectives Milestone Lifecycle Architecture Milestone Initial Operational Milestone Product Release Milestone

NINE DISCIPLINES OF RATIONAL Business modeling Requirements Analysis and design Implementation Test Deployment Engineering Disciplines Configuration and Change Management Project Management Environment Supporting Disciplines

EIGHT PRINCIPLES OF RATIONAL RUP PrincipleRelated Principle Attack risks early and continuously Satisfy customer through early and continuous delivery Ensure you deliver value to your customerWorking software is primary measure of success Stay focused on executable softwareDelivery working software frequently Accommodate change early in the project Welcome changing requirements, even late in development Baseline an executable architecture early onEnterprise Architecture Build your system with componentsDRY Work together as one teamBusiness people and developers work together Make quality a way of life, not an afterthoughtGive continuous attention to technical excellence Agile ManifestoPragmatic ProgrammingAgile

CONTENT ELEMENTS ElementTypeDescription RolesWho?Set of related skills, competencies and responsibilities Work Products/ArtifactsWhat?Results of a task, including documents and models Tasks/ActivitiesHow?Units of work assigned to a Role

RUP VS. SCRUM/XP Detailed and specialized Based on Unified Process UML companion references Role responsibility for artifacts Defined team interactions Specific engineering guidance Applicable to broader audience Tool recommendations Team members all equal Incremental and Iterative Rational Unified Process Scrum/XP

AGILE UNIFIED PROCESS DEVELOPED BY SCOTT AMBER FOCUS ON LIGHT-WEIGHT UML MODELING SIMPLIFIED VERSION OF UNIFIED PROCESS COMMON TECHNIQUES: TEST-DRIVEN DEVELOPMENT (TDD) AGILE CHANGE MANAGEMENT DATABASE REFACTORING

BEST PRACTICES DEVELOP ITERATIVELY MANAGE REQUIREMENTS USE COMPONENTS MODEL VISUALLY VERIFY QUALITY CONTROL CHANGES

ASSESSMENT QUESTION #1

ASSESSMENT QUESTION #2

ASSESSMENT QUESTION #3

ASSESSMENT QUESTION #4

ASSESSMENT QUESTION #5