Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Establish and challenge requirements: A top-down design approach is taken, starting with system goals and distilling those down to functional and engineering requirements. Requirements are constantly challenged to ensure they accurately reflect the goals of the system. Bias is taken towards having the lowest possible number of requirements to ensure a lean system. If a requirement is missed it can be added at a later stage. Conversely, it is very unlikely that an unnecessary requirement will be deemed as such identified at a later stage and removed.

  2. Delete parts: All parts of the system are analyzed and their existence justified. Components not required to fulfill the predetermined requirements should be removed from the system. Before attempting to solve a problem, it should be determined whether the problem needs to be solved in the first place.

  3. Simplify and optimize: The remaining parts are simplified and optimized for the requirement they are intended to fulfill. Simplicity improves efficiency, reduces the chances of failure, and shortens the development cycle which ensures a higher chance of success. However, optimization should not be performed on parts that shouldn't exist, hence it is the last stage in the design process.

...