CHAPTER 9 Flashcards
SDLC recognising factors
- Highest risk when furthest away from completion
- Costs are cheapest at the start, ramp up in the middle and taper off at the end
- Changes at the start of the project have less impact and cost less
Standardized SDLC approaches
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
Standardized SDlC approaches part 2
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
Waterfall method
emphasises requirements gathering process
sequence of phases that cant happen until previous is done
output of one is input of next
Fountain Model
Possible overlapping, needs effective control procedures
clients may not know what they want upfront, may not actually be feasible
Iterative/Incremental
scheduling and staging which parts of a system are developed at different times or rates
then integrated once complete
Prototyping
puts together a working model/prototype to test and gain use feedbackA
Spiral
combines prototype and waterfall methods
create prototype, risk manage then build another
Agile
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
Joint Application Development
Involves the client in development through successful workshops
Rapid Application Development
Prototypes can be quickly constructed to replicate the desired product in order to test
Build and Fix or Fix and Fail
modifying code until client is happy
End USer development
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
Synchronise and Stabalise
teams work parallel on individual applications and then come together
synchronies regularly to debug
PRINCE2
Projects are divided into manageabe phases or stages
enables efficient monitoring and control
roles and responsibilities are fully described and adaptable
Phases of PRINCE2
Starting up
Planning
initiating
directing
controlling
managing delivery
managing stage boundaries
closing
Qualifications needed for PRINCE2
Foundation and practitioner exam
PMBOK Guide - project intiation
developing and executing a project plan
principle approach
PMBOK Guide - 5 process groups
Initiating
planning
executing
controlling
monitoring
closing
ISO9000:2000 ISO 9001 ISO9004
Quality Management Systems
Software testing - purpose of testing
gain software that performs to an acceptable defect rate
Test Stages
- Unit testing in isolation
- Integration testing to show defects
- Fucntional testing at levels
- System testing - does it meet requirements
- load testing - high volume data
- system integration testing - against 3rd parties
- user acceptance testing
- penetration testing security
Software Axions
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
Regression testing
modfying changes in software functionality
