1.3 Design Development Testing Q

Question 1

Activities that take place during development

Answer 1

Software package developed 
Code is produced/ features of the software package is developed 
Data structures developed 
Data checking procedures developed 
User interface developed

Question 2

Activities that take place during testing (asked as ‘components of a test plan’) on some ppqs

Answer 2

Parts of the system to be tested 
Test data 
Expected results 
Success/ failure criteria 
Staff responsibilities

Question 3

Purpose of design

Answer 3

Produce system specification

Possibility also storyboards, dataflow diagrams, flowcharts for algorithms

Question 4

Purpose of development

Answer 4

To develop a software package. Possibly broken down into modules with algorithms expressed as code.

Question 5

Purpose of testing

Answer 5

Ensure the system works as described in the system specification.
Ensure user requirements are met, use valid, invalid/ extreme data.

Question 6

How would story boarding be used during database development

Answer 6

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.

Question 7

Features of a good storyboard

Answer 7

Diagrams of each page/ screen
Elements of user interface specified, inputs, outputs, macro buttons.
Navigation paths, colour scheme, font sizing and positioning of elements.

Question 8

Evaluate the use of prototyping in the development of a user interface/ data model

Answer 8

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.

Question 9

Compare and contrast evolutionary and throwaway prototyping.

Evolutionary

Answer 9

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.

Question 10

Compare and contrast evolutionary and throwaway prototyping

Throwaway

Answer 10

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.

Question 11

Explain how testing can ensure system quality.

“Explain three measures/ indicators of system quality”

Answer 11

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.

Question 12

Identify/ described the features of system testing

Describe purpose of system testing.

Answer 12

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.

Question 13

Identify/ describe the features of alpha testing

Describe the purpose of alpha testing.

Answer 13

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.

Question 14

Identify/ describes the features of beta testing

Describe the purpose of beta testing.

Answer 14

Purpose- better refine user requirements, get feedback.

Features- working version given to potential users not aware Of system specification.

Realistic rigorous.

Question 15

Identify/ describe the features of acceptance testing

Describe the purpose of acceptance testing

Answer 15

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.

Question 16

Compare and contrast system and acceptance testing

Answer 16

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.

Question 17

Compare and contrast alpha and beta testing

Answer 17

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.

Question 18

Explain the purpose of a test plan.

Answer 18

A detailed document for testers to follow to ensure the system works as stated on the system specification.

Question 19

Explain how a test plan will be developed as part of system design

Answer 19

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.

Question 20

Describe components of a test plan

Answer 20

Parts of the system to be tested 
Test data to be entered 
Expected results 
Success/ failure criteria 
Staff responsibilities

Question 21

Explain how different types of test data can be used in the testing of a system

Answer 21

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.

Question 22

Testing

Answer 22

Module
Integration
Black box
White box

Question 23

Module testing

Answer 23

Each different module of the system is tested separately

Question 24

Integration testing

Answer 24

Checks to see if the Somerset parts work together

Question 25

Black box testing

Answer 25

Only checks if the outputs that a user needs are produced

Ignored internal processes that produce these outputs

Question 26

White box testing

Answer 26

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.

Question 27

How prototyping used to design user interface

Answer 27

Initial non functioning model of UI created

This has no database access.

Additional interaction added from feedback from user.

Question 28

How storyboarding used to design user interface

Answer 28

Diagrams used to show content of screens

Sequence of screens

Different navigational paths xx