Copyright  2001 - Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.

Slides:



Advertisements
Similar presentations
Testing Workflow Purpose
Advertisements

Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
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
Rational Unified Process Software Engineering Lab. Summer 2006.
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 470 Software Development Processes James Nowotarski 21 April 2003.
Copyright  Larry Dribin, Ph.D. SE470_ProjMgmt_v1.ppt SE470 - ProjMgmt - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Unified Software Practices v 5.0 Copyright  1998 Rational Software, all rights reserved 1 R Introduction to Rational Unified Process.
SE470 - Rational Unified Process Overview
Copyright  Larry Dribin, Ph.D. SE470_RUP_v1_1.ppt Software Engineering SE470 - RUP - 1 Excellence in Software Engineering Repeatable Level Defined.
SwE 313 Introduction to Rational Unified Process (RUP)
Copyright  Larry Dribin, Ph.D. SE470_Overview_v1.ppt SE470 OV - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level.
Rational Unified Process – Part 2
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
RUP Requirements RUP Artifacts and Deliverables
UML - Development Process 1 Software Development Process Using UML (2)
Rational Unified Process
1 IBM Software Group ® PRJ270: Essentials of Rational Unified Process Module 4: RUP Content.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
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
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
LECTURE 1 What does a Business Analyst do? IFS 231 Business Analysis.
RUP Implementation and Testing
Rational Unified Process Fundamentals Module 4: Disciplines II.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
SWE © Solomon Seifu CONSTRUCTION. SWE © Solomon Seifu Lesson 13-2 Testing.
Object Oriented Design and Analysis Rational Unified Process.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Software Practices v 5.0 Copyright  1998 Rational Software, all rights reserved 1 R Introduction to Rational Unified Process Adapted by Dr. Spiegel.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Rational Unified Process Fundamentals Module 3: Disciplines I.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
The principles of an object oriented software development process Week 04 1.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Introduction to Rational Unified Process
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
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.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
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.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 Rational Unified Process – Part 2 Original slides modified.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
1 Process activities. 2 Software specification Software design and implementation Software validation Software evolution.
Process 4 Hours.
UML: Unified modeling language
Applied Software Implementation & Testing
Introduction to Software Engineering
Object Oriented Analysis and Design
Rational Unified Process
Software engineering -1
OO Design and Development
Software Development Process Using UML Recap
Presentation transcript:

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level SE470 - Engineering Workflow Excellence in Software Engineering Repeatable Level Defined Level Managed Level Initial Level Optimizing Level Larry Dribin, Ph.D. - DePaul University Phone: (847) Fax: (847) Copyright  Larry Dribin, Ph.D. - v1 10/28/01

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 2 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Full Life Cycle Software Engineering Processes Needs Analysis Design Build Operate Project Planning Project Tracking & Oversight Subcontractor Management Quality Assurance Configuration Management & Documentation Standards Performance Measurement Systems Management Call Management Tech. Support & Maintenance Requirements Management Software Product Engineering Project Evaluation & Prioritization (Work Request) Technology Organization Technology Strategy Organization Process Function IT Value Chain

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 3 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Rational Process Workflows & Full Life Cycle Software Engineering Processes Needs Analysis Design Build Operate Project Planning Project Tracking & Oversight Subcontractor Management Quality Assurance Configuration Management & Documentation Standards Performance Measurement Systems Management Call Management Tech. Support & Maintenance Requirements Management Software Product Engineering Project Evaluation & Prioritization (Work Request) Technology Organization Technology Strategy Organization Process Function IT Value Chain Rational Workflows only cover these areas. Rational Workflows only cover these areas.

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 4 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Rational Unified Process - Core Workflows

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 5 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level During each Iteration, the Engineering Workflows follow a mini-Waterfall Selected Scenarios Product Release The Iteration Life Cycle is a mini-waterfall. AD - Analysis & Design RD - Requirements Definition IM - Implementation DE - Deployment BM - Business Modeling TE - Testing

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 6 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Benefits of an Iterative Approach  Risk Mitigation  Requirements Risks  Integration Risks  Architectural Risks  Easier to Accommodate Change  Requirements  Tactical  Technology  Learning As You Go  Increased Opportunity for Reuse  Better overall Quality

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 7 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Often, Workers or Worker Teams are working on Multiple Iterations at one time AD-1 RD-1 IM-1 DE-1 BM-1 TE-1 Iteration 1Iteration 2Iteration 3 AD-2 RD-2 IM-2 DE-2 BM-2 TE-2 AD-3 RD-3 IM-3 DE-3 BM-3 TE-3 AD-4 RD-4 IM-1 DE-4 BM-4 TE-4 Iteration 4 AD-1 RD-1 IM-1 DE-1 BM-1 TE-1 AD-2 RD-2 IM-2 DE-2 BM-2 TE-2 Iteration 1 Iteration 2 Iteration 3 Analysis Team Implementation Team AD-3 RD-3 IM-3 DE-3 BM-3 TE-3

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 8 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Business Modeling  Purpose  Understand the structure & dynamics of the organization  Identify Issues & Improvements  Ensure common understanding among stakeholders  Identify the system requirements  Workers  Business Process Analyst  Business Designer  Business Stakeholders  Outcomes / Artifacts  Business Vision Document  Business Use-Case Model  Business Object Model Case  Business Rules  Risk Assessment  Tools  UML & Rational Rose  Requirements Management Tools like RequsitePro BM

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 9 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level System Use Cases  A Use Case is a sequence of actions a system performs that yields an observable result of value to a particular actor  An Actor is someone or something outside the system that interacts with the system Withdraw Money Client Check Balance Transfer Money Use Case for an ATM (RUP p100) BM

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 10 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Business Use Case Models to System Models  Business Use Case Models are similar to System Use Case Models  They begin with the business Workers as candidate actors  They area a sequence of actions that the business performs that yields an observable result of value to a particular business actor  A Business Actor is someone or something outside the system that interacts with the system Withdraw Money Customer Check Balance Money Transaction Clerk Loan Specialist Business Use Case Model Business Object Model System Use Case Model RUP p 149 BM

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 11 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Business Modeling Workflow BM

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 12 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Requirements Definition  Purpose  To define system requirements  To establish & maintain the agreement with customers as to what system should do  To provide developers with an understanding of the system  To define system boundaries  To provide a basis for planning & estimating  Workers  System Analyst  Use-Case Specifier  User Interface Designer  Outcomes / Artifacts  Vision Document  Stakeholder Requests  Use-Case Model (System)  Supplementary Specifications  Glossary  Use-case Storyboard  User-Interface Prototype  Tools  UML - Rational Rose  RequsitePro  MS/Word RD

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 13 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Requirements  Requirement - is a condition or capability to which a system must conform.  Type of Requirements: FURPS  F unctional - those things that we expect the system to do  Non- Functional - those attributes that the system must exhibit – U sability – R eliability – P erformance – S upportability Stakeholders Requests - Raw input that the stakeholder states (may or may not be valuable to the user) Stakeholders Needs - those requests that are needed by the user to get value from the system System Features - a service that the system provides that fulfills a need Software Requirements - The definition of what the software will provide Workflow:  Analyze the problem  Understand stakeholder needs  Define the system  Manage the scope RD

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 14 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Requirements Engineering - Dr. Dribin’s view Develop As Is Model: 1.Study Current System & its Functions 2.Develop Model of Current System 3.Document Current System - As Is Model Develop (Design) To Be Model : 4.Determine Problems to be Corrected and any New Requirements 5.Develop Model of Future System = Current System Function + Problems + New Features 6.Document Future System - To Be Model 7.Validate that “ To Be ” model solves problems identified in “ As Is ” Analysis RD

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 15 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Requirements Workflow RD

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 16 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Analysis & Design  Purpose  To translate the requirements into a specification that describers how to implement the system  Workers  Architect - co-ordinates overall design  Designer - leads design of one or more classes  Data Base Designer - designs the database  Reviewers - specialists who review the design  Outcomes / Artifacts  Analysis Model - is a rough sketch of the design model (optional)  Design Model - primary artifact of this phase  Interface Definitions  Tools  UML - Rational Rose AD

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 17 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Analysis & Design AD

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 18 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Implementation  Purpose  To define the organization of the code in terms of subsystems  To implement the classes and objects in terms of components  To “Unit” test the components  To integrate the components into an executable system  Workers  Architect - defines the structure  Implementer - develops the components  System Integrator - constructs the build  System Reviewer - inspects the code for quality  Outcomes / Artifacts  Builds - is an operational version of a system or part of a system (once per day to once per several weeks)  Integration - integrates separate software components and subsystems into the whole system  Prototypes - are used to reduce risk – Behavioral – Structural – Exploratory – Evolutionary  Tools  Traditional software development tools / environments – Editors – Compliers – Linkers – Debuggers IM

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 19 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Implementation Workflow IM

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 20 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level TE Testing (Verification & Validation)  Quality Definitions:  The absence of defects  Fitness for Purpose  Purpose  Verify the interactions of components  Verify the proper integration of components  Verify that all requirements have been implemented correctly  Identify and correct all defects  Workers  Test Designer  Tester  Outcomes / Artifacts  Test Plan  Test Model – Test Cases – Test Procedures – Test Scripts – Test Classes and Components – Test Collaborations – Notes  Test Results  Defects  Tools  Rational’s: – TestStudio – PerformanceStudio

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 21 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Testing  Types of Testing  Benchmark  Configuration  Function  Installation  Integrity  Load  Regression  Stages of Testing  Unit  Integration  System  Acceptance TE

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 22 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Testing Workflow TE

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 23 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Deployment  Purpose  Establish the Projects Scope  Define the high level Requirements / Use Cases  Exhibit a candidate Architecture  Estimate the Cost & Schedule  Estimate the Risk  Workers  Deployment Manager  Project Manager  Technical Writer  Course Developer  Tester for Acceptance Tests  Outcomes / Artifacts  The executable software system  Release Notes  Support Material like User Manuals  Training Manuals  Type of Releases  Alpha Release(s)  Beta Release(s)  Production Release(s)  Tools  Not applicable DE

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 24 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Deployment Workflow DE

Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 25 Excellence in Software Engineering Repeatable Level Defined Level Manage d Level Initial Level Optimized Level Workflow Review