1. System Life Cycle Processes
1.1 Agreement Processes
1.1.1 Acquisition
Process
1.1.2 Supply
Process
1.2 Organizational Project-Enabling
Processes
1.2.1 Life Cycle
Model Management Process
1.2.2
Infrastructure Management Process
1.2.3 Project
Portfolio Management Process
1.2.4 Human
Resource Management Process
1.2.5 Quality
Management Process
1.3 Project Processes
1.3.1 Project
Planning Process
1.3.2 Project
Assessment and Control Process
1.3.3 Decision
Management Process
1.3.4 Risk
Management Process
1.3.5
Configuration Management Process
1.3.6 Information
Management Process
1.3.7 Measurement
Process
1.4 Technical Processes
1.4.1 Stakeholder
Requirements Definition Process
1.4.2 System
Requirements Analysis Process
1.4.3 System
Architectural Design Process
1.4.4
Implementation Process
1.4.5 System
Integration Process
1.4.6 System
Qualification Testing Process
1.4.7 Software
Installation Process
1.4.8 Software
Acceptance Support Process
1.4.9 Software
Operation Process
1.4.10 Software
Maintenance Process
1.4.11 Software
Disposal Process
1.1 Agreement
Processes
1.1.1 Acquisition Process [buy something]
Purpose
The purpose of the Acquisition
Process is to obtain the product and/or service that satisfies the need
expressed by the acquirer. The process begins with the identification of
customer needs and ends with the acceptance of the product and/or service
needed by the acquirer.
Activities and tasks
Acquisition preparation
- The
acquirer begins the acquisition process by describing a concept or a need
to acquire,
- develop
or enhance a system, software product or software service. The acquirer
shall define and analyze the system requirements.
- The
acquirer may perform the definition and analysis of software requirements
by itself or may retain a supplier to perform this task.
Acquisition
advertisement
·
The
acquirer shall communicate the request for the supply of a product or service
to identified suppliers.
Supplier
selection
·
The
acquirer should select a supplier based upon the evaluation of the suppliers'
proposals, capabilities, and in accordance with the acquirer's acceptance
strategy and conditions.
Contract
agreement
·
The
acquirer shall then prepare and negotiate a contract with the supplier that
addresses the
acquisition
requirements, including the cost and schedule, of the software product or
service to be delivered.
Agreement monitoring
- ·
The
acquirer shall monitor the supplier's activities in accordance with the
Software Review Process and the Software Audit Process.
- ·
The
acquirer shall cooperate with the supplier to provide all necessary information
in a timely manner and resolve all pending items.
Acquirer
acceptance
- The
acquirer should prepare for acceptance based on the defined acceptance
strategy and criteria. The preparation of test cases, test data, test
procedures, and test environment should be included.
Closure
- The
acquirer shall make payment or provide other agreed consideration to the
supplier for the product or service rendered.
1.1.2 Supply Process
Purpose
The purpose of the Supply Process
is to provide a product or service to the acquirer that meets the agreed requirements.
Activities and tasks
Opportunity
identification
- The
supplier should determine the existence and identity of an acquirer who
has, or who represents an
organization or organizations having, a need for a product or service.
Supplier
tendering
- The
supplier should make a decision to bid or accept the contract.
- The
supplier shall prepare a proposal in response to the request for proposal.
Contract
agreement
·
The
supplier shall negotiate and enter into a contract with the acquirer
·
The
supplier may request for modification to the contract
Contract
execution
- The
supplier shall conduct a review of the acquisition requirements to define
the framework for managing and
assuring the project and for assuring the quality of the deliverable software
product or service.
Product/service
delivery and support
- The
supplier shall deliver the software product or service as specified in the
contract.
- The
supplier shall provide assistance to the acquirer in support of the
delivered software product or service
Closure
- The
supplier shall accept and acknowledge payment or other agreed
consideration.
- The
supplier shall transfer the responsibility for the product or service to
the acquirer,
1.2 Organizational
Project-Enabling Processes
1.2.1 Life Cycle Model Management Process
Purpose
The purpose of the Life Cycle
Model Management Process is to define, maintain, and assure availability of
policies, life cycle processes, life cycle models, and procedures for use by
the organization with respect to the
scope of this
International Standard.
Activities and tasks
Process
establishment
- The organization
shall establish a suite of organizational processes for all software life cycle processes and life cycle
models as they apply to its business activities.
Process
assessment
- The organization
should develop, document and apply a process assessment procedure. Assessment records
should be produced and maintained.
Process
improvement
- The organization
shall effect such improvements to its processes as it determines to be necessary
as a result of process assessment and review. Process documentation should be
updated to reflect improvement in the organizational processes.
1.2.2 Infrastructure Management Process
Purpose
The purpose of the Infrastructure
Management Process is to provide the enabling infrastructure and services to
projects to support organization and project objectives throughout the life
cycle.This process defines, provides and
maintains the facilities, tools, and communications and information technology
assets needed for the organization’s business with respect to the scope of this
International Standard.
Activities and tasks
Process implementation
- The
infrastructure should be defined and documented to meet the requirements
of the process employing
this process, considering the applicable procedures, standards, tools, and
techniques.
Establishment of the infrastructure
- The
configuration of the infrastructure should be planned and documented.
Maintenance of the infrastructure
- The
infrastructure shall be maintained, monitored, and modified as necessary
to ensure that it continues to satisfy the requirements of the process
employing this process.
1.2.3 Project Portfolio Management Process
Purpose
The purpose of the Project
Portfolio Management Process is to initiate and sustain necessary, sufficient
and suitable projects in order to meet the strategic objectives of the
organization.
Activities and tasks
Project
initiation
- The organization shall define accountabilities and
authorities for each project.
- The organization shall identify the expected outcomes of
the projects.
- The organization shall allocate resources for the achievement
of project objectives.
Portfolio
evaluation
- The organization shall evaluate ongoing projects to confirm that Projects are
making progress towards achieving established goals.
Project
closure
- After completion of
the agreement for products and services, the organization shall act to close the project per
organizational policies and procedures and the agreement.
1.2.4 Human Resource Management Process
Purpose
The purpose of the Human Resource
Management Process is to provide the organization with necessary human
resources and to maintain their competencies, consistent with business needs.
Activities and tasks
Skill
identification
Skill
development
Skill
acquisition and provision
Knowledge
management
1.2.5 Quality Management Process
Purpose
The purpose of the Quality
Management Process is to assure that products, services and implementations of
life cycle processes meet organizational quality objectives and achieve
customer satisfaction..
Activities and tasks
Quality
management
- The
organization shall establish quality management policies, standards and
procedures.
- The
organization shall establish organization quality management goals and
objectives based on business strategy for customer satisfaction.
Quality
management corrective action
- The
organization shall take corrective actions when quality management goals
are not achieved.
1.3 Project Processes
1.3.1 Project Planning Process
Purpose
The purpose of the Project
Planning Process is to produce and communicate effective and workable project
plans.
Activities and tasks
Project initiation:
The manager shall
establish the requirements of the project to be undertaken.
Project planning
The manager shall
prepare the plans for execution of the project.
Project activation
- The manager shall obtain authorization for the project.
- The manager shall submit requests for necessary resources
to perform the project.
1.3.2 Project Assessment and Control
Process
Purpose
The purpose of the Project
Assessment and Control Process is to determine the status of the project and
ensure that the project performs according to plans and schedules, and within
projected budgets, and that it satisfies technical objectives.
Activities and tasks
Project
monitoring
Project
control
Project
assessment
Project
closure
1.3.3 Decision Management Process
Purpose
The purpose of the Decision
Management Process is to select the most beneficial course of project action
where alternatives exist.
Activities and tasks
Decision planning:
- The project shall
define a decision-making strategy.
Decision
analysis
Decision
tracking
1.3.4 Risk Management Process
Purpose
The purpose of the Risk Management
Process is to identify, analyze, treat and monitor the risks continuously. The
Risk Management Process is a continuous process for systematically addressing
risk throughout the life
cycle of a system or software
product or service. It can be applied to risks related to the acquisition,
development, maintenance or operation of a system.
Activities and tasks
Risk management planning
Risk profile management
Risk analysis
Risk treatment
Risk monitoring
Risk management
process evaluation
1.3.5 Configuration Management Process
Purpose
The purpose of the Configuration Management Process is to
establish and maintain the integrity of all identified outputs of a project or
process and make them available to concerned parties.
Activities and tasks
Configuration
management planning.
Configuration
management execution.
1.3.6 Information Management Process
Purpose
The purpose of the Information Management Process is to provide
relevant, timely, complete, valid and, if , confidential information to
designated parties during and, as appropriate, after the system life cycle.
Activities and tasks
Information
management planning.
Information
management execution.
1.3.7 Measurement Process
Purpose
The purpose of the Measurement Process is to collect,
analyze, and report data relating to the products developed and processes
implemented within the organizational unit, to support effective management of
the processes, and to objectively demonstrate the quality of the products.
Activities and tasks
Measurement
planning.
Measurement
performance.
Measurement
evaluation.
1.4 Technical Processes
1.4.1 Stakeholder Requirements Definition
Process
Purpose
The purpose of the Stakeholder Requirements Definition
Process is to define the requirements for a system that can provide the
services needed by users and other stakeholders in a defined environment.
It identifies stakeholders, or stakeholder classes,
involved with the system throughout its life cycle, and their needs and
desires. It analyzes and transforms these into a common set of stakeholder
requirements that express the intended interaction the system will have with
its operational environment and that are the reference against which each
resulting operational service is validated in order to confirm that the system
fulfils needs.
Activities and tasks
Stakeholder
identification.
Requirements
identification.
Requirements
evaluation.
Requirements
agreement.
Requirement
recording.
1.4.2 System Requirements Analysis Process
Purpose
The purpose of System Requirements Analysis is to
transform the defined stakeholder requirements into a set of desired system
technical requirements that will guide the design of the system.
Activities and tasks
Requirements
specification.
The system
requirements specification shall describe: functions and capabilities of the
system;
business,
organizational and user requirements; safety, security, human-factors
engineering (ergonomics),interface, operations, and maintenance requirements;
design constraints and qualification requirements. The system requirements
specification shall be documented.
Requirements
evaluation
system requirements
shall be evaluated considering the criteria listed
1.4.3 System Architectural Design Process
Purpose
The purpose of the System Architectural Design Process is
to identify which system requirements should be allocated to which elements of
the system.
Activities and tasks
Establishing
architecture.
Architectural
evaluation.
1.4.4 Implementation Process
Purpose
The purpose of the Implementation Process is to realize a
specified system element.
Activities and tasks
1.4.5 System Integration Process
Purpose
The purpose of the System Integration Process is to
integrate the system elements (including software items, hardware items, manual
operations, and other systems, as necessary) to produce a complete system that
will satisfy the system design and the customers’ expectations expressed in the
system requirements.
Activities and tasks
Integration.
Test readiness.
1.4.6 System Qualification Testing Process
Purpose
The purpose of the Systems Qualification Testing Process
is to ensure that the implementation of each system requirement is tested for
compliance and that the system is ready for delivery.
Activities and tasks
Qualification
testing.
1.4.7 Software Installation Process
Purpose
The purpose of the Software Installation Process is to
install the software product that meets the agreed requirements in the target
environment.
Activities and tasks
Software
installation.
1.4.8 Software Acceptance Support Process
Purpose
The purpose of the Software Acceptance Support Process is
to assist the acquirer to achieve confidence that the product meets
requirements.
Activities and tasks
Software
acceptance support.
1.4.9 Software Operation Process
Purpose
The purpose of the Software Operation Process is to
operate the software product in its intended environment and to provide support
to the customers of the software product.
Activities and tasks
Preparation for
operation.
Operation
activation and check-out.
Operational use.
Customer support.
Operation problem
resolution
1.4.10
Software Maintenance Process
Purpose
The purpose of the Software Maintenance Process is to
provide cost-effective support to a delivered software product.
Activities and tasks
Process
implementation.
Problem and
modification analysis.
Modification
implementation.
Maintenance
review/acceptance.
Migration
1.4.11 Software Disposal Process
Purpose
The purpose of the Software Disposal Process is to end the
existence of a system’s software entity.
Activities and
tasks
Software
disposal planning.
Software
disposal execution.
