Lecture 7 Flashcards
1
Q
What is validating requirements?
A
- Describes how use cases and prototypes have been used together to validate requirements t
- Determines if the correct requirements have been specified
- Specifies if the system-to-be meets the expectations of stakeholders
Common validation techniques
- Reviewing requirements with stakeholders
- Prototyping requirements to demonstrate them
2
Q
What is Verification of requirements?
A
- Investigates the properties of requirements specification
- Quality criteria for requirements: complete, correct, traceable, consistent, up-to-date etc.
Common verification techniques
- VOLERE Quality Gateway to detect the problems
- Model Based Analysis to discover undesirable properties
- Review Satisfaction Arguments whether S > R
3
Q
What is Impact Scenarios?
A
- Explores the incoming events from the environment the future system must handle
- A ‘Precondition’ of complete requirements specification
- Explores the positive & negatives impacts on the environment
- Usually has walk-throughs to be cheaper than implementing a real-life system incase it is likely to have negative feedback
4
Q
What is Prototyping?
A
A partial implemented software where it allows users and customers to evaluate and find the problem
5
Q
Different types of Prototypes
A
- Presentation Prototypes: used for proof of concept, explain design features etc
- Exploratory Prototypes: Determines the problem, compare design options
- Beaboards/Experimental Prototypes: Explores technical feasibility, technology
- Evolutionary Prototype
6
Q
What is Agile Software Development?
A
- Focuses on code than design
- Iterative software development
- Requirments and solutions evolve parallel
7
Q
Agile Software Manifesto values
A
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer Collaboration over contract negotiation
- Responding to change over a plan
8
Q
What Agile Method is used?
A
Scrum, extreme programming
9
Q
What is User Stories?
A
- Requirements in agile method
- Expressed as simple user stories
- Describes a simple requirement, Simple and small
- 1-2 sentences
