CIS 1250 Lecture Notes - Lecture 4: Pareto Principle, Software Design
Document Summary
Nasa has like everything they want, but turns out they have some hardcore constraints especially on memory. Take the experience and you use it in your design to remove possible errors. Not considered to be lazy, but actually a good practice to see what happened in that expertise and then you took it from other people and you use it in your design. So you understand what worked what didn"t worked and why. It"s a learning process from other people"s experience. Software design is the process through which you plan how to solve a task. What"s happening during this process: learn more about the problem, build a model/plan, use prototypes, evaluate, refine the plan to build the right solution. You use teams to help avoiding mistakes, because you learn from each other. You have your theme and so much ideas, but the point is some of the ideas aren"t gonna work for this problem/design/product.