CMPUT 770 - Software Process & QualityCust-Supplier - slide#1  P. Sorenson Customer Supplier Process Category CUS.1 Acquire Process CUS 1.1 Acquisition.

Slides:



Advertisements
Similar presentations
Requirements Specification and Management
Advertisements

Ensure Vendor/Engineer of Choice Product Quality
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
WM Software Process & Quality SPiCE Requirements - slide#1 1  Paul Sorenson REQUIREMENTS FOR A SPiCE ASSESSMENT A set of defined input information.
Quality Management System
Avra Software CMPUT Process Quality and Software Assessment Case Study - slide#1©P. Sorenson and Amr Kamel Assessment Plan for Assessment Plan for.
WM Software Process & Quality Generic Processes - Slide #1  P. Sorenson SPiCE Reference Model - how to read Chapter 5 Capability Levels (process.
CMPUT Software Process & QualityProcess Categories - slide# 1©P. Sorenson Engineering Process Category  Processes that specify, implement, or maintain.
BSBPMG507A Manage Project Communications Manage Project Communications Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit.
BSBPMG408A Apply Contract and Procurement Procedures Apply Contract and Procurement Procedures Unit Guide C ertificate IV in Project Management Qualification.
Systems Engineering Management
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 12 Integration Management Practising a common, coordinated.
ISO 9000 Certification ISO 9001 and ISO
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
Software Configuration Management
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
Project Management Process Overview
S/W Project Management
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
CC20O7N - Software Engineering 1 CC2007N Software Engineering 1 Requirements Engineering Practices with Techniques.
Introduction to Software Quality Assurance (SQA)
Manage Project Procurement Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG509A.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Software Configuration Management
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
Chapter 4 The Project. 2 Learning Objectives Third phase starts after a contract is drawn up and ends when the project objective is accomplished; final.
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
Copyright 2010, The World Bank Group. All Rights Reserved. Planning a Statistical Project Section A 1.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.
Performance Development at The Cathedral of the Incarnation A Supervisor’s Guide.
Project Planning QMS Training.
Chapter 5 Defining and Managing Project and Product Scope Copyright 2012 John Wiley & Sons, Inc. 5-1.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Service Transition & Planning Service Validation & Testing
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Requirements Engineering: What, Why, Who, When, and How
Software Project Management
Systems Analysis & Design Project Management. 2 Question ●When someone says ‘project’ what comes to mind?
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
N O T E “CLICK” TO CONTINUE… If the slide show is not launched, click on View  Slide Show in the menu bar at the top of the Power Point window. When the.
© Mahindra Satyam 2009 Configuration Management QMS Training.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
Copyright © 2007 Pearson Education Canada 1 Chapter 21: Completing the Audit.
Project Management Processes for a Project
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Lesson 1: Examining Professional Project Management Topic 1A: Identify Project Management Processes.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
Project Management Basics
The Second Annual Medical Device Regulatory, Reimbursement and Compliance Congress Presented by J. Glenn George Thursday, March 29, 2007 Day II – Track.
BSBPMG408A Apply Contract and Procurement Procedures Apply Contract and Procurement Procedures Unit Guide C ertificate IV in Project Management Qualification.
Software Requirements Specification Document (SRS)
BSBPMG508A Manage Project Risk Manage Project Risk Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG508A.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
Information Technology Project Management, Seventh Edition.
Agenda  Purpose  Processes  Deliverables  Executing Activities 4.3.
Reporting, Monitoring and Evaluation Giovanni Rum, Chao Xing GEO Secretariat GEO Work Programme Symposium Geneva, 2-4 May 2016.
Acquisition Support New Horizons Consulting Services, LLC’s, premier business unit is an offering of a full range of services and support for acquisition.
Chapter 11: Software Configuration Management
Software Configuration Management
TechStambha PMP Certification Training
The Design Process.
Chapter 11: Software Configuration Management
Presentation transcript:

CMPUT 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

CMPUT 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.

CMPUT 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.

CMPUT 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

CMPUT 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)

CMPUT 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

CMPUT 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