Section 20 : validate requirements through product delivery Flashcards
1
Q
What is testing ?
A
- Requirements can be validated through testing
- Actual product behavior
- Expected behavior
- Manual testing methods
- Automated testing method
2
Q
What is user acceptance testing ? UAT
A
- Needs
- Expectations
- The product is tested by stakeholders
3
Q
What is the review and acceptance ?
A
- Review requirements
- Provide feedback
- Completeness
- Correctness
- Clarity
4
Q
What is the demonstration ?
A
- Showing the product to stakeholders and receiving feedback
- Expectations
- Requirements
- Needs
5
Q
What is prototyping ?
A
- 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
6
Q
What is the acceptance criteria based on the situation ?
A
- Customers
- End users
- Complete
- Ready for acceptance
- Behaviors
- Features
- Characteristics
7
Q
What are the acceptance criteria ?
A
- 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
8
Q
Give me some example of acceptance criteria ?
A
- 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