After the system has been analyzed , now the system analysts must design the new system

needed for the improvements . So he will need the help of the programmer , who is the person who writes the software , if it needed to be written. They have to design

Inputs and outputs of the system

Databases store

Process of the system

Validation checks

Testing data for the system

 Data collection forms are either : hard copy , or screen based. It must be easy to use.

Example for the basic form of data collecting forms

Designing the input screen Several factors must be taken in account 1- the fashion of the screen is easy to use. 2- it need to be attractive 3- limit the possibility of inaccurate data to be entered. 6- must contain guidelines .
7- easy to navigate from one screen to another.

4-users must not be distracted by over elaborate design.

5- avoid the over use of colors as it leads to doing mistakes. This leads to Choosing the input devices

 This level is influenced by the users requirements. It has to contain several factors , or , properties : 1- attractive 2- not being over elaborate. 3- instructions should be included for easier usage.

Two main aspects for designing the output:

1- format of the output. 2- medium it is to be produced

Formats :

Mediums :

Ex 1 : Graphs Ex2 : Lists of records Ex 3 :

Ex 1 :
Paper Ex2 : Screen display Ex 3 : Sound

Reports
Ex 4 : Tables

 Flowcharts must be designed by the systems analyst. The programmer will break them down into algorithms or program flowcharts. Two files must be included in the structure design : 1- master file containing data never changes , like name . Works no.

2- transaction file : data in it , changes each week .

 Both pre explained files , will be processed together , to give the specific type of product. Before combining the two files , the transaction file , must be checked from errors . Magnetic disks are used for backing up the system , instead of the magnetic taps. The transaction file is stored on a disk , even if it is having data in sequential order.

Field names Selection of the key field Master file Field description Validation rules Field lengths Field types

 To ensure that the number of errors which are entered , and retyped , will be small . This can be done by validation . Numbers and types of routines depend on : 1- form of the input . 2- the file structure being used in the system . Validation can not be used in : 1- peoples names 2- calculation fields. Range checks is used for those fields with numeric data. Text fields have length check Format and picture checks will be used to check if the Works number contains 4 number followed by a letter.

This is an example of the validations in each fields , along with their types.

Invalid character check

Checking if the fields requirements match with the input data .

Check digit
When calculation of a long series of digits or string of digits , to produce an extra digit at the end , the computer recalculates the new data m and check whether it matches it or not.

First method Second method

Using the coding method By making the data shortened .

Using direct input data Using barcode reading or optical mark.

Based on cost

Based of reliability Based on after-sale support

supplier

Thus , the hardware and software is being specified .

Off-the-shelf software
Which is already available

Purpose built software

Has to be specially written to solve the problem

Software type Off the shelf software

Pros Cheaper as it is mass produced Testing carried out be the developers. Available straight way. Helpline are provided for tough problems.

Cons Difficult to be adapted . Distracting extra features. May not match up with the system .

Purpose-built software

Specially designed for tasks. no need for adaptations. Any changes can be done.

Costs a lot for writing the code for each task. Limited testing for the programmer only. Limited support to the programmers. Consuming time while development.