Topic 9 System development life cycle Flashcards
System Development Life Cycle Phases (6)
Feasibility Study Analysis/Investigation Design Implementation Changeover Methods/ installation Maintenance Phase
Feasibilty report
The summary of an initial investigation to look at the likelihood of being able to create a new system
What should a Feasibility report/ investigation include (6)
User requirements (aims and objectives)
Cost benefit anlaysis of the new system
Details of existing hardware and software
Conclusion
Benefits of the new system
Identification of problems with the current system
Reasons why a new system could be required (4)
Failure to supply users with the information they require
The cost of user support is too high
Too much time spent updating the new system
There are security breaches which were not envisioned when the system was first developed
BOT (Feasibility)
Budget
Objectives
Time
TELOS (Feasibility)
Technical Economic Legal Operational Schedule
Methods of investigation (4)
Interview
Observation
Questionnaires
Document Inspection
Features of a process that could be considered when designing a system (4)
Design of input methods
Design of processes
Design of output
Security procedures
4 types of changeover
Direct changeover
Parallel changeover
Phased conversion
Pilot conversion
Direct changeover
Stop using the old system one day and start using the other
Risky
If the system fails it can end badly for the business
Requires fewer resources and is simple, provided nothing goes wrong
Parallel changeover
Old ICT system is being used alongside the new ICT system until the management is happy that the new system is working correctly
Minimises risk
Can compare results to ensure that the new ICT system is working correctly
Lot of unnecessary work and therefre expensive in people time
Adds the amount of planning needed for the implementation
Phased conversion
A module at a time is converted to the new system until the whole system is transffered
Pilot conversion
One branch at a time
3 methods of maintainance
Perfective
Adaptive
Corrective
Perfective
Improving the performance of the software
e.g. modification of user interface upon feedback from users who are finding it difficult to use