Structured System Design | |||||||||||||||||||||||||||||||||||||||
Structure
This word 'structure' keeps appearing.....what is it and why do we need to keep talking about it? It really means...the way in which different parts are arranged and how they are linked together. When designing a system it is important that the modules are simple enough to be easily understood by all the people who are going to be working on them... ....if they are easy to understand, then it is easy to create the system and to solve problems... ....if it is easy to solve problems, then there will be fewer errors. Lack of structure means a confused, complex and error-riddled system which is difficult to sort out!
|
|||||||||||||||||||||||||||||||||||||||
Modules in Programming
Top-down design is useful for tackling large programs. In a program the modules are called subroutines (procedures and functions in Pascal). Advantages of a modular approach to programming :
Hints for programming
Remember..a well-designed program...
|
|||||||||||||||||||||||||||||||||||||||
Hierarchical representation
of the design of an algorithm.
Hierarchical means something has different 'levels' which are 'related' in some way. (Think of a family tree of all your ancestors) Example : A program is to be written which would create an invoice from a customer order for a clothing catalogue company. The diagram shows how each stage has been broken down into 'smaller' tasks.
...and so on... Another Example : The directories (folders) on a computer are stored in a hierarchy. The root directory is at the 'top', and has sub-directories. Each of these sub-directories may themselves have sub-directories etc...
|
|||||||||||||||||||||||||||||||||||||||