1. IEEE Std 1074: Standard for Software Lifecycle

2. IEEE Std 1074: Standard for Software Lifecycle
Process Group
IEEE Std 1074
Project
Management
Pre-
Development
Develop-
ment
Post-
Development
Cross-
Development
(Integral Processes)
> Project Initiation
>Project Monitoring
&Control
> Software Quality
Management
> Requirements
Analysis
> Design
> Implemen-
tation
> Installation
> Operation &
Support
> Maintenance
> Retirement
> V & V
> Configuration
Management
> Documen-
tation
> Training
> Concept
Exploration
> System
Allocation
Project initiation: task plan, schedule, budget, organization and project environment are defined.
Processes

3. Discussing the process groups of the IEEE standard
Project Management
During project management, the project manager initiates, monitors, and controls the project through the software life cycle.
Project management processes

4. Project Management
The Project Initiation Process creates the infrastructure for the project.
During this phase, the task plan, schedule, budget, organization, and project environment are defined.
The project environment includes: project standards, communication infrastructure, meeting and reporting procedure, development methodology, and development tools.
Most of the information generated during this process is documented in the Software Project Management Plan (SPMP).
The Project Initiation Process is complete as soon as a stable environment for the project is established.

5. Project Management
The Project Monitoring and Control Process ensures that the project is executed according to the task plan and budget.
If the project manager observes any deviation from the schedule, he will take corrective action such as reallocating some of the resources, changing procedures, or replanning the schedule. The SPMP is updated to reflect any of these changes.
The Project Monitoring and Control Process is active throughout the lifecycle.

6. Project Management
The Software Quality Management Process ensures that the system under construction meets the required quality standards (which were selected during Project Initiation).
This process is executed by a separate quality management team to avoid conflict in interest (i.e. the goal of the developers is to complete the system on time, and the goal of the quality management team is to ensure that the system is not considered complete until it meets the required quality standard).
The Software Quality Management Process is active throughout most of the lifecycle.

7. Pre-Development
During Pre-Development, management and a client identify an idea or a need.
This can be addressed with a new development effort (greenfileld engineering), or a change to the interface of an existing system (interface engineering), or software replacement of an existing business process (reengineering).
The system Allocation Process establishes the initial system architecture and identifies hardware, software, and operational requirements.
The subsystem decomposition is the foundation of the communication infrastructure among the project members.

8. Pre-Development
The requirements, subsystem decomposition, and communication infrastructure are described in the problem statement, which serves as input for the development process.
The pre-Development processes are depicted in the following table.
Pre-Development Processes

9. Development
Development consists of the processes directed toward the construction of the system.
Development Processes

10. Development
The Requirement Process starts with the informal description of the requirements and defines the system requirements in terms of high-level functional requirements, producing a complete specification of the system and a prioritization of the requirements.
The Design Process takes the architecture produced during the System Allocation Process and the specification from the Requirements and produces a coherent and well-organized representation of the system.
The activities Perform Architectural Design and Design Interfaces refine the subsystem decomposition.

11. Development
The activities Perform Architectural Design and Design Interfaces also includes:
The allocation of requirements to hardware and software systems.
Description of boundary conditions.
The selection of off-the-shelf components.
The definition of design goals.
The detailed design of each subsystem is done during the Perform Detailed Design activity.
The design process results in the definition of the design objects, their attributes and operations, and their organization into packages.
The Implementation Process takes the design model and produces an equivalent executable representation.

12. Post-Development
Post-Development consists of the installation, maintenance, operation and support, and retirement processes.
Post-Development Process

13. Post-Development
During installation, the system software is distributed and installed at the client site.
The installation culminates with the client acceptance test according to the criteria defined in the Project Agreement.
Operation and Support is concerned with the resolution of the software errors, faults, and failures after the delivery of the system.
Maintenance requires ramping of the software life cycle processes and activities into a new project.
Retirement removes an existing system, terminating its operation; this occur when the system is upgraded or replaced by a new system.
To ensure a smooth transition between the two systems, both systems are often run in parallel until the users have gotten used to the new system.

14. Integral Processes
Several processes take place during the complete duration of the project. These are called Integral Processes and include: Validation and Verification, Software Configuration Management, Document Development, and Training.

15. Integral Processes
Verification and Validation includes the V & V tasks.
Verification tasks focus on showing that the system models comply with the specification.
Validation tasks ensure that the system addresses the client’s needs
V & V activities occur through the life cycle with the intent of detecting anomalies as early as possible.
Collect and Analyze Metric Data generates project data that can also serve for future projects and contribute to the knowledge of the organization.
The activities Plan Testing and Develop Test Requirements can be initiated as early as after the completeion of the requirements .

16. Integral Processes
The Configuration Management Process focuses on the tracking and control of changes of work products.
The Documentation Process deals with the work product (excluding code), documenting the results produced by the other processes.

17. Questions