NJIT Evolutionary Requirements Chapter 5 Applying UML and Patterns Craig Larman.

Slides:



Advertisements
Similar presentations
Web Services Architecture An interoperability architecture for the World Wide Service Network.
Advertisements

Chapter 05: Evolutionary Requirements Definition : Requirements  “Requirements are capabilities and conditions to which the system, and more broadly.
CS3773 Software Engineering Lecture 01 Introduction.
Object-Oriented Analysis and Design LECTURE 2: INCEPTION PHASE.
Chapter 5 Evolutionary requirements –Expect change! –Learn as you go –Validate as you build Why – 25% requirements change on an average software project.
Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.
Object-Oriented Analysis and Design
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 Analysis CMPT 371 Fall 2004 J.W. Benham.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Understanding Requirements
SE 555 Software Requirements & Specification Requirements Quality Attributes.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
NJIT 1 Domain Model Visualizing Concepts Chapter 9 Applying UML and Patterns Craig Larman.
Dr. Kivanc DincerCS319 Week 1 - Sept.12,20051 Chapter 4 INCEPTION IS NOT THE REQUIREMENTS PHASE Objectives Define the inception step. Motivate the following.
Software Engineering Georges Grinstein Olsen 301E Class materials:
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
NJIT Inception is not the Requirements Phase Chapter 4 Applying UML and Patterns Craig Larman.
Software Architecture. Agenda " Why architect? " What is architecture? " What does an architect do? " What principles guide the process of architecting?
Object Oriented Analysis and Design Using the UML
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.
Requirements Engineering
Copyright © Craig Larman All Rights Reserved Requirements.
RUP Fundamentals - Instructor Notes
Supplementary Specifications (Chapters 20,22 - Requirements Text) Question 1 by Steve & Chandan (Along with others in the past! - See notes, below)
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Investigating System Requirements
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Software Requirements Engineering CSE 305 Lecture-2.
Object-Oriented Analysis and Design An Introduction.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
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.
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.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Chapter 5 Evolutionary Requirements. Introduction 5.1 Definition: Requirements 5.2 Evolutionary vs. Waterfall Requirements 5.3 What are Skillful Means.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Systems Development Life Cycle
Understanding Requirements Chapter 5 Applying UML and Patterns -Craig Larman.
SWE 513: Software Engineering
Week 2. Topics Inception phase Evolutionary requirements Use cases.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Requirement Discipline Spring 2006/1385 Semester 1.
CS 389 – Software Engineering Lecture 2 – Part 2 Chapter 2 – Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
Investigating System Requirements
Applying UML and Patterns
Evolutionary requirements
(Professional Business Analyst Training organisation)
Inception.
Unified Process(UP) popo.
COMP 350: Object Oriented Analysis and Design Lecture 2
Rational Unified Process
Week 2.
Requirements Analysis
Evolutionary Requirements
Software Engineering Furqan Rustam.
Software Engineering Lecture #3
Chapter 5 Evolutionary requirements
Software Requirements
User Requirements: The user requirement(s) document (URD) or user requirement(s) specification is a document usually used in software engineering that.
Presentation transcript:

NJIT Evolutionary Requirements Chapter 5 Applying UML and Patterns Craig Larman

Requirements These are the capabilities and conditions that the system, the project, and the product must provide and meet. Managing requirements is a best practice for project managers. Requirement issues are the leading cause of project failure. Even if you do a perfect job of building the wrong thing, its no good!

Not Waterfall Requirements There is an attempt in the waterfall method to describe the requirements fully and accurately and “freeze” them. Unified process realizes that change is constant, so plans for change instead of setting an impossible goal.

Managing Requirements Stakeholder requirements are frequently unclear and change over time. Frequently new requirements are discovered as part of the development process. There must be a “systematic approach to finding, documenting, organizing, and tracking the changing requirements of a system.” (RUP)

FURPS+ Functional (features, capabilities, security) Usability (human factors, help, documents) Reliability (failures, recovery, predictable) Performance (response, throughput, etc) Supportability (maintainability, configuration) + ancillary and sub-factors (next slide)

Ancillary and sub-factors Implementation (includes limitations) Interface Operations Packaging Legal Requirements

Functional Requirements Detailed in the Use Case Model and in the System Features list of the Vision artifact. They are specified in detail in Operation Contracts where necessary.

Non-functional requirements Often called the “-ilities” of a system; quality, reliability, usability, performance, etc. The glossary, data dictionary and supplemental specifications describe many non-functional requirements. In addition, architectural documents may have non-functional requirements.

Hints for Vision Homework There is no UML or other formal format for a Vision Statement. Text has some examples. Make sure you cover scope, main functionality, and Go/No Go decision. A Business Case usually has financial metrics like IRR, while a Vision has less financial detail. You can do either.