Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements.

Slides:



Advertisements
Similar presentations
IBM Software Group ® Traceability From Need To Solution What, Why and How Tammy Lavi Alon Bar-Ner.
Advertisements

Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
Software Reviews Copyright, 1999 © Jerzy R. Nawrocki Personal Software Process Lecture.
Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Weaver Vale Housing Trust Annual Planning. The Organisational Activity Model Philosophy Strategy Projects Routine Operations.
Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Intuicyjne zarządzanie przedsięwzięciem Copyright, 2001 © Jerzy R. Nawrocki Doskonalenie.
Project Management with XPrince Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki „Trabrennen” in.
Static Structure: Process Description
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Quality Assurance Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.
Feb. 2, 2004CS WPI1 CS 509 Design of Software Systems Lecture #3 Monday, Feb. 2, 2004.
SE 555 Software Requirements & Specification Requirements Validation.
Introduction to ISO 9001:2000 Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxilliary.
RequisitePro (2) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Rational Suite and CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
DiscussionsDiscussions Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
Requirements Analysis
Configuration Management Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Chapter 1: Introduction to Project Management
Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
Requirements Verification & Validation Requirements Engineering & Project Management.
Good Practices of Requirements Eng. Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Use-Cases Elicitation and FAST Copyright, 2003 © Jerzy R. Nawrocki Requirements Engineering.
PRINCE 2 for Managers Copyright, 2003 © Jerzy R. Nawrocki
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Requirements Engineering.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
Requirements Gathering How do we find out what we are supposed to be building?
Quality of Usage Scenarios Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Wideband Delphi Technique George Ukkuru. Introduction Consensus based approach for estimation Developed in the 1940’s at Rand Corporation Team of experts.
Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Introduction to Requirements Engineering Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Develop Project Charter
ReviewsReviews Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
RUP and Elaboration Phase Copyright, 2003 © Jerzy R. Nawrocki Requirements Engineering.
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Software Size Estimation Copyright, 2006 © L. Ouyang Liubo Ouyang Personal Software Process Lecture 5.
Requirements Specification Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Configuration Management at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Change Management Requirements Engineering & Project Management Lecture 10.
DiscussionsDiscussions Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Introduction to Quality Management Copyright, 2000 © Jerzy R. Nawrocki Quality.
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Viking Estimation Team Assignment 13 Team 2-1. Content 1/ Introduction 2 / Wideband Delphi & COCOMO II 3 / The assemble task formula 4 / Wideband Delphi.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.
Requirements Engineering Lecture 7
Requirements Engineering Lecture 13
Requirements Engineering Lecture 4
Requirements Engineering Lecture 2
Chapter 6: Database Project Management
Introduction to PRINCE 2
Requirements Engineering Lecture 2
Unit 5 – eProject – Starting to look at projects Unit 5
QA Reviews Lecture # 6.
Requirements Engineering Lecture 6
Joint Application Development (JAD)
Presentation transcript:

Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture 1 Requirements Engineering Lecture 1

J. Nawrocki, Requirements Eng. (1) 2 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

J. Nawrocki, Requirements Eng. (1) 3 Success stories Scholarships of the Ministry of National Education: Leszek GawronLeszek Gawron Wojtek GryncewiczWojtek Gryncewicz Grzegorz JachimkoGrzegorz Jachimko Tomek JaniszewskiTomek Janiszewski Michał JasinskiMichał JasinskiKKIO’2001: Grzegorz WieczerzakGrzegorz Wieczerzak

J. Nawrocki, Requirements Eng. (1) 4 SDS 2001/02 Laboratory 214 (6 workstations + server) Rational Suite CMMI Level 2 + XP (Customer) + RUP Standard activities: FAST, Delphi, Fagan inspectionsFAST, Delphi, Fagan inspections Roles for 5th-year students: Facilitator, Tester (acceptance tests), ReviewerFacilitator, Tester (acceptance tests), Reviewer Roles for 4 th -year students: Analyst, Project Manager, Configuration Manager, TrackerAnalyst, Project Manager, Configuration Manager, Tracker

J. Nawrocki, Requirements Eng. (1) 5 LecturesLectures 3.10: Introduction 3.10: Introduction 10.10: RequisitePro (1) 15.10: RequisitePro (2), 15:15, Prof. Club 24.10: RequisitePro (3) 31.10: ClearCase LT (1) 7.11: ClearCase LT (2) 7.11: ClearCase LT (2) 14.11: ClearQuest 21.11: SoDA (1) 28.11: SoDA (2)

J. Nawrocki, Requirements Eng. (1) 6 LecturesLectures 5.12: Rose (1) 5.12: Rose (1) 12.12: Rose (2) 19.12: CMMI Level : Personality issues 9.01: Personality issues 16.01: Pre-exam

J. Nawrocki, Requirements Eng. (1) 7 LaboratoriesLaboratories 10.10: Organisational issues, team game 24.10: RequisitePro 31.10: RequisitePro 7.11: ClearCase LT 7.11: ClearCase LT 14.11: ClearCase LT 21.11: ClearQuest 28.11: SoDA 5.12: SoDA 5.12: SoDA 12.12: Rose : Pre-exam 23.01: Grades

J. Nawrocki, Requirements Eng. (1) 8 GradingGrading Pre-exam: 14.01, 2 groups: 13:45 group A + B (rooms )13:45 group A + B (rooms ) 15:00 group C + D (rooms )15:00 group C + D (rooms ) 21.01: grades announcement Exam grades: 0.6 x Paper x Tutorials x Presence

J. Nawrocki, Requirements Eng. (1) 9 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

J. Nawrocki, Requirements Eng. (1) 10 Sommerville’s Model Requirements elicitation Requirements analysis Requirements negotiation RequirementsdefinitionRequirementsdefinition

J. Nawrocki, Requirements Eng. (1) 11 Developers Customers FASTFAST FAST = Facilitated Application Specification Technique JAD Joint Application Development - another approach to FAST Facilitator Recorder

J. Nawrocki, Requirements Eng. (1) 12 FASTFAST Facilitator - runs the meeting(s) Recorder - takes notes, serves tape recorder or video recorder Developers & customer representatives - work on requirements Senior manager - knows about the meeting date & time Persons involved

J. Nawrocki, Requirements Eng. (1) 13 FASTFAST The list of stakeholders and views should be ready before the project leaders start to organise the first FAST meeting. Get from the customer the initial list of requirements sources (manuals, organisation charts, technical data,..) and read it before the meeting. Conducting a FAST meeting via phone or should be avoided. Before the first meeting

J. Nawrocki, Requirements Eng. (1) 14 FASTFAST Product request (  Project Proposal) Aim & goals of the meeting Agenda for the meeting Information about place and time Input documents

J. Nawrocki, Requirements Eng. (1) 15 FASTFAST A worksheet to fill in Missing stakeholders Missing requirements sources Objects (devices, documents, etc.): external to the system produced by the system internal - used by the system Services that manipulate the objects Constraints (cost, size, time,...) Input documents

J. Nawrocki, Requirements Eng. (1) 16 FASTFAST Product justification (consensus) Presentation of the worksheets (one by one, no critique) Deciding (discussion) about: Stakeholders System architecture (objects) Services Constraints Validation criteria An agenda example

J. Nawrocki, Requirements Eng. (1) 17 FASTFAST Direct: Meeting minutes Indirect: Software Requirements Specification (validation criteria!) Meeting outcomes

J. Nawrocki, Requirements Eng. (1) 18 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

J. Nawrocki, Requirements Eng. (1) 19 Delphi method Rand Corporation, Boehm’81 A few experts individually produce effort estimates.A few experts individually produce effort estimates. A Delphi process is used to reach a consensus.A Delphi process is used to reach a consensus. Pythia

J. Nawrocki, Requirements Eng. (1) 20 Delphi method 1. Experts get the specification and an estimation form 2. They meet for discussion (project goals, assumptions, estimation issues) 3. Each expert anonymously lists the tasks and estimates the size 4. The estimates go to the estimate moderator. He tabulates the results and returns them to the experts. The Delphi procedure The estimate moderator

J. Nawrocki, Requirements Eng. (1) 21 Delphi method Estimator: Jerzy Nawrocki Date: Project: Sorting routine The estimates from the 1st round: e E M e e e E M e e e - estimates, E - your estimate, M - median estimate Your estimate for the next round: Hours. A rationale for your estimate:

J. Nawrocki, Requirements Eng. (1) 22 Delphi method 5. The experts meet to discuss the results. They review the tasks they have defined but not their size estimates. 6. The procedure is repeated from step 3 until the estimates are acceptably near The Delphi procedure The estimate moderator

J. Nawrocki, Requirements Eng. (1) 23 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

J. Nawrocki, Requirements Eng. (1) 24 Designer Fagan inspections Implementor Moderator Tester Review session

J. Nawrocki, Requirements Eng. (1) 25 Fagan inspections 1. Overview (whole team) 2. Preparation (individual) 3. Inspection (whole team) 4. Rework 5. Follow-up Designer Implem. Moderator Tester Review session

J. Nawrocki, Requirements Eng. (1) 26 Fagan inspections Overview (whole team) 500 not necessary Preparation (individual) Inspection (whole team) Rework Follow-up - - I1I1I1I1 I2I2I2I2 Rate of progress (loc/h) Inspection session <= 2 hours sessions per day

J. Nawrocki, Requirements Eng. (1) 27 SummarySummary RE has to support SDS Main theme: Rational Suite Structured meetings (FAST & inspections)

J. Nawrocki, Requirements Eng. (1) 28 Quality assessment 1. What is your general impression? (1 - 6) 2. Was it too slow or too fast? 3. What important did you learn during the lecture? 4. What to improve and how?