Presentation 5 Contract review Contract review process and stages

Slides:



Advertisements
Similar presentations
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.
Advertisements

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.
1 IS371 WEEK 8 Last and Final Assignment Application Development Alternatives to Application Development Instructor Online Evaluations.
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
Mitun PatelMXP07U. Organisational structure Top management; this includes the organisation’s general manager and its executives Department managers; this.
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.
Initiating and Planning Systems Development projects
Software Quality assurance SQA – SWE 333
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 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.
Module 10 Session 10.4 Visual 1 Module 10 Organizing Procurement Session 10.4 Procurement of Services: Use of Consultants and Developing Terms of Reference.
Assuring the quality of external participants' contributions Michael Rooney mpr07u.
Chapter 5 Contract review Contract review process and stages
Overview of SQA Components
EARTO – working group on quality issues – 2 nd session Anneli Karttunen, Quality Manager VTT Technical Research Centre of Finland This presentation.
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.
Prepared by Scott M. Shafer, Updated by William E. Matthews and Thomas G. Roberts, William Patterson University Copyright 2007 John Wiley & Sons, Inc.5-1.
Pre-Project Components
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.
OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing.
An introduction to Project Management Ainsley Smith
Chapter 11: Alternative Approach - Purchasing Systems.
1 IT Project Management, Project Failure and Success  Introduction  Projects operate in a broad organizational environment.  Project managers need to.
OHT 15.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Templates The contribution of templates to software quality The organizational.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
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.
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
CHAPTER 6 Contract An agreement between parties that defines the benefits and responsibilities for those concerned (client & developer) Why need a contract?
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(C.S.E) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.
UNIVERSITY OF DAR ES SALAAM t Selection and Employment of Consultants Negotiations with Consultants; Monitoring Performance of Consultants; Resolving Disputes.
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.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Contract Review Software Quality Assurance and Testing.
Chapter 7.2. Continuing:  Factors affecting intensity of SQA activities  Verification, validation and qualification  Development and quality plans.
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
Supporting quality devices
Components of software quality assurance system overview
MRABFH SE604 Software Testing and QA Lecture #2: Contract Review Lecture #3: SQA Planning . Slides by Mohammad El-Ramly,
The Software Quality Challenge
FOUNDATIONAL CONCEPTS
Presentation 5 Contract review Contract review process and stages
Chapter # 4 Development and Quality Plans
Chapter # 3 The Components of SQA
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

Implementation of a contract review (1/2) Factors affecting the extent of a contract review - project magnitude, technical complexity, acquaintance/ experience with/in the project area, project organizational complexity Who performs a contract review? (In ascending order with complexity) - the leader or another member of the proposal team - the members of the proposal team - an outside professional or a company staff - a team of outside experts

(2/2) Implementation of a review for major proposals - Def. of major proposals - The difficulties of carrying out contract reviews *time pressures, requires professional work, time conflict Recommended avenues for implementing major contract reviews - the review should be scheduled. - a team should carry out the review. - a review team leader should be appointed.

Contract Review Subjects Based on the contract review objectives. Checklists are useful devices. Contract review team determines the list of subjects pertinent for the project.

Contract reviews for internal projects - 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 developers (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