1/11
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Black box testing
Inputting data and testing the outputs without knowing the code. Just testing to see if it meets the specification. Done by testers.
White box testing
Testing every path the code could take. Done by the software developers.
Alpha testing
Carried out by in-house team and user to reveal errors or where it fails to meet the requirements
Beta testing
Carried out by potential users who use the software and then report back any faults
Five methodologies?
Waterfall, spiral, agile (a collection of methodologies), RAD and extreme (type of agile)
Waterfall
Stages completed in order, low user input, clear documentation
Spiral
Prioritises risk assessment (large + high budget projects are risky), iterates the cycle, prototype developed every cycle
Agile
Collection of methodologies, prioritises flexible code that can adapt to changing requirements, poor documentation
Extreme programming (agile)
Paired programming (one writes the code while the other critiques it). This was high quality code can be written in less time. User must constantly be involved.
Rapid Application Development
Prioritises speed, many parts of the project made in parallel each with their own cycle, used for projects with short time-frames.
Methodologies with good documentation?
waterfall, spiral
Methodologies with high user input?
Spiral, extreme programming