12 - software development

Question 1

library routines

Answer 1

are pretested functions/procedures ready for use

Question 2

program development lifecycle

Answer 2

the process of developing a program
analysis, design, coding, testing, maintenance

Question 3

analysis

Answer 3

investigation as to whagt is needed to be done and specification of what required

Question 4

design

Answer 4

uses spec to show hwo it shoudl develop

Question 5

waterfall model

Answer 5

each stage is completed and signed off before the next begins

Question 6

iterative model

Answer 6

first develop a subset of the requirements then then the cycle again until the full system is developed - repeats waterfalls

Question 6

waterfall + /-

Answer 6

+ easy to manage/ use
+ stages do not overlap and are completed one at a time
+ each stage has specific deliverables
difficult to change the requirements at a later stage
- not suitable for programs where the requirements could be subject to change
- working program is produced late in the lifecycle
- not suitable for long, complex projects

Question 7

iterative + /-

Answer 7

+ quick to develop early stage
+ easier to debug smaller programs
+ more flexible
+ customers involved in each iteration
- need to define whole system to break it down
- needs to be good planning
- not for short projects

Question 8

RAD - Rapid Application Development

Answer 8

• develops different parts in parallel using prototyping to provide early involvement with the user

Question 9

RAD + /-

Answer 9

+ shorter time
+ frequent feedback
+ flexible
+ modification is easier as parts work separately
- need to be a modular system
- not for short projects

Question 10

structure chart

Answer 10

used to decompose a problem into sub tasks
shows a hierarchy of different modules and how they connect via oupits / input
each module is a box and parameters are arrows

Question 11

finite state machine

Answer 11

can be one of a fixed set of possibile states - states are changes by input

Question 12

state transition diagram

Answer 12

states are circles
transitions are arrows
events are labelled
conditions can be specified in []
initial state is an arrow with a black dot
the final state is a double cirle

Question 13

locating errors

Answer 13

• most IDEs flag syntax errors
• logic errors are found in testing
• can single step to find errors or manual work through a trace table

Question 14

run time errors

Answer 14

happen in the execution of the program
may halt unexpectedly or infinitely loop

Question 15

test plan

Answer 15

shows all stages of testing and how and when it should be tested
once tested add results to the test plan to show progress

Question 16

dry run

Answer 16

developer works through program manually wiht a trace table eg though pseudocode

Question 17

walkthrough

Answer 17

used predefined test cases where another member dry runs the pseudocode to check specific areas eg to test the calc use 20 + 10 = 30

Question 18

types of test data

Answer 18

normal data - acceptable
abnormal data - rejected
extreme data - on the limit
boundary data - within or just outside limits

Question 19

white box testing

Answer 19

involves testing the structure and logic of every path through a program

Question 20

black box testing

Answer 20

test inputs and outputs

Question 21

integrations

Answer 21

tests seperately written modules work together

Question 22

stub testing

Answer 22

used dummy modules to test whole code while certain modules aren’t finished yet
eg run whole code and once the add module is called it will output run add module

Question 23

alpha testing

Answer 23

the completed program is tested in house by the development team

Question 24

beta testing

Answer 24

tested by a small group of users

Question 25

acceptance testing

Answer 25

used for the completed program to prove to the customer it works in the required environment

Question 26

corrective maintenance

Answer 26

correct any errors that appear during use eg run time error missed in testing

Question 27

perfective maintenance

Answer 27

improve the performance of a program in its use eg improving speed

Question 28

adaptive maintenance

Answer 28

alter program so it can perform new tasks required by the user eg adding the ability for voice commands as well as text