Copyright © Craig Larman. 2000 All Rights Reserved Requirements.

Slides:



Advertisements
Similar presentations
Chapter 05: Evolutionary Requirements Definition : Requirements  “Requirements are capabilities and conditions to which the system, and more broadly.
Advertisements

Chapter 5 Evolutionary requirements –Expect change! –Learn as you go –Validate as you build Why – 25% requirements change on an average software project.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Chapter 4: Inception is Not the Requirements Phase
Object-Oriented Analysis and Design
Detailing Requirements with Requisite Pro
COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
Requirements Specification
Requirements Analysis CMPT 371 Fall 2004 J.W. Benham.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
NJIT Evolutionary Requirements Chapter 5 Applying UML and Patterns Craig Larman.
© Copyright Eliyahu Brutman Programming Techniques Course.
Chapter 4: Requirements Elicitation 4.5: Managing Requirements Elicitation Supervised by: Dr. Qutaibah Malluhi Software Engineering Done by: Sarah Al-Aqailly.
SwE 313 Introduction to Rational Unified Process (RUP)
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
SE 555 – Software Requirements & Specifications Introduction
COMP 350: Object Oriented Analysis and Design Lecture 2
Recall The Team Skills Analyzing the Problem
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Object Oriented Analysis and Design Using the UML
Requirements Management Plan - Documents
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.
UML - Development Process 1 Software Development Process Using UML (2)
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.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
Rational Unified Process Fundamentals Module 4: Disciplines II.
An Introduction to Software Architecture
SOEN 6011 Software Engineering Processes Section SS Fall 2007 Dr Greg Butler
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Object Oriented.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Object-Oriented Analysis and Design An Introduction.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
INFO 637Lecture #51 Software Engineering Process II Defining Requirements INFO 637 Glenn Booker.
Chapter 7 Applying UML and Patterns -Craig Larman
Chapter 7 Applying UML and Patterns Craig Larman
Jan 7, A UP project organizes the work and iterations across four major phases: – Inception -- approximate vision, business case, scope, vague estimates.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
GRASP: Designing Objects with Responsibilities
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
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.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Understanding Requirements Chapter 5 Applying UML and Patterns -Craig Larman.
RequisitePro Software Requirement Management Tool A peresentation by: Mojdeh Jalali-Heravi Maryam Daneshi.
Inception is not Requirement phasee Chapter 3 and 4 Applying UML and Patterns -Craig Larman.
Essentials of Modeling with IBM Rational Software Architect V7.5
Rational Unified Process Fundamentals Module 3: Core Workflows I - Concepts Rational Unified Process Fundamentals Module 3: Core Workflows I - Concepts.
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.
Summary from previous lectures
Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem.
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.
1 Week 5 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
Evolutionary requirements
Recall The Team Skills Analyzing the Problem (with 5 steps)
COMP 350: Object Oriented Analysis and Design Lecture 2
Other System Requirements
Presentation transcript:

Copyright © Craig Larman All Rights Reserved Requirements

Copyright © Craig Larman All Rights Reserved 2 Introduction n Sloppy requirements specification and management is a major risk in software development. – Therefore, worth the effort to do very well. n The UP defines several artifacts: – Vision document – Use-case model – Supplementary Specifications Includes requirement lists and attributes – Stakeholder requests – UI prototype – Use-case UI storyboard – Glossary n Advice: Create every one!

Copyright © Craig Larman All Rights Reserved 3 Scope of our Seminar n We could easily spend 5 days exploring these artifacts. n However, we will just focus on practicing use case modeling. – The others are important. – Carefully learn the art of requirements specification and management. n See the Resources section for good references.

Copyright © Craig Larman All Rights Reserved 4 Types of Requirements n FURPS+ model: – Functionality – Usability – Reliability – Performance – Supportability n The "+" in FURPS+ : – design constraints – implementation requirement – interface requirements – physical requirements

Copyright © Craig Larman All Rights Reserved 5 Use Cases n A use case tells a story of actors using a system. – “Rent Videos” – A use-case is a sequence of actions a system performs that yields an observable result of value to a particular actor. n One artifact to express (especially) functional requirements. n Emphasizes thinking about the valuable objectives-oriented viewpoint of the users.

Copyright © Craig Larman All Rights Reserved 6 Supplementary Specifications 1. Functionality Requirement list and attributes 2. Usability 3. Reliability 4. Performance 5. Supportability 6. Design Constraints 7. Online User Documentation and Help System Requirements 8. Purchased Components 9. Interfaces 10. Licensing Requirements 11. Legal, Copyright and Other Notices 12. Applicable Standards

Copyright © Craig Larman All Rights Reserved 7 Requirement Lists & Attributes n For those not easily captured in use cases (which only emphasize functional requirements). – Fault tolerance, supportability, documentation,... n Includes requirement attributes.

Copyright © Craig Larman All Rights Reserved 8 Use Cases and Requirement Lists n Advice: Create in parallel. n Enhance each other. n Alternate ways to explore, think, talk. n Use cases are a simple, familiar communication vehicle for non-analysts. – Reduces barriers to communication—very important!

Copyright © Craig Larman All Rights Reserved 9 Use Cases and Requirement Lists n Use cases help us focus on – the business value of using a system – the priorities of development n If only create requirement lists, it is easier to lose sight of the important elements and their priority in terms of business value. n Use cases are awkward to record non-functional requirements. – The Supplementary Specification is suitable

Copyright © Craig Larman All Rights Reserved 10 Tracebility n Key ideas – Everything has codes. FEA-1,... – Track how requirements trace to other artifacts, components, issues, change requests, tests,... n Advice: Use a real requirements management and change request tool. – Alternative: Use a simple tool such as MS Access to create a database of elements and their relationships.

Copyright © Craig Larman All Rights Reserved 11 Resources n In all cases – Rational Unified Process Web Tool has some advice or templates. – The Unified Software Development Process – (fall 2000) Applying UML and Patterns in the Unified Process n Vision document – Practical Software Requirements (A) – Managing Software Requirements (B) n Use-case model – Applying UML and Patterns (C) – Applying Use Cases n Supplementary Specifications – A, B, C – Exploring Requirements: Quality Before Design n Stakeholder requests – A, B n UI prototype – Usability Engineering – Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design n Glossary – C