Product Life cycle (RUP)

Slides:



Advertisements
Similar presentations
CSC 480 Software Engineering Lecture 20 Nov 13, 2002.
Advertisements

1 IBM Software Group ® PRJ270: Essentials of Rational Unified Process Module 3: RUP Structure and Navigation.
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.
Static Structure: Process Description
1 The Business Modeling Discipline. 2 Purpose of Business Modeling  To understand the structure and dynamics of the organization in which a system is.
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
Rational Unified Process
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
Requirements Analysis CMPT 371 Fall 2004 J.W. Benham.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
SE 555 – Software Requirements & Specifications Introduction
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
Requirement engineering for an online bookstore system
Object Oriented Analysis and Design Using the UML
Jouhayna Al-Ayoubi SWEN 5230 – Software Project Management.
Slide 1 Requirements Workflow. Slide 2 The Phases/Workflows of the Unified Process Figure 3.1 l Phase is Business context of a step Workflow is Technical.
RUP Requirements RUP Artifacts and Deliverables
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
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
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Requirements Analysis
Rational Unified Process (Part 1) CS3300 Fall 2015.
RUP Implementation and Testing
Chapter – 6. Requirements Capture - Difficult A System has many Users. Each of them know what to do but no one knows the entire picture. Users do not.
Volunteer Management System Presented by Team SE18-08S.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Object Oriented Design and Analysis Rational Unified Process.
Chapter 3 – The Analysis Workflow CSC532: Fall 2003 Original presentation by Joshua Hughes Zehra Raoshan Kiran Balagani Guang Li This presentation will.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
Chapter 7 Applying UML and Patterns Craig Larman
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
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.
UML-1 3. Capturing Requirements and Use Case Model.
Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 Use Case 1 what are use cases? “A specification of sequences of actions, including variant.
UML-1 8. Capturing Requirements and Use Case Model.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
Gerhard Dueck -- CS3013Requirements Capture 1  From Vision to Requirements  Why it is difficult?  Developers are not users  Inadequate requirements.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
UML Diagrams for Caradon developers Daniel DG Moth Core Development Group, Research Student University of Brighton, MSc Object Oriented Software Technology.
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
Requirements Analysis
Business Modeling and Analysis
CONNECTING COMPONENT Pertemuan Matakuliah: M Analisis dan Perancangan Sistem Informasi Lanjut Tahun:
Requirement Discipline Spring 2006/1385 Semester 1.
BMC Software Confidential Copyright 2002 All rights reserved. Usability Design using “The Bridge” March 2004.
Lecture 5 Introduction to Use Case Analysis and the Analysis Model Introduction to the UML.
Documenting Software Architectures. Outline  Introduction  Uses of Architectural Documentation  Views  Choosing the Relevant Views  Documenting a.
Requirement Engineering Management Amna Shifia Nisafani Feby Artwodini M. Department of Information Systems Subject : Requirement Engineering.
Enterprise Use Cases CCB December 10, Agenda Enterprise Use Case Status Report Enterprise Use Case Artifacts Enterprise Use Case Development Process.
INCOSE Usability Working Group
Topic for Presentaion-2
Requirements Elicitation and Elaboration
Unified Process Source & Courtesy: Jing Zou.
Requirements Elicitation – 1
Introduction to Software Engineering
Chapter 1 (pages 4-9); Overview of SDLC
Other Requirement Artifacts
Requirements Very High level specification of what system should do
Problem Statement. : Team Name. :. Team Leader Name. :
Software Development Process Using UML Recap
Requirements “Content Guide”
Presentation transcript:

Product Life cycle (RUP)

Requirements workflow CSC532: Fall 2003

Outline Introduction. Capture requirements. Artifacts. Workers. Activities. Next step.

Introduction The fundamental principle. Difficulties. - communication. - articulation. - clarity.

Capture requirements Reach agreement on system context - Domain model - Business Model - Use case diagrams List candidate requirements Identify and negotiate functional requirements Specify non-functional requirements

Artifacts. Domain model Business model Glossary Actor Use case User-interface prototype Use case model Architecture description Supplementary requirements

Artifacts

Workers System Analyst. Use case specifier User-interface designer architect

Activities Build domain model Build business model Find actors and use cases Prototype the user interface Prioritize the use cases Detail a use case Structure the use case model

Activities