Why is planning too much up front a mistake in an OOSAD
project?
Answer Posted / subrata
Every project (be it OO or otherwise) has certain unknown factors. It is just impossible to know every constraint in advance. Many things are discovered during detailed design and implementation stage. Hence too much of planning is a wastage of effort when unknown factors are bound to pop up. Hence the focus should be on flexibility rather than rigidness that comes with excess planning.
| Is This Answer Correct ? | 6 Yes | 1 No |
Post New Answer View All Answers
Write basic concepts of oops?
Why do we use oops concepts? What is its advantage?
What are Classes and Objects?
Which OOPS concept exposes only the necessary information to the calling functions?
Write a program to show the inheritance used in a class.
Define exceptions?
Can I implement polymorphism using abstract class?
What's the benefit of using inheritance?
Is @functionalinterface annotation mandatory to define a functional interface? What is the use of @functionalinterface annotation? Why do we need functional interfaces in java?
What are the major differences between late and dynamic binding?
What are the four important foundation concepts of OOP ?
What is the difference between public, private and protected access modifiers?
How can I be thrown polymorphically?
What is the use if instanceof keyword?
Differentiate between a class and a method.