Software Subcontractor

Slides:



Advertisements
Similar presentations
Contract CloseOut.
Advertisements

Software Quality Assurance Plan
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
How ISO9001 Compares with CMM Mark C. Paulk JAN,1995 CMM version 1.1 ISO9001 July 1994 presented by Zhilan Zhou.
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
Project Change Management
Stepan Potiyenko ISS Sr.SW Developer.
Project Management October 2011 Inf Sys 3810 Information Systems Analysis Fall 2011 Understand Project Management principles.
Project Management April 2015 Understand Project Management principles.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Development and Quality Plans
SystematicSystematic process that translates quality policy into measurable objectives and requirements, and lays down a sequence of steps for realizing.
1 M&S Teachers Seminar: Project Management Presented by: Paul E. Paquette September 26, 2013.
Employee Orientation and Training
SQA Work Procedures.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Release & Deployment ITIL Version 3
Effective Methods for Software and Systems Integration
© 1999 Prentice-Hall, Inc. Chap Level 3: Key Processes Defined Group 9: LaTanya Moore Ali Imajat Asim Eldaroty.
How to integrate the parts of your project to achieve success.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Introduction to Software Quality Assurance (SQA)
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
Software Quality Assurance Activities
Industrial Engineering Roles In Industry
Michael Dermody September 2010  Capability Maturity Model Integration ◦ Is a Trademark owned by the Software Engineering Institute (SEI) of Carnegie.
S Q A.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Preparing for the Launch Mohammed El- Affendi. Launch Major Tasks  The Launch is performed according to script “LAU1”, table 3.1 in the book (page 39),
Systems Analysis & Design Project Management. 2 Question ●When someone says ‘project’ what comes to mind?
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Georgia Institute of Technology CS 4320 Fall 2003.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Pre-Project Components
Chapter 13 Project Management. Objectives After reading the chapter and reviewing the materials presented the students will be able to: Define and give.
QUALITY MANAGEMENT STATEMENT
OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
The following training presentation is for all 1Prospect subcontract employees and is taken upon joining a contract or task order to which 1Prospect is.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
The following training presentation is for all Advancia Corporation subcontract employees and is taken upon joining a contract or task order to which Advancia.
INTERNAL AUDITS A Management Tool
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Fall 2010 Software Planning Guidelines.
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Unit Guide C ertificate IV in Project Management Qualification.
Project Quality Management
Software Quality Control and Quality Assurance: Introduction
The following training presentation is for all subcontract employees and is taken upon joining a contract or task order to which we are the Prime vendor.
Software Configuration Management
CSC 480 Software Engineering
Software and Systems Integration
TechStambha PMP Certification Training
IT 440: SYSTEM INTEGRATION
Software Requirements
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Software and System Delivery
Engineering Processes
Guidance notes for Project Manager
By Jeff Burklo, Director
Lockheed Martin Canada’s SMB Mentoring Program
Writing of SDP.
Software Engineering I
Engineering Processes
Team Software Process (TSP)
Software Reviews.
Presentation transcript:

Software Subcontractor IT 440:SYSTEM INTEGRATION

Upon completion of this week’s activities, you will be able to: Describe the methods that are performed by a software sub­contractor to provide the necessary support and employment that would benefit military and aerospace programs and projects. Identify which activities performed are in accordance with a purchase contract, and the software work products. Discuss the role of software sub­contractor and how they can be hired for program and project planning.

SOFTWARE SUBCONTRACTOR Purpose: program and project planning, configuration management, quality issues, software design/development, testing, and execution of activities/ tasks related to the delivery of software work products to customers. Activities: in accordance with a purchase contract, and the software work products are delivered to satisfy and comply with specified requirements.

PROGRAM AND PROJECT SELECTION Importance: selection of a subcontractor is important because of expectations and technical work disciplines required. Hiring-responsibility of program and project managers. Provide direction to perform job tasks related to the day-to-day software design/development to be delivered for subcontracted work products. Planning: performed during program and project start-up Statement of work (SOW) will list subcontractor requirements. Search and Selection of Subcontractor: required by program/project plans or the subcontractor program or project managers. Support includes teams or coordinated experience of software engineers for understanding all aspects.

SUBCONTRACTOR APPROACH Software subcontractor is an integral part of the team for product development. Ensure progress by the appropriate subcontractor Software activities/progress based on agreed evidence of completion. Responsibility of program and project organizations as well as senior managers to oversee the subcontractor’s work quality

SOFTWARE SUBCONTRACTOR PLAN Purpose: provides direction for the subcontractor, program, and projects for understanding the requirements and guidelines. Subcontractor Responsibility: configuration management software at the subcontractor’s facilities in accordance with the plans/procedures while abiding to the standards, processes, and procedures of the program/projects under a signed contract.

SUBCONTRACTOR PLAN APPROACH The plan should describe the following in detail: Subcontractor task Configuration management and quality audits process Job requirements Management of risk Management configuration Delivery schedules for work products

SOFTWARE AUDITS Subcontractor software plans and procedures are audited per defined and documented audit methods to trace information for software requirements per the signed contract. ensures software test environment performs intended functions and meets contract requirements. Purpose: ensures that the software under test is qualified on acceptable test tools.

SOFTWARE AUDITS Criteria: prepared/provided to subcontractor before audits are performed. audit checklist is provided, audit questions will be filled out, presented to the customer. agenda and participants are identified with a defined audit process applicable per the contract. Approach: involvement in the software first-article inspection (FAI)