ict Flashcards
Consistency check
Checks if fields correspond (tie up) with each other
Data type check
Data being entered needs should be of the same type as the data type specified
Format check
Performed on codes to make sure that they are the correct combinations of characters
Length check
Checks if the input data contains the required number of characters
Presence check
Checks if data is actually present and hasn’t been missed out
Range check
Checks whether numerical data is within given / acceptable values
Direct Changeover
The old system is stopped overnight and the new system is introduced immediately.
Parallel Running
The old and the new systems are run side by side for a time before the new system takes over altogether.
Pilot Implementation
The new system is introduced into one part of the company (eg into a warehouse of a supermarket) and its performance assessed.
Phased Implementation
Initially, only part of the new system is introduced. Only when it proves to work satisfactorily is the next part introduced, and so on, until the old system is fully replaced.
This is when to use Direct Changeover
A small organisation which can afford to lose data/where system needs to be up and running very quickly/where the new system has been thoroughly tested
This is when to use Parallel Running
An organisation with large amounts of data which would take too long to re-enter / cannot afford to lose data/where time taken/cost to implement is not an issue/where the new system needs to be thoroughly tested
This is when to use Pilot Implementation
An organisation where there are clearly defined separate processes/where the new system needs to be thoroughly tested
This is when to use Phased Implementation
An organisation where there are several branches all doing the same work)/where the new system needs to be thoroughly tested
Examples of User Documentation
Error handling / meaning of errors, How to add, delete or amend records, How to do a search, Troubleshooting Guide/FAQs
Examples of Technical Documentation
File structures, Known bugs in the system, Programming language used
Analysis
First stage of the system life cycle
Design
Second stage of the system life cycle
Development & Testing
Third stage of the system life cycle
Implementation
Fourth stage of the system life cycle
Documentation
Fifth stage of the system life cycle
Evaluation
Final stage of the system life cycle
Evaluation methods
looking at the efficiency, ease of use and appropriateness of the solution.
Evaluation strategies
Comparing the solution with the original requirements, Identifying any limitations and necessary improvements
Post evaluation actions
Update of hardware and software due to feedback from users, new hardware available, changes in legislation
Testing Designs
describe how data/file structures, validation, input and output methods are created and tested
Visual Verification
Human carefully compares what has been entered with data source (application form / order etc)
Double Data Entry
Data source entered into the computer twice, and only if the two sets are identical will they be accepted for processing (Computer checks)
Validation
Routines try to ensure data going into the system is reasonable
Verification
Methods to ensure that the data entered into the systems is copied accurately from the source
Observation
Watching personnel using the existing system to find out exactly how it works
Questionnaires
Distributing {these things} to the workforce, clients or users to find out their views
Interviews
A one-to-one question and answer session between the analyst and employee
Examining existing paperwork
Allows analysis to see how paper files are kept to
Data flow diagram
shows the flows of data, input and output requirements with processing and types of data storage neede
