CHAPTER 9

Question 1

SDLC recognising factors

Answer 1

1. Highest risk when furthest away from completion
2. Costs are cheapest at the start, ramp up in the middle and taper off at the end
3. Changes at the start of the project have less impact and cost less

Question 2

Standardized SDLC approaches

Answer 2

Terms of reference - managers decide what capabilities they want system to have
Feasibility Study - Is system actually going to be achievable, can we update old system or have to make new one
Fact finding and Recording - Questionnaires on how current system used and see whats wrong

Question 3

Standardized SDlC approaches part 2

Answer 3

Analysis - free from costs, managers brainstorm using terms of reference stage
Design - produce one or more models to see what the system would look like and create a description document
System Specification - Specific plan and chose suppliers/models etc
Implementation and review - set up and install, train staff
Use
Close

Question 4

Waterfall method

Answer 4

emphasises requirements gathering process
sequence of phases that cant happen until previous is done
output of one is input of next

Question 5

Fountain Model

Answer 5

Possible overlapping, needs effective control procedures
clients may not know what they want upfront, may not actually be feasible

Question 6

Iterative/Incremental

Answer 6

scheduling and staging which parts of a system are developed at different times or rates
then integrated once complete

Question 7

Prototyping

Answer 7

puts together a working model/prototype to test and gain use feedbackA

Question 8

Spiral

Answer 8

combines prototype and waterfall methods
create prototype, risk manage then build another

Question 9

Agile

Answer 9

Face to face communication
lots of small packages and each one counts as an iteration
Lots of iterations made with the aim goal to have a non bugged one published to the market

Question 10

Joint Application Development

Answer 10

Involves the client in development through successful workshops

Question 11

Rapid Application Development

Answer 11

Prototypes can be quickly constructed to replicate the desired product in order to test

Question 12

Build and Fix or Fix and Fail

Answer 12

modifying code until client is happy

Question 13

End USer development

Answer 13

techniques and activities that allows individuals who are not professional developers to create/modify a software object
end users have specialist business knowledge and can implement without explanation

Question 14

Synchronise and Stabalise

Answer 14

teams work parallel on individual applications and then come together
synchronies regularly to debug

Question 15

PRINCE2

Answer 15

Projects are divided into manageabe phases or stages
enables efficient monitoring and control
roles and responsibilities are fully described and adaptable

Question 16

Phases of PRINCE2

Answer 16

Starting up
Planning
initiating
directing
controlling
managing delivery
managing stage boundaries
closing

Question 17

Qualifications needed for PRINCE2

Answer 17

Foundation and practitioner exam

Question 18

PMBOK Guide - project intiation

Answer 18

developing and executing a project plan
principle approach

Question 19

PMBOK Guide - 5 process groups

Answer 19

Initiating
planning
executing
controlling
monitoring
closing

Question 20

ISO9000:2000 ISO 9001 ISO9004

Answer 20

Quality Management Systems

Question 21

Software testing - purpose of testing

Answer 21

gain software that performs to an acceptable defect rate

Question 22

Test Stages

Answer 22

1. Unit testing in isolation
2. Integration testing to show defects
3. Fucntional testing at levels
4. System testing - does it meet requirements
5. load testing - high volume data
6. system integration testing - against 3rd parties
7. user acceptance testing
8. penetration testing security

Question 23

Software Axions

Answer 23

programs cant be fully tested
risk based
if no bugs exist wont be shown
more bugs found, more bugs there are
not all bugs can or need to be fixed
product is never final

Question 24

Regression testing

Answer 24

modfying changes in software functionality

Question 25

Code walkthrough

Answer 25

manual testing where program logic is traced manually using test logic to analyze the programmers logic/assumptions

Question 26

Whitebox testing

Answer 26

tester has access to the source code and writes specifc test to that area

Question 27

Blackbox testing

Answer 27

tester accesses it through client interface to confirm functionality

Question 28

Grey Box testing

Answer 28

combination of white and black
tester know limited number of test cases but applys inputs to observe

Question 29

smoke testing

Answer 29

exmanination of all basic components in system without refernce so determines if they work together

Question 30

Agile testng

Answer 30

unit tests are written first and dail initially until code is written

Question 31

Handshake test

Answer 31

aims to prove its possible to send and receive communications between 2 or more software

Question 32

test cycle - test planing

Answer 32

test strategy - stages and techniques
test bed - hardware used to complete test
test plan - allocates resources

Question 33

test cycle - test development

Answer 33

test case - conditions to see if satisfied
test script 0 details inputs
test scenario - collection of test cases

Question 34

ISO 9126

Answer 34

Standard for software evaulatuon
qulaity model
inernal/external metrics
quality in use metrics

Question 36

Disruptive Innovation

Answer 36

improves a product or service that the market would not expect
creates demand for new services