A software project is not only concerned with the actual writing of software. Infact, where a software application is bought "off the shelf " , there may be no software writing as such, but this is still fundamentally a software project because so many of the other activities associated with software will still be present.
The feasibility study/plan/execution cycle
The feasibility Study :- assesses whether a project is worth starting-that it has a valid ' business case '. Information is gathered about the requirements of the proposed application. Requirements elicitation can, at least initially, be complex and difficult. The stakeholders may know the aim they wish to pursue, but not be sure about the means of achievement. The developmental and the operational costs, and the value of the benefits of the new system, will also have to be estimated.
Planning :- If the feasibility study indicates that the prospective project appears viable, then project planning can start. We create an outline plan for the whole project and a detailed one for the first stage. Because we will have more detailed and accurate project information after the earlier stages of the project have been completed, planning of the later stages is left to nearer their start.
Project execution :- The project can now be executed. The execution of a project often contains design and implementation sub-phases. Design is making decision about the form of the products to be created. This could relate to the external appearance of the software, that is, the user interface, or the internal architecture. The plan details the activities to be carried out to create these products. Planning and design can be confused because at the most detailed level. planning decisions are influenced by design decisions.