1. CMPUT 770 - Software Process & QualityCust-Supplier - slide#1  P. Sorenson Customer Supplier Process Category CUS.1 Acquire Process CUS 1.1 Acquisition Preparation Process CUS 1.2 Supplier Selection Process CUS.1.3 Supplier Monitoring Process CUS.1.4 Customer Acceptance Process CUS.2 Supplier Process CUS.3 Requirements Elicitation Process CUS.4 Operations CUS.4.1 Operation Use Process CUS.4.2 Customer Support Process

2. CMPUT 770 - Software Process & QualityCust-Supplier - slide#2  P. Sorenson CUS.1 - Acquire Software ï Purpose: to obtain the product and/or service which will satisfy the need expressed by the customer begins ends  Process begins with the identification of a customer need and ends with the acceptance of the product and/or service by the customer.

3. CMPUT 770 - Software Process & QualityCust-Supplier - slide#3  P. Sorenson CUS.1 - Acquire Software contract product and/or service acquisition ï Expected Outcomes: - a contract will be developed that expresses the expectations, responsibilities, and liabilities of both the supplier and the customer; - a product and/or service is produced which satisfies the customer need; - the acquisition is managed so that specific constraints, such as cost and schedule, are met.

4. CMPUT 770 - Software Process & QualityCust-Supplier - slide#4  P. Sorenson Performance Indicators: Base Practices for Acquire Software + CUS.1.1Identify the need + CUS.1.2Define the requirements + CUS.1.3Prepare acquisition strategy + CUS.1.4Prepare request for proposal + CUS.1.5Select software product supplier + CUS.1.6Determine subcontractor interfaces + CUS.1.7Negotiate contract

5. CMPUT 770 - Software Process & QualityCust-Supplier - slide#5  P. Sorenson Performance Indicators: Work Products for CUS.1 Customer request Internal requirements Supplier proposal response Supplier history record Assessment record Contract Analysis results Acquisition strategy Product needs assessment Product/service requirements Acquisition strategy or plan Request for proposal Analysis results Review records Contract Acceptance test strategy InputsOutputs (see Part 5 - page 66)

6. CMPUT 770 - Software Process & QualityCust-Supplier - slide#6  P. Sorenson CUS.2 Manage Customer Needs gathering, processing and tracking software requirements baseline changesPurpose: - to manage the gathering, processing and tracking of ongoing customer needs and requirements throughout the operational life of the software; - to establish a software requirements baseline that serves as a basis for the project’s software work products; - to manage changes to the baseline

7. CMPUT 770 - Software Process & QualityCust-Supplier - slide#7  P. Sorenson CUS.2 Manage Customer Needs clear and ongoing communication defined baseline monitoring status & dispositionExpected Outcomes: -clear and ongoing communication with the customer is established; - the documented and agreed to customer requirements will be defined, with managed changes; - customer requirements will be established as a baseline for project use; - a mechanism will be established for ongoing monitoring of customer needs - a mechanism will be established for ensuring customers can determine the status & disposition of their requests