var defaultQueryStr = '?proc=_vCtak0JHEdq4z9xc-r201w&path=_vCtak0JHEdq4z9xc-r201w,_vChNR0JHEdq4z9xc-r201w,_vCtaiEJHEdq4z9xc-r201w,_GfLPAUraEdqNBM3TV2Y0Vw'; var backPath = './../../'; var imgPath = './../../images/'; var nodeInfo=null; contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);
Activity: Define Project Plans
This covers general planning for the release. It does not include detailed planning for product testing (the evaluation mission).This covers general planning for the release. It does not include detailed planning for product testing (the evaluation mission).
This pattern, or set of activities, groups all of the general planning for a release together into one
pattern. Since the individual planning activities are not of particular interest by themselves, including
this high-level pattern in iteration plans emphasizes the goal to be achieved, but leaves the details of the
activities it takes to do accomplish the goal to the next level of detail. This allows an activity diagram,
such as an iteration workflow, to show these activities going on, without excessively cluttering up the diagram.
By using this pattern in the Templates for Delivery Processes (the capability patterns designed to describe the
activities in a particular iteration) the details of these planning activities can be suppressed in an Activity Diagram
(or workflow diagram) for an iteration, since what is of interest is the planning for all aspects of the project, not
the individual plan areas.
In this activity, the project planning tasks appropriate to Inception are performed - planning for integration and test
will occur in Elaboration and Construction.