5.4 Problem Solving

5.4.1 Analysis

Research - interview, observation, questionnaire, document search

Record information

Identify problems

Describe user requirements

Establish information, inputs, outputs and processing required

Specify hardware and software

Document system requirements

Analyst's report would include: Identified problems, input required, output required, processing required, suitable hardware, suitable software, recommendations

5.4.2 Design

Documents and files

Inputs

Outputs

Validation

Diagrams

5.4.3 Development, Testing, Implementation

Create required file structures

Create inputs and outputs and validation rules

Design test data

Test the system

Implementation methods: direct, phased, parallel, pilot. Features of each - direct changeover means switch to full system from day 1, this may cause confusion or resentment (Terminal 5!). Need extensive testing to be sure that the new system will work as planned. Phased avoids confusion but means different parts of organisation have different versions of the system. Parallel is secure but involves more resources as both systems are kept going until the new system is passed as fit for purpose.

5.4.4 Documentation

Purpose and limitations of system

Hardware and software requirements

User guide

Input and output formats

Sample runs

Error messages

5.4.5 Evaluation

Compare solution with original design

Conclusions drawn from testing and any modifications and improvements

Back