Rational Unified Process Fundamentals Module 4: Disciplines II.

Slides:



Advertisements
Similar presentations
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Advertisements

® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 4: Phase Management - Elaboration.
Rational Unified Process Software Engineering Lab. Summer 2006.
Mastering Object-Oriented Analysis and Design with UML Module 4: Analysis and Design Overview.
PRJ270: Essentials of Rational Unified Process
Rational Unified Process
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 Chapter 2 Text Introduction to Rational Unified Process Modified.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
Unified Software Practices v 5.0 Copyright  1998 Rational Software, all rights reserved 1 R Introduction to Rational Unified Process.
SwE 313 Introduction to Rational Unified Process (RUP)
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Iterative development and The Unified process
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Object Oriented Analysis and Design Using the UML
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 19 Chapter 2 Text Introduction to Rational Unified Process.
RUP Requirements RUP Artifacts and Deliverables
UML - Development Process 1 Software Development Process Using UML (2)
Rational Unified Process
1 IBM Software Group ® PRJ270: Essentials of Rational Unified Process Module 4: RUP Content.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
RUP Fundamentals - Instructor Notes
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
RUP Implementation and Testing
An Introduction to Software Architecture
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
RUP Design RUP Artifacts and Deliverables
Identify steps for understanding and solving the
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
Object Oriented Design and Analysis Rational Unified Process.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Unified Software Practices v 5.0 Copyright  1998 Rational Software, all rights reserved 1 R Introduction to Rational Unified Process Adapted by Dr. Spiegel.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
RUP Life Cycle Software Engineering Learning Programme Software Engineering Foundation.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 Chapter 2 Text Introduction to Rational Unified Process.
Rational Unified Process Fundamentals Module 3: Disciplines I.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
Introduction to OOAD & Rational Rose cyt. 2 Outline RUP OOAD Rational Rose.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 9: Describe the Run-time Architecture.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
The principles of an object oriented software development process Week 04 1.
Introduction to Rational Unified Process
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Rational Unified Process Fundamentals Module 3: Core Workflows I - Concepts Rational Unified Process Fundamentals Module 3: Core Workflows I - Concepts.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
4+1 View Model of Software Architecture
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
OOAD Using the UML - Describe Concurrency, v 4.0 Copyright  Rational Software, all rights reserved 1 R Thread Process X Thread Process ZProcess.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Process 4 Hours.
Unified Process Source & Courtesy: Jing Zou.
Recall The Team Skills Analyzing the Problem (with 5 steps)
Rational Unified Process
4+1 View Model of Software Architecture
4+1 View Model of Software Architecture
Presentation transcript:

Rational Unified Process Fundamentals Module 4: Disciplines II

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 2 Objectives  Understand discipline concepts for:  Analysis & Design  Test  Implementation  Deployment  Configuration & Change Management

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 3 Disciplines

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 4 Discipline: Analysis & Design  Purpose:  To transform the requirements into a design of the system-to-be  To evolve a robust architecture for the system  To adapt the design to match the non- functional requirements and the implementation environment  Design is a refinement of analysis  Primary artifact is Design Model

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 5 The Design Model Artifact:  Consists of a collection of models that collaborate to describe the structure and behavior of the system.  Is an object model describing the realization of use cases.  Serves as an abstraction of the implementation model and its source code.  Is used as essential input to activities in implementation and test.

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 6 Use Cases Drive Analysis & Design Supplementary Specifications Use-Case Model Design Model Data Model Architecture Document Analysis and Design Analysis Model (optional)

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 7 Analysis & Design Considerations  Transform requirements into classes and subsystems  Adhere to constraints of  Nonfunctional requirements  Implementation environment  Design the database  Mapping the design model to a data model  Identify components  Subsystems and interfaces

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 8 Use-Case Realization in Analysis & Design Use Case (Use-Case Model) Use-Case Realization (Design Model) > Class Diagrams Sequence Diagrams Collaboration Diagrams Use Case

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 9 Use-Case Analysis & Design  The complete behavior of a use case is allocated to collaborating classes

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 10 Sample UML Class Diagram A University Course Registration System MainForm // select maintain schedule() > MaintainScheduleForm + // open() + // select 4 primary and 2 alternate offerings() > CourseCatalogSystem // get course offerings() > 10..* RegistrationController // add courses to schedule() // get course offerings () > 1 1 Schedule // create with offerings() >

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 11 Purposes of Architecture  Intellectual control  Basis for reuse  Basis for project management

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 12 Architecture: Intellectual Control  Architecture is used for different things by various stakeholders  Customer: visualize what they are buying  Project manager: scheduling and resource allocation  System analyst: organize requirements  Developer: understand boundaries of their chunk of the project  Software architect: reason about evolution or reuse  Multidimensional reality (i.e. multiple views)  Multiple views: functional, implementation, dynamic, structural, spatial (physical distribution), etc.

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 13 Intellectual Control: Architecture Views Conceptual Physical Process ViewDeployment View Logical View Use-Case View Implementation View End-user Functionality Programmers Software management Performance Scalability Throughput System integrators System topology Delivery, installation communication System engineering Analysts/Designers Structure

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 14 Architecture: Basis for Reuse  The structural elements and interfaces which compose the system  The behavior seen in the collaboration of these elements  The composition of these elements into progressively larger subsystems

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 15 Architecturally Significant Elements  Not all design is architecture  Main business classes  Important mechanisms  Processors and processes  Layers and subsystems  Architectural views = slices through models

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 16 Architecture: Basis for Project Management  Architecture Milestone in Elaboration phase is the Lifecyle Architecture milestone  Architecture primarily results from Analysis & Design  Architecture in phases and iterations:  It drives the risk mitigation of iterations  Architecture baseline is an exit criterion for Elaboration

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 17 Discipline: Test  Purpose: Testing focuses primarily on the evaluation or assessment of quality realized through a number of core practices:  Finding and documenting defects in software quality.  Generally advising about perceived software quality.  Proving the validity of the assumptions made in design and requirement specifications through concrete demonstration.  Validating the software product functions as designed.  Validating that the requirements have been implemented appropriately.  Test discipline acts in many respects as a service provider to the other disciplines.

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 18 Artifacts of Test Discipline

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 19 Workflow Detail: Define Evaluation Mission For each Iteration:  Identify the objectives for and deliverables of the testing effort  Identify a good utilization strategy for test resources  Define the scope and boundaries for the test effort  Outline the approach that will be used  Define how progress will be monitored and assessed Define Evaluation Mission Roles responsible for related activities:  Test Manager (mainly)  Test Analyst  Test Designer

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 20 Concept: Test Automation and Tools  Data acquisition tools  Static measurement tools  Dynamic measurement tools  Simulators or Drivers  Test management tools

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 21 Implementation Model Discipline: Implementation  The purposes of Implementation are:  To implement classes and objects in terms of components  To define the organization of the components in terms of implementation subsystems  To test the developed components as units  To create an executable system  Implementation results in an Implementation Model.

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 22 What Is an Implementation Model? Trading Services Telephone Banking A B > Components and implementation subsystems in a Telephone Banking System.  An Implementation Model consists of:  Components  Implementation Subsystems  Components include:  Deliverable components, such as executables  Components from which the deliverables are produced, such as source code files

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 23 Concept: Build  Operational version of a system or part of a system  Demonstrates a subset of the capabilities provided in the final product  Integral part of the iterative lifecycle  Provides review points  Helps uncover integration problems as soon as they are introduced

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 24 Discipline: Deployment  Purpose: Manage the activities associated with ensuring that the software product is available for its end users, such as:  Product deployment  Testing at the installation and target sites  Beta testing  Creating end-user support material  Creating user training material  Releasing to customer (in the form of shrink- wrapped package, download site, etc.)

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 25 Use Cases and End-User Documentation Use-Case Model Deployment End-User Support Material User’s Guide Online Help Demos Tutorials Training Material Supplementary Specification

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 26 Discipline: Configuration & Change Management  Purpose: Track and maintain integrity of project artifacts  Change control  Configuration identification and management  Configuration status accounting  Change tracking  Version selection  Software manufacture  Workspace management

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 27 The Configuration and Change Management (CCM) Cube

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 28 Configuration Management (CM)  Describes the product structure (logically correct configurations)  Identifies which artifacts are to be tracked  Identifies dependencies among artifacts  Maintaining traceability between artifacts  Isolate individual and team workspaces

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 29 Change Request Management (CRM) Addresses:  The capture and management of requested changes to one or more artifacts by various stakeholders.  A change request has a lifecycle: new, logged, approved, assigned and complete.  Not all change requests are acted on. The potential impact of a proposed change determines if it will be acted on.

Rational Unified Process Fundamentals Copyright © Rational Software, all rights reserved 30 Configuration Status Accounting  This type of accounting describes the state of the product based on the type, number, rate, and severity of defects found and fixed during the course of product development.  Metrics derived under this aspect, either through audits or raw data, are useful in determining the overall completeness status of the project.  Problem areas that require attention