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


Please Help Members By Posting Answers For Below Questions

Can we have a default method definition in the interface without specifying the keyword "default"?

536


What is the main use of message metaphor in object-oriented programming?

665


Explain the term constructor

628


Explain the implementation phase with respect to oop?

550


What are the rules to define a functional interface?

532






How can we call the base method without creating an instance?

591


What is the difference between class and interface?

584


What do you mean by operator overloading?

614


What are all the languages which support oop?

543


How do I make sure that an object is released in code such as a connection or file object?

615


What is the base type from which all structs inherit directly?

537


What is the function of pure virtual functions?

518


Can we have default method with same name and signature in the derived interface as the static method in base interface and vice versa?

557


How many methods do u implement if implement the serializable interface?

545


How to achieve data abstraction?

526