1.3 Design Development Testing Q Flashcards
Activities that take place during development
Software package developed Code is produced/ features of the software package is developed Data structures developed Data checking procedures developed User interface developed
Activities that take place during testing (asked as ‘components of a test plan’) on some ppqs
Parts of the system to be tested Test data Expected results Success/ failure criteria Staff responsibilities
Purpose of design
Produce system specification
Possibility also storyboards, dataflow diagrams, flowcharts for algorithms
Purpose of development
To develop a software package. Possibly broken down into modules with algorithms expressed as code.
Purpose of testing
Ensure the system works as described in the system specification.
Ensure user requirements are met, use valid, invalid/ extreme data.
How would story boarding be used during database development
Shows the planned sequence of screen displays.
May be a branching diagram that shows the different paths available to the user.
All elements of the user interface is specified including inputs, outputs and macro buttons.
Features of a good storyboard
Diagrams of each page/ screen
Elements of user interface specified, inputs, outputs, macro buttons.
Navigation paths, colour scheme, font sizing and positioning of elements.
Evaluate the use of prototyping in the development of a user interface/ data model
Advantages-
Can be used to refine user requirements
Can be used to get feedback from users to inform development of next prototype.
Disadvantages-
Development of many prototypes can lead to code being duplicated
Final product may be unnecessarily large.
Compare and contrast evolutionary and throwaway prototyping.
Evolutionary
Evolutionary-
User will evaluate the prototype and provide feedback to the systems analyst.
Analyst will make changes to the prototype, give it back to the user who will then evaluate the changes.
This process will continue as refinements are made to the prototype.
The result of these refinements May result into a fully working system.
Negative- final iteration may contain unnecessary code that has built up as each prototype leads to the next.
Compare and contrast evolutionary and throwaway prototyping
Throwaway
Throwaway- Aim to produce a set of user requirements not a finished system.
Negative- May waste development time as many prototypes could get discarded just to establish what the user requirements are the final system will have to be developed from scratch.
Whereas evolutionary should result as a fully working system.
Explain how testing can ensure system quality.
“Explain three measures/ indicators of system quality”
Suitability- ensuring that the system is compatible with current technology/ hardware/ software/ data.
Ensuring it meets all the user requirements.
Usability- ensuring the user interface is intuitive.
Ensuring training is provided if required.
Effectiveness- ensuring the system performs its tasks efficiently/ quickly.
Ensuring it has been designed to facilitate maintenance.
Identify/ described the features of system testing
Describe purpose of system testing.
Purpose- ensures that the correct output is produced.
Features- checks that each individual function works with extreme and invalid data.
Also checks whole system together- I. E. That input data produces correct outposts.
Identify/ describe the features of alpha testing
Describe the purpose of alpha testing.
Purpose- to ensure the system works as described in the system specification.
Features- includes module, integration and system testing carried out in house by software developer.
Follows system specification.
Identify/ describes the features of beta testing
Describe the purpose of beta testing.
Purpose- better refine user requirements, get feedback.
Features- working version given to potential users not aware Of system specification.
Realistic rigorous.
Identify/ describe the features of acceptance testing
Describe the purpose of acceptance testing
Purpose- to get an agreement between the end user and the software developer, ensure it meets user requirements.
Features- tested by end user, live environment, real volumes of data, user provides feedback.
Compare and contrast system and acceptance testing
System testing- uses sample data to ensure correct output follows a test plan.
Tested by developer.
Acceptance testing- testing by end user, live environment, real volumes of data.
Ensure meets user requirements.
Provide feedback.
Aim is to get agreement between the user and developer.
Compare and contrast alpha and beta testing
Alpha testing is carried out in house by members of the development team.
Includes module, integration and system testing.
Follow system specification.
Beta testing- working version of the software given to potential users.
Provide feedback
Not aware of systems specification.
More realistic and rigorous.
Explain the purpose of a test plan.
A detailed document for testers to follow to ensure the system works as stated on the system specification.
Explain how a test plan will be developed as part of system design
User requirements will be used to create a table which details how each element of the system should work.
Should contain, the requirement being tested, sample data (valid, invalid, extreme) and expected result.
Describe components of a test plan
Parts of the system to be tested Test data to be entered Expected results Success/ failure criteria Staff responsibilities
Explain how different types of test data can be used in the testing of a system
Normal data- data that the program will accept
Extreme data- this is on the limits of acceptability.
Exceptional data- data entered should be invalid and not accepted.
Testing
Module
Integration
Black box
White box
Module testing
Each different module of the system is tested separately
Integration testing
Checks to see if the Somerset parts work together
Black box testing
Only checks if the outputs that a user needs are produced
Ignored internal processes that produce these outputs
White box testing
Investigated every level of processes to see if each one works
Many of these would be invisible to the end user but they combine to produce expected output.
How prototyping used to design user interface
Initial non functioning model of UI created
This has no database access.
Additional interaction added from feedback from user.
How storyboarding used to design user interface
Diagrams used to show content of screens
Sequence of screens
Different navigational paths xx
