Professional Documents
Culture Documents
1 Introduction
11.1.1 Project Selection
A business organisation may have more than one reason for the introduction of computers. Usually a
particular area of the business is selected for computerisation.
Have a very good understanding of the organisation and how computers can be used.
expansion
technological advances
or other factors
At this point a Systems Analyst is employed.
11.2 Analysis
11.2.1 Problem Definition
Constraints
Maximum cost.
Avaliable equipment.
Technological Feasibility
Social Feasibility
What will be the effect on employees and customers if the new system is implemented?
Economic Feasibility
The procedures
The data
The future
News reports
Problems
The following are ways of investigating existing procedures and the existing problems:
Observation
Questionnaires
Interviews
11.3 Design
In designing a new system all aspects of the design must be documented.
This involves:
11.3.2 Prototyping
In a computing context, prototyping involves building a simple model of software under development.
This could involve using special software to quickly design input screens and validate data input.
This gives the user a chance to experience the look and feel of the input process.
Note that prototyping would also be used during analysis.
These are software tools that insist in the design or development of a system.
Project Management Tools - schedule the steps in analysis, design, coding and testing.
Processing Method
The systems designer will need to choose between Batch Processing and On-Line Processing. This
decision will be dependent on:
Software Solution
Usability
Performance
Suitability
Maintenance
Hardware Solution
The software
Volume of data
Processing method
Security considerations
This type of representation is concerned with how data moves through a system not with such details as
what type of data storage is used.
Conventions
1. Data flows may not go directly to and from data stores and entities.
A systems flow chart shows an overview of the whole system. In particular it represents:
The files.
Input/Output
Keyboard Input
Process
Manual Operation
Sort
Online Storage
Magnetic Tape
Disk Storage
Visual Display
Example
Data validation of mail order forms.
11.5 Development
11.5.1 Program Development
Each program in the system must have a specification written for it which describes what it will do (and
how it will do it).
Psuedocode
Flowcharts
Applications Generator
These are software tools that generate complete systems. The user defines the input, output, data, files
and what the system needs to do. The applications generator then produces the program code.
Report Generator
A report generator will produce reports from information supplied by the user. The way that they work
is that the user supplies the headings, the fields to be printed, what order they are in, the space to allow
for each field and what totals are required.
The CASE software tools that aid the programmer in the development stage are:
Applications Packages
Programs may not need to be written for the new system. If an "off-the-shelf" package may be suitable
then it is the analyst's job to evaluate the package and make sure that it will meet the requirements.
Following the hardware considerations in the design stage of the life cycle, sutiable equipment needs to
be acquired.
11.6 Testing
11.6.1 Acceptance Testing
The tasks the finished system must perform in order to be accepted (by the user) can be used as the
basis for different tests.
Bottom-Up Testing
The individual modules are tested in a stand-alone fashion. The individual modules are combined and
tested. Finally, a system test is performed.
Top-Down Testing
The whole system (or at least a skeleton of it) is tested. Individual modules, yet to be completed, are
replaced by 'stubs'. Stubs often display a message on screen to show that the module has been called.
A test plan should be developed which will go through as many paths as possible in the system.
testing procedure.
It should include:
invalid data
We need to ask:
We test the program by examining the code and trying to test each possible path in the program at least
once.
In Black Box we are not concerned with the program code. The progarm specification is used as the basis
for producing a set of test data that covers all the inputs, outputs and program functions
Performance Testing
The system is tested to see if it can handle the volume of data anticipated in the user environment.
Recovery Testing
Here we need to ensure that the system can recover from various types of failure.
Before the new system can come into operation hardware will probably have to be installed. This may
include:
New computers
New peripherals
Prior to the new system going live, all the staff involved in the system will need hands on training.
All the master files will have to be created before the system can be used.
Phase 1
All the data that will not change can be typed in over a few days or weeks.
Phase 2
Data that is liable to change needs to be keyed in just before the changeover to the new system.
a. Direct Changeover
The organisation stops using the old system one day and starts using the new system the next.
Advantages
o Fast
o Efficient
Disadvantages
The old system is kept running alongside the new system for a few weeks or months.
Advantages
o The old system can be relied upon while any problems with the new system are fixed
o Results from the new system can be checked against the old system
Disadvantages
This is used with larger system that can be broken down into several stages.
d. Pilot Conversion
11.8 Maintenance
11.8.1 Post Implementation Review
This is carried out several weeks or months after the system has been implemented.
For example:
Here we are concerned with taking an acceptable system and making it better.
There may still be problems with our system that need to be corrected.
To ensure everyone understands how their aspect of the system should work
A system specification
Program descriptions
Operating instructions
This details how to enter data what format the data should be in.
A user manual
Tutorials