Thank you, This one is close. While going through the BABOK V2 "Knowledge ares are not intended to represent phases in a project. It is certainly possible and permissible to proceed from performing enterprise analysis activites, to requirements analysis activities, to solution assessment and validation activities, and treat each as a distinct phase in project."

At one point its listed tha each stage cannot be treated as a project phase.
I am a little confuse. Please help me on this.

[email protected]

Look forward to hear from anybody

The BABOK sometimes uses poor language to describe it's intent. That's going to happen when you write such a large body of reference.

What they are saying is that knowledge areas don't need to be completed in a strict linear fashion like many SDLC methodolodies. The knowledge areas do not represent a waterfall SDLC. You may start apply the skills and complete the tasks of one knowledge area and then start another before the first is completed. Their tasks overlap and intertwine a bit. Also, the tasks of some knowledge areas are intended to be a bit iterative. So you complete them, you do something else, and then you circle back and complete them again until you have arrived at a strong solution.

The purpose of knowledge areas is simply to group and organize tasks in a logical way.