Section 20 : validate requirements through product delivery

Question 1

What is testing ?

Answer 1

• Requirements can be validated through testing
• Actual product behavior
• Expected behavior
• Manual testing methods
• Automated testing method

Question 2

What is user acceptance testing ? UAT

Answer 2

• Needs
• Expectations
• The product is tested by stakeholders

Question 3

What is the review and acceptance ?

Answer 3

• Review requirements
• Provide feedback
• Completeness
• Correctness
• Clarity

Question 4

What is the demonstration ?

Answer 4

• Showing the product to stakeholders and receiving feedback
• Expectations
• Requirements
• Needs

Question 5

What is prototyping ?

Answer 5

• Feasibility prototypes
  
  • Just enough code to see if it’s feasible
  • Understand technical risk
• Low-fidelity user prototypes
  
  • An interactive wire frame
  • Test the work flow
  • Simulates process to identify usability
• High-fidelity user prototypes
  
  • Working simulation
  • Communicating proposed solution
• Live-data prototypes
  
  • Limited implementation to prove solution
  • Real data / real traffic

Question 6

What is the acceptance criteria based on the situation ?

Answer 6

• Customers
• End users
• Complete
• Ready for acceptance
• Behaviors
• Features
• Characteristics

Question 7

What are the acceptance criteria ?

Answer 7

• Typically defined during the requirements gathering phase
• Clear, specific, measurable
• Based on the needs and expectations of the end user
• Aligned with the overall goals and objectives of the project

Question 8

Give me some example of acceptance criteria ?

Answer 8

• Specific feature or functionality
• Handle a certain number of users or transactions
• Able to process data within a certain time frame
• Certain level of performance or reliability
• Must meet accessibility or security standards