System Analysis Design Guidelines
System should be asynchronous which is well guarded using state-machine(s).
Different parts of the system should be independently update-able.
Different features of the system should be well documented and searchable.
Design of the system should make access to different features be very intuitive.
System should have no more than what is necessary for it to work. Rest all could be optional bundles.
System should have statistics about different parts of the system that it deals with.
Tracing, logging, monitoring, and debugging should be painless in the system.
Basics of Unix Philosophy 18 Rules of Success:
Rule of Modularity: Write simple parts connected by clean interfaces.
Rule of Clarity: Clarity is better than cleverness.
Rule of Composition: Design programs to be connected to other programs.
Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
Rule of Simplicity: Design for simplicity; add complexity only where you must.
Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.
Rule of Transparency: Design for visibility to make inspection and debugging easier.
Rule of Robustness: Robustness is the child of transparency and simplicity.
Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.
Rule of Least Surprise: In interface design, always do the least surprising thing.
Rule of Silence: When a program has nothing surprising to say, it should say nothing.
Rule of Repair: When you must fail, fail noisily and as soon as possible.
Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
Rule of Optimization: Prototype before polishing. Get it working before you optimize it.
Rule of Diversity: Distrust all claims for “one true way”.
Rule of Extensibility: Design for the future, because it will be here sooner than you think.
Rule of Open Systems: Use open standards and specifications wherever possible.
<note important>PS: Write programs that do one thing and do it well. Write programs to work together.</note>