The Rational Unified Process (RUP) An Architecture-Centric Process

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

4+1 View Model of Software Architecture “Software architecture” course Presented By: Mazeiar Salehie October 2004.
Outline About author. The problem that discussed in the article.
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.
Rational Worldwide Software Symposium
1 SWE Introduction to Software Engineering Lecture 5.
Iterative development and The Unified process
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
Comp 245 Data Structures Software Engineering. What is Software Engineering? Most students obtain the problem and immediately start coding the solution.
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.
Rational Unified Process Fundamentals Module 4: Disciplines II.
University of Utah SoCCS Lecture 61 Architecture – An Introduction CS Lecture 6 Nathan Dykman.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
Architectural Blueprints The “4+1” View Model of Software Architecture
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
10 Software Architecture CSCU 411 Software Engineering.
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.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
An Architecture-Centric Process
The Rational Unified Process 1 EECS810: Software Engineering.
PRJ566 Project Planning & Management Software Architecture.
Introduction to OOAD & Rational Rose cyt. 2 Outline RUP OOAD Rational Rose.
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.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Configuration.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Introduction to Rational Unified Process
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Rational Unified Process (RUP)
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
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Wrap up. Structures and views Quality attribute scenarios Achieving quality attributes via tactics Architectural pattern and styles.
Process 4 Hours.
The Web Application Development Process Models
OO Methodology OO Architecture.
University of Central Florida COP 3330 Object Oriented Programming
UML: Unified modeling language
Recall The Team Skills Analyzing the Problem (with 5 steps)
Rational Worldwide Software Symposium
Rational Unified Process
Rational Unified Process (RUP)
Rational Worldwide Software Symposium
SWEN 5230 Your Project Title
4+1 View Model of Software Architecture
4+1 View Model of Software Architecture
Applying Use Cases (Chapters 25,26)
Applying Use Cases (Chapters 25,26)
Rational Worldwide Software Symposium
From Use Cases to Implementation
Presentation transcript:

The Rational Unified Process (RUP) An Architecture-Centric Process Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki

The Importance of Models A large part of the RUP focuses on modeling. Models help us understand both the: problem and solution. The model is not the reality but best models are ones that stick very close to reality

Architecture Suppose the task: describing a system so that designers, programmers, users, and managers would be able to do the following: Understand what the system does Understand how the system works Be able to work on one piece of the system Extend the system Reuse part of the system to build another one

Architecture Multiple Views For a building, different types of blueprints are used to represent different aspects of the architecture: Floor plans Elevations Electrical cabling Water pipes, central heating, and ventilation The look of the building in its environment (in sketches)

The 4+1 View Model of Architecture

The 4+1 View Model of Architecture The Logical View It is an abstraction of the design model and identifies: major design packages/subsystems, and classes

The 4+1 View Model of Architecture

The 4+1 View Model of Architecture The Implementation View It addresses the issues of ease of development, management of software assets, reuse

The 4+1 View Model of Architecture The Process View the concurrency and synchronization aspects of the design

The 4+1 View Model of Architecture The Deployment View Addresses: how the various executables and other runtime components are mapped to the underlying platforms or computing nodes.

The 4+1 View Model of Architecture The Use-Case View It contains a few key scenarios or use cases. Initially, are used to drive the discovery and design of the architecture in the inception and elaboration phases, later they will be used to validate the different views.

An Architecture-Centric Process RUP defines two artifacts related to architecture: The software architecture description (SAD), which describes the architectural views relevant to the project The architectural prototype, which serves to validate the architecture and serves as the baseline for the rest of the development

An Architecture-Centric Process These two key artifacts are the roots of three others: Design guidelines Product structure The development environment is based on the implementation view. Team structure is based on the structure of the implementation view.