Requirements validation Csaba Veres. What is it? Validation is the process of checking the requirements document for –completeness –consistency –accuracy.

Slides:



Advertisements
Similar presentations
Requirements Validation
Advertisements

Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Introduction to Software Engineering Dr. Basem Alkazemi
Introduction to Software Engineering
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
1 To introduce the concepts of user and system requirements To introduce the concepts of user and system requirements To describe functional and non- functional.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
Requirements Engineering Processes
Overview of Software Requirements
Requirements Specifications Today: Homework #1 due For next class: Pressman 11; SRD Team Status Reports Requirements Process (continued) Bio Break ( 5.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
Course Instructor: Aisha Azeem
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
DFD examples.
Requirements Engineering Processes
LEARNING WALKS How we can share good practice and learn from one another.
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Dr. Tom WayCSC Software Requirements CSC 4700 Software Engineering Lecture 2 Based on Sommerville, Chapter 6.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Requirements Engineering Requirements Specification Lecture-22.
Structured Analysis.
Requirements Reference: Chapters 5, 6, & 8. CMSC 345, Fall Objectives To introduce the concepts of user and system requirements To explain functional.
Requirements Engineering Overview Senior Design Don Evans.
Chapter 4 Software Requirements
Tips.  Your system should be robust and easy to use.  Display meaningful text, mention units & assumptions (maybe as a tool-tip).  Use meaningful error.
Requirements Validation
Week 3: Requirement Analysis & specification
Requirements Engineering. Requirements engineering processes The processes used for RE vary widely depending on the application domain, the people involved.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Requirements Engineering Process
Section 05DFD - Complete Top-Level1 05 Data Flow Diagrams - Completing the top-level And Franchise Colleges By MANSHA NAWAZ.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Requirement Engineering
Requirements Engineering Requirements Management Lecture-25.
Requirements Analysis
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
Software Engineering, COMP201 Slide 1 Software Requirements BY M D ACHARYA Dept of Computer Science.
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,
 Problem Analysis  Coding  Debugging  Testing.
REQUIREMENTS ENGINEERING PROCESSES Chapter 6. Activities in Requirements Engineering processes  Requirements elicitation;  Requirements analysis; 
Using Human Errors to Inspect SRS
Software Requirements
Chapter 4 – Requirements Engineering
Requirements Validation – II
Software Process Activities.
Requirements Engineering (continued)
Requirements Verification and Validation
Requirements Elicitation – 1
COIT20235 Business Process Modelling
Software Engineering (CSI 321)
Software Requirements analysis & specifications
UNIT II.
Requirements Reference: Software Engineering, by Ian Sommerville, 6th edition, Chapters 5, 6, & 8.
Requirements Analysis
Quality Assurance Functionality:
Requirements Verification and Validation
Requirements Verification and Validation
Lecture # 7 System Requirements
SE-565 Software System Requirements VII. Requirements Validation
Requirements Validation – I
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Software Reviews.
INTRODUCTION OF REQUIREMENT ENGINEERING Chapter- one.
Presentation transcript:

Requirements validation Csaba Veres

What is it? Validation is the process of checking the requirements document for –completeness –consistency –accuracy Requires all stakeholders

Why is it different from RE? RE is concerned with eliciting and documenting raw requirements –’what are the right requirements?’ Validation concerns the document –is it complete, consistent, etc.? –’have we got the requirements right?’

The division between analysis and validation

Problems discovered during validation lack of conformance to quality standards poorly worded, ambiguous requirements errors in models of the system or the problem to be solved any remaining requirements conflicts

Validation is a final check of the document as a clear statement of the stakeholders’ needs Requirements validation Requirements document Inputs Outputs Organisational knowledge Organizational standards List of problems Agreed actions

Requirements reviews

Review checklists ● Quality properties used to derive checklist

Review questions ● Specific questions to look out for in a particular organization/session

Possible outcomes Requirements clarification –poor expression and lack of clarity Missing information –some stakeholders needs are absent Requirements conflict –stakeholders must negotiate to solve conflict Unrealistic requirement –stakehoders must come to a mutual decision

Pre-review checking ”Simple” errors should be fixed by one person prior to validation –document structure –adherence to standards Possible actions –return document to RE team –distribute document with notes

Pre-review checking...

Model validation The requirements might include models Validation has three objectives –to demonstrate that the model is self consistent –external consistency –accuracy Models are sometimes not easy to understand –convert to natural language

Converting to NL Use a form or table with sub headings e.g. DFD 1.transformation name 2.transformation inputs and input sources 3.transformation function 4.transformation outputs 5.control

Check user Check item Issue item e.g. library function “Issue” Library card Requested item User details User status Item status Issued item Update details