Professional Documents
Culture Documents
SAD Lect 7 Step5
SAD Lect 7 Step5
SAD Lect 7 Step5
1 3 5
System design is not easy
Nine (09) Broad Skill and experience: Creative
Steps of System elements are there
Cannot be taught….! Learned
Analysis
process
Conscious and Unconscious
Step Five design principals are followed
by the designers to achieve a
Design successful system Design
B.Sc QS/FM Program B.Sc QS/FM Program B.Sc QS/FM Program
1
System Design Principles [13] System Design Principles [13] System Design Principles [13]
7 9 11
4. The Design should be user friendly 5. Each Single element of data 7. Data should be
Man machine interface – easy use
Screen displays –
should be part of the available to everyone
coherent data base :
user vs machine dialog should be Consistent Limits data redundancy and
“with a need to know”
:
eliminates problem of same
same layout
data derived from different
move about without getting lost
Minimize key in sources Freely available to all
use menus: users whose work
No complex code:
provide help information: Online :
Avoid ill- thought-out needs it : “Complete
collection of files or a data
Regular and Non regular user
transaction paths base design unrestricted access”
B.Sc QS/FM Program B.Sc QS/FM Program B.Sc QS/FM Program
2
System Design Principles [13] System Design Principles [13]
13 15
10.Systems performance should 17
8. System should be designed for
maximum flexibility : be satisfactory for the users
Inadequate hardware
It can be changed and it will be Communication links
changed Inefficient software
User Dept Declares “needs never Slow response times
change” : But fails to survive the 3 second / 10 second / 5 minutes
first month of operation: Poor response times
Provide a Most Flexible Design will have a severe negative
Modular design – redeveloped without impact on acceptance of the
complete rework entire system by the user
Keep Data storage and processing community
separate : Enables data changes
System Design Principles [13] System Design Principles [13] System Design Principles [13]
14
9. Systems should be designed 11. The ability to perform each 16 12. Back up Recovery procedures: 18
transaction and access to all data Restore Acceptable time limits
to facilitate maintenance should be controlled by security
measure, and it must be possible Needs to be well
Maintenance is inevitable to trace the execution of each documented and staff
Eg Legislative changes to tax in transactions trained
payroll Manipulate data – Main Issue??
Eliminate bugs in original Access to the system and data accessed
System Crash could be
should be protected due to
system
Internal Controls : Accidental and External factors : Fire, Food,
Minor changes to facilitate deliberate threats : Internal dept. Manager accidents, acts of terrorism,
and staff holds responsibility
changed user needs External risk : Total security is never
other disasters
Good documentation – achievable: Insurance : contingency plans They come at the most
in the event of a security breach important, busiest time of
Requirement for easy Data Access and Security Measures : Physical / Systems the day
maintenance control / Audit and legislative controls :
Security Depends on the systems sensitivity
3
System Design Principles [13]
19
13. System output should be provided
directly to the person requiring it in
a format suited to his / her needs
VDU / Hardcopy
To the direct user – not through
supervisory staff [ Delay]
Should be part of the regular work
schedule
Format should be what the recipient
needs
To meet specific requirements [Avoid
inches thick computer prints. or
hunts within the report to find
required data ]
20
5 – Design
Questions ?