SlideShare a Scribd company logo
1 of 35
Download to read offline
Session 03: Requirement
R2S Academy – Internal Use – Author: Tuan Ngo
Table of Content
Requirement (types / attributes / sources)
Good vs bad requirement
Requirement examples & Exercises
R2S Academy – Internal Use – Author: TUAN NGO
1
2
3
Objectives
Business needs vs Requirements
1
Requirement
Requirement
Business needs vs Requirements
Business needs Requirements
Are goals and objectives a
business must achieve
Are things that we need to do in
order to achieve a need
Can be seperated into lower-level,
detailed requirements
A need can have one more than
requirement
Not as specific as requirements More specific and detailed
Business Analyst Requirement Engineer
Requirement
Business needs vs Requirements
28/02/2022 R2S Academy - Internal Use
Business needs Requirements
Build a big house for my
large family
- The house shall have 3 rooms
+ 2 small bedrooms
+ 1 living room
- The house shall have a backyard
- The house shall be 3 levels
- The floors shall be wood
- The wood color shall be dark brown
Get a BA job - I should take a BA course
- I should create a resume
- I should practice mockup interviews
Build my portfolio website - The website shall allow clients to contact me
- The website shall have a blog
- The website shall present my projects
Requirement Types
Requirement
Requirement
Types
Requirement
Types
Requirement
Types
1. Business Requirements
• a high level statement describing what is required from the business’s
perspective
2. Stakeholder Requirements
• The stakeholders are the main source of requirements. They have specific
needs that the analyst must identify
3. Technical Requirements
• They are the technical constraints and policies that must be adhered to.
• These fall under the following four subheadings: Hardware, Software,
Interoperability, Internet
4. Functional Requirements
• Describes how the solution must behave
• What the system does?
5. Non-Functional Requirements
• Describes the attributes a system or process must perform
• How the system works?
• Examples:
• A website should be capable enough to handle 20 million users (CCU)
• The website should have response time less than 5 seconds
6. Transition Requirements
• Describe the capabilities / conditions that the solution must have to
transition from the current state to the future state
Requirement
Types
Requirement
Non-functional Requirement
Requirement
Requirement
Requirement Attributes
Requirement
Requirement
Attributes
28/02/2022 15
R2S Academy - Internal Use
1. Unique ID Easily find it and link it to its business objectives and test cases.
2. Date Created Allows us to precisely trace when and where it originated;
provide valuable information for prioritization and change management.
3. Current Version The requirement version number can be used for flagging different versions of the same
requirement to prevent confusion. (e.g. v.0.1, v.1.0)
4. Requirement Author Indicates who proposed a requirement.
5. Assigned To To facilitate improved balancing of overall workload and lead to increased productivity in the entire
team.
6. Requirements Status Verbalized, Drafted, Confirmed, Verified, Validated, Prioritize, Approved
Requirement
Attributes
28/02/2022 16
R2S Academy - Internal Use
7. Priority Not all requirements are made equal. Some have much higher priority than others, and we should be able to
see which ones are the most important and which ones can be deferred to a later release. This attribute
provides an indication of which requirement should be implemented first.
High, Medium, Low
8. Risk To answer: What’s at stake if the requirement isn’t implemented?
9. Stability Before we start working on a requirement, we should confirm that it has reached a certain level of stability.
Developing software based on requirements that are subject to constant change is not efficient and is far
from productive.
10. Stakeholders This attribute indicates who will be affected should any changes be made to a requirement.
France
Technical Req. 2019
1/2
France
Technical Req. 2019
2/2
Denmark
Technical Req. 2021
KOREA
Project Req.
2018
US
Functional Req.
2020
Vietnam
Functional Req. 2021
Requirement Sources
Requirement
Requirement
Sources
28/02/2022 24
R2S Academy - Internal Use
New project Running project
ü By government/ users/ stakeholders (interview,
observation)
ü Knowledge transfer from colleagues or employees already working on
that project
ü Talk about project to business analyst, product manager, project lead
and developers
ü Analyze the existing system in the same domain ü Analyze previous system version that is already implemented into the
system
ü Analyze the older requirement document of the project
ü Look into the past Bug reports, some of the bug reports are turned
into enhancement request which may be implemented into current
version
ü Look into installation guide if it is available to see what are the
installation required
ü Analyze the domain or industry knowledge
Good vs Bad Requirement
Requirement
Good requirement
Good requirement
Example of bad requirement
R2S Academy - Internal Use
Good requirement
28/02/2022 28
R2S Academy - Internal Use
1. Unambiguous There should be only one way to interpret the requirement. Sometimes ambiguity is introduced by
undefined acronyms (e.g. TBD)
2. Testable (verifiable) Testers should be able to verify whether the requirement is implemented correctly. The test should
either pass or fail.
Avoid these words
• Some adjectives: robust, safe, accurate, efficient, expandable, flexible, reliable, user-friendly
• Some adverbs and adverbial phrases: quickly, safely, in a timely manner
• Indefinite pronouns: few, many, most, much, several, any, anybody, anything, some, etc.
Some ambiguous words or phrasing
• Modifying phrases: as appropriate, as required, if necessary, shall be considered
• Vague words: manage, handle
• Passive voice: the subject of the sentence receives the action of the verb rather than
performing it
Good requirement
28/02/2022 29
R2S Academy - Internal Use
3. Clear (Concise, Terse, Simple, Precise) Requirements should not contain unnecessary verbiage or information. They should be
stated clearly and simply
4. Correct If a requirement contains facts, these facts should be true
5. Understandable Requirements should be grammatically correct and written in a consistent style.
Standard conventions should be used. The word “shall” should be used instead of
“will,” “must,” or “may.”
6. Feasible (Realistic, Possible) The requirement should be doable within existing constraints such as time, money, and
available resources
7. Independent To understand the requirement, there should not be a need to know any other
requirement
8. Atomic The requirement should contain a single traceable element
Good requirement
28/02/2022 30
R2S Academy - Internal Use
9. Necessary A requirement is unnecessary if
- None of the stakeholders needs the requirement OR
- Removing the requirement will not affect the system
10. Implementation-free (Abstract) Requirements should not contain unnecessary design and implementation information.
11. Consistent There should not be any conflicts between the requirements.
Conflicts may be direct or indirect.
• Direct conflicts occur when, in the same situation, different behavior is expected. In this case
the conflict cannot be resolved by adding conditions, so one of the requirements should be
changed or removed
• Indirect conflicts occurs when requirements do not describe the same functionality, but it is not
possible to fulfill both requirements at the same time.
12. Nonredundant Each requirement should be expressed only once and should not overlap with another
requirement
13. Complete A requirement should be specified for all conditions that can occur
Good Requirement
Team work
S03_E03: Find mistake(s) in
below requirements
Good Requirement
Team work
S03_E03: Find mistake(s) in
below requirements
Good Requirement
Team work
S03_E03: Find mistake(s) in
below requirements
Good Requirement
Team work
S03_E03: Find mistake(s) in
below requirements
Session 3
Review

More Related Content

Similar to Session03-Requirement (1).pdf

1) Question Add Targets to Balanced score Card
1) Question  Add Targets to Balanced score Card1) Question  Add Targets to Balanced score Card
1) Question Add Targets to Balanced score CardAbbyWhyte974
 
1) question add targets to balanced score card
1) question  add targets to balanced score card1) question  add targets to balanced score card
1) question add targets to balanced score cardsmile790243
 
Sheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docx
Sheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docxSheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docx
Sheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docxedgar6wallace88877
 
From catalogues to models: transitioning from existing requirements technique...
From catalogues to models: transitioning from existing requirements technique...From catalogues to models: transitioning from existing requirements technique...
From catalogues to models: transitioning from existing requirements technique...James Towers
 
Requirements Gathering Best Practice Pack
Requirements Gathering Best Practice PackRequirements Gathering Best Practice Pack
Requirements Gathering Best Practice PackAmy Slater
 
Business RequirementsReference number Document Control
Business RequirementsReference number Document ControlBusiness RequirementsReference number Document Control
Business RequirementsReference number Document ControlTawnaDelatorrejs
 
Driving Ambiguities Out of Requirements through Stronger Elicitation Techniques
Driving Ambiguities Out of Requirements through Stronger Elicitation TechniquesDriving Ambiguities Out of Requirements through Stronger Elicitation Techniques
Driving Ambiguities Out of Requirements through Stronger Elicitation TechniquesSusan Schanta
 
The Art and Science of Requirements Gathering
The Art and Science of Requirements GatheringThe Art and Science of Requirements Gathering
The Art and Science of Requirements GatheringVanessa Turke
 
Business Requirements development
Business Requirements development Business Requirements development
Business Requirements development Mark Opanasiuk
 
Doing It On Your Own: When to Call in the Consultants, When to Leave Them Out
Doing It On Your Own: When to Call in the Consultants, When to Leave Them OutDoing It On Your Own: When to Call in the Consultants, When to Leave Them Out
Doing It On Your Own: When to Call in the Consultants, When to Leave Them OutNTEN
 
Website Design RFP Template
Website Design RFP TemplateWebsite Design RFP Template
Website Design RFP TemplateDemand Metric
 
Lecture 04
Lecture 04Lecture 04
Lecture 04Rana Ali
 
Lecture_three_Requirements_analysis.pptx
Lecture_three_Requirements_analysis.pptxLecture_three_Requirements_analysis.pptx
Lecture_three_Requirements_analysis.pptxGracePeter10
 
Requirements and Traceability With Pictures
Requirements and Traceability With PicturesRequirements and Traceability With Pictures
Requirements and Traceability With PicturesLeslie Munday
 
Free CCBA V3 question bank
Free CCBA V3 question bankFree CCBA V3 question bank
Free CCBA V3 question bankLN Mishra CBAP
 
2013 SharePoint Fest DC - Build a SharePoint Intake/Request List
2013 SharePoint Fest DC - Build a SharePoint Intake/Request List2013 SharePoint Fest DC - Build a SharePoint Intake/Request List
2013 SharePoint Fest DC - Build a SharePoint Intake/Request ListWes Preston
 

Similar to Session03-Requirement (1).pdf (20)

1) Question Add Targets to Balanced score Card
1) Question  Add Targets to Balanced score Card1) Question  Add Targets to Balanced score Card
1) Question Add Targets to Balanced score Card
 
1) question add targets to balanced score card
1) question  add targets to balanced score card1) question  add targets to balanced score card
1) question add targets to balanced score card
 
Sheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docx
Sheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docxSheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docx
Sheet1RFP RUBRICMaxYour PointsClear Statement of Work including .docx
 
From catalogues to models: transitioning from existing requirements technique...
From catalogues to models: transitioning from existing requirements technique...From catalogues to models: transitioning from existing requirements technique...
From catalogues to models: transitioning from existing requirements technique...
 
Requirements Gathering Best Practice Pack
Requirements Gathering Best Practice PackRequirements Gathering Best Practice Pack
Requirements Gathering Best Practice Pack
 
Business RequirementsReference number Document Control
Business RequirementsReference number Document ControlBusiness RequirementsReference number Document Control
Business RequirementsReference number Document Control
 
Driving Ambiguities Out of Requirements through Stronger Elicitation Techniques
Driving Ambiguities Out of Requirements through Stronger Elicitation TechniquesDriving Ambiguities Out of Requirements through Stronger Elicitation Techniques
Driving Ambiguities Out of Requirements through Stronger Elicitation Techniques
 
The Art and Science of Requirements Gathering
The Art and Science of Requirements GatheringThe Art and Science of Requirements Gathering
The Art and Science of Requirements Gathering
 
Business Requirements development
Business Requirements development Business Requirements development
Business Requirements development
 
Doing It On Your Own: When to Call in the Consultants, When to Leave Them Out
Doing It On Your Own: When to Call in the Consultants, When to Leave Them OutDoing It On Your Own: When to Call in the Consultants, When to Leave Them Out
Doing It On Your Own: When to Call in the Consultants, When to Leave Them Out
 
Website Design RFP Template
Website Design RFP TemplateWebsite Design RFP Template
Website Design RFP Template
 
CARES
CARESCARES
CARES
 
Lecture 04
Lecture 04Lecture 04
Lecture 04
 
Lecture_three_Requirements_analysis.pptx
Lecture_three_Requirements_analysis.pptxLecture_three_Requirements_analysis.pptx
Lecture_three_Requirements_analysis.pptx
 
Requirements Everywhere
Requirements EverywhereRequirements Everywhere
Requirements Everywhere
 
Requirements and Traceability With Pictures
Requirements and Traceability With PicturesRequirements and Traceability With Pictures
Requirements and Traceability With Pictures
 
Free CCBA V3 question bank
Free CCBA V3 question bankFree CCBA V3 question bank
Free CCBA V3 question bank
 
Business Analyst interview Questions
Business Analyst interview QuestionsBusiness Analyst interview Questions
Business Analyst interview Questions
 
2013 SharePoint Fest DC - Build a SharePoint Intake/Request List
2013 SharePoint Fest DC - Build a SharePoint Intake/Request List2013 SharePoint Fest DC - Build a SharePoint Intake/Request List
2013 SharePoint Fest DC - Build a SharePoint Intake/Request List
 
Deep's resume
Deep's resumeDeep's resume
Deep's resume
 

More from PeterTran514407

Session17-Software Testing.pdf
Session17-Software Testing.pdfSession17-Software Testing.pdf
Session17-Software Testing.pdfPeterTran514407
 
Session13-Class Diagram (1).pdf
Session13-Class Diagram (1).pdfSession13-Class Diagram (1).pdf
Session13-Class Diagram (1).pdfPeterTran514407
 
Session15+16-User Story (2).pdf
Session15+16-User Story (2).pdfSession15+16-User Story (2).pdf
Session15+16-User Story (2).pdfPeterTran514407
 
Session01-BA Introduction.pdf
Session01-BA Introduction.pdfSession01-BA Introduction.pdf
Session01-BA Introduction.pdfPeterTran514407
 

More from PeterTran514407 (6)

Session17-Software Testing.pdf
Session17-Software Testing.pdfSession17-Software Testing.pdf
Session17-Software Testing.pdf
 
Session13-Class Diagram (1).pdf
Session13-Class Diagram (1).pdfSession13-Class Diagram (1).pdf
Session13-Class Diagram (1).pdf
 
Session07-Diagram.pdf
Session07-Diagram.pdfSession07-Diagram.pdf
Session07-Diagram.pdf
 
bdd-190104042740.pdf
bdd-190104042740.pdfbdd-190104042740.pdf
bdd-190104042740.pdf
 
Session15+16-User Story (2).pdf
Session15+16-User Story (2).pdfSession15+16-User Story (2).pdf
Session15+16-User Story (2).pdf
 
Session01-BA Introduction.pdf
Session01-BA Introduction.pdfSession01-BA Introduction.pdf
Session01-BA Introduction.pdf
 

Recently uploaded

Osisko Gold Royalties Ltd - Corporate Presentation, April 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 2024Osisko Gold Royalties Ltd - Corporate Presentation, April 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 2024Osisko Gold Royalties Ltd
 
Investing in an initial public offering (IPO)
Investing in an initial public offering (IPO)Investing in an initial public offering (IPO)
Investing in an initial public offering (IPO)Shivam538298
 
Falcon Invoice Discounting unlock your cash flow potential
Falcon Invoice Discounting unlock your cash flow potentialFalcon Invoice Discounting unlock your cash flow potential
Falcon Invoice Discounting unlock your cash flow potentialAravindKumarChillapa
 
Corporate Presentation Probe April 2024.pdf
Corporate Presentation Probe April 2024.pdfCorporate Presentation Probe April 2024.pdf
Corporate Presentation Probe April 2024.pdfProbe Gold
 
Mandalay Resources 2024 April IR Presentation
Mandalay Resources 2024 April IR PresentationMandalay Resources 2024 April IR Presentation
Mandalay Resources 2024 April IR PresentationMandalayResources
 
Collective Mining | Corporate Presentation | April 2024
Collective Mining | Corporate Presentation | April 2024Collective Mining | Corporate Presentation | April 2024
Collective Mining | Corporate Presentation | April 2024CollectiveMining1
 
Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024Osisko Gold Royalties Ltd
 

Recently uploaded (9)

Osisko Gold Royalties Ltd - Corporate Presentation, April 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 2024Osisko Gold Royalties Ltd - Corporate Presentation, April 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 2024
 
Investing in an initial public offering (IPO)
Investing in an initial public offering (IPO)Investing in an initial public offering (IPO)
Investing in an initial public offering (IPO)
 
Falcon Invoice Discounting unlock your cash flow potential
Falcon Invoice Discounting unlock your cash flow potentialFalcon Invoice Discounting unlock your cash flow potential
Falcon Invoice Discounting unlock your cash flow potential
 
Corporate Presentation Probe April 2024.pdf
Corporate Presentation Probe April 2024.pdfCorporate Presentation Probe April 2024.pdf
Corporate Presentation Probe April 2024.pdf
 
michang oil 003650 Algorithm Investment Report
michang oil 003650 Algorithm Investment Reportmichang oil 003650 Algorithm Investment Report
michang oil 003650 Algorithm Investment Report
 
Korea District Heating Corporation 071320 Algorithm Investment Report
Korea District Heating Corporation 071320 Algorithm Investment ReportKorea District Heating Corporation 071320 Algorithm Investment Report
Korea District Heating Corporation 071320 Algorithm Investment Report
 
Mandalay Resources 2024 April IR Presentation
Mandalay Resources 2024 April IR PresentationMandalay Resources 2024 April IR Presentation
Mandalay Resources 2024 April IR Presentation
 
Collective Mining | Corporate Presentation | April 2024
Collective Mining | Corporate Presentation | April 2024Collective Mining | Corporate Presentation | April 2024
Collective Mining | Corporate Presentation | April 2024
 
Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024
Osisko Gold Royalties Ltd - Corporate Presentation, April 10, 2024
 

Session03-Requirement (1).pdf

  • 1. Session 03: Requirement R2S Academy – Internal Use – Author: Tuan Ngo
  • 2. Table of Content Requirement (types / attributes / sources) Good vs bad requirement Requirement examples & Exercises R2S Academy – Internal Use – Author: TUAN NGO 1 2 3 Objectives
  • 3. Business needs vs Requirements 1 Requirement
  • 4. Requirement Business needs vs Requirements Business needs Requirements Are goals and objectives a business must achieve Are things that we need to do in order to achieve a need Can be seperated into lower-level, detailed requirements A need can have one more than requirement Not as specific as requirements More specific and detailed Business Analyst Requirement Engineer
  • 5. Requirement Business needs vs Requirements 28/02/2022 R2S Academy - Internal Use Business needs Requirements Build a big house for my large family - The house shall have 3 rooms + 2 small bedrooms + 1 living room - The house shall have a backyard - The house shall be 3 levels - The floors shall be wood - The wood color shall be dark brown Get a BA job - I should take a BA course - I should create a resume - I should practice mockup interviews Build my portfolio website - The website shall allow clients to contact me - The website shall have a blog - The website shall present my projects
  • 9. Requirement Types 1. Business Requirements • a high level statement describing what is required from the business’s perspective 2. Stakeholder Requirements • The stakeholders are the main source of requirements. They have specific needs that the analyst must identify 3. Technical Requirements • They are the technical constraints and policies that must be adhered to. • These fall under the following four subheadings: Hardware, Software, Interoperability, Internet
  • 10. 4. Functional Requirements • Describes how the solution must behave • What the system does? 5. Non-Functional Requirements • Describes the attributes a system or process must perform • How the system works? • Examples: • A website should be capable enough to handle 20 million users (CCU) • The website should have response time less than 5 seconds 6. Transition Requirements • Describe the capabilities / conditions that the solution must have to transition from the current state to the future state Requirement Types
  • 15. Requirement Attributes 28/02/2022 15 R2S Academy - Internal Use 1. Unique ID Easily find it and link it to its business objectives and test cases. 2. Date Created Allows us to precisely trace when and where it originated; provide valuable information for prioritization and change management. 3. Current Version The requirement version number can be used for flagging different versions of the same requirement to prevent confusion. (e.g. v.0.1, v.1.0) 4. Requirement Author Indicates who proposed a requirement. 5. Assigned To To facilitate improved balancing of overall workload and lead to increased productivity in the entire team. 6. Requirements Status Verbalized, Drafted, Confirmed, Verified, Validated, Prioritize, Approved
  • 16. Requirement Attributes 28/02/2022 16 R2S Academy - Internal Use 7. Priority Not all requirements are made equal. Some have much higher priority than others, and we should be able to see which ones are the most important and which ones can be deferred to a later release. This attribute provides an indication of which requirement should be implemented first. High, Medium, Low 8. Risk To answer: What’s at stake if the requirement isn’t implemented? 9. Stability Before we start working on a requirement, we should confirm that it has reached a certain level of stability. Developing software based on requirements that are subject to constant change is not efficient and is far from productive. 10. Stakeholders This attribute indicates who will be affected should any changes be made to a requirement.
  • 24. Requirement Sources 28/02/2022 24 R2S Academy - Internal Use New project Running project ü By government/ users/ stakeholders (interview, observation) ü Knowledge transfer from colleagues or employees already working on that project ü Talk about project to business analyst, product manager, project lead and developers ü Analyze the existing system in the same domain ü Analyze previous system version that is already implemented into the system ü Analyze the older requirement document of the project ü Look into the past Bug reports, some of the bug reports are turned into enhancement request which may be implemented into current version ü Look into installation guide if it is available to see what are the installation required ü Analyze the domain or industry knowledge
  • 25. Good vs Bad Requirement Requirement
  • 27. Good requirement Example of bad requirement R2S Academy - Internal Use
  • 28. Good requirement 28/02/2022 28 R2S Academy - Internal Use 1. Unambiguous There should be only one way to interpret the requirement. Sometimes ambiguity is introduced by undefined acronyms (e.g. TBD) 2. Testable (verifiable) Testers should be able to verify whether the requirement is implemented correctly. The test should either pass or fail. Avoid these words • Some adjectives: robust, safe, accurate, efficient, expandable, flexible, reliable, user-friendly • Some adverbs and adverbial phrases: quickly, safely, in a timely manner • Indefinite pronouns: few, many, most, much, several, any, anybody, anything, some, etc. Some ambiguous words or phrasing • Modifying phrases: as appropriate, as required, if necessary, shall be considered • Vague words: manage, handle • Passive voice: the subject of the sentence receives the action of the verb rather than performing it
  • 29. Good requirement 28/02/2022 29 R2S Academy - Internal Use 3. Clear (Concise, Terse, Simple, Precise) Requirements should not contain unnecessary verbiage or information. They should be stated clearly and simply 4. Correct If a requirement contains facts, these facts should be true 5. Understandable Requirements should be grammatically correct and written in a consistent style. Standard conventions should be used. The word “shall” should be used instead of “will,” “must,” or “may.” 6. Feasible (Realistic, Possible) The requirement should be doable within existing constraints such as time, money, and available resources 7. Independent To understand the requirement, there should not be a need to know any other requirement 8. Atomic The requirement should contain a single traceable element
  • 30. Good requirement 28/02/2022 30 R2S Academy - Internal Use 9. Necessary A requirement is unnecessary if - None of the stakeholders needs the requirement OR - Removing the requirement will not affect the system 10. Implementation-free (Abstract) Requirements should not contain unnecessary design and implementation information. 11. Consistent There should not be any conflicts between the requirements. Conflicts may be direct or indirect. • Direct conflicts occur when, in the same situation, different behavior is expected. In this case the conflict cannot be resolved by adding conditions, so one of the requirements should be changed or removed • Indirect conflicts occurs when requirements do not describe the same functionality, but it is not possible to fulfill both requirements at the same time. 12. Nonredundant Each requirement should be expressed only once and should not overlap with another requirement 13. Complete A requirement should be specified for all conditions that can occur
  • 31. Good Requirement Team work S03_E03: Find mistake(s) in below requirements
  • 32. Good Requirement Team work S03_E03: Find mistake(s) in below requirements
  • 33. Good Requirement Team work S03_E03: Find mistake(s) in below requirements
  • 34. Good Requirement Team work S03_E03: Find mistake(s) in below requirements