Technical Specifications and Documentation Control Victor Billig International Space University Strasbourg 2010
|
|
|
- Joleen Clark
- 7 years ago
- Views:
Transcription
1 Technical Specifications and Documentation Control Victor Billig International Space University Strasbourg
2 Baseline Documentation Project Contract (legal terms & definitions) System Specifications (technical definition) System Requirements Specification Subsystem Requirements Specifications Interface Specification Quality Assurance Specification AIT Specification Statement of Work (SOW) Description of Tasks to be performed Summary of Deliverables Deliverable Items List (DIL) (hardware & software) Document Requirements List (DRL) Document Requirements Description 2
3 Baseline Documentation Sample Table of Content of Space System Specifications: Introduction Space Segment Spacecraft Design (Satellite or Other Space Object) Spacecraft AIT Associated Ground Support Equipment (MGSE& EGSE) Transportation to Launch Site Ground Segment Ground Control Centre (GCC) Tracking System Services Software Spacecraft Software GCC Software Software Acceptance (End-to-End-Tests) Software Operating Procedures Launch and Launch Support Launch Vehicle Compatibility Launch Site Support Post-Launch Support Project Reviews PDR, CDR, FRR, MRR, FAR 3
4 Baseline Documentation Sample Table of Content of a Statement of Work: Introduction (Purpose) Scope General Background Technical Requirements, Constraints Applicable Documents Reference Documents Task description Engineering Tasks Design (Hardware and Software) Development Prototyping Tests Prototype Manufacturing Prototype Testing Reporting and Documentation Project Management Project Deliverable Items List (DIL) Hardware Software Contract Document Requirements List (CDRL) Data Requirements Description (DRD) 4
5 Baseline Documentation Project Plans Work Breakdown Structure (WBS) Project Milestone List Project Time Schedules Project Cost Plans Project Control Plan Schedule Control Cost Control Earned Value Analysis Documentation Control Plan Configuration Control Plan Design & Development Plan Assembly, Integration & Test (AIT) Plan Facility Plan 5
6 Baseline Documentation Sample Table of Content of Project Contracts: Scope of Work (Reference to Specifications, SOW and Plans) Deliverables and Services and related Prices Project Options Payment Schedules Delivery Dates and Adjustments for late Deliveries Progress and Status Reports Inspection and Acceptance Project Changes and Change Control Rights in Data and Proprietary Information Intellectual Property Rights Subcontractors and Key Personnel Communications and Project Language Force Majeure Arbitration, Applicable Law Effective Date of Contract End of Contract and Termination 6
7 The PM is obligated to control the actual status of all project documentation and the system configuration At project start the PM shall prepare a documentation requirement list (DRL), respectively a contractual DRL (CDRL) A sample DRL is provided at following slide 7
8 Document Requirement List PROGRAM/ PROJECT DATA REQUIREMENTS LIST (DRL) DRL-Nr.: DOC-Nr. Document Title/Brief Description Due Date SP-01 Sp-02 System Specification Subsystem Specification To To + 1 mo. PL-01 PL-02 PL-03 PL-04 PL-05 Program Plan D& Plan Master Time Schedule Manpower & Cost Plan Monthly Status Report To To + 3 mo. To To monthly 8
9 Sample Documentation Code PPP DDD WWW RRRR I. a PPP = Project Name DDD = Document Code (SP = Specification, PL = Plan WWW = WBS Code (if applicable) RRRR = Unique Running Number (0001 to 9999) I = Issue (I, II, III, etc.) a = Change index within an issue (a, b, c, etc.) Documentation release and distribution to the assigned recipients shall be performed by the PM in accordance with the implemented project organization 9
10 Configuration Control Procedure Configuration control starts after approval of the system specification at the System Requirement Review (SRR) A formal configuration control procedure will be implemented at contract award and confirmed at the preliminary design review (PDR) The aim is to ensure that the products developed within the frame of the program/project are conforming to an agreed system specification 10
11 Configuration Control Procedure Configuration control system covers the following topics: 1. Identification of the Configuration Items (CI's); 2. Identification, maintenance and updating of the configuration baseline; 3. Identification and control of all physical and functional interfaces; 4. Organization of Configuration Control Board (CCB) meetings 5. For change an engineering change proposal (ECP) shall be prepared; 6. Customer changes shall be filed as class A changes 7. All other engineering changes are to be filed as class B changes; 8. For class A changes a contract change notice (CCN) shall be issued; 9. PM shall provide on a regular basis a design and as built configuration and waiver status list 11
12 Configuration Control Procedure The configuration control function is related to identification, control and reporting, of the following: 1. Baseline control including identification and documentation of functional and physical characteristics of systems, subsystems and products; 2. Control of changes to the characteristics of the identified items, with verification of compliance to agreed requirements; 3. Detection of implication of changes applied to one configuration items on others and on systems; 4. Recording of changes, documentation and reporting of changes and implementation status; 5. To make sure that all program/project participants have the same view and use identical data during the life cycle of the program, in a consistent and controlled manner. 12
13 Configuration Control Board The CCB will approve or disapprove the request for an ECP. Permanent members of the CCB will be the key people of the PM team Specialists from functional departments and/or partners may be invited to participate to the CCB All CCB members, whether permanently assigned or specially invited, must be fully authorized to take decisions on behalf of their respective organization, and to accept actions placed upon the organization they represent 13
14 Recommended Project Management Literature Kerzner, Project Management & Study Guide, 8th Edition Madauss, Projektmanagement, 6th Edition, 2000, German Verzuh, The Fast Forward MBA in Project Management, 1999 Terry, Principles of Management, 7th Edition ESA, Space Project Management, ECSS-M 14
TENDERING PROCESS WINNING PROPOSL
TENDERING PROCESS WINNING PROPOSL Bernd Madauss International Space University (presented by Victor Billig) bernd@madauss.com October 2010 1 Just like project work, a proposal must be managed But, proposals
Bernd Madauss Project-Management-Team Bad Aibling, Germany. bernd@madauss.com. Fundamentals of Project Management (PM): Life Cycle
IMPRS, Katlenburg-Lindau, 23-25 May 2005 Bernd Madauss Project-Management-Team Bad Aibling, Germany bernd@madauss.com Table of Content Fundamentals of (PM): Life Cycle Considerations, Project Control Methodologies
Space engineering. System engineering. ECSS-E-10 C Draft 1
Space engineering System engineering This ECSS document is a draft standard distributed for Public Review. It is therefore subject to change without any notice and may not be referred to as an ECSS Standard
SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
Appendix E Program Management Plan Template
Appendix E Program Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions
IBIS DOCUMENT TYPE: INSTRUMENT MANAGEMENT PLAN. DOCUMENT No.: TL PAGE: I of V,26. PROJECT Ref.: ISSUE No.: Draft DATE: January, 97 CHECKED BY:
DOCUMENT TYPE: PLAN TITLE: INSTRUMENT MANAGEMENT PLAN DOCUMENT No.: TL PAGE: I of V,26 PROJECT Ref.: ISSUE No.: Draft DATE: January, 97 PREPARED BY: G. FUGGETTA CHECKED BY: SYSTEM MANAGER: DATE: PAPM:
CONFIGURATION MANAGEMENT REQUIREMENTS EXM-MS-RS-ESA-00008
Page: 1/22 ExoMars CONFIGURATION MANAGEMENT REQUIREMENTS EXM-MS-RS-ESA-00008 Issue 1, Rev. 0 Date and Signature Prepared Agreed HME-CLS P. Provasi 29 June 2007 Approved HME-ME D. McCoy 29 June 2007 Page:
Goddard Procedures and Guidelines
Goddard Procedures and Guidelines DIRECTIVE NO. APPROVED BY Signature: Original signed by NAME: A. V. Diaz TITLE: Director Responsible Office: Title: Code 300 / Office of Systems Safety and Mission Assurance,
Space Flight Project Work Breakdown Structure
APPENDIX G. (WBS) Space Flight Project Work Breakdown Structure G.1 Introduction G.1.1 The Project Work Breakdown Structure (WBS) is a key element of project management. The purpose of a WBS is to divide
Configuration Management ISO 10007
Configuration Management ISO 10007 Introduction Configuration Management Overview: What is Configuration Management? Collection of tools, techniques and experience designed to reduce costs and improve
An Introduction to the ECSS Software Standards
An Introduction to the ECSS Software Standards Abstract This introduces the background, context, and rationale for the creation of the ECSS standards system presented in this course. Addresses the concept
Technical Baseline Management
Technical Baseline Management September 30, 2003 Pat Hascall LAT System Engineering 1 Technical Baseline Management We are required to manage the configuration of our technical baseline What is configuration
Developing Work Breakdown Structures
Developing Work Breakdown Structures International Cost Estimating & Analysis Association June 2014 Neil F. Albert MCR, LLC nalbert@mcri.com 703-506-4600 2014 MCR, LLC Distribution prohibited without express
CalMod Design-Build Electrification Services
SECTION 01800 SYSTEMS INTEGRATION AND INTEGRATOR REQUIREMENTS PART 1 GENERAL DESCRIPTION A. This section specifies the system-wide integration requirements for the Caltrain Electrification system, i.e.
Space project management
ECSS-M-ST-40C Rev. 1 Space project management Configuration and information management ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is
PROJECT MANAGEMENT PLAN CHECKLIST
PROJECT MANAGEMENT PLAN CHECKLIST The project management plan is a comprehensive document that defines each area of your project. The final document will contain all the required plans you need to manage,
5 FAH-5 H-520 LIFE CYCLE MANAGEMENT
5 FAH-5 H-520 LIFE CYCLE MANAGEMENT (CT:ITS-5; 02-05-2013) (Office of Origin: (IRM/BMP/SPO/PM) 5 FAH-5 H-521 CONFIGURATION MANAGEMENT REQUIREMENTS Configuration management (CM) is a function deployed throughout
WORK BREAKDOWN STRUCTURE
Chapter 9 Work Breakdown Structure CHAPTER 9 WORK BREAKDOWN STRUCTURE 9.1 INTRODUCTION The Work Breakdown Structure (WBS) is a means of organizing system development activities based on system and product
Space product assurance
ECSS-Q-ST-80C Space product assurance Software product assurance ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS
IT Project: System Implementation Project Template Description
2929 Campus Drive Suite 250 IT Project: System Implementation Project Template Description Table of Contents Introduction... 2 Project Phases... 3 Initiation & Requirements Gathering Milestone... 3 Initiation
Space engineering. Software engineering handbook. ECSS-E-HB-40A 11 December 2013
Space engineering Software engineering handbook ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Handbook is one document of the series of ECSS Documents
Introducing ECSS Software-Engineering Standards within ESA
r bulletin 111 august 2002 Introducing ECSS Software-Engineering Standards within ESA Practical approaches for space- and ground-segment software M. Jones & E. Gomez Ground Segment Engineering Department
CONTRACT-BASED PROGRAM MANAGER OBJECTIVE
CONTRACT-BASED PROGRAM MANAGER OBJECTIVE Successful execution of contract-based programs means managing volumes of information to efficiently meet all contractual obligations. Tracking, reporting and communicating
Mission Operation Ground. Assurance @ ESA. Mario Merri GSAW, Los Angeles, USA 2 Mar 2011 ESA UNCLASSIFIED
Mission Operation Ground Software Systems Product Assurance @ ESA Mario Merri GSAW, Los Angeles, USA 2 Mar 2011 The European Cooperation for Space Standardisation (ECSS) Established: in 1993 Goal: coherent,
Configuration Management
Configuration Management Co Al Florence This presenter s affiliation with the MITRE Corporation is provided for identification purposes only and is not intended to convey or imply MITRE s concurrence with
Space Project Management
EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space Project Management Configuration Management Secretariat ESA ESTEC Requirements & Standards Division Noordwijk, The Netherlands Published by: Price:
ECSS-E-ST-40C 6 March 2009. Space engineering. Software. ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands
ECSS-E-ST-40C Space engineering Software ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS Standards intended to
The Impacts Of Agile Development On The System Engineering Process
The Impacts Of Agile elopment On The System Engineering Process 17 th Annual Systems Engineering Conference October 27-30, 2014 Springfield, Virginia Discussion Topics Background What Is Agile elopment
Software Classification Methodology and Standardisation
Software Classification Methodology and Standardisation 07 March 2003 1/10 Table of Contents 1. INTRODUCTION a Galileo system overview Ε b Master schedule Ε 2. GALILEO SAFETY CASE APPROACH Ε 3. SYSTEM
PROJECT AND CONSTRUCTION MANAGEMENT SERVICES FOR KUWAIT PORT AUTHORITY FOR PROJECTS AT SHUAIBA PORT
PROJECT AND CONSTRUCTION MANAGEMENT SERVICES FOR KUWAIT PORT AUTHORITY FOR PROJECTS AT SHUAIBA PORT - INTRODUCTION 1.1. General. Kuwait Ports Authority (KPA) through the Ministry Of Finance (MOF) wishes
Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201
PURCHASE ORDER ATTACHMENT Q-201A Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201 1. A qualified employee shall be selected by the Software Quality Manager
ENOVIA Aerospace and Defense Accelerator for Program Management
ENOVIA Aerospace and Defense Accelerator for Program Management Through project pipeline dashboards, ENOVIA Aerospace and Defense Accelerator for Program Management provides real-time visibility into a
DEPARTMENT OF THE AIR FORCE HEADQUARTERS AERONAUTICAL SYSTEMS CENTER (AFMC) WRIGHT-PATTERSON AIR FORCE BASE OHIO
DEPARTMENT OF THE AIR FORCE HEADQUARTERS AERONAUTICAL SYSTEMS CENTER (AFMC) WRIGHT-PATTERSON AIR FORCE BASE OHIO BULLETIN AWB 002A 17 May 2011 ((supersedes AWB-002) United States Air Force (USAF) Airworthiness
DOCUMENT REQUIREMENTS DESCRIPTIONS
DOCUMENT REQUIREMENTS DESCRIPTIONS Document number... SKA-TEL.SE-SKO-DRD-001 Revision... 1 Author... Jason Spyromilio Date... 2013-03-10 Status... Released Name Designation Affiliation Date Signature Owned
Space engineering ECSS. System engineering Part 1: Requirements and process. ECSS-E-10 Part 1B EUROPEAN COOPERATION FOR SPACE STANDARDIZATION
-E-10 Part 1B EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space engineering System engineering Part 1: Requirements and process Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The
Project QA and Collaboration Plan for <project name>
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and
Requirements Management John Hrastar
Requirements Management John Hrastar NASA Project Management Conference March 30-31, 2004 University of Maryland Conference Center Introduction Three aspects of requirements management Requirements in
Cost Estimating Procedure. Table of Contents
Cost Estimating Procedure Table of Contents 1.0 PURPOSE... 1 2.0 SCOPE... 1 3.0 REFERENCES... 1 4.0 DESCRIPTION... 1 5.0 PROCEDURE DETAILS... 2 5.1 Developing a Detailed Cost Estimate... 2 5.2 Basis of
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
ESA s Data Management System for the Russian Segment of the International Space Station
iss data management system ESA s Data Management System for the Russian Segment of the International Space Station J. Graf, C. Reimers & A. Errington ESA Directorate of Manned Spaceflight and Microgravity,
Space project management
ECSS-M-ST-60C Space project management Cost and schedule management ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of
Facility Maintenance Management Competency 4.9
Competency 4.9 Facility maintenance management personnel shall demonstrate the ability to perform project management duties as required to provide facility maintenance management technical support to a
DATA REQUIREMENTS DESCRIPTION (DRD)
DATA REQUIREMENTS DESCRIPTION (DRD) 1. DPD NO.: XXX ISSUE: Draft 2. DRD NO.: STD/EDAL 3. DATA TYPE: 3 4. DATE REVISED: 5. PAGE: 1/3 6. TITLE: Engineering Drawings and Associated Lists 7. DESCRIPTION/USE:
Overview of SAE s AS6500 Manufacturing Management Program. David Karr Technical Advisor for Mfg/QA AFLCMC/EZSM 937-255-7450 david.karr@us.af.
Overview of SAE s AS6500 Manufacturing Management Program David Karr Technical Advisor for Mfg/QA AFLCMC/EZSM 937-255-7450 david.karr@us.af.mil 1 Outline Background Objectives Requirements Implementation
CONFIGURATION MANAGEMENT PLAN GUIDELINES
I-680 SMART CARPOOL LANE PROJECT SYSTEM ENGINEERING MANAGEMENT PLAN CONFIGURATION MANAGEMENT PLAN GUIDELINE SECTIONS: PLAN GUIDELINES 1. GENERAL 2. ROLES AND RESPONSIBILITIES 3. CONFIGURATION MANAGEMENT
<Project Name> Software Quality Assurance (SQA) Plan. <Document Control Number>
Software Quality Assurance (SQA) Plan Date: CHECK THE AT< WEBSITE Address> TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. General Tailoring Guidelines This
STATEMENT OF WORK FOR DESIGN, FABRICATION, INTEGRATION AND TESTING OF THE TELESCOPE STRUCTURE SYSTEM TMT.STR.MGT.12.001.REL01
STATEMENT OF WORK FOR DESIGN, FABRICATION, INTEGRATION AND TESTING OF THE TELESCOPE STRUCTURE SYSTEM TMT.STR.MGT.12.001.REL01 27 July, 2012 TMT.STR.TEC.12.001.DRF01 Page 2 of 13 Table of Contents 1. INTRODUCTION
Tailoring of ECSS Software Engineering Standards for Ground Segments in ESA
BSSC 2005(1) Issue 1.0 June 2005 Tailoring of ECSS Software Engineering Standards for Ground Segments in ESA Part A: Software Engineering Prepared by: ESA Board for Software Standardisation and Control
System Engineering Management Plan MDOT-ITS 001-01-006
System Engineering Management Plan MDOT-ITS 001-01-006 ITS Projects - Systems Engineering Process Compliance Version 2.0 March 20, 2009 Prepared by: Gresham, Smith and Partners, MS, P.C. DBA Gresham, Smith
Statement of work CDRL, And Tracking Tool (SCATT)
Statement of work CDRL, And Tracking Tool (SCATT) September 2011 1 Agenda Overview & Introduction Brief History SCATT Tool Components SOW Questionnaire CDRL Wizard CDRL Tracking Tool Who uses the SCATT
Project Management for Everyone
Project Management for Everyone Contact Information Adam Donaldson, PMP Business Management & Analysis Group Phone: (202) 994-6867 Cell: (240) 472-2171 Email: adonald@gwu.edu Objectives Basic understanding
Configuration Management Self Assessment Checklist
Configuration Management Self Assessment Checklist Introduction: The purpose of this Configuration Management (CM) Self- Assessment Checklist is to ensure that the Organization correctly understands the
NODIS Library Program Formulation(7000s) Search
NODIS Library Program Formulation(7000s) Search NASA Procedural Requirements This Document Is Uncontrolled When Printed. Check the NASA Online Directives Information System (NODIS) Library to verify that
LISA Pathfinder SUMMARY
Page 2 of 36 SUMMARY This document defines the Independent Software Verification and Validation requirements for the Implementation Phase of the LISA Pathfinder project. Page 3 of 36 TABLE OF CONTENTS
074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements
Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality
Effective Space Project Management
Effective Space Project Management Nghi M. Nguyen, P.E., PMP, President, NDV Project Management Services Inc. and Project Management Consultant, Canadian Space Agency (CSA) Introduction The application
Project Management Guidelines
Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.
An Introduction to IMP/IMS
An Introduction to IMP/IMS In 2003 the US Government revised its acquisition policies with a procurement strategy focused on process improvement and acquisition reform implemented by performance-based
Criteria for Flight Project Critical Milestone Reviews
Criteria for Flight Project Critical Milestone Reviews GSFC-STD-1001 Baseline Release February 2005 Approved By: Original signed by Date: 2/19/05 Richard M. Day Director, Independent Technical Authority
Proton Launch System Mission Planner s Guide APPENDIX B. Quality Management System
Proton Launch System Mission Planner s Guide APPENDIX B Quality Management System B. QUALITY MANAGEMENT SYSTEM B.1 Proton Quality Assurance Plan B.1.1 KhSC Quality Management Overview ILS Proton launch
Information Technology Project Management (ITPM)
FUNCTIONAL AREA 10 Project Management (ITPM) Incumbents in this functional area direct information technology system solution and/or improvement projects for cost, time, scope, risk, and quality. They
NOTICE: This publication is available at: http://www.nws.noaa.gov/directives.
Department of Commerce National Oceanic & Atmospheric Administration National Weather Service NATIONAL WEATHER SERVICE INSTRUCTION 30-1201 OCTOBER 13, 2003 Maintenance, Logistics, & Facilities Configuration
Software Quality Assurance Plan for the EMD Project
104-EMD-001 ECS Maintenance and Development Project Software Quality Assurance Plan for the EMD Project Revision - October 2003 Raytheon Company Upper Marlboro, Maryland Software Quality Assurance Plan
System Engineering Plan
Project Documentation Document SPEC-0064 Revision A System Engineering Plan Rob Hubbard, Jeremy Wagner, Larry Daggert, Larry Stepp, Christoph Keller Systems Engineering / Project Management 5 October 2006
Superseded by T MU AM 04001 PL v2.0
Plan T MU AM 04001 PL TfNSW Configuration Management Plan Important Warning This document is one of a set of standards developed solely and specifically for use on the rail network owned or managed by
CONFIGURATION MANAGEMENT PLAN
CONFIGURATION MANAGEMENT PLAN Integrated Procurement System U.S. Election Commission i CONFIGURATION MANAGEMENT PLAN TABLE OF CONTENTS Page # 1.0 CONFIGURATION CONTROL...3 1.1 Change Control Board (CCB)...3
BUSINESS OCR LEVEL 3 CAMBRIDGE TECHNICAL. Cambridge TECHNICALS BUSINESS PROJECT MANAGEMENT CERTIFICATE/DIPLOMA IN K/502/5459 LEVEL 3 UNIT 18
Cambridge TECHNICALS OCR LEVEL 3 CAMBRIDGE TECHNICAL CERTIFICATE/DIPLOMA IN BUSINESS BUSINESS PROJECT MANAGEMENT K/502/5459 LEVEL 3 UNIT 18 GUIDED LEARNING HOURS: 60 UNIT CREDIT VALUE: 10 BUSINESS PROJECT
Schedule of Construction. Project Management and Control
Ocean Observatories Initiative Schedule of Construction Project Management and Control Anthony Ferlaino OOI Project Manager Science Community Workshop I Baltimore, Nov 11-12, 2009 Process Controls of a
Dependable (Safe/Reliable) Systems. ARO Reliability Workshop Software Intensive Systems
Dependable (Safe/Reliable) Systems Composing, Analyzing and Validating s to Assess / Develop / Validate Methods and Supporting Tools for the Creation of Dependable Systems ARO Reliability Workshop Intensive
Integrating the Worldwide Project Management Method (WWPMM) into an IBM Global Services Method Project
IBM Global Services Integrating the Worldwide Project Management Method (WWPMM) into an IBM Global Services Method Project Technique Paper (TP) Copyright International Business Machines Corporation, 2000
Appendix B: Work Breakdown Structure (WBS)
: Work Breakdown Structure (WBS) B.1. Introduction The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. In accordance with
Space Environment Technologies (SET) QUALITY ASSURANCE PROGRAM. Command Media. Approved by: Approved by: Approved by:
Space Environment Technologies (SET) QUALITY ASSURANCE PROGRAM Command Approved by: Approved by: Approved by: S. Dave Bouwer Rian Shelley W. Kent Tobiska SECTION 1 - QUALITY POLICY & ADMINISTRATION Scope
Space Project Management
EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space Project Management Project Phasing and Planning Secretariat ESA ESTEC Requirements & Standards Division Noordwijk, The Netherlands Published by: Price:
CMS Policy for Configuration Management
Chief Information Officer Centers for Medicare & Medicaid Services CMS Policy for Configuration April 2012 Document Number: CMS-CIO-POL-MGT01-01 TABLE OF CONTENTS 1. PURPOSE...1 2. BACKGROUND...1 3. CONFIGURATION
Space Project Management
Space Project Management F.J. Fuentes ITER Project, France 22-26 October 2012 UNAM, Mexico D.F. 22-26 October 2012 Page 1 Course General Outline and Scope Day 1. Management Principles Objectives and Requirements
Page 1. Outline of the Lecture. What is Software Configuration Management? Why Software Configuration Management?
Books: Software Configuration Management 1. B. Bruegge and A. H. Dutoit, Object-Oriented Software Engineering: Using UML, Patterns, and Java (Chapter 13) Outline of the Lecture Purpose of Software Configuration
How to Write a Software Process Procedures and Policy Manual for YOUR COMPANY
How to Write a Software Process for YOUR COMPANY 1. Introduction MicroTools is proposing to assist YOUR COMPANY in improving the existing software process. The purpose of this project is to both improve
REQUEST FOR PROPOSAL INFORMATION SECURITY PROGRAM PROVIDER
REQUEST FOR PROPOSAL INFORMATION SECURITY PROGRAM PROVIDER OCTOBER 18, 2013 1 Table of Contents I. EXECUTIVE OVERVIEW... 3 II. BACKGROUND... 3 A. Goals & Objective of Request... 3 B. Project Scope... 4
5 FAH-5 H-510 CONFIGURATION MANAGEMENT
5 FAH-5 H-500 CONFIGURATION MANAGEMENT 5 FAH-5 H-510 PROJECT DEVELOPMENT AND CHANGE CONTROL (CT:ITS-4; 06-21-2012) (Office of Origin: IRM/BMP/GRP/GP) (Updated only to revise Office of Origin) 5 FAH-5 H-511
Software Project Management Plan (SPMP)
Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.
Space engineering ECSS. Software - Part 1: Principles and requirements. ECSS-E-40 Part 1B EUROPEAN COOPERATION FOR SPACE STANDARDIZATION
-E-40 Part 1B EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space engineering Software - Part 1: Principles and requirements Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands
Configuration & Build Management
Object-Oriented Software Engineering Using UML, Patterns, and Java Configuration & Build Management Outline of the Lecture Purpose of Software Configuration Management (SCM) Some Terminology Software Configuration
Work Breakdown Structure Element Dictionary Construction
Initiation CON 5.1 Initiation encompasses deliverables associated with the development, implementation and control of the project s schedule, budget and scope, including the solicitation for a contractor
Software Engineering. Software Engineering. Software Costs
Software Engineering Software Engineering is the science and art of building significant software systems that are: 1) on time 2) on budget 3) with acceptable performance 4) with correct operation. Ian
Software Requirements Management
Software Requirements Management Space Shuttle Lessons Learned #3377 1/27/2011 Hal Turner NASA Kennedy Space Center NE-C1 Application and Simulation Software Engineering Harold.H.Turner@nasa.gov (321)
WROCI Configuration Management Plan (CMP)
WROCI Configuration Management Plan (CMP) Western Range Operations Communications and Information (WROCI) Contract No. F04684-03-C-0050 CDRL A009 Configuration Management Prepared for Department of the
What methods are used to conduct testing?
What is testing? Testing is the practice of making objective judgments regarding the extent to which the system (device) meets, exceeds or fails to meet stated objectives What the purpose of testing? There
Software Configuration Management. Addendum zu Kapitel 13
Software Configuration Management Addendum zu Kapitel 13 Outline Purpose of Software Configuration Management (SCM) Motivation: Why software configuration management? Definition: What is software configuration
<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
Software Quality Assurance Plan
Software Quality Assurance Plan Submitted to: George C. Marshall Space Flight Center National Aeronautics and Space Administration Marshall Space Flight Center, AL 35812 Submitted by: Center for Space
pm4dev, 2016 management for development series Project Scope Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS
pm4dev, 2016 management for development series Project Scope Management PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS PROJECT MANAGEMENT FOR DEVELOPMENT ORGANIZATIONS A methodology to manage development
A Brazilian Software Industry Experience in Using ECSS for Space Application Software Development
A Brazilian Industry Experience in Using ECSS for Space Application Development Fátima MattielloFrancisco a,1, Valdivino Santiago a, Ana Maria Ambrósio a, Leise Jogaib b and Ricardo Costa b a National
Project Communication Plan Template
by: Michael B. Bender Contact Information: Michael B. Bender Ally Business Developers 23W236 Kimberwick Lane Naperville, IL 60540 Phone: 630/548-0399 e-mail: MBender@AllyBusiness.com (c) 2005 Allibus Corp.
PROJECT PLAN TEMPLATE
Treasury Board of Canada Secretariat Secrétariat du Conseil du Trésor du Canada Enhanced Management Framework for Information Management/Information Technology PROJECT PLAN TEMPLATE Document Revision Draft
Project Charter and Scope Statement
Prepared by: Mike Schmidt Version: 1.0 Last Revision Date: April 14, 2010 Create Date: May 6, 2010 EXECUTIVE SUMMARY... 3 1 INTRODUCTION... 4 2 PROJECT OBJECTIVES... 4 2.1 MISSION... 4 2.2 OBJECTIVES...
ALS Configuration Management Plan. Nuclear Safety Related
Westinghouse Non-Proprietary Class 3 Advanced Logic System 6002-00002-NP, Rev. 10 Function Author Nuclear Safety Related July 2014 APPROVALS Name and Signature Anthony C. Pagano* Integrated Process Lead,
ISRO Ka-Band HTS Satellite Procurement RFP
ISRO/ISAC/HTS/RFP/Pre-Bid/Q&A/2016/01 ISRO Ka-Band HTS Satellite Procurement RFP Tender Enquiry RFP No. IGSE-2015-0-32117-01 for procurement of ISRO Ka HTS Pre-bid Meeting Questions & Answers February
SKA DOCUMENT MANAGEMENT PLAN
SKA DOCUMENT MANAGEMENT PLAN Document number... SKA-TEL.OFF.MGT-SKO-MP-001 Revision... 1 Author... TJ Stevenson Date... 2013-03-10 Status... Released Name Designation Affiliation Date Signature Owned by:
THE CITY OF NORTH LAS VEGAS REQUEST FOR INFORMATION FOR ASSET TRACKING & INVENTORY MANAGEMENT RFI# 06-30-09-01 RELEASE DATE: JUNE 30, 2009
THE CITY OF NORTH LAS VEGAS REQUEST FOR INFORMATION FOR ASSET TRACKING & INVENTORY MANAGEMENT RFI# 06-30-09-01 RELEASE DATE: JUNE 30, 2009 RESPONSES TO BE RECEIVED BY JULY 21, 2009 2:00 P.M. RETURN TO