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

Slides:



Advertisements
Similar presentations
Requirements Engineering Process
Advertisements

CS3773 Software Engineering Lecture 03 UML Use Cases.
1 Use Cases 2 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 20, 2004.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” - may be of.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Object Oriented Analysis Process
COMP1007 Intro to Systems Requirements © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Intro to System Requirements Lecture 2 Use-Cases.
Functional Requirements – Use Cases Sriram Mohan/Steve Chenoweth (Chapters 14, 21 – Requirements Text) 1.
1 UML Component and Deployment Diagrams. Models, Views, and Diagrams Use Case Diagrams Use Case Diagrams Use Case Diagrams Scenario Diagrams Scenario.
A use case describes one “case” of how a user can use the system.
Requirements Analysis 4. 1 Use Case I b504.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Use-Cases.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
UML Notations Activity diagrams State diagrams Class diagrams Use-case diagrams.
Object-Oriented Analysis and Design
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 System and Software Engineering.
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
Principles of Object Technology Module 1: Principles of Modeling.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
RUP Requirements RUP Artifacts and Deliverables
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
CS 4310: Software Engineering Lecture 3 Requirements and Design.
From Problem Statement to Design
1 Requirements Modeling using UML 2.0 Use Cases. 2 Requirements Engineering Software Lifecycle Activities System Engineering Requirements Analysis Software.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 10: Structure the Use-Case Model.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Faculty of Computer & Information Software Engineering Third year
Chapter 6 A Use-Case-Driven Process. 2 Definitions The choice of models and the choice of techniques used to express them have a significant impact on.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
What state are we in?. What are the two main parts of a computer program? – Data – Algorithms We have previously emphasized – how real-world information.
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.
Faculty of Computer & Information
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki 1 Machine Learning.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
1 Use Case Modeling Reference: RUP Doc. Use Case Example 2.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
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.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Unit-3 Identifying use cases Object Analysis Classification
UML (Unified Modeling Language)
UML - Development Process 1 Software Development Process Using UML.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Coming up: Unified Modeling Language Introduction.
Requirement Discipline Spring 2006/1385 Semester 1.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Introduction to the Unified Modeling Language.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
State Diagrams What state are we in?.
Requirements Engineering Process
Recall The Team Skills Refining the Use cases
The Rational Unified Process (RUP) An Architecture-Centric Process
“Unified Modeling Languge“ Class Diagram
Agile Methodologies Course Title: Advanced Software Engineering
Software Design Lecture : 15.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Presentation transcript:

Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational Unified Process (RUP) A Use-Case-Driven Process

Definitions  In this Lesson:  we focus primarily on one method of understanding and modeling the problem.  An effective method, and one  recommended by the RUP,  is the technique of use-case modeling 2

Definitions  Use cases:  provide a means of expressing the problem in a way  that is understandable to a wide range of stakeholders:  users,  developers, and  customers 3

Organizing Use Cases There are three ways to exploit commonality among use cases:  Inclusion  Extension  Generalization/specialization 4

Organizing Use Cases- Inclusion  Several use cases can include a common flow- of-event text organized as a use case.  In the ATM example, both Withdraw Money and Check Balance include "User enters PIN."  There is no need to express the flow of events associated with the entry of the PIN two or three times in the same model.  Both use cases could include a use case "Authenticate the User." 5

6 Organizing Use Cases- Inclusion

 The extension can be thought of as:  "injecting" additional descriptive text  into the extended use case,  at the extension point,  under particular conditions. 7 Organizing Use Cases- Extension

Unlike "include"  in which the basic flow of events is incomplete without the inclusion,  when you use "extend," the basic flow of events should still be complete; 8 Organizing Use Cases- Extension

 A use case can specialize more general one by  adding to or  refining the original flow of events.  For example, in an air traffic control system,  the Entry of an ICAO Flight Plan follows  the same basic principles and sequences of actions as the general Entry of a Flight Plan  but has some refinements as well as specific steps or attributes 9 Organizing Use Cases- Generalization

10

 The Rational Unified Process is a use-case-driven approach.  This means that the use cases defined for a system are the basis for the entire development process 11 Use Cases in the Process

12 Use Cases in the Process

13 Use Cases in the Process