Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.

Slides:



Advertisements
Similar presentations
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Advertisements

CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
Practical Business Modeling in the Unified Process Tom Morgan Software Architect, Fidelity National Information Services
Requirements wg RUP Materiały na seminarium „Metodyki tworzenia SI” Wykonał Marcin Wiącek Styczeń 2006 Wojskowa Akademia Techniczna Wydział Cybernetyki.
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
Rational Unified Process
Use-case Modeling.
Systems Analysis and Design in a Changing World, Fourth Edition
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Documenting Requirements using Use Case Diagrams
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
A use case describes one “case” of how a user can use the system.
Use Cases: The Technique
SwE 313 Introduction to Rational Unified Process (RUP)
SE 555 Software Requirements & Specification Requirements Analysis.
Recall The Team Skills Analyzing the Problem
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Jouhayna Al-Ayoubi SWEN 5230 – Software Project Management.
RUP Requirements RUP Artifacts and Deliverables
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
RUP Fundamentals - Instructor Notes
Object-Oriented Analysis - Instructor Notes
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Rational Unified Process (Part 1) CS3300 Fall 2015.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
1 Objectives  Describe design constraints.  Identify methods of specifying functional requirements.  Describe techniques for writing and structuring.
From Use Cases to Test Cases 1. A Tester’s Perspective  Without use cases testers will approach the system to be tested as a “black box”. “What, exactly,
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
(c) Addison Wesley Copyright © 2000 by Addison Wesley Version 1.0
1 Modeling System Requirements with Use Cases. 2 Why Do We Need Use Cases? Primary challenge in a system design process –ability to elicit correct and.
Rational Unified Process Fundamentals Module 3: Disciplines I.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Unit-3 Identifying use cases Object Analysis Classification
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
UML - Development Process 1 Software Development Process Using UML.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Use Case Model Use case description.
Requirement Discipline Spring 2006/1385 Semester 1.
Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
PART II INCEPTION Chapter 4 Inception is Not The Requirements Phase.
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
Requirement Engineering Management Amna Shifia Nisafani Feby Artwodini M. Department of Information Systems Subject : Requirement Engineering.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 9 Use Cases.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Engineering Quality Software
Use Case Modeling Part of the unified modeling language (U M L)
Software Development Process Using UML Recap
Presentation transcript:

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Chapter 6 Requirements

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Introduction Requirement Management is a systematic approach to: –Eliciting, organizing, and documenting the requirements of the system –Establishing and maintaining agreement between the customer and the project team on the system’s changing requirements Requirement Artifacts –Use Case Model –Supplementary Specification –Glossary

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Requirements and Iterative Development

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Requirements Overview Two workflow details: 1.Define the System –The scope of the system is established and documented in the use-Case Model –Concentrates on the requirements “big Picture” 2.Refine the System Definition –Concentrates on the details of the Use Cases being addressed in the current iteration, and on refining the overall system definition, where neccessary

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Requirement Discipline Overview Diagram

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Workflow detail: Define the system Objectives: –To initially define what is to be included in the system, and what is not –Activity: Capture a Common Vocabulary Find Actors and Use Cases Prioritize Use Case Review the requirements

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Define the System Workflow Detail Overview Diagram

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Capture a Common Vocabulary Overview: –To define a common vocabulary that is used during the development of the system Input Artifacts: –Use-case Model –Vision Resulting Artifacts: –Glossary Steps: –Identify Common Terms

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Find Actors and Use Cases Overview: –To define the scope of the system by describing what will be handled by the system what will be handled outside the system Who and what will interact with the system Input Artifacts: –Glossary –Use-case Modeling Guidelines –Vision Resulting Artifacts: –Supplementary Specifications –Use Case Model

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Find Actors and Use Cases (2) Steps: –Find actors –Find use cases –Collect supplementary requirements –Describe how actors and use Cases Interact –Package Use Cases and Actors

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Online Auction Application Actors

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Actors” Package in the Use Case Model Structure

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Use Cases” Package in the Use Case Model Structure

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Interaction between Initial Actors and Use Cases in the Online Auction Application

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Prioritize use Cases Overview: –To define the relative priority of the Use Cases, which then drives the content and planning of the iterations Input Artifacts: –Risk List –Software Architecture Document –Use-case Model –Vision Resulting Artifacts: –Use Case Priority List –Software Architecture Document Steps: –Prioritize the Use Cases –Update the Software Architecture Document

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Review the Requirements Overview: –To review the common terms, system scope, and relative priorities before detailing the system requirements Input Artifacts: –Glossary –Risk List –Supplementary specification –Use-case Model –Use-case Modeling Guidelines –Use Case priority List –Vision Resulting Artifacts: –Change Request –Review Record Steps: –Conduct the Review

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Workflow detail: Refine the System Definition Objectives: –Refining the initial system definition to gain a deeper understanding of the requirements –Primary Output: A detailed set of Use Cases A refined Supplementary Specification (possibly) A restructured Use-Case Model

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Refine the System Definition Workflow Detail Overview Diagram

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Detail a Use Cases Overview: –To add a detailed content to the use-case description Input Artifacts: –Glossary –Supplementary Specification –Use-case Model –Use-case Modeling Guidelines –Vision Resulting Artifacts: –Supplementary Specifications –Use Case Model

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Detail a Use Cases (2) Steps: –Detail the flows of events of the use cases –Describe the special requirements of the use case –Describe preconditions of the use case –Describe postconditions of the use case

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Use Cases Specification in the Use Case Model Structure

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 “Close Auction” Use Case Local Use Case Diagram

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Structure the Use Case Model Overview: –To extract common, optional, and exceptional behavior from existing Use Cases and create new Use Cases –Additional actors may also be identified –This activity is optional Input Artifacts: –Glossary –Supplementary Specification –Use-case Model –Use-case Modeling Guidelines

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Structure the Use Case Model (2) Resulting Artifacts: –Use Case Model Steps: –Structure the Use Cases –Structure the Actors

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 An Include Relationship Between Use Cases

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 An Extend Relationship Between Use Cases

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Generalized Actor in the Online Auction Application

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared by Agus Widodo D2098 Activity: Review the Requirements Overview: –To review the detailed requirements before moving on to the analysis of these requirements Input Artifacts: –Glossary –Supplementary specification –Use-case Model –Use-case Modeling Guidelines –Vision Resulting Artifacts: –Change Request –Review Record Steps: –Conduct the Review