Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality.

Slides:



Advertisements
Similar presentations
Requirements Engineering Processes – 2
Advertisements

Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
SWE Introduction to Software Engineering
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
WKES 3202 SOFTWARE REQUIREMENTS ENGINEERING SEMESTER 1 SESSION 2004/2005.
Requirements Engineering Processes
Requirements Engineering Processes
Overview of Software Requirements
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements Engineering Process – 1
Requirements Engineering
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
Requirements Engineering Processes
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
 To describe the principal requirements engineering activities and their relationships  To introduce techniques for requirements elicitation and analysis.
Software Requirements Engineering CSE 305 Lecture-2.
Requirements Verification & Validation Requirements Engineering & Project Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Chapter 4 Requirements Engineering Processes Objectives l To describe the principal requirements engineering activities and their relationships l To.
Good Practices of Requirements Eng. Copyright, 2000 © Jerzy R. Nawrocki Requirements.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Lecture 7: Requirements Engineering
Quality of Usage Scenarios Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Introduction to Requirements Engineering Copyright, 2000 © Jerzy R. Nawrocki Requirements.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Software Engineering, 8th edition. Chapter 7 1 Courtesy: ©Ian Sommerville 2006 March 20 th, 2008 Lecture # 12 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements.
Requirements Specification Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Requirements Engineering. Requirements engineering processes The processes used for RE vary widely depending on the application domain, the people involved.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements Engineering Process
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Change Management Requirements Engineering & Project Management Lecture 10.
Introduction to Quality Management Copyright, 2000 © Jerzy R. Nawrocki Quality.
Requirements Engineering Requirements Validation and Management Lecture-24.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
CS223: Software Engineering Lecture 8: Requirement Engineering.
Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
1 Requirements Elicitation – 2 Lecture # Requirements Engineering Process Requirements Elicitation Requirements Analysis and Negotiation Requirements.
1 Requirements Analysis Lecture # Recap of Requirements Elicitation - 1 Requirements elicitation deals with discovering requirements for a software.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
REQUIREMENTS ENGINEERING PROCESSES Chapter 6. Activities in Requirements Engineering processes  Requirements elicitation;  Requirements analysis; 
Requirements Engineering Processes
Chapter 4 – Requirements Engineering
Requirements Engineering Lecture 13
Requirements Engineering Lecture 2
Requirement Management
EKT 421 SOFTWARE ENGINEERING
Requirements Elicitation – 1
Introduction to PRINCE 2
Software Requirements analysis & specifications
Requirements Engineering Process – 1
Requirements Engineering Lecture 6
Presentation transcript:

Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary Material Quality Management Auxiliary Material

J. Nawrocki, Quality Model for Req. Plan of the lecture Overview of RE guidelines Scoring Maturity levels for RE Basic guidelines Intermediate guidelines Advanced guidelines

J. Nawrocki, Quality Model for Req. Overview of RE guidelines The requirements document Requirements elicitation Reqs analysis & negotiation Describing requirements System modelling Requirements validation Requirements management RE for critical systems BasicIntermAdv

J. Nawrocki, Quality Model for Req. ScoringScoring 3 - standardised: documented standard followed and checked as part of the quality management process; 2 - normal use: widely followed but not mandatory; 1 - discretionary use: used at discretion of project manager; 0 - never: never or very rarely used; 3 0

J. Nawrocki, Quality Model for Req. Maturity levels for RE Defined > 85 Basic & > 40 Interm & Adv Defined > 85 Basic & > 40 Interm & Adv Repeatable > 55 Basic & < 40 Interm & Adv Repeatable > 55 Basic & < 40 Interm & Adv Initial < 55 Basic Initial < 55 Basic

J. Nawrocki, Quality Model for Req. Legend for RE quidelines Responsibility of Project Managers Responsibility of SDS Senior Managers or Quality AssurersResponsibility of SDS Senior Managers or Quality Assurers At a discretion of Project Managers

J. Nawrocki, Quality Model for Req. Basic guidelines Requirements document Define a standard document structure Explain how to use the document Include a summary of the requirements Make a business case for the system Define specialised terms Lay out the document for readability Help readers find information Make the document easy to change 

J. Nawrocki, Quality Model for Req. Basic guidelines Requirements elicitation Assess system feasibility Be sensitive to organisational & political considerations Identify and consult stakeholders Record requirement sources Define operating environment Use business concerns to drive requirements elicitation Give me a crocodile!

J. Nawrocki, Quality Model for Req. Basic guidelines Analysis and negotiation Define system boundaries Use checklists for requirements analysis Provide software to support negotiations Plan for conflicts and conflict resolution Prioritise requirements

J. Nawrocki, Quality Model for Req. Basic guidelines Describing requirements Define standard templates for describing requirements Use language simply & concisely Use diagrams appropriately Supplement natural language with other descriptions of requirements

J. Nawrocki, Quality Model for Req. Basic guidelines System modelling Develop complementary system models Model the system’s environment Model the system architecture

J. Nawrocki, Quality Model for Req. Basic guidelines Requirements validation Check that the requirements document meets your standard Organise formal requirements inspections Use multidisciplinary teams to review requirements Define validation checklists 

J. Nawrocki, Quality Model for Req. Basic guidelines Requirements management Uniquely identify each requirement Define policies for requirements management Define traceability policies Maintain a traceability manual

J. Nawrocki, Quality Model for Req. Basic guidelines RE for critical systems Create safety requirements checklists Involve external reviewers in the validation process

J. Nawrocki, Quality Model for Req. Intermediate guidelines Requirements elicitation Look for domain constraints Record requirements rationale Collect requirements from multiple viewpoints Prototype poorly understood requirements Use scenarios Define operational processes Give me a crocodile!

J. Nawrocki, Quality Model for Req. Intermediate guidelines Analysis and negotiation Classify requirements using using a multidimensional approach Use interaction matrices to find conflicts and overlaps

J. Nawrocki, Quality Model for Req. Intermediate guidelines Describing requirements Specify requirements quantitatively

J. Nawrocki, Quality Model for Req. Intermediate guidelines System modelling Use structured methods for system modelling Use a data dictionary Document the links between stakeholder requirements and system models

J. Nawrocki, Quality Model for Req. Intermediate guidelines Requirements validation Use prototyping to animate requirements Write a draft user manual Propose requirements test cases 

J. Nawrocki, Quality Model for Req. Intermediate guidelines Requirements management Use a database to manage requirements Define change management policies Identify global system requirements

J. Nawrocki, Quality Model for Req. Intermediate guidelines RE for critical systems Identify and analyse hazards Derive safety requirements from hazard analysis Cross-check operational and functional requirements against safety requirements

J. Nawrocki, Quality Model for Req. Advanced guidelines Requirements elicitation Reuse requirements Give me a crocodile!

J. Nawrocki, Quality Model for Req. Advanced guidelines Analysis and negotiation Assess requirements risks

J. Nawrocki, Quality Model for Req. Advanced guidelines Requirements validation Paraphrase system models 

J. Nawrocki, Quality Model for Req. Advanced guidelines Requirements management Identify volatile requirements Record rejected requirements

J. Nawrocki, Quality Model for Req. Advanced guidelines RE for critical systems Specify systems using formal specification Collect incident experience Learn from incident experience Establish an organisational safety culture

J. Nawrocki, Quality Model for Req. Further readings I. Sommerville, P. Sawyer, Requirements Engineering, John Wiley & Sons, Chichester, 

J. Nawrocki, Quality Model for Req. 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?