Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.

Slides:



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

By Philippe Kruchten Rational Software
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.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
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.
Rational Worldwide Software Symposium
1 SWE Introduction to Software Engineering Lecture 5.
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.
Principles of Object Technology Module 1: Principles of Modeling.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
UML - Development Process 1 Software Development Process Using UML (2)
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
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.
Rational Unified Process Fundamentals Module 4: Disciplines II.
An Introduction to Software Architecture
University of Utah SoCCS Lecture 61 Architecture – An Introduction CS Lecture 6 Nathan Dykman.
RUP Design RUP Artifacts and Deliverables
Architecting Web Services Unit – II – PART - III.
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.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Software Engineering COSC 4460 Class 4 Cherry Owen.
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 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
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.
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.
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.
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Rational Unified Process (RUP)
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
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
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.
The Web Application Development Process Models
OO Methodology OO Architecture.
The Rational Unified Process (RUP) An Architecture-Centric Process
UML: Unified modeling language
Rational Worldwide Software Symposium
Rational Unified Process
Rational Worldwide Software Symposium
4+1 View Model of Software Architecture
4+1 View Model of Software Architecture
Rational Worldwide Software Symposium
Presentation transcript:

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

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 2

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 3

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) 4

The 4+1 View Model of Architecture 5

1) The Logical View  It is an abstraction of the design model and identifies:  major design packages/subsystems, and  classes 6

The 4+1 View Model of Architecture 7

2) The Implementation View  It addresses the issues of  ease of development,  management of software assets,  reuse 8

The 4+1 View Model of Architecture 3) The Process View  This view illustrates the process decomposition of the system, including the mapping of classes and subsystems on to processes and threads. 9

The 4+1 View Model of Architecture 10

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

12

13

The 4+1 View Model of Architecture 5) 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.  For example as a starting point for tests of an architecture prototype 14

15

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

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. 17