Topic 9 System development life cycle Flashcards

1
Q

System Development Life Cycle Phases (6)

A
Feasibility Study
Analysis/Investigation
Design
Implementation
Changeover Methods/ installation
Maintenance Phase
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Feasibilty report

A

The summary of an initial investigation to look at the likelihood of being able to create a new system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What should a Feasibility report/ investigation include (6)

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Reasons why a new system could be required (4)

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

BOT (Feasibility)

A

Budget
Objectives
Time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

TELOS (Feasibility)

A
Technical
Economic
Legal
Operational
Schedule
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Methods of investigation (4)

A

Interview
Observation
Questionnaires
Document Inspection

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Features of a process that could be considered when designing a system (4)

A

Design of input methods
Design of processes
Design of output
Security procedures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

4 types of changeover

A

Direct changeover
Parallel changeover
Phased conversion
Pilot conversion

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Direct changeover

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Parallel changeover

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Phased conversion

A

A module at a time is converted to the new system until the whole system is transffered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Pilot conversion

A

One branch at a time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

3 methods of maintainance

A

Perfective
Adaptive
Corrective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Perfective

A

Improving the performance of the software

e.g. modification of user interface upon feedback from users who are finding it difficult to use

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Adaptive

A

Software may need to be changed owning to the changing needs of the business

e.g. A new virus threat/hacker threat means that the software will need to be adapted to protect against this

17
Q

Corrective

A

Bugs in the software which were not discovered during testing may need correcting

e.g. A piece of software may crash when being used with another piece of software