1. Discuss the relationship between project life cycle and product/system life cycle. For this one, you may assume the spiral model for the product life cycle.
The following example explains exceptionally well how the spiral model for the product life cycle relates to the project life cycle:
Example: Phases of the Software project (excerpt)
Software projects (e.g., project life cycle) are divided into individual phases. These phases collectively and there chronological sequences are termed the software product life cycle (e.g., spiral model for the product life cycle, etc.).
Software life cycle: a time span in which a software product is developed and used, extending to its retirement. The cyclical nature of the model expresses that the phases can be carried out repeatedly in the development of a software product. In other words, the spiral model for the product life cycle is one phase in the overall project life cycle.
The spiral model (developed by Boehm 1988) (excerpt)
The spiral model is a software development model that combines many models (e.g., The classical sequential software life-cycle model, The prototyping-oriented life-cycle model, and/or The Waterfall model - see full article uploaded below for more detail of each of these models), or includes them as special cases. The model makes it possible to choose the most suitable approach for a given project. Each cycle encompasses the same sequence of steps for each part of the target product and for each stage of completion.
A spiral cycle begins with the establishment of the following point:
- Goals for and requirements on the (sub)product
- Alternatives to realization of the (sub)product
- Constraints and restrictions
It ties into the project life cycle in the next step: The next step evaluates the proposed solution variant with respect to the project goals and applicable constraints, emphasizing the detection of risks and uncertainties. If such are found, measures and strategies are considered to reduce these risks and their effects.
Important aspects of the spiral model:
- Each cycle has its own validation step that includes all persons participating in the project and the affected future users or organizational unit,
- Validation encompasses all products emanating from the cycle, including the planning for the next cycle and the required resources. (Excerpted from http://www.netnam.vn/unescocourse/se/13.htm).
See full article uploaded below for convenience, which is an excellent resource.
1.3 The phases of a software project
Software projects are divided into individual phases. These phases collectively and their chronological sequence are termed the software product life cycle.
Software life cycle: a time span in which a software product is developed and used, extending to its retirement.
The cyclical nature of the model expressed that the phases can be carried out repeatedly in the development of a software product.
1.3.1 The classical sequential software life-cycle model
Figure 1.2 The classical sequential software life-cycle model
Requirements analysis and planning phase
- Determining and documenting:
- Which steps need to be carried out,
- The nature of their mutual effects,
- Which parts are to be automated, and
- Which recourses are available for the realization of the project?
- Completing the requirements analysis,
- Delimiting the problem domain,
- Roughly sketching the components of the target system,
- Making an initial estimate of the scope and the economic feasibility of the planned project, and
- Creating a rough project schedule.
- User requirements,
- Project contract, and
- Rough project schedule.
System specification phase
- A contract between the client and the software producer (precisely specifies what the target software system ...
Discusses the relationship between project life cycle and product/system life cycle, such as the spiral model for the product life cycle.