|
System Design |
|
The
systems analyst will need to create a detailed
design for the
new system... Design elements that will need to be
considered are...
|
|
|
- Data
- What data needs to be stored?
- How is the data collected?
- Automatic? Eg bar codes;
OMR etc
- Design of new data capture
forms
- Design of the new database
- Input
- How is the data input?
- Keyed in? Automatic methods?
- Design of data validation
methods
- Processing
- What processing needs to
be performed on the data?
- New programs will need
to be designed
- What type of system? -
batch, real-time?
- Output
- Screen designs for
displaying output
- Design of printed reports
- Hardware
- Design of appropriate hardware
- Positioning of hardware
- Network configurations
- Software
- What software will be
installed?
- What HCI (Human Computer
Interface?)
- GUI, Menu, Command Line, Speech?
- Security
- How will the system be kept secure?
|
|
| |
|
Forms used for input should ...
- be clear and uncluttered
- careful use of space needed.
- be easy to understand - no
ambiguous questions
- give clear instructions - Eg the
format of data should be clearly indicated.
- use language appropriate to the user
- Eg Don't use difficult language for school pupils.
- not be too big - or people will not
use them
- have help facilities - either
printed or online.
- look attractive - careful use of
colour and graphics.
|
|
|
Reports for output should ...
- be concise - don't provide
useless information. Relevant information should be easy to find.
- have a title - so that it is easy
to see what information the report is giving.
- have a clear purpose - masses of
data can be meaningless.
- be organised - so it is easy to
understand
|
|
| |
| |
