The Seven Step Design Process
understand the overall needs that the system must meet before you begin to zero in on the details.
Overall System Design Often referred to as performing a needs analysis.
You may achieve this through interviews and prototypes
the overall design/system objectives guide the report design and selection
Report Design (Output) determine the data items and text that make up the report
design the report layout.
take an inventory of all the information or data fields that you need to create the desired output - reports and forms.
Data Design (Fields) One of the best methods is to list the data items in each report.
Another method is to see whether you can separate the data items into some logical arrangement.
Table Design arguably the most important step in developing a database-oriented application
finally organise the data into tables
(Relationships)
identify relationships betwen tables
establish relationships using fields with common values (matching primary keys and foreign keys)
define your fields and tables in greater detail (field names, types, and sizes)
Field Design (Validation)
determine data-validation rules for each field and to define some new tables to help with data validation
may include designing lookup tables (used for validation)
create test data to test data entry rules (the word populate means filling or entering data)
Form Design (Input)
Forms are made up of the fields that can be entered or viewed in edit mode.
If possible, your screens should look much like the forms that you use in a manual system
Menu Design Tie all your forms and reports together using switchboards and menus
Switchboards are graphical menus, which are usually built with command buttons with text or pictures on them
(Automation)
Menus refer to the lists of commands at the top of a window
Users must be able to follow the system to understand how to move from place to place.