SPiCE Processes

PLC Primary Processes

ACQ Acquisition

Processes performed by the customer in order to acquire a product and/or a service.

ACQ.1 Acquisition Preparation

The purpose of the process is to establish the needs and goals of the acquisition and to communicate these with the potential suppliers.

Outcomes

[1]		The concept or the need for the acquisition, development, or enhancement is established.
[2]		The needed acquisition requirements defining the project needs are defined and validated.
[3]		The customer's known requirements are defined and validated.
[4]		An acquisition strategy is developed.
[5]		Supplier selection criteria are defined.

ACQ.2 Supplier Selection

The purpose of the process is to choose the organisation that is to be responsible for the delivery of the requirements of the project.

Outcomes

[1]		The supplier selection criteria are established and used to evaluate potential suppliers.
[2]		The supplier is selected based upon the evaluation of the supplier's proposals, process capabilities and other factors.
[3]		An agreement is established and negotiated between the customer and the supplier.

ACQ.3 Contract Agreement

The purpose of process is to negotiate and approve a contract / agreement that clearly and unambiguously specifies the expectations, responsibilities, work products / deliverables and liabilities of both the supplier(s) and the acquirer.

Outcomes

[1]		A contract or agreement is negotiated, reviewed, approved and awarded to the supplier(s).
[2]		Mechanisms for monitoring the capability and performance of the supplier(s)and for mitigation of identified risks are reviewed and considered for inclusion in the contract conditions.
[3]		Proposers/tenderers are notified of the result of proposal/tender selection.

ACQ.4 Supplier Monitoring

The purpose of the process is to track and assess performance of the supplier against agreed requirements.

Outcomes

[1]		Joint activities between the customer and the supplier are performed as needed.
[2]		Information on technical progress is exchanged regularly with the supplier.
[3]		Performance of the supplier is monitored against the agreed requirements.
[4]		Agreement changes, if needed, are negotiated between the acquirer and the supplier and documented in the agreement.

ACQ.5 Customer Acceptance

The purpose of the process is to approve the supplier's deliverable when all acceptance criteria are satisfied.

Outcomes

[1]		The delivered software product and/or service are evaluated with regard to the agreement.
[2]		The customer's acceptance is based on the agreed acceptance criteria.
[3]		The software product and/or service is accepted by the customer.

SPL Supply

Processes performed by the supplier in order to propose and deliver a product and/or a service.

SPL.1 Supplier Tendering

The purpose of process is to establish an interface to respond to customer inquiries and requests for proposal, prepare and submit proposals, and confirm assignments through the establishing of a relevant agreement / contract.

Outcomes

[1]		A communication interface is established and maintained in order to respond to customer inquiries and requests for proposal.
[2]		requests for proposal are evaluated according to defined criteria to determine whether or not to submit a proposal.
[3]		The need to undertake preliminary surveys or feasibility studies is determined.
[4]		suitable resources are identified to perform the proposed work.
[5]		A supplier proposal is prepared and submitted in response to the customer request.
[6]		Formal confirmation of agreement is obtained.

SPL.2 Product Release

The purpose of process is to control the availability of a product to the intended customer.

Outcomes

[1]		The contents of the product release are determined.
[2]		The release is assembled from configured items.
[3]		The release documentation is defined and produced.
[4]		The release delivery mechanism and media is determined.
[5]		Release approval is effected against defined criteria.
[6]		Release products are made available to the intended customer.
[7]		Confirmation of release is obtained.

SPL.3 Product Acceptance Support

The purpose of process is to assist the customer to achieve confidence in taking ownership of the product.

Outcomes

[1]		The product is completed and delivered to the customer.
[2]		The product is put into operation in the customer's environment.
[3]		Customer acceptance tests and reviews are supported.

ENG Engineering

Processes that directly elicit and manage the customer's requirements, specify, implement, and/or maintain the software product and it’s relation to the system.

ENG.1 Requirements Elicitation

The purpose of the process is to gather, process and track evolving customer needs and requirements throughout the life of the product and/or service so as to establish a requirements baseline that serves as the basis for defining the needed work products.

Outcomes

[1]		Continuing communication with the customer is established.
[2]		Agreed customer requirements are defined and baselined.
[3]		A change mechanism is established to evaluate and incorporate changes to customer requirements into the baselined requirements based on changing customer needs.
[4]		A mechanism is established for continuous monitoring of customer needs.
[5]		A mechanism is established for ensuring that customers can easily determine the status and disposition of their requests.
[6]		Enhancements arising from changing technology and customer needs are identified and their impact is managed.

ENG.2 System Requirements Analysis

The purpose of the process is to transform the defined stakeholder requirements into a set of desired system technical requirements that will guide the design of the system.

Outcomes

[1]		A defined set of system functional and non-functional requirements describing the problem to be solved are established.
[2]		The appropriate techniques are performed to optimise the preferred project solution.
[3]		System requirements are analysed for correctness and testability.
[4]		The impact of the system requirements on the operating environment are understood.
[5]		The requirements are prioritised, approved and updated as needed.
[6]		Consistency and traceability are established between the system requirements and the customer's requirements baseline.
[7]		Changes to the baseline are evaluated for cost, schedule and technical impact.
[8]		The system requirements are communicated to all affected parties and baselined.

ENG.3 System Architectural Design

The purpose of the process is to identify which system requirements should be allocated to which elements of the system.

Outcomes

[1]		A system architecture design is defined that identifies the elements of the system and meets the defined requirements.
[2]		The system's functional and non-functional requirements are addressed.
[3]		The requirements are allocated to the elements of the system.
[4]		internal and external interfaces of each system element are defined.
[5]		Verification between the system requirements and the system architecture is performed.
[6]		The requirements allocated to the system elements and their interfaces are traceable to the customer's requirements baseline.
[7]		Consistency and traceability between the system requirements and system architecture design is maintained.
[8]		The system requirements, the system architecture design and their relationships are baselined and communicated to all affected parties.

ENG.4 Software Requirements Analysis

The purpose of the process is to establish the requirements of the software elements of the system.

Outcomes

[1]		The requirements allocated to the software elements of the system and their interfaces are defined.
[2]		Software requirements are analysed for correctness and testability.
[3]		The impact of software requirements on the operating environment are understood.
[4]		Consistency and traceability are established between the software requirements and system requirements.
[5]		Prioritisation for implementing the software requirements is defined.
[6]		The software requirements are approved and updated as needed.
[7]		Changes to the software requirements are evaluated for cost, schedule and technical impact.
[8]		The software requirements are baselined and communicated to all affected parties.

ENG.5 Software Design

The purpose of the process is to provide a design for the software that implement and can be verified against the requirements.

Outcomes

[1]		A software architectural design is developed and baselined that describes the software elements that will implement the software requirements.
[2]		Internal and external interfaces of each software elements are defined.
[3]		A detailed design is developed that describes software units that can be built and tested.
[4]		Consistency and traceability are established between software requirements and software design.

ENG.6 Software Construction

The purpose of the process is to produce executable software units that properly reflect the software design.

Outcomes

[1]		Verification criteria are defined for all software units against their requirements.
[2]		Software units defined by the design are produced.
[3]		Consistency and traceability are established between software requirements and design and software units.
[4]		Verification of the software units against the requirements and the design is accomplished.

ENG.7 Software Integration

The purpose of the process is to combine the software units, producing integrated software items, consistent with the software design, that demonstrate that the functional and non-functional software requirements are satisfied on an equivalent or complete operational platform.

Outcomes

[1]		An integration strategy is developed for software units consistent with the software design and the prioritised software requirements.
[2]		Verification criteria for software items are developed that ensure compliance with the software requirements allocated to the items.
[3]		Software items are verified using the defined criteria.
[4]		Software items defined by the integration strategy are produced.
[5]		Results of integration testing are recorded.
[6]		Consistency and traceability are established between software design and software items.
[7]		A regression strategy is developed and applied for re-verifying software items when a change in software units (including associated requirements, design and code.

ENG.8 Software Testing

The purpose of the process is to confirm that the integrated software product meets its defined requirements.

Outcomes

[1]		Criteria for the integrated software are developed that demonstrates compliance with the software requirements.
[2]		Integrated software is verified using the defined criteria.
[3]		Test results are recorded.
[4]		A regression strategy is developed and applied for re-testing the integrated software when a change in software items is made.

ENG.9 System Integration

The purpose of the 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.

Outcomes

[1]		A strategy is developed to integrate the system according to the priorities of the system requirements.
[2]		Criteria are developed to verify compliance with the system requirements allocated to the system elements, including the interfaces between system elements.
[3]		The system integration is verified using the defined criteria.
[4]		A regression strategy is developed and applied for re-testing the system [elements] when changes are made.
[5]		Consistency and traceability are established between the system design and the integrated system elements.
[6]		An integrated system, demonstrating compliance with the system design and validation that a complete set of useable deliverable system elements exists, is constructed.

ENG.10 System Testing

The purpose of the process is to ensure that the implementation of each system requirement is tested for compliance and that the system is ready for delivery.

Outcomes

[1]		Criteria for the integrated system are developed that demonstrates compliance with system requirements.
[2]		The integrated system is verified using the defined criteria.
[3]		Test results are recorded.
[4]		A regression strategy is developed and applied for re-testing the integrated system should a change be made to existing system elements.

ENG.11 Software Installation

The purpose of the process is to install the software product that meets the agreed requirements in the target environment.

Outcomes

[1]		A software installation strategy is developed.
[2]		Criteria for software installation are developed that demonstrates compliance with the software installation requirements.
[3]		The software product is installed in the target environment.
[4]		Assure that the software product is ready for use in its intended environment.

ENG.12 Software and System Maintenance

The purpose of the process is to modify a system/software product after delivery to correct faults, improve performance or other attributes, or to adapt to a changed environment.

Outcomes

[1]		A maintenance strategy is developed to manage modification, migration and retirement of products according to the release strategy.
[2]		The impact of changes to the existing system on organisation, operations or interfaces are identified.
[3]		Affected system/software documentation is updated as needed.
[4]		Modified products are developed with associated tests that demonstrate that requirements are not compromised.
[5]		Product upgrades are migrated to the customer's environment.
[6]		On request, products are retired from use in a controlled manner that minimises disturbance to the customers.
[7]		The system/software modification is communicated to all affected parties.

OPE Operation

Processes performed in order to provide for the correct operation and use of the software product and/or service.

OPE.1 Operational Use

The purpose of the process is to ensure the correct and efficient operation of the product for the duration of its intended usage and in its installed environment.

Outcomes

[1]		Operational risks for the product introduction and operation are identified and monitored.
[2]		The product is operated in its intended environment according to requirements.
[3]		Criteria for the operational use are developed that demonstrates compliance with the agreed requirements.

OPE.2 Customer Support

The purpose of the process is to establish and maintain an acceptable level of service through assistance and consultation to the customer to support effective use of the product.

Outcomes

[1]		Service needs for customer support are identified and monitored on an ongoing basis.
[2]		Customer satisfaction with both the support services being provided and the product itself is evaluated on an ongoing basis.
[3]		Operational support is provided by handling customer inquiries and requests and resolving operational problems.
[4]		Customer support needs are met through delivery of appropriate services.

OLC Organisation & Management Processes

MAN Management

Processes that contain practices that may be used by anyone who manages any type of project or process within a software life cycle.

MAN.1 Organisational Alignment

The purpose of the process is to enable the software processes needed by the organisation to provided software products and services, to be consistent with its business goals.

Outcomes

[1]		The organisation's business goals are identified.
[2]		The process framework is identified and defined that include a set of software processes needed to achieve the business goals of the organisation.
[3]		A strategy is defined for process definition, implementation and improvement support is provided to enable this strategy.
[4]		The organisation's mission, core values, vision, goals and objectives is made known to all employees.
[5]		Individuals in the organisation share a common vision, culture and understanding of the business goals to empower them to function effectively.
[6]		Each individual in the organisation understands their role in achieving the goals of the business and is able to perform that role.

MAN.2 Organisation Management

The purpose of the process is to establish and perform software management practices, during the performance of the processes, needed for providing software products and services that are consistent with the business goals of the organisation.

Outcomes

[1]		The organisation will invest in the appropriate management infrastructure.
[2]		The best practices are identified to support the implementation of effective organisation and project management.
[3]		Provide a basis for evaluating the achievement of organisation business goals based on these management practices.

MAN.3 Project Management

The purpose of the process is to identify, establish, coordinate and monitor the activities, tasks and resources necessary for a project to produce a product and/or service, in the context of the project's requirements and constraints.

Outcomes

[1]		The scope of the work for the project is defined.
[2]		The feasibility of achieving the goals of the project with available resources and constraints are evaluated.
[3]		The tasks and resources necessary to complete the work are sized and estimated.
[4]		Interfaces between elements in the project and with other project and organisational units, are identified and monitored.
[5]		Plans for the execution of the project are developed and implemented.
[6]		Progress of the project is monitored and reported.
[7]		Actions to correct deviations from the plan and to prevent recurrence of problems identified in the project are taken when project targets are not achieved.

MAN.4 Quality Management

The purpose of the process is to achieve customer satisfaction by monitoring the quality of the products and services, at the organisational and project level, to ensure they meet customer requirements.

Outcomes

[1]		Quality goals based on the customer's stated and implicit quality requirements are established.
[2]		An overall strategy is developed to achieve the defined goals.
[3]		A quality management system is established to implement the strategy.
[4]		identified quality control and assurance activities are performed and their performance confirmed.
[5]		Actual performance against the quality goals is monitored.
[6]		Appropriate action is taken when quality goals are not achieved.

MAN.5 Risk Management

The purpose of the process is to identify, analyse, treat and monitor the risks continuously.

Outcomes

[1]		The scope of the risk management to be performed is determined.
[2]		Appropriate risk management strategies are defined and implemented.
[3]		Risks are identified as they develop during the conduct of the project.
[4]		The risks are analysed and the priority in which to apply resources to treatment of these risks is determined.
[5]		Risk measures are defined, applied and assessed to determine changes in the status of risk and the progress of the treatment activities.
[6]		Appropriate treatment is taken to correct or avoid the impact of risk based on its priority, probability and consequence or other defined risk threshold.

MAN.6 Measurement

The purpose of the process is to collect and analyse data relating to the products developed and processes implemented within the organisation and its projects, to support effective management of the processes and to objectively demonstrate the quality of the products.

Outcomes

[1]		Organisational commitment is established and sustained to implement the measurement process.
[2]		The measurement information needs of organisational and management processes are identified.
[3]		An appropriate set of measures, driven by the information needs are identified and/or developed.
[4]		Measurement activities are identified and performed.
[5]		The required data is collected, stored, analysed and the results interpreted.
[6]		Information products are used to support decisions and provide an objective basis for communication.
[7]		The measurement process and measures are evaluated and communicated to the process owner.

PIM Process Improvement

Processes performed in order to define, deploy, assess and improve the processes performed in the organizational unit.

PIM.1 Process Establishment

The purpose of the process is to establish a suite of organisational processes for all life cycle processes as they apply to its business activities.

Outcomes

[1]		A defined and maintained standard set of processes are established, along with an indication of each process's applicability.
[2]		The detailed tasks, activities and associated work products of the standard process are identified, together with expected performance characteristics.
[3]		A strategy for tailoring the standard process for the product or service is developed in accordance with the needs of the project.
[4]		Information and data related to the use of the standard process for specific projects exist and are maintained.

PIM.2 Process Assessment

The purpose of the process is to determine the extent to which the organisation's standard processes contribute to the achievement of its business goals and to help the organisation focus on the need for continuous process improvement.

Outcomes

[1]		Information and data related to the use of the standard process for specific projects will exist and be maintained.
[2]		The relative strengths and weaknesses of the organisation's standard processes are understood.
[3]		Accurate and accessible assessment records are kept and maintained.

PIM.3 Process Improvement

The purpose of the process is to continually improve the organisation's effectiveness and efficiency through the processes used and maintained aligned with the business need.

Outcomes

[1]		Commitment is established to provide resources to sustain improvement actions.
[2]		Issues arising from the organisation's internal / external environment are identified as improvement opportunities and justified as reasons for change.
[3]		Analysis of the current status of the existing process is performed, focusing on those processes from which improvement stimuli arise.
[4]		Improvement goals are identified and prioritised and consequent changes to the process are defined and implemented.
[5]		The effects of process implementation are monitored and confirmed against the defined improvement goals.
[6]		Knowledge gained from the improvements is communicated within the organisation.
[7]		The improvements made are evaluated and consideration given for using the solution elsewhere within the organisation.

RIN Resource and Infrastructure

Processes performed in order to provide adequate human resources and necessary infrastructure as required by any other process performed by the organizational unit.

RIN.1 Human Resource Management

The purpose of the process is to provide the organisation and projects with individuals who possess skills and knowledge to perform their roles effectively and to work together as a cohesive group.

Outcomes

[1]		Individuals with the required skills and competencies are identified and recruited.
[2]		Effective interaction between individuals and groups are supported.
[3]		The work force have the skills to share information and co-ordinate their activities efficiently.
[4]		Objective criteria are defined against which group and individual performance is monitored to provide performance feedback and to enhance performance.

RIN.2 Training

The purpose of the process is to provide the organisation and project with individuals who possess the needed skills and knowledge to perform their roles effectively.

Outcomes

[1]		Training is developed or acquired to address the organisation and project training needs.
[2]		Training is conducted to ensure that all individuals have the skills required to perform their assignments, using mechanisms such as training strategies and materials.

RIN.3 Knowledge Management

The purpose of the process is to ensure that individual knowledge, information and skills are collected, shared, reused and improved throughout the organisation.

Outcomes

[1]		Infrastructure is established and maintained for sharing common and domain information across the organisation.
[2]		Knowledge is readily available and shared throughout the organisation.
[3]		The organisation will select an appropriate knowledge management strategy.

RIN.4 Infrastructure

The purpose of the Infrastructure process is to maintain a stable and reliable infrastructure that is needed to support the performance of any other process.

Outcomes

[1]		The requirements for infrastructure to support processes in the organisational unit are defined.
[2]		The infrastructure elements are identified and specified.
[3]		Infrastructure elements are acquired.
[4]		The elements of the infrastructure are implement.
[5]		A stable and reliable infrastructure is maintained.

REU Reuse

Performed in order to systematically exploit reuse opportunities in organization’s reuse programmers.

REU.1 Asset Management

The purpose of the process is to manage the life of reusable assets from conception to retirement.

Outcomes

[1]		An asset management strategy is documented.
[2]		An asset classification scheme is established.
[3]		Criteria for asset acceptance, certification and retirement are defined.
[4]		An asset storage and retrieval mechanism is operated.
[5]		The use of assets are recorded.
[6]		Changes to the assets are controlled and.
[7]		Users of assets are notified of problems detected, modifications made, new versions created and deletion of assets from the storage and retrieval mechanism.

REU.2 Reuse Program Management

The purpose of the process is to plan, establish, manage, control and monitor an organisation's reuse program and to systematically exploit reuse opportunities.

Outcomes

[1]		The organisation's reuse strategy, including its purpose, scope, goals and objectives, is defined.
[2]		The domains for potential reuse opportunities are identified.
[3]		The organisation's systematic reuse capability is assessed.
[4]		The reuse potential of each domain is assessed.
[5]		Reuse proposals are evaluated to ensure the reuse product is suitable for the proposed application.
[6]		The reuse strategy is implemented in the organisation.
[7]		Feedback, communication and notification mechanisms are established, that operate between affected parties.
[8]		The reuse program is monitored and evaluated.

REU.3 Domain Engineering

The purpose of the process is to develop and maintain domain models, domain architectures and assets for the domain.

Outcomes

[1]		The representation forms for the domain models and the domain architectures are selected.
[2]		The boundaries of the domain and its relationships to other domains are established.
[3]		A domain model that captures the essential common and different features, capabilities, concepts and functions in the domain are developed.
[4]		A domain architecture describing the family of systems within the domain is developed.
[5]		Assets belonging to the domain are specified.
[6]		Assets belonging to the domain are acquired or developed and maintained throughout their life cycles.
[7]		The domain models and architectures are maintained throughout their life cycles

SLC Support Processes

SUP Support

Processes which may be employed, by any other processes at various points in the software life cycle. These processes belong to the Support process group (SUP) and are performed: ??to control and maintain the integrity of the product or service developed by the engineering processes; ??to provide assurance that work products and processes comply with predefined provisions and plans.

SUP.1 Quality Assurance

The purpose of the process is to provide assurance that work products and processes comply with predefined provisions and plans.

Outcomes

[1]		A strategy for conducting quality assurance is developed.
[2]		Evidence of quality assurance is produced and maintained.
[3]		Problems and/or non-conformance with agreed requirements are identified and recorded.
[4]		Adherence of products, processes and activities to the applicable standards, procedures and requirements are verified.

SUP.2 Verification

The purpose of the process is to confirm that each software work product and/or service of a process or project properly reflects the specified requirements.

Outcomes

[1]		A verification strategy is developed and implemented.
[2]		Criteria for verification of all required software work products is identified.
[3]		Required verification activities are performed.
[4]		Defects are identified and recorded.
[5]		Results of the verification activities are made available to the customer and other involved parties.

SUP.3 Validation

The purpose of the process is to confirm that the requirements for a specific intended use of the software work product are fulfilled.

Outcomes

[1]		A validation strategy is developed and implemented.
[2]		Criteria for validation of all required work products are identified.
[3]		Required validation activities are performed.
[4]		Problems are identified and recorded.
[5]		Evidence is provided that the software work products as developed are suitable for their intended use.
[6]		Results of the validation activities are made available to the customer and other involved parties.

SUP.4 Joint Review

The purpose of the process is to maintain a common understanding with the stakeholders of the progress against the objectives of the agreement and what should be done to help ensure development of a product that satisfies the stakeholders. Joint reviews are at both project management and technical levels and are held throughout the life of the project.

Outcomes

[1]		Management and technical reviews are held based on the needs of the project.
[2]		The status and products of an activity of a process are evaluated through joint review activities between the stakeholders.
[3]		Review results are made known to all affected parties.
[4]		Action items resulting from reviews are tracked to closure.
[5]		problems are identified and recorded.

SUP.5 Audit

The purpose of the process is to independently determine compliance of selected products and processes with the requirements, plans and agreement, as appropriate.

Outcomes

[1]		An audit strategy is developed and implemented.
[2]		Compliance of selected software work products and/or services or processes with requirements, plans and agreement is determined according to the audit strategy.
[3]		The conduct of audits by an appropriate independent party are performed.
[4]		Problems detected during an audit are identified and communicated to those responsible for corrective action and resolution.

SUP.6 Product Evaluation

The purpose of the process is to ensure through systematic examination and measurement that a product meets the stated and implied needs of the users of that product.

Outcomes

[1]		The requirements for evaluation are established.
[2]		The criteria for product evaluation are identified.
[3]		The methods to be employed for evaluation are defined and the activities needed are identified and performed.
[4]		Measures are collected and the results assessed against defined criteria.
[5]		Results of the product evaluation activities are made available to the interested parties.

SUP.7 Documentation

The purpose of the process is to develop and maintain the recorded information produced by a process.

Outcomes

[1]		A strategy identifying the documentation to be produced during the life cycle of a product or service is developed.
[2]		The standards to be applied for the development of the documentation are identified.
[3]		Documentation to be produced by the process or project is identified.
[4]		The content and purpose of all documentation is specified, reviewed and approved.
[5]		Documentation is developed and made available in accordance with identified standards.
[6]		Documentation is maintained in accordance with defined criteria.

SUP.8 Configuration Management

The purpose of the process is to establish and maintain the integrity of the work products/items of a process or project and make them available to concerned parties.

Outcomes

[1]		A configuration management strategy is developed.
[2]		Work products/items generated by the process or project are identified, defined and baselined.
[3]		Modifications and releases of the work products/items are controlled.
[4]		Modifications and releases are made available to affected parties.
[5]		Thestatus of the work products/items and modifications are recorded and reported.
[6]		The completeness and consistency of the work products/items is ensured.
[7]		Storage, handling and delivery of the work products/items are controlled.

SUP.9 Problem Resolution Management

The purpose of the process is to ensure that all discovered problems are identified, analysed, managed and controlled to resolution.

Outcomes

[1]		A problem management strategy is developed.
[2]		Problems are recorded, identified and classified.
[3]		Problems are analysed and assessed to identify acceptable solution(s).
[4]		Problem resolution is implemented.
[5]		Problems are tracked to closure.
[6]		The status of all problem reports is known.

SUP.10 Change Request Management

The purpose of the process is to ensure that change requests are managed, tracked and controlled.

Outcomes

[1]		A change management strategy is developed.
[2]		Requests for changes are recorded and identified.
[3]		Dependencies and relationships to other change requests are identified.
[4]		Criteria for confirming implementation of change requests are defined.
[5]		Requests for change are prioritised and resource requirements estimated.
[6]		Changes are approved on the basis of priority and availability of resources.
[7]		Approved changes are implemented and tracked to closure.
[8]		The status of all change requests is known.

HS @ 25.03.05