The key work here seems to be Apply although I have not found any question from pre assessment exam that would emphasis the "apply" aspect. Do you think that it is safe to assume that only think you need to know to satisfy this objective is what iterative and incremental process is? I suspect that this objective covers also Refactoring techniques. What do you think?
This isn't a direct answer to your question... here's a question from IBM's sample test: Q: An iterative development process: a) is a technique for managing complexity and plans for change during software development b) represents a structured methodology, which includes functional decomposition c) is a top-down approach without the dataflow diagrams d) is equivalent to an incremental development process
Joined: Jul 06, 2000
Yes, I remember this question. I'm under the impression that I saw one more on iterative/incremental process and one more on Refactoring, but those are rather basic question. Do you think that on the reall exam I might see something more in-depth? ... by the way only answer that seem rite is a, isn't it? [This message has been edited by Michal Harezlak (edited September 12, 2000).]
"Iterative development has been around for a while under many names: incremental, evolutionary, staged, spiral... lots of names."
So answer D would be correct also. Does anyone use incremental development with a different meaning?
Joined: Jul 06, 2000
This is one of thise questions. I would like to see what is IBMs answer. My understanding was that the Unified Process is incremental and iterative. Iterative as in repetitive and incremental as you add new functionality in defined increments?
Q: An iterative development process: a) is a technique for managing complexity and plans for change during software development b) represents a structured methodology, which includes functional decomposition c) is a top-down approach without the dataflow diagrams d) is equivalent to an incremental development process [/B]
I am not sure about the answer of the question, this is supposed to be a single select question. I'd select a, but b sounds right to me too. Anyone who has the answer to the question? Thanks!
Hi, I would lean towards A. A is correct, since, you can divide complexity and plan for change in business needs using Iterative Development Process. B is incorrect - Iterative Development Process is not a methodology - It doesnot define how to conduct the analysis (problem solving efforts).You can follow any methodology you desire. C is incorrect - A top-down approach is typical example of Waterfall cycle.You do one-time analysis, design, implementation and testing- unlike the iterative devlopment process.You may not/shouldn't use dataflow diagrams (DFD's);they are not a part of UML artifact. D is incorrect -Iterative Development Process is not equivalent to an Incremental Development Process.In the former, you take care of changing business needs attached to the same business functionality.In the latter, you add a new functionality to the system. Essentially, the end product of an Iterative Development cycle would be a production release of the application.On the other hand, an Incremental Development Process (which involves many such Iterative Development Cycles) will yield a new Production Release. Please read Development Process Issues, Chapter 37,Section 37.4.2, Applying UML and Patterns, Craig Larman for the difference between the two development processes. Hope this helps, -- Sandeep [This message has been edited by Desai Sandeep (edited May 16, 2001).]