Dagmar Monett, profile picture
Uploaded byDagmar Monett
PDF, PPTX4,558 views

Methods for Validating and Testing Software Requirements (lecture slides)

The document outlines a 60-minute presentation on methods for validating and testing software requirements. It discusses the key topics of requirements validation, reviewing requirements through both informal and formal approaches like inspections, testing requirements using acceptance criteria, and good validation practices. The presentation also references additional reading materials and sources for further inspiration.

Embed presentation

Download as PDF, PPTX
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Methods for Validating and Testing Software Requirements Prof. Dr. Dagmar Monett Díaz Computer Science Dept. Faculty of Cooperative Studies Berlin School of Economics and Law dagmar@monettdiaz.com Europe Week, 2nd – 6th March 2015 60 Minutes
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Dilbert  Scott Adams At http://dilbert.com/strip/2014-02-25/ (Educational/Classroom usage permission is granted by Universal Uclick. All Rights Reserved) Different goals… 2
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 3 Main topics
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 4 Main topics  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 5 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 6 ©
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Software Requirements Karl Wiegers and Joy Beatty 3rd Edition, 672 pp. Microsoft Press, 2013 ISBN-13: 978-0-7356-7966-5 (See more at http://aka.ms/SoftwareReq3E/files) 7 Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Software Engineering Ian Sommerville 9th Edition, 792 pp. Addison-Wesley, 2010 ISBN-13: 978-0137035151 (10th Edition: April 2015. See more at http://iansommerville.com/software- engineering-book/) 8 Sommerville
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 9 The traditional software development process: Perceptions, communication patterns and interests…
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 10Cartoon  http://projectcartoon.com/
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 11Cartoon  http://projectcartoon.com/
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 12 Requirements and Requirements Engineering – An Overview –
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 13 Requirement: A definition According to Wiegers & Beatty: “[A requirement is a] statement of a customer need or objective, or of a condition or capability that a product must possess to satisfy such a need or objective. A property that a product must have to provide value to a stakeholder.” See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Requirements Engineering Definition according to Wiegers & Beatty: Requirements engineering is the subdiscipline of systems engineering and software engineering that encompasses all project activities associated with understanding a product's necessary capabilities and attributes. Includes both requirements development and requirements management. 14 See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 15 Subdisciplines of Requirements Engineering
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 16 Subdisciplines of Requirements Engineering Requirements Engineering Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 17 Subdisciplines of Requirements Development Elicitation Requirements Engineering Analysis Specification Validation Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 18 Subdisciplines of Requirements Management Tracking Requirements Engineering Managing Controlling Tracing Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 19 Topics of other related lectures
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 20 Subdisciplines of Requirements Engineering Elicitation Requirements Engineering Analysis Specification Validation Requirements Development Requirements Management All are topics of lecture: “A Structured Approach to Requirements Analysis”
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 21 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Analysis Specification Validation Topic of lecture “Requirements Engineering Techniques for Eliciting Requirements”
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 22 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Specification Validation Topics of lecture “Requirements Engineering Methods for Documenting Requirements” Analysis
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 23 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Analysis Specification Validation Also topic of lecture “Modelling Software Requirements. Important diagrams and templates”
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 24 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Analysis Specification Validation Topic of (this) lecture “Methods for Validating and Testing Software Requirements”
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 25 A Requirements Development process framework
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 26 Subdisciplines of Requirements Development Elicitation Requirements Engineering Analysis Specification Validation Requirements Development Requirements Management Acc. to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield RD process framework 27 Elicitation Analysis Specification Validation re-evaluate Adapted from Wiegers & Beatty identifying, discovering evaluating, verifying documenting, SRS classifying, representing, deriving, negotiating RD: Requirements Development SRS: Software Requirements Specification See lecture “A Structured Approach to Requirements Analysis” for details!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 28 A structured approach to Requirements Development
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 29 A structured approach to RD (1) Define stakeholders!  Who is interested in the system?  Who makes decisions?  Who are the users, managers, developers, etc.? In other words, WHO has influence on the software requirements? (2) Define goals!  Stakeholders have goals (define coarse goals!)  These goals can be divided into more specific goals (define granular goals!) In other words, WHAT should be implemented or achieved? (3) Define requirements!  Goals can be derived into concrete requirements  How to get to the requirements? (goal-based!)  Model those requirements using diagrams, templates, etc. In other words, HOW will the goals be achieved?
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 30 A structured approach to RD Granular goals CG3 CG2 CG1 Coarse goals Define stakeholders Define goals Define requirements Diagrams Templates Models WHO WHAT HOW See lecture “A Structured Approach to Requirements Analysis” for details!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 31 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 32 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 33 Requirements Validation
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield RD process framework 34 Elicitation Analysis Specification Validation re-evaluate Adapted from Wiegers & Beatty identifying, discovering evaluating, verifying documenting, SRS classifying, representing, deriving, negotiating RD: Requirements Development SRS: Software Requirements Specification
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield RD process framework 35 Elicitation Analysis Specification Validation re-evaluate Adapted from Wiegers & Beatty identifying, discovering evaluating, verifying documenting, SRS classifying, representing, deriving, negotiating RD: Requirements Development SRS: Software Requirements Specification
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Validation and verification 36 Acc. to Wiegers & Beatty “[Validation is the] process of evaluating a project deliverable to determine whether it satisfies customer needs.” ‘Are we building the right product?’ “[Verification is the] process of evaluating a project deliverable to determine whether it satisfies the specifications on which it was based.” ‘Are we building the product right?’
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 37 Key actions in validation
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Key actions 38 Acc. to Wiegers & Beatty Validation Reviewing the documented requirements to correct any problems before the development group accepts them. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Key actions 39 Acc. to Wiegers & Beatty Validation Reviewing the documented requirements to correct any problems before the development group accepts them. Developing acceptance tests and criteria to confirm that a product based on the requirements would meet customer needs and achieve the business objectives. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 40 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 41 Active learning exercise Image © renjith krishnan at http://www.freedigitalphotos.net/
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Quiz 42 Which is an activity in the validation process? (A) Negotiating. (B) Discovering. (C) Evaluating. (D) Classifying.
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 43 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 44 Reviewing requirements
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Dilbert  Scott Adams At http://dilbert.com/strip/2013-02-25/ (Educational/Classroom usage permission is granted by Universal Uclick. All Rights Reserved) Failed feedback… 45
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Peer review 46 “[A peer review is an] activity in which one or more persons other than the author of a work product examine that product with the intent of finding defects and improvement opportunities.” According to Wiegers & Beatty:
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Peer review approaches 47 Peer deskcheck: asking one colleague to look over your own work product. According to Wiegers & Beatty Passaround: inviting several colleagues to examine a deliverable concurrently. Walkthrough: the author describes a deliverable and solicits comments on it. Informal peer reviews:
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 48 The inspection process
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 49 Inspection: A definition According to Wiegers & Beatty: “[Inspection is a] type of formal peer review that involves a trained team of individuals who follow a well-defined process to examine a work product carefully for defects.”  Originally developed by Michael Fagan at IBM (1976)  Software industry best practice  Best-established type of formal peer review
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 50 Inspection The participants (<7) The author of the work product and perhaps peers of the author People who are the sources of information that fed into the item being inspected People who will do work based on the item being inspected People who are responsible for interfacing systems that will be affected by the item being inspected According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 51 Inspection roles Author They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 52 Inspection roles Author Moderator They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. - Plans inspection with author, coordinates activities, facilitates the inspection meeting. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 53 Inspection roles Author Moderator Reader They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. - Plans inspection with author, coordinates activities, facilitates the inspection meeting. - Paraphrases requirements and model elements. The other participants point out potential defects and issues they see. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 54 Inspection roles Author Moderator Reader Recorder They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. - Plans inspection with author, coordinates activities, facilitates the inspection meeting. - Paraphrases requirements and model elements. The other participants point out potential defects and issues they see. - Documents issues raised and defects found. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield The inspection process 55 Initial work product Planning Preparation Inspection meetingRework Follow-up Baselined work product Entry criteria Exit criteria According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Defect checklist 56  Helps reviewers look for typical kinds of errors. According to Wiegers & Beatty Image © Stuart Miles @ http://www.freedigitalphotos.net/
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Defect checklist 57 Examples of topics to check out: Completeness  Do the requirements address all known customer or system needs? Correctness  Do any requirements conflict with or duplicate other requirements? Organisation and traceability  Is each requirement uniquely and correctly labelled? According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 58 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 59 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 60 Testing requirements
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Tests 61  Powerful tool for both validating and verifying requirements.  Evaluate functional requirements, analysis models, and prototypes.  Should cover normal and alternative flows identified during elicitation and analysis. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Example of conceptual test 62 Use case: Test: According to Wiegers & Beatty “User enters order number to view, order exists, user had placed the order. Expected result: show order details.” View a stored order
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 63 Validating with acceptance criteria
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Acceptance criteria 64 According to Wiegers & Beatty: “[Acceptance criteria are] conditions that a software product must satisfy to be accepted by a user, customer, or other stakeholder.”  From “What do you need to do with the system?”…  …to “How would you judge whether the solution meets your needs?”
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Acceptance Test 65 According to Wiegers & Beatty: “[An acceptance test is a] test that evaluates anticipated usage scenarios to determine the software's acceptability. Used in agile development both to express details about a user story and to determine whether a user story is fully and correctly implemented.”
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 66 The front of a story card Acc. to Cohn Image © Stuart Miles @ http://www.freedigitalphotos.net/ Conver- sations The description A company can pay for a job posting with a credit card. Note: Will we accept Discover cards? Note for UI: Don’t have a field for card type (it can be derived from first two digits on the card)
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 67 The back of the story card Image © Stuart Miles @ http://www.freedigitalphotos.net/ How to test the user story Test with Visa/MasterCard/American Express. Acc. to Cohn Test with Diner’s Club. Test with good/bad/missing card ID numbers. Test with expired cards. Test with over $100 and under $100. (fail) (pass)
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 68 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 69 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 70 Good practices: Requirements validation
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Good practices  Review the requirements (peer review, rigorous inspection, etc.).  Test the requirements for documenting the expected behaviour under specified conditions.  Define acceptance criteria together with users and based on their requirements.  Simulate the requirements (simulations with mock-ups to validate requirements and make design choices if necessary). 71 Acc. to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 72 To take away…
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Key actions 73 Acc. to Wiegers & Beatty Validation Reviewing the documented requirements to correct any problems before the development group accepts them. Developing acceptance tests and criteria to confirm that a product based on the requirements would meet customer needs and achieve the business objectives. According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield The inspection process 74 Initial work product Planning Preparation Inspection meetingRework Follow-up Baselined work product Entry criteria Exit criteria According to Wiegers & Beatty
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 75 The back of the story card Image © Stuart Miles @ http://www.freedigitalphotos.net/ How to test the user story Test with Visa/MasterCard/American Express. Acc. to Cohn Test with Diner’s Club. Test with good/bad/missing card ID numbers. Test with expired cards. Test with over $100 and under $100. (fail) (pass)
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 76 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 77 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 78 What comes next?
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 79 Subdisciplines of Requirements Management Tracking Requirements Engineering Managing Controlling Tracing Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 80 Other references
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Requirements-Engineering und -Management: Aus der Praxis von klassisch bis agil Chris Rupp & die SOPHISTen 6th Edition, 570 pp. Carl Hanser Verlag München, 2014 ISBN-13: 978-3-446-43893-4 In German (Chapters and related topics in English are available for free at https://www.sophist.de/) 81 Rupp & The SOPHISTs
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Other books 82
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Other books 83
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Further reading  IREB - International Requirements Engineering Board e.V. http://www.ireb.org/en/service/downloads.html 84
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Conference sites…  21st International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2015), Essen, Germany http://refsq.org/2015/ 85
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Conference sites…  23rd IEEE International Requirements Engineering Conference (RE’15), Ottawa, Canada http://re15.org/ 86
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 87 The traditional software development process: Perceptions, communication patterns and interests…
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 88Cartoon  http://projectcartoon.com/
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 89 The ideal, perfect, still possible software development process: Perceptions, communication patterns and interests…
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 90Adapted from cartoon  http://projectcartoon.com/
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield 91 Done!  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
D. Monett – Europe Week 2015, University of Hertfordshire, Hatfield Methods for Validating and Testing Software Requirements Prof. Dr. Dagmar Monett Díaz Computer Science Dept. Faculty of Cooperative Studies Berlin School of Economics and Law dagmar@monettdiaz.com Europe Week, 2nd – 6th March 2015 monettdiaz@dmonett

More Related Content

PDF
Modelling Software Requirements: Important diagrams and templates (lecture sl...
byDagmar Monett
 
PDF
A Structured Approach to Requirements Analysis (lecture slides)
byDagmar Monett
 
PDF
Requirements Engineering Methods for Documenting Requirements (lecture slides)
byDagmar Monett
 
PDF
Requirements Engineering Techniques for Eliciting Requirements (lecture slides)
byDagmar Monett
 
PDF
SQA Components
byLuthfia Ulinnuha
 
PDF
Sa03 tactics
byAmberMughal5
 
PPTX
Ch 6 development plan and quality plan
byKittitouch Suteeca
 
PDF
COCOMO Model By Dr. B. J. Mohite
byZeal Education Society, Pune
 
Modelling Software Requirements: Important diagrams and templates (lecture sl...
byDagmar Monett
 
A Structured Approach to Requirements Analysis (lecture slides)
byDagmar Monett
 
Requirements Engineering Methods for Documenting Requirements (lecture slides)
byDagmar Monett
 
Requirements Engineering Techniques for Eliciting Requirements (lecture slides)
byDagmar Monett
 
SQA Components
byLuthfia Ulinnuha
 
Sa03 tactics
byAmberMughal5
 
Ch 6 development plan and quality plan
byKittitouch Suteeca
 
COCOMO Model By Dr. B. J. Mohite
byZeal Education Society, Pune
 

What's hot

PPTX
Software Development Process
byAmira Elsayed Ismail
 
PPT
Pressman ch-3-prescriptive-process-models
bysaurabhshertukde
 
PPT
PROCESS MODELS.ppt
byDrTThendralCompSci
 
PPS
8 Characteristics of good user requirements
byguest24d72f
 
PPT
SE CHAPTER 1 SOFTWARE ENGINEERING
byAbrar ali
 
PDF
Requirements Validation
byAntonio Villegas
 
PPTX
requirement documentation
byratneshsinghparihar
 
PPT
Requirements analysis
byasimnawaz54
 
PPT
Software Quality Challenge
byHelmy Satria
 
PDF
Software project management
byR A Akerkar
 
PPT
Requirement elicitation
byvivacemente
 
PPT
Different approaches to software design
bySandeep Kumar Nayak
 
PPTX
Ch 3 software quality factor
byKittitouch Suteeca
 
PPTX
RAD Model & Prototyping Of Software Engineering
byUmeed Charity
 
PPTX
Modified Genetic Algorithm for Solving n-Queens Problem
byInternational Islamic University
 
PDF
Case tools
byRoy Antony Arnold G
 
PPTX
Ch 2 what is software quality
byKittitouch Suteeca
 
PPTX
Requirements validation - requirements engineering
byRa'Fat Al-Msie'deen
 
PPTX
Iterative and Incremental Development (RAD)
byRoshan Karunarathna
 
PDF
Software Requirements and Specifications
byvustudent1
 
Software Development Process
byAmira Elsayed Ismail
 
Pressman ch-3-prescriptive-process-models
bysaurabhshertukde
 
PROCESS MODELS.ppt
byDrTThendralCompSci
 
8 Characteristics of good user requirements
byguest24d72f
 
SE CHAPTER 1 SOFTWARE ENGINEERING
byAbrar ali
 
Requirements Validation
byAntonio Villegas
 
requirement documentation
byratneshsinghparihar
 
Requirements analysis
byasimnawaz54
 
Software Quality Challenge
byHelmy Satria
 
Software project management
byR A Akerkar
 
Requirement elicitation
byvivacemente
 
Different approaches to software design
bySandeep Kumar Nayak
 
Ch 3 software quality factor
byKittitouch Suteeca
 
RAD Model & Prototyping Of Software Engineering
byUmeed Charity
 
Modified Genetic Algorithm for Solving n-Queens Problem
byInternational Islamic University
 
Case tools
byRoy Antony Arnold G
 
Ch 2 what is software quality
byKittitouch Suteeca
 
Requirements validation - requirements engineering
byRa'Fat Al-Msie'deen
 
Iterative and Incremental Development (RAD)
byRoshan Karunarathna
 
Software Requirements and Specifications
byvustudent1
 

Viewers also liked

PDF
Key Issues for Requirements Engineering (lecture slides)
byDagmar Monett
 
PPTX
Human aspect in scrum
byAJAY RAWAT
 
PPT
Scrum Concepts
byRick Barron
 
PPTX
How to deal with bad requirements of software
byBugRaptors
 
PPTX
Put Risk Based Testing in place right now!
bySQALab
 
PPTX
Requirements Driven Risk Based Testing
byJeff Findlay
 
PPTX
ATLAS Automation POC
byaakashmc
 
PPT
Practical Application Of Risk Based Testing Methods
byReuben Korngold
 
PPTX
Risk-based Testing
byJohan Hoberg
 
PPTX
risk based testing and regression testing
byToshi Patel
 
PDF
Bringing the hacker mindset into requirements and testing by Eapen Thomas and...
byQA or the Highway
 
PDF
What to do with the problems you cannot solve?
bySQALab
 
PDF
Software Requirements for Safety-related Systems
byVittorio Giovara
 
PDF
Requirements are King – Better Requirements = Better Software
byCA Technologies
 
PDF
Agile or traditional Software Engineering?
byDagmar Monett
 
PDF
Walking the path from the MOOC to my classroom: My collection of methods and ...
byDagmar Monett
 
PDF
MATHEON Center Days: Index determination and structural analysis using Algori...
byDagmar Monett
 
PDF
Predicting Star Ratings based on Annotated Reviewss of Mobile Apps [Slides]
byDagmar Monett
 
PDF
Using BDI-extended NetLogo Agents in Undergraduate CS Research and Teaching
byDagmar Monett
 
PDF
Joint Software Engineering to support STEM Education: Experiences before, dur...
byDagmar Monett
 
Key Issues for Requirements Engineering (lecture slides)
byDagmar Monett
 
Human aspect in scrum
byAJAY RAWAT
 
Scrum Concepts
byRick Barron
 
How to deal with bad requirements of software
byBugRaptors
 
Put Risk Based Testing in place right now!
bySQALab
 
Requirements Driven Risk Based Testing
byJeff Findlay
 
ATLAS Automation POC
byaakashmc
 
Practical Application Of Risk Based Testing Methods
byReuben Korngold
 
Risk-based Testing
byJohan Hoberg
 
risk based testing and regression testing
byToshi Patel
 
Bringing the hacker mindset into requirements and testing by Eapen Thomas and...
byQA or the Highway
 
What to do with the problems you cannot solve?
bySQALab
 
Software Requirements for Safety-related Systems
byVittorio Giovara
 
Requirements are King – Better Requirements = Better Software
byCA Technologies
 
Agile or traditional Software Engineering?
byDagmar Monett
 
Walking the path from the MOOC to my classroom: My collection of methods and ...
byDagmar Monett
 
MATHEON Center Days: Index determination and structural analysis using Algori...
byDagmar Monett
 
Predicting Star Ratings based on Annotated Reviewss of Mobile Apps [Slides]
byDagmar Monett
 
Using BDI-extended NetLogo Agents in Undergraduate CS Research and Teaching
byDagmar Monett
 
Joint Software Engineering to support STEM Education: Experiences before, dur...
byDagmar Monett
 

Similar to Methods for Validating and Testing Software Requirements (lecture slides)

PPSX
Verifying and Validating Requirements
byRavikanth-BA
 
PPT
Software requirement verification & validation
byAbdul Basit
 
PPT
Requirement verification & validation
byAbdul Basit
 
PPTX
Requirements engineering activities
bySyed Zaid Irshad
 
PDF
Lecture 6 - Requirements Engineering (Part 2).pdf
bydotnetfiler
 
PPT
Software Engineering Lec 4-requirments
byTaymoor Nazmy
 
PPT
Requirement Management.ppt
bySoham De
 
ODP
Requirement analysis
bySangeet Shah
 
PPT
5. Requirement Engineering Process(1).ppt
byniyatipatel481617
 
PDF
Teaching Students Collaborative Requirements Engineering. Case Study Red:Wire
byDagmar Monett
 
PDF
Crutial steps in requirement gathering
byAbhinav Sabharwal- Business Analyst Mumbai
 
PPT
Requirements analysis lecture
byMakerere University
 
PPT
Requirment Engineering WITH SPECIAL EFFECTS
byAssadLeo1
 
PPTX
Chapter 3 - Requirement Specification 2.pptx
byRobelAmare2
 
PPT
Requirements - validation in software engineering
bymohammedarshadhussai4
 
PPT
Lecture 03-Software Requirement nnew.ppt
byzaifclothings
 
PPTX
requirement Engineeringggggggggggggggggg
bypspreeti916
 
PPT
Requirements engineering vii
byindrisrozas
 
PPT
5. SE RequirementEngineering task.ppt
byHaiderAli252366
 
PPTX
Requirements Engineering Essentials.pptx
byblltariq21
 
Verifying and Validating Requirements
byRavikanth-BA
 
Software requirement verification & validation
byAbdul Basit
 
Requirement verification & validation
byAbdul Basit
 
Requirements engineering activities
bySyed Zaid Irshad
 
Lecture 6 - Requirements Engineering (Part 2).pdf
bydotnetfiler
 
Software Engineering Lec 4-requirments
byTaymoor Nazmy
 
Requirement Management.ppt
bySoham De
 
Requirement analysis
bySangeet Shah
 
5. Requirement Engineering Process(1).ppt
byniyatipatel481617
 
Teaching Students Collaborative Requirements Engineering. Case Study Red:Wire
byDagmar Monett
 
Crutial steps in requirement gathering
byAbhinav Sabharwal- Business Analyst Mumbai
 
Requirements analysis lecture
byMakerere University
 
Requirment Engineering WITH SPECIAL EFFECTS
byAssadLeo1
 
Chapter 3 - Requirement Specification 2.pptx
byRobelAmare2
 
Requirements - validation in software engineering
bymohammedarshadhussai4
 
Lecture 03-Software Requirement nnew.ppt
byzaifclothings
 
requirement Engineeringggggggggggggggggg
bypspreeti916
 
Requirements engineering vii
byindrisrozas
 
5. SE RequirementEngineering task.ppt
byHaiderAli252366
 
Requirements Engineering Essentials.pptx
byblltariq21
 

More from Dagmar Monett

PDF
Deconstructing the AI Myth: Fallacies and Harms of Algorithmification
byDagmar Monett
 
PDF
Narratives that speak AI lingua? AI vocabulary in listed companies' annual re...
byDagmar Monett
 
PDF
Game-based Learning as a Suitable Approach for Teaching Digital Ethical Think...
byDagmar Monett
 
PDF
University-Industry Collaboration's Next Level: A Comparative Study as Basis ...
byDagmar Monett
 
PDF
The Changing Landscape of Digital Technologies for Learning
byDagmar Monett
 
PDF
Will Robots Take all the Jobs? Not yet.
byDagmar Monett
 
PDF
Coming to terms with intelligence in machines
byDagmar Monett
 
PDF
The Intelligence Corpus, an Annotated Corpus of Definitions of Intelligence: ...
byDagmar Monett
 
PDF
Artificial Intelligence: The Promise, the Myth, and a Dose of Reality
byDagmar Monett
 
PDF
Intelligence, the elusive concept and general capability still not found in m...
byDagmar Monett
 
PDF
The I in AI (or why there is still none)
byDagmar Monett
 
PDF
Erfahrungen aus Projektbasiertes Lernen im Informatik Studium - The Missing p...
byDagmar Monett
 
PDF
Simulating the Fractional Reserve Banking using Agent-based Modelling with Ne...
byDagmar Monett
 
PDF
E-Learning Adoption in a Higher Education Setting: An Empirical Study
byDagmar Monett
 
PDF
Evolving Lesson Plans to Assist Educators: From Paper-Based to Adaptive Lesso...
byDagmar Monett
 
PDF
Understanding the Cuban Blogosphere: Retrospective and Perspectives based on ...
byDagmar Monett
 
PDF
Genetic Algorithms and Ant Colony Optimisation (lecture slides)
byDagmar Monett
 
PDF
Introduction to Agents and Multi-agent Systems (lecture slides)
byDagmar Monett
 
PDF
Experiences in Software Testing (lecture slides)
byDagmar Monett
 
PDF
Agile Project-Based Teaching and Learning
byDagmar Monett
 
Deconstructing the AI Myth: Fallacies and Harms of Algorithmification
byDagmar Monett
 
Narratives that speak AI lingua? AI vocabulary in listed companies' annual re...
byDagmar Monett
 
Game-based Learning as a Suitable Approach for Teaching Digital Ethical Think...
byDagmar Monett
 
University-Industry Collaboration's Next Level: A Comparative Study as Basis ...
byDagmar Monett
 
The Changing Landscape of Digital Technologies for Learning
byDagmar Monett
 
Will Robots Take all the Jobs? Not yet.
byDagmar Monett
 
Coming to terms with intelligence in machines
byDagmar Monett
 
The Intelligence Corpus, an Annotated Corpus of Definitions of Intelligence: ...
byDagmar Monett
 
Artificial Intelligence: The Promise, the Myth, and a Dose of Reality
byDagmar Monett
 
Intelligence, the elusive concept and general capability still not found in m...
byDagmar Monett
 
The I in AI (or why there is still none)
byDagmar Monett
 
Erfahrungen aus Projektbasiertes Lernen im Informatik Studium - The Missing p...
byDagmar Monett
 
Simulating the Fractional Reserve Banking using Agent-based Modelling with Ne...
byDagmar Monett
 
E-Learning Adoption in a Higher Education Setting: An Empirical Study
byDagmar Monett
 
Evolving Lesson Plans to Assist Educators: From Paper-Based to Adaptive Lesso...
byDagmar Monett
 
Understanding the Cuban Blogosphere: Retrospective and Perspectives based on ...
byDagmar Monett
 
Genetic Algorithms and Ant Colony Optimisation (lecture slides)
byDagmar Monett
 
Introduction to Agents and Multi-agent Systems (lecture slides)
byDagmar Monett
 
Experiences in Software Testing (lecture slides)
byDagmar Monett
 
Agile Project-Based Teaching and Learning
byDagmar Monett
 

Recently uploaded

PDF
Risks and opportunities of artificial intelligence in education: A critical view
byYannis
 
PPTX
HABIT. Cognitive process. I Semester Shilpa Hotakar pptx
bySHILPA HOTAKAR
 
PDF
NCA New Family Orientation 2026 Dosemagen.pdf
bytimdosemagen1
 
PPTX
COMMUNICATION ITS PROCESS ELEMENTS & BARRIER .pptx
byPoojaSen20
 
PPTX
TLE 8 W1 Q4 D2.pptx COMMON FLOOR PLAN SYMBOLS PLUMBING SYMBOLS
byraquelanaaltres1
 
PDF
Information about Presentation strategies
bymansivaja18126
 
PDF
Take This Quirky Quiz! - QGI 1st Anniversary .pdf
byNiyati Jois
 
PPTX
Powerpoint for testing in embed test with Sway
byjeanpierrefort3
 
PPTX
Metabolism ( BIOCHEMISTRY & CLINICAL PATHOLOGY )
byBushraDeshpande
 
PPTX
Central Line Associated Bloodstream Infection
bynabinabhaila40
 
PPTX
Exploring Higher education and its pathways
byEVAMAEBONGHANOY5
 
PPTX
That long silence - Novel by Shashi Deshapande
bysanjanavaghela65
 
PDF
Oscillations /Revision notes prepared by K sandeep swamy (Msc,BEd)/For online...
bySandeep Swamy
 
PDF
Aminoglycosides.pdf for B.Pharmacy Medicinal Chemistry-III (BP601T), GPAT, a...
bymominzarinamdnajeeb
 
PPTX
Unit 3- Culture.pptx....................
byAkanksha Kotangale
 
PPTX
The night at deoli - Ruskin bond's story of first love
byrajibhammar4
 
PPTX
" Jaya : Silence as Resistance " - That long silence
bydharabhandari35
 
PPTX
Reimagining Academic Library Services through Artificial Intelligence: A Case...
byDon Bosco College, Itanagar
 
PDF
ĐỀ MINH HỌA KỲ THI TỐT NGHIỆP TRUNG HỌC PHỔ THÔNG NĂM 2026 MÔN TIẾNG ANH 2026...
byNguyen Thanh Tu Collection
 
PPTX
MENTAL STATUS EXAMINATION Part-1.Shilpa hotakar.pptx
bySHILPA HOTAKAR
 
Risks and opportunities of artificial intelligence in education: A critical view
byYannis
 
HABIT. Cognitive process. I Semester Shilpa Hotakar pptx
bySHILPA HOTAKAR
 
NCA New Family Orientation 2026 Dosemagen.pdf
bytimdosemagen1
 
COMMUNICATION ITS PROCESS ELEMENTS & BARRIER .pptx
byPoojaSen20
 
TLE 8 W1 Q4 D2.pptx COMMON FLOOR PLAN SYMBOLS PLUMBING SYMBOLS
byraquelanaaltres1
 
Information about Presentation strategies
bymansivaja18126
 
Take This Quirky Quiz! - QGI 1st Anniversary .pdf
byNiyati Jois
 
Powerpoint for testing in embed test with Sway
byjeanpierrefort3
 
Metabolism ( BIOCHEMISTRY & CLINICAL PATHOLOGY )
byBushraDeshpande
 
Central Line Associated Bloodstream Infection
bynabinabhaila40
 
Exploring Higher education and its pathways
byEVAMAEBONGHANOY5
 
That long silence - Novel by Shashi Deshapande
bysanjanavaghela65
 
Oscillations /Revision notes prepared by K sandeep swamy (Msc,BEd)/For online...
bySandeep Swamy
 
Aminoglycosides.pdf for B.Pharmacy Medicinal Chemistry-III (BP601T), GPAT, a...
bymominzarinamdnajeeb
 
Unit 3- Culture.pptx....................
byAkanksha Kotangale
 
The night at deoli - Ruskin bond's story of first love
byrajibhammar4
 
" Jaya : Silence as Resistance " - That long silence
bydharabhandari35
 
Reimagining Academic Library Services through Artificial Intelligence: A Case...
byDon Bosco College, Itanagar
 
ĐỀ MINH HỌA KỲ THI TỐT NGHIỆP TRUNG HỌC PHỔ THÔNG NĂM 2026 MÔN TIẾNG ANH 2026...
byNguyen Thanh Tu Collection
 
MENTAL STATUS EXAMINATION Part-1.Shilpa hotakar.pptx
bySHILPA HOTAKAR
 

Methods for Validating and Testing Software Requirements (lecture slides)

  • 1.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Methods for Validating and Testing Software Requirements Prof. Dr. Dagmar Monett Díaz Computer Science Dept. Faculty of Cooperative Studies Berlin School of Economics and Law dagmar@monettdiaz.com Europe Week, 2nd – 6th March 2015 60 Minutes
  • 2.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Dilbert  Scott Adams At http://dilbert.com/strip/2014-02-25/ (Educational/Classroom usage permission is granted by Universal Uclick. All Rights Reserved) Different goals… 2
  • 3.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 3 Main topics
  • 4.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 4 Main topics  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 5.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 5 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 6.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 6 ©
  • 7.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Software Requirements Karl Wiegers and Joy Beatty 3rd Edition, 672 pp. Microsoft Press, 2013 ISBN-13: 978-0-7356-7966-5 (See more at http://aka.ms/SoftwareReq3E/files) 7 Wiegers & Beatty
  • 8.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Software Engineering Ian Sommerville 9th Edition, 792 pp. Addison-Wesley, 2010 ISBN-13: 978-0137035151 (10th Edition: April 2015. See more at http://iansommerville.com/software- engineering-book/) 8 Sommerville
  • 9.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 9 The traditional software development process: Perceptions, communication patterns and interests…
  • 10.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 10Cartoon  http://projectcartoon.com/
  • 11.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 11Cartoon  http://projectcartoon.com/
  • 12.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 12 Requirements and Requirements Engineering – An Overview –
  • 13.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 13 Requirement: A definition According to Wiegers & Beatty: “[A requirement is a] statement of a customer need or objective, or of a condition or capability that a product must possess to satisfy such a need or objective. A property that a product must have to provide value to a stakeholder.” See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
  • 14.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Requirements Engineering Definition according to Wiegers & Beatty: Requirements engineering is the subdiscipline of systems engineering and software engineering that encompasses all project activities associated with understanding a product's necessary capabilities and attributes. Includes both requirements development and requirements management. 14 See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
  • 15.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 15 Subdisciplines of Requirements Engineering
  • 16.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 16 Subdisciplines of Requirements Engineering Requirements Engineering Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
  • 17.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 17 Subdisciplines of Requirements Development Elicitation Requirements Engineering Analysis Specification Validation Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
  • 18.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 18 Subdisciplines of Requirements Management Tracking Requirements Engineering Managing Controlling Tracing Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
  • 19.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 19 Topics of other related lectures
  • 20.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 20 Subdisciplines of Requirements Engineering Elicitation Requirements Engineering Analysis Specification Validation Requirements Development Requirements Management All are topics of lecture: “A Structured Approach to Requirements Analysis”
  • 21.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 21 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Analysis Specification Validation Topic of lecture “Requirements Engineering Techniques for Eliciting Requirements”
  • 22.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 22 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Specification Validation Topics of lecture “Requirements Engineering Methods for Documenting Requirements” Analysis
  • 23.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 23 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Analysis Specification Validation Also topic of lecture “Modelling Software Requirements. Important diagrams and templates”
  • 24.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 24 Subdisciplines of Requirements Development Requirements Engineering Requirements Development Requirements Management Elicitation Analysis Specification Validation Topic of (this) lecture “Methods for Validating and Testing Software Requirements”
  • 25.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 25 A Requirements Development process framework
  • 26.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 26 Subdisciplines of Requirements Development Elicitation Requirements Engineering Analysis Specification Validation Requirements Development Requirements Management Acc. to Wiegers & Beatty
  • 27.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield RD process framework 27 Elicitation Analysis Specification Validation re-evaluate Adapted from Wiegers & Beatty identifying, discovering evaluating, verifying documenting, SRS classifying, representing, deriving, negotiating RD: Requirements Development SRS: Software Requirements Specification See lecture “A Structured Approach to Requirements Analysis” for details!
  • 28.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 28 A structured approach to Requirements Development
  • 29.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 29 A structured approach to RD (1) Define stakeholders!  Who is interested in the system?  Who makes decisions?  Who are the users, managers, developers, etc.? In other words, WHO has influence on the software requirements? (2) Define goals!  Stakeholders have goals (define coarse goals!)  These goals can be divided into more specific goals (define granular goals!) In other words, WHAT should be implemented or achieved? (3) Define requirements!  Goals can be derived into concrete requirements  How to get to the requirements? (goal-based!)  Model those requirements using diagrams, templates, etc. In other words, HOW will the goals be achieved?
  • 30.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 30 A structured approach to RD Granular goals CG3 CG2 CG1 Coarse goals Define stakeholders Define goals Define requirements Diagrams Templates Models WHO WHAT HOW See lecture “A Structured Approach to Requirements Analysis” for details!
  • 31.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 31 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 32.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 32 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 33.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 33 Requirements Validation
  • 34.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield RD process framework 34 Elicitation Analysis Specification Validation re-evaluate Adapted from Wiegers & Beatty identifying, discovering evaluating, verifying documenting, SRS classifying, representing, deriving, negotiating RD: Requirements Development SRS: Software Requirements Specification
  • 35.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield RD process framework 35 Elicitation Analysis Specification Validation re-evaluate Adapted from Wiegers & Beatty identifying, discovering evaluating, verifying documenting, SRS classifying, representing, deriving, negotiating RD: Requirements Development SRS: Software Requirements Specification
  • 36.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Validation and verification 36 Acc. to Wiegers & Beatty “[Validation is the] process of evaluating a project deliverable to determine whether it satisfies customer needs.” ‘Are we building the right product?’ “[Verification is the] process of evaluating a project deliverable to determine whether it satisfies the specifications on which it was based.” ‘Are we building the product right?’
  • 37.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 37 Key actions in validation
  • 38.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Key actions 38 Acc. to Wiegers & Beatty Validation Reviewing the documented requirements to correct any problems before the development group accepts them. According to Wiegers & Beatty
  • 39.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Key actions 39 Acc. to Wiegers & Beatty Validation Reviewing the documented requirements to correct any problems before the development group accepts them. Developing acceptance tests and criteria to confirm that a product based on the requirements would meet customer needs and achieve the business objectives. According to Wiegers & Beatty
  • 40.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 40 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 41.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 41 Active learning exercise Image © renjith krishnan at http://www.freedigitalphotos.net/
  • 42.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Quiz 42 Which is an activity in the validation process? (A) Negotiating. (B) Discovering. (C) Evaluating. (D) Classifying.
  • 43.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 43 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 44.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 44 Reviewing requirements
  • 45.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Dilbert  Scott Adams At http://dilbert.com/strip/2013-02-25/ (Educational/Classroom usage permission is granted by Universal Uclick. All Rights Reserved) Failed feedback… 45
  • 46.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Peer review 46 “[A peer review is an] activity in which one or more persons other than the author of a work product examine that product with the intent of finding defects and improvement opportunities.” According to Wiegers & Beatty:
  • 47.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Peer review approaches 47 Peer deskcheck: asking one colleague to look over your own work product. According to Wiegers & Beatty Passaround: inviting several colleagues to examine a deliverable concurrently. Walkthrough: the author describes a deliverable and solicits comments on it. Informal peer reviews:
  • 48.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 48 The inspection process
  • 49.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 49 Inspection: A definition According to Wiegers & Beatty: “[Inspection is a] type of formal peer review that involves a trained team of individuals who follow a well-defined process to examine a work product carefully for defects.”  Originally developed by Michael Fagan at IBM (1976)  Software industry best practice  Best-established type of formal peer review
  • 50.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 50 Inspection The participants (<7) The author of the work product and perhaps peers of the author People who are the sources of information that fed into the item being inspected People who will do work based on the item being inspected People who are responsible for interfacing systems that will be affected by the item being inspected According to Wiegers & Beatty
  • 51.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 51 Inspection roles Author They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. According to Wiegers & Beatty
  • 52.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 52 Inspection roles Author Moderator They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. - Plans inspection with author, coordinates activities, facilitates the inspection meeting. According to Wiegers & Beatty
  • 53.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 53 Inspection roles Author Moderator Reader They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. - Plans inspection with author, coordinates activities, facilitates the inspection meeting. - Paraphrases requirements and model elements. The other participants point out potential defects and issues they see. According to Wiegers & Beatty
  • 54.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 54 Inspection roles Author Moderator Reader Recorder They look for defects and improvement opportunities - Plays passive role during inspection, listens to comments, answers questions. - Plans inspection with author, coordinates activities, facilitates the inspection meeting. - Paraphrases requirements and model elements. The other participants point out potential defects and issues they see. - Documents issues raised and defects found. According to Wiegers & Beatty
  • 55.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield The inspection process 55 Initial work product Planning Preparation Inspection meetingRework Follow-up Baselined work product Entry criteria Exit criteria According to Wiegers & Beatty
  • 56.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Defect checklist 56  Helps reviewers look for typical kinds of errors. According to Wiegers & Beatty Image © Stuart Miles @ http://www.freedigitalphotos.net/
  • 57.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Defect checklist 57 Examples of topics to check out: Completeness  Do the requirements address all known customer or system needs? Correctness  Do any requirements conflict with or duplicate other requirements? Organisation and traceability  Is each requirement uniquely and correctly labelled? According to Wiegers & Beatty
  • 58.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 58 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 59.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 59 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 60.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 60 Testing requirements
  • 61.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Tests 61  Powerful tool for both validating and verifying requirements.  Evaluate functional requirements, analysis models, and prototypes.  Should cover normal and alternative flows identified during elicitation and analysis. According to Wiegers & Beatty
  • 62.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Example of conceptual test 62 Use case: Test: According to Wiegers & Beatty “User enters order number to view, order exists, user had placed the order. Expected result: show order details.” View a stored order
  • 63.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 63 Validating with acceptance criteria
  • 64.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Acceptance criteria 64 According to Wiegers & Beatty: “[Acceptance criteria are] conditions that a software product must satisfy to be accepted by a user, customer, or other stakeholder.”  From “What do you need to do with the system?”…  …to “How would you judge whether the solution meets your needs?”
  • 65.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Acceptance Test 65 According to Wiegers & Beatty: “[An acceptance test is a] test that evaluates anticipated usage scenarios to determine the software's acceptability. Used in agile development both to express details about a user story and to determine whether a user story is fully and correctly implemented.”
  • 66.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 66 The front of a story card Acc. to Cohn Image © Stuart Miles @ http://www.freedigitalphotos.net/ Conver- sations The description A company can pay for a job posting with a credit card. Note: Will we accept Discover cards? Note for UI: Don’t have a field for card type (it can be derived from first two digits on the card)
  • 67.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 67 The back of the story card Image © Stuart Miles @ http://www.freedigitalphotos.net/ How to test the user story Test with Visa/MasterCard/American Express. Acc. to Cohn Test with Diner’s Club. Test with good/bad/missing card ID numbers. Test with expired cards. Test with over $100 and under $100. (fail) (pass)
  • 68.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 68 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 69.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 69 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 70.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 70 Good practices: Requirements validation
  • 71.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Good practices  Review the requirements (peer review, rigorous inspection, etc.).  Test the requirements for documenting the expected behaviour under specified conditions.  Define acceptance criteria together with users and based on their requirements.  Simulate the requirements (simulations with mock-ups to validate requirements and make design choices if necessary). 71 Acc. to Wiegers & Beatty
  • 72.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 72 To take away…
  • 73.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Key actions 73 Acc. to Wiegers & Beatty Validation Reviewing the documented requirements to correct any problems before the development group accepts them. Developing acceptance tests and criteria to confirm that a product based on the requirements would meet customer needs and achieve the business objectives. According to Wiegers & Beatty
  • 74.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield The inspection process 74 Initial work product Planning Preparation Inspection meetingRework Follow-up Baselined work product Entry criteria Exit criteria According to Wiegers & Beatty
  • 75.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 75 The back of the story card Image © Stuart Miles @ http://www.freedigitalphotos.net/ How to test the user story Test with Visa/MasterCard/American Express. Acc. to Cohn Test with Diner’s Club. Test with good/bad/missing card ID numbers. Test with expired cards. Test with over $100 and under $100. (fail) (pass)
  • 76.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 76 So far…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 77.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 77 Next topics…  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 78.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 78 What comes next?
  • 79.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 79 Subdisciplines of Requirements Management Tracking Requirements Engineering Managing Controlling Tracing Requirements Development Requirements Management Acc. to Wiegers & Beatty See lecture “A Structured Approach to Requirements Analysis” for more on this topic!
  • 80.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 80 Other references
  • 81.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Requirements-Engineering und -Management: Aus der Praxis von klassisch bis agil Chris Rupp & die SOPHISTen 6th Edition, 570 pp. Carl Hanser Verlag München, 2014 ISBN-13: 978-3-446-43893-4 In German (Chapters and related topics in English are available for free at https://www.sophist.de/) 81 Rupp & The SOPHISTs
  • 82.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Other books 82
  • 83.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Other books 83
  • 84.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Further reading  IREB - International Requirements Engineering Board e.V. http://www.ireb.org/en/service/downloads.html 84
  • 85.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Conference sites…  21st International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2015), Essen, Germany http://refsq.org/2015/ 85
  • 86.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Conference sites…  23rd IEEE International Requirements Engineering Conference (RE’15), Ottawa, Canada http://re15.org/ 86
  • 87.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 87 The traditional software development process: Perceptions, communication patterns and interests…
  • 88.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 88Cartoon  http://projectcartoon.com/
  • 89.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 89 The ideal, perfect, still possible software development process: Perceptions, communication patterns and interests…
  • 90.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 90Adapted from cartoon  http://projectcartoon.com/
  • 91.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield 91 Done!  Where does the major content come from?  Requirements Engineering and Requirements Development: An Overview  Requirements validation. Key actions  Reviewing requirements - Informal and formal approaches  Testing requirements - Validating with acceptance criteria  Good practices in validation  What’s next? Further reading, sources of inspiration
  • 92.
    D. Monett –Europe Week 2015, University of Hertfordshire, Hatfield Methods for Validating and Testing Software Requirements Prof. Dr. Dagmar Monett Díaz Computer Science Dept. Faculty of Cooperative Studies Berlin School of Economics and Law dagmar@monettdiaz.com Europe Week, 2nd – 6th March 2015 monettdiaz@dmonett