System Lifecycle

Question 1

Steps of System Life Cycle

Answer 1

Analysis
Design
Development & Testing
Implementation
Documentation
Evaluation

Question 2

Analysis

Answer 2

Investigation of how current system works and what is required for new system.
( what needs to be improved )

Question 3

Methods of Analysis

Answer 3

Observation
Interviews
Questionnaires
Examination of existing documents

Question 4

Observation adv/dis

Answer 4

First hand real life data

people don’t work properly when being watched

Question 5

Interviews adv

Answer 5

In-depth details about system
Follow up questions can be asked

Question 6

Interview dis

Answer 6

Expensive
Time consuming
Not anonymous so might be pressured

Question 7

Observation dis

Answer 7

Can be time-consuming
May not reveal all issues
People will not work properly when know they being watched

Question 8

Questionnaire adv

Answer 8

Quick and simple
Less time consuming
Can be done online and automatically marked

Question 9

Questionnaire dis

Answer 9

People don’t take time to answer a questionnaire well
Information is limited to the questions
May suffer from low response rates

Question 10

Existing Documents adv

Answer 10

Easy way to find comprehensive info about the system
Finds all inputs and outputs
Can reveal unknown issues

Question 11

Existing documents dis

Answer 11

Difficult to understand from someone who is not in organization
Could be outdated
Doesn’t always show all processes and procedures in a system

Question 12

Stuff analysis identifies

Answer 12

inputs and outputs
problems
how data is processed

Question 13

What needs to be specified for the new system?
(analysis)

Answer 13

purpose
data
how data is processed
user requirements
what software/hardware needed ( justified too)

Question 14

What should design show?

Answer 14

file/data structures
input/output formats
validation rules

Question 15

Validation routiunes

Answer 15

Range check ( range eg 0-17)
Character check (certain characters F or M )
Length check
Type check (text or numeric etc)
Format check (must be in a specific pattern eg. __/__/__)
Precense check
Check digit ( extra calculation to make sure it right)

Question 16

Test strategy definition

Answer 16

A set of guidelines on how testing will be carried out.

Test each module: verify each component works
Test each function: ensure everything works
Test the whole system: test performance and intergration

Question 17

Test design

Answer 17

The result of the testing

test data
expected outcomes
actual outcomes
remedial action

Question 18

Test plan

Answer 18

describes all tests to be carried out

Stuff that should be tested:
data file structures
input/output format
validation routines

Question 19

Types of data used for testing

Answer 19

normal - expected
extreme/boundary - upper and lower limits
abnormal - unacceptable

Question 20

Methods of implementation

Answer 20

Direct changeover
Parallel Running (run it until it effective and all people are confident in using)
Pilot Running ( small group to test)
Phased implementation ( slowly change to it)

Question 21

Direct changeover adv/dis

Answer 21

fast implementation
cost effective

high risks of failure
no fallback
users can’t be trained on a new system

Question 22

Phased implementation dis

Answer 22

takes longer
compatibility issues
confusing with old system and new system at same time

Question 23

phased implementation adv

Answer 23

reduced risk
easier to manage
more time to adjust

Question 24

Pilot Running adv

Answer 24

low risk
allows for fine tunning
staff have time to train
few errors

Question 25

Pilot Running dis

Answer 25

slower implementation
expensive to keep 2 up
systems have to be synchronised

Question 26

Parallel running adv

Answer 26

lower risk
easy system comparison
if problems old can be used

Question 27

parallel running dis

Answer 27

expensive 2 systems
have to be synchronised

Question 28

Stuff needed in technical documentation

(what future technician needs to understand how system works

update and fixing problems also needs it)

Answer 28

purpose of system
limitations
programs used
program language
program flowcharts
system flowcharts
hardware and software requirements
file structures
input/output format
test runs
validation routines

Question 29

Stuff needed in user documentation
(features and how to use it)

Answer 29

purpose
limitations
hardware/software req
how to run/install
how to deal w error
trouble shooting guide
FAQ’s
glossary
test runs
input output format

Question 30

Stuff that will be evaluated

Answer 30

If it meets the original requirements
Limitations and issues to improve (user feedback included)
How efficient
Ease of use
suitability ( suitable or too much )