The problems

Previously a project can be planned and their objectives and scope should be established and alternative solutions should be considered, technical and management constraints should be identified. Without this information it  is  not possible to describe  reasonable and  actual estimates of  the  cost  an  effective assessment of risk there is a realistic breakdown of project tasks or a manageable project schedule that give a important indication of process.

The customer and software developer must have meet to describe project goal and scope.  In many cases, this activity starts as a part of the system engineering process and continues as the first step in software need analysis.  Goal identifies the overall targets of the project without considering how these targets will be got.  Scope identifies the primary functions, data, and behaviors that characterize the problem and more important attempts to bind these characteristics in a quantitative manner.

Once the project goal and scope are understood the alternative solutions are considered. Otherwise very little details is discussed the alternatives enable managers and practitioners to select a best approach given the constraints imposed through delivery deadlines and budgetary restrictions personnel availability and technical interfaces and myriad other factors.