0420 - Computer Studies - 2
0420 - Computer Studies - 2
This covers the following topics found in section 2 of the computer studies
syllabus:
1 Feasibility study 2
2 Analysis 2
3 Design 4
4 Implementation 5
5 System maintenance and evaluation 7
6 Project tools 8
7 Systems flowcharts 9
8 Problems based on section 2 topics 11
1
Systems Analysis
Many of the topics are covered elsewhere (such as how to choose hardware,
validation techniques, testing, etc.).
This involves writing a report to convince management of the merits of adopting the
proposed new system. Some aspects of the study include:
• Description of the existing system (including any problems and the projected
costs)
If the feasibility study is accepted then the systems analyst moves to the next stage
which is a full analysis of the system.
2.2 Analysis
2
Fact finding
This involves watching the personnel using the existing system to find out
exactly how it works. There are a number of advantages and disadvantages
of using this method to gather information about the existing system:
Questionnaires
Interviewing
This involves a one to one question and answer session between the analyst
and employee/customer. A good method if the analyst wants to probe deeply
into one specific aspect of the existing system. As with the previous method,
there are a number of advantages and disadvantages:
3
Disadvantages - can be a very time consuming exercise
- can be expensive to carry out
- unable to remain anonymous
This allows the analyst to see how paper files are kept, look at operating
instructions and training manuals, check accounts, etc. This will give the
analyst some idea of the scale of the problem, memory size requirements,
type of input/output devices needed, and so on. They will often gain
information not obtained by any of the other methods described above.
However, it can be a very time consuming exercise.
2.3 Design
Once the analysis has taken place and the systems analyst has some idea of the
scale of the problem and what needs to be done, the next stage is to design the key
parts of the recommended system. The following is a list of tasks that are usually
done (this is by no means an exhaustive list):
4
2.4 Implementation
Once the “final” system has been designed it is then necessary to put together the
hardware and software and introduce the new system. There are many stages in this
complicated process:
• produce the documentation; there are two basic types here to consider:
User documentation
Technical documentation
- program listing/coding
- programming language(s) used
- flowchart/algorithm
- purpose of the system/program/software
- input formats
- hardware requirements
- software requirements
- minimum memory requirements
- known “bugs” in the system
- list of variables used (and their meaning/description)
- file structures
- sample runs (with results and actual test data used)
- output formats
- validation rules
5
normal data
abnormal/erroneous data
extreme/boundary data
• transfer the paper files across to the new system; this may involve the
following:
change over is usually done in one of four ways; the following notes
summarise these methods and gives advantages and disadvantages of all the
techniques:
direct changeover
with this technique, the old system is stopped and the new system is used
straight away;
- this method can be disastrous if the new system fails at any point
- however, the benefits are immediate and less time is wasted
- costs are reduced (only one system in use so save on staff costs)
- less likelihood of a malfunction since the new system will have been fully
tested
parallel
with this technique, the old and new systems are run together for a time
- if the new system goes down for any reason, you still have the old system
to fall back on so a failure wouldn’t be disastrous
- it is possible to gradually train staff/time to get used to the new system
- more expensive than direct since need extra staff to run both systems
- more time consuming since both systems need to be run and evaluated
6
pilot
with this technique, the new system is introduced into one part of the
company (e.g. into one warehouse of a supermarket) and its performance
assessed
- if the new system fails only one part is affected; the rest is still functional
- it is possible to fully train staff in one area only which is much quicker and
less costly than parallel
- the costs are also less than parallel since only one system is being used in
the pilot warehouse
phased
in this technique only part of the new system is introduced and only when it
proves to work satisfactorily is the next part introduced, and so on, until the
old system is fully replaced
- if the latest part fails, only need to go back in the system to the point of
failure; hence a failure isn’t disastrous
- more expansive than direct since it is necessary to evaluate each phase
before moving to the next stage
- can ensure the system works properly before expanding
The following table summarises the risks involved in all four methods:
7
2.6 Other information
Tools
Systems analyst have a number of tools to help them in carrying out their work.
Since many of their projects are for big companies it is necessary to keep track of
costs, resources and time. The following are only mentioned as a basic
introduction and a guideline for further study:
8
System flowcharts
System flowcharts are used to show how all the components in a system link
together (e.g. input, storage, output, processing, etc.). They are very different to
normal flowcharts since they don’t go into detail of how something is actually done –
they are a general overview. The table below shows the most common system flow
chart symbols:
Terminator
Visual Display Unit Data processing
(Start and end of the flow
(Monitor) operation
diagram)
Merge
Document output Manual input (e.g. join two files
(printed hard copy) (e.g. keyboard) together)
Connector, off-page.
Hard disk (file) (link from this diagram to Input/Output operation
another diagram)
9
START
Write sorted
data to member
Member
file
file
STOP
10
2.7 Problems
(b) What would need to be done before the new computerised system
became “live”?
(c) Why would PILOT and PARALLEL change over methods be suitable
in this application?
(2) A program is written to input daily temperatures. Name three types of test
data that could be used. Give examples of each type of test data which could
be used and discuss the outputs you would expect to get.
(3) Name five tasks that would be carried out at the DESIGN stage in systems
analysis.
(4) Name four methods used to change over from a manual system to a new
computerised system. Discuss the relative advantages and disadvantages of
these four methods.
(5) Describe how the effectiveness of a new computer system can be assessed.
(6) What tools exist to help the analyst draw up an action plan and ensure that
the project is completed on time and to budget?
(7) What information would a systems analyst need to gather to decide on what
hardware is required for a new computerised system?
(8) What five items need to be included in the USER GUIDE and in the
TECHNICAL GUIDE of a newly developed computerised system?
(9) Choose six symbols used in systems flow charts and explain what each
symbol means.
11
(10) A company selling CDs and DVDs presently uses a manual, paper-based
system to keep track of:
- stock levels
- files containing CD and DVD information
- sales information
When a customer comes into the shop s/he goes to the desk and either asks
the assistant to find a particular CD/DVD. The shop assistant locates the files
for the item the customer has requested and,
If the customer has already found the CD/DVD in the shop s/he takes it to the
desk and the shop assistant finds the item file to check for its price. The
customer pays for the CD/DVD and the following then happens:
- shop assistant fills out a sales receipt and puts it into a file
- at the end of the day, all the sales are recorded and the number of
each item in stock is updated
- if the number of items are low a request for new stock is filled out
- the value of the day’s sales are recorded in an accounts book.
A customer goes into the shop and finds a CD/DVD s/he wants to buy. The
shop assistant scans the bar code on the item and the CD/DVD details have
been found including its price. The stock files are updated (i.e. 1 is reduced
from the number in stock) and the takings file updated. The stock levels for
that item are checked and an automatic order is sent out after accessing the
supplier database.
If the customer has requested the assistant to find a particular CD/DVD the
assistant keys in the name/artist and finds out if the item is in stock, where it
can be found and it’s price (the next stage is the same as above). If the item
isn’t in stock, the assistant takes the customer details and updates the
database and adds a request for the item to be ordered and this is added to
the customer’s file.
12
(a) Draw the systems flow charts to show how the above system
will work.
(c) Why would the new system reduce the shop’s costs?
13