Presentation 5 Contract review Contract review process and stages

Slides:



Advertisements
Similar presentations
1.07 Employ sales-promotion activities to inform or remind customers of business/product.
Advertisements

By: MSMZ. Objective After completing this chapter, you will be able to: Explain 2 contract review stage List the objective of each stage of the contract.
Develop an Information Strategy Plan
Session 8 Implementing PPPs
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
Monitoring and Control
SOFTWARE QUALITY ASSURANCE Maltepe University Faculty of Engineering SE 410.
MethodAssess System Assessment. Methoda Computers Ltd 2 List of Subjects 1. Introduction 2. Actions and deliverables 3. Lessons and decisions.
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
Software Development Contracts and Legal Issues Cost plus Fixed price Combined.
Software Development Problems Range of Intervention Theory Prevention, Treatment and Maintenance Planning, Development and Use Cost of Intervention.
OHT 22.1 Galin, SQA from theory to implementation © Pearson Education Limited Objectives of cost of software quality metrics 2.The classic model.
Components of software quality assurance system overview
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
Chapter 8 Assuring the quality of external participants’ contributions
Pertemuan 15 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
SQA Architecture Software Quality.
Development and Quality Plans
Development plan and quality plan for your Project
Prof. Mohamed Batouche Costs of software quality Introduction  More and more, commercial companies or public organizations are requiring.
SE513 Software Quality Assurance Lecture04: Contract Review Galin, SQA from Theory to Education Limited 2004.
SQA Architecture Software Quality By: MSMZ.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Chapter 8 - The Planning and Writing of Persuasive Proposals 1 Proposals Proposals are marketing tools that sell your ideas to others A persuasive document.
Chapter 4 Components of the Software Quality Assurance System
Software Project Management Introduction to Project Management.
Software Quality Assurance Activities
OHT 25.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The quality assurance organizational framework Top management’s quality.
Assuring the quality of external participants' contributions Michael Rooney mpr07u.
Chapter 5 Contract review Contract review process and stages
Overview of SQA Components
CHAPTER 3 Pre-Project Components. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser Learning Objectives: To discuss: Contract Review Development and Quality.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.
OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction The foundations of high quality Foundation 1: software.
Pre-Project Components
Geographical Enlargement of CERN Associate membership Principles and criteria S. Intoudi / 8 July
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Lecture 4. IS Planning & Acquisition To be covered: To be covered: – IS planning and its importance Cost-benefit analysis Cost-benefit analysis Funding.
Projects spanning over two programming periods Department for Programme and Project Preparation Beatrix Horváth, Deputy Head of Department Budapest, 5.
Information System Project Management Lecture three Chapter one
An introduction to Project Management Ainsley Smith
Chapter 11: Alternative Approach - Purchasing Systems.
1 STRATEGY EVALUATION CRITERIA: PERFORMANCE AUDITS AUDIT: Crucial audit for assessing and identifying the implementation and performance status of formulated.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
1 A Seminar On Pharmaceutical Outsourcing A Seminar On Pharmaceutical Outsourcing.
CHAPTER 6 Contract An agreement between parties that defines the benefits and responsibilities for those concerned (client & developer) Why need a contract?
Prof. Mohamed Batouche An SQA Architecture Project Development plan and Quality Plan Ch.6 Pre-project SQA components Project Life.
Multitude of source of errors - various style of source of errors will affect the SQA components * The environment in which software development & maintenance.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
P RE - PROJECT P RE - PROJECT SOFTWARE QUALITY COMPONENTS Dr. Ahmad F. Shubita.
Contract management 1. Acquiring software from external supplier This could be: a bespoke system - created specially for the customer off-the-shelf -
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Contract Review Software Quality Assurance and Testing.
Contract review. What Is a Contract?  an agreement between two or more parties to the doing or to provide a product or service.
Development and Quality Plans
Software Quality Assurance
Components of software quality assurance system overview
COMM02 Project Monitoring and Control Unit 8
Presentation 5 Contract review Contract review process and stages
Components of software quality assurance system overview
Procurement Management
MRABFH SE604 Software Testing and QA Lecture #2: Contract Review Lecture #3: SQA Planning . Slides by Mohammad El-Ramly,
The Software Quality Challenge
Chapter # 6 Software Configuration Management
Chapter # 4 Development and Quality Plans
Chapter # 3 The Components of SQA
Construction Contract Administration
Definition of Project “An organized endeavor aimed at accomplishing a specific non-routine or low-volume task.” Definition of Project Management “The.
Presentation transcript:

Presentation 5 Contract review Contract review process and stages Contract review objectives Implementation of contract review Contract review subjects Contract review for internal projects

Common contract situations Participation in a tender Proposal submission according to customer’s RFP Receipt of an order from a company’s customer Internal request from another department in the organization

Contract review stages Proposal draft review + Contract draft review --------------------------- Contract review

Proposal draft review - Objectives To make sure that the following activities have been satisfactorily carried out: Customer requirements clarified and documented Alternative approaches for carrying out the project examined Formal aspects of the relationship between the customer and the software firm specified Development risks identified Project resources and timetable adequately estimated The firm’s capacity with respect to the project examined The customer’s capacity to fulfill his commitments examined Partner and subcontractor’s participation conditions defined Protection of proprietary rights defined

Contract draft review - Objectives To make sure that the following activities have been satisfactorily carried out: 1. No unclarified issues remain in the contract draft 2. All understandings reached subsequent to the proposal are correctly documented 3. No “new” changes, additions, or omissions have entered the contract draft

Types of internal projects (1) Administrative or operative software to be applied internally (2) Software packages originally intended to be sold to the public as “off-the-shelf” packages (3) Firmware to be embedded in the company’s products

internal projects – Disadvantages "Loose relationship" internal projects – Disadvantages to internal customers Subject Disadvantages to the internal customer (1) Inadequate definition of project requirements * Implementation deviates from the needed applications * Low satisfaction (2) Poor estimate of the required resources * Unrealistic expectations about project feasibility (3) Poor timetable * Missing scheduled dates for beginning the distribution of new products (4) Inadequate awareness of development risks * Customer unprepared for project risks and their consequences

internal projects – Disadvantages to internal developers "Loose relationship" internal projects – Disadvantages to internal developers Subject Disadvantages to the internal customer (1) Inadequate definition of project requirements * Higher change requirements * Wasted resources due to introducing avoidable changes (2) Poor estimate of the required resources * Substantial deviations from budget * Friction between units induced by requirements for budget additions (3) Poor timetable * Development activities are under time pressures and suffer from low quality * Delays in freeing staff for their next project (4) Inadequate awareness of development risks * Tardy initiation of efforts to overcome difficulties