Software design just like any other engineering design endeavor, requires a fair amount of effort, experience, patience and knowhow in order to be done right.
Based on Akin’s Laws of Spacecraft Design I present our readers with a slightly modified list of what I believe are the basic “Laws of Software design” especially when you are dealing with customer oriented, “tailored” software product solutions.
As this is considered a “basic” list, let me clarify that you are more than welcome to contribute with you own experiences and comments on the matter. So lets start …
- Software design is done with numbers. Analysis without numbers is only an opinion.
- To design software products right takes an infinite amount of effort. This is why it’s a good idea to design them to operate when some things are wrong.
- Design is an iterative process. The necessary number of iterations is one more than the number you have currently done. This is true at any point in time.
- Your best design efforts will inevitably wind up being useless in the final design. Learn to live with the disappointment.
- (Miller’s Law) Three points determine a curve.
- (Mar’s Law) Everything is linear if plotted log-log with a fat magic marker.
- At the start of any design effort, the person who most wants to be team leader is least likely to be capable of it.
- In nature, the optimum is almost always in the middle somewhere. Distrust assertions that the optimum is at an extreme point.
- Not having all the information you need is never a satisfactory excuse for not starting the analysis.
- When in doubt, estimate. In an emergency, guess. But be sure to go back and clean up the mess when the real numbers come along.
- Sometimes, the fastest way to get to the end is to throw everything out and start over.
- There is never a single right solution. There are always multiple wrong ones, though.
- Design is based on requirements. There’s no justification for designing something one bit “better” than the requirements dictate.
- (Edison’s Law) “Better” is the enemy of “good”.
- (Shea’s Law) The ability to improve a design occurs primarily at the interfaces. This is also the prime location for screwing it up.
- The previous people who did a similar analysis did not have a direct pipeline to the wisdom of the ages. There is therefore no reason to believe their analysis over yours. There is especially no reason to present their analysis as yours.
- Past experience is excellent for providing a reality check. Too much reality can doom an otherwise worthwhile design, though.
- The odds are greatly against you being immensely smarter than everyone else in the field. If your analysis says your terminal velocity is twice the speed of light, you may have invented warp drive, but the chances are a lot better that you’ve screwed up.
- A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately.
- (Larrabee’s Law) Half of everything you hear in a classroom is crap. Education is figuring out which half is which.
- When in doubt, document. (Documentation requirements will reach a maximum shortly after the termination of a program.)
- The schedule you develop will seem like a complete work of fiction up until the time your customer fires you for not meeting it.
- It’s called a “Work Breakdown Structure” because the Work remaining will grow until you have a Breakdown, unless you enforce some Structure on it.
- (Bowden’s Law) Following a testing failure, it’s always possible to refine the analysis to show that you really had negative margins all along.
- (Montemerlo’s Law) Don’t do nuthin’ dumb.
- (Varsi’s Law) Schedules only move in one direction.
- (Heinlein’s Law) There ain’t no such thing as a free lunch.
- (von Tiesenhausen’s Law of Program Management) To get an accurate estimate of final program requirements, multiply the initial time estimates by pi, and slide the decimal point on the cost estimates one place to the right.
- (von Tiesenhausen’s Law of Engineering Design) If you want to have a maximum effect on the design of a new software system, learn to draw. Engineers always wind up designing the vehicle to look like the initial artist’s concept.
- (Mo’s Law of Evolutionary Development) You can’t get to the moon by climbing successively taller trees.
- (Atkin’s Law of Demonstrations) When the hardware is working perfectly, the really important visitors don’t show up.
- (Patton’s Law of Program Planning) A good plan violently executed now is better than a perfect plan next week.
- (Roosevelt’s Law of Task Planning) Do what you can, where you are, with what you have.
- (de Saint-Exupery’s Law of Design) A designer knows that he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.
- Any run-of-the-mill engineer can design something which is elegant. A good engineer designs systems to be efficient. A great engineer designs them to be effective.
- (Henshaw’s Law) One key to success in a mission is establishing clear lines of blame.
- Capabilities drive requirements, regardless of what the systems engineering textbooks say.
- Do not reinvent the wheel if you want to keep a new manned program affordable and on schedule.
Hope you liked it
Related Articles :
- Things Every Programmer Should Know
- Top 10 JavaCodeGeeks posts for 2010
- Java Best Practices – Vector vs ArrayList vs HashSet
- Java Best Practices – String performance and Exact String Matching
- Java Best Practices – High performance Serialization
- Java Best Practices – DateFormat in a Multithreading Environment
This guide will introduce you to the world of Software Architecture!
This 162 page guide will cover topics within the field of software architecture including: software architecture as a solution balancing the concerns of different stakeholders, quality assurance, methods to describe and evaluate architectures, the influence of architecture on reuse, and the life cycle of a system and its architecture. This guide concludes with a comparison between the professions of software architect and software engineer.