Initiation and Planning activities occur at the beginning of a project.
A project may be for the creation of a new product, or the enhancement of an existing product. It may even involve the merging of capabilities from multiple products into a new, more capable product. It is always necessary to have an understanding of what the outcome of the project is. This is often called the High Level Requirements. These requirements set direction for the project. Once the direction is set, an early activity is the Make, Buy or Reuse decision.
Panel
borderColor
blue
title
NPR 7150.2B para 3.1.1
Software life cycle planning covers the software aspects of a project from inception through retirement. The software life cycle planning is an organizing process that considers the software as a whole and provides the planning activities required to ensure a coordinated, well-engineered process for defining and implementing project activities. These processes, plans, and activities are coordinated within the project. At project conception, software needs for the project are analyzed, including acquisition, supply, development, operation, maintenance, retirement, decommissioning, and supporting activities and processes. The software effort is scoped, the development processes defined, measurements defined, and activities are documented in software planning documents.
1.1 Inputs
Documents and orders that initiate the Planning Activity
High level requirements that define the scope of the software product
Time and budget constraints that further define the scope of the project
1.2 Predecessor Activities
The predecessor activities include planning, architecture and design activities from other projects and systems where the concept for the software product is defined. Examples include:
New, or changed, hardware system that requires new software to monitor or control it.
1.3 Outputs
Outputs from Planning include a variety of documents, plans, and other work products that are used by downstream activities
