How the NCSX Project Does Business

Slides:



Advertisements
Similar presentations
Technical System Options
Advertisements

Archiving NCSX Construction Information Using the PPPL Windows Based Server.
Software Quality Assurance Plan
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Software Quality Assurance Plan
Chapter 2 – Software Processes
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Work Breakdown Structures. Purpose The WBS shows different levels within the product hierarchy. For Government program managers levels 1-3 are of prime.
CS 411W - Notes Product Development Documentation.
Software Requirements
Project Management Session 7
Chapter 5: Project Scope Management
Systems Engineering Management
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Software Requirement Specification(SRS)
LSU 07/24/2004Defining Project Tasks1 Defining the Project Tasks Project Management Unit, Lecture 4.
SystematicSystematic process that translates quality policy into measurable objectives and requirements, and lays down a sequence of steps for realizing.
Engineering Systems of.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.
Introduction to Software Quality Assurance (SQA)
Typical Software Documents with an emphasis on writing proposals.
1 Lecture 3.9: RFP, SOW and CDRL (SEF Ch 19) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1/18/2005Module 41 How the NCSX Project Does Business Work Planning & Design Review Processes.
MSF Requirements Envisioning Phase Planning Phase.
Classroom Assessments Checklists, Rating Scales, and Rubrics
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Software Requirements Engineering CSE 305 Lecture-2.
Electronic Engineering Department Final Year Projects September 2008.
8 8 Chapter 8 The University Lab: Conceptual Design Verification, Logical Design, and Implementation Database Systems: Design, Implementation, and Management.
NCSX NCSX Design Review Guide May 27, 2005 Wayne Reiersen NCSX.
12/2/04Module 2D1 The NCSX Engineering Web – An Overview Part IV Engineering Management & Systems Engineering and Other.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
August 2005 TMCOps TMC Operator Requirements and Position Descriptions Phase 2 Interactive Tool Project Presentation.
12/2/2004Module 2A1 The NCSX Engineering Web – An Overview Part I Work Planning, Project Files, Management Plans and Procedures.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
Systems Development Life Cycle
NCSX Systems Engineering Management Plan Peer Review Bob Simmons May 15, 2003.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
ISO Registration Common Areas of Nonconformances.
NCSX Data Management Plan Peer Review Bob Simmons March 31, 2003.
Software Requirements Specification Document (SRS)
1 PDS MC Requirements Process March 29, 2007 (v2).
11/23/2004Module # 11 The NCSX Project Web An Indoctrination and Overview.
September 10, FY 2003 Plans Bob Simmons. September 10, Introduction Overview of Project and Engineering Plans Project Plans Engineering Plans.
NCSX Interface Control Management Plan and Implementing Procedure 003 Peer Review December 19, 2002.
12/2/04Module 2C1 The NCSX Engineering Web – An Overview Part III Design Data, Fabrication, Assembly, and Installation Plans.
NCSX Document and Records Plan Peer Review Bob Simmons March 14, 2003.
1 WBS 1 Preparation for FDRs NCSX WBS 1 Engineering Meeting March 17, 2003 What establishes the plan? What are near term deliverables? How will we status.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
Statistical process model Workshop in Ukraine October 2015 Karin Blix Quality coordinator
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
SQA project process standards IEEE software engineering standards
Accelerator Readiness Review October 31, 2006
SQA project process standards IEEE software engineering standards
Prepared by Rand E Winters, Jr. ASR Senior Auditor October 2014
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Level - 3 Process Areas (CMMI-DEV)
Project Charter I want to design a project
Project Management Process Groups
DOE Review of the LCLS Project October 2006
Presentation transcript:

How the NCSX Project Does Business Specifications and Statements of Work 12/3/2004 Module 3

Purpose Provides review of how the NCSX Project does business This module will focus on: Specifications Design Criteria Statements of Work Later modules to will address other parts of how the NCSX Project will do business Modules 1 & 2 are intended to provide overview of the NCSX Project Web and the NCSX Engineering Web Modules 4-10 will focus other aspects of how the NCSX Project will do business The NCSX Engineering Web is, to a major extent, the electronic NCSX filing system Exceptions are the models and drawings contained in the Pro/INTERALINK data base and the hard copy supplier and other PPPL documents stored in the PPPL Operations Center However – bulk of files stored electronically on this web 12/3/2004 Module 3

Specifications and Statements of Work (SOW) Statement of Work Guidelines GRD Specifications Specification Format Guidelines Statements of Work (SOWs) 12/3/2004 Module 3

Types of Specifications General Requirements Document (GRD) Top level NCSX Project technical specification and provides a complete set of performance requirements and constraints at the overall project level Overall system requirements in the GRD allocated down to a set of specific developmental requirements and further down to the appropriate product component/procurement level Development (Performance) Specifications Document design requirements for cog engineers System Requirements Documents (SRDs), generally prepared for each 2-digit WBS, are the prime examples Product Specifications Serve as a basis for a procurement or fabrication Product function spec defines the product by specifying its functionality – used when supplier does the design Product fabrication spec defines the product by specifying the design – used when project does the design Other Product specs to be added as necessary Other Specifications Situations may occur that require specifications such as processes or materials Product Requirements List (PRL) Used to specify minimum requirements when purchasing a catalog item when a formal specification would be overkill 12/3/2004 Module 3

General Requirements Document (GRD) Latest version of GRD available on the NCSX Engineering Web Major parts of the GRD System Requirements (Details in Appendix A of GRD) Definition - system elements and functions Characteristics – performance; external interfaces; & physical characteristics (e.g., maximum lift, maximum dimensions, and maximum floor loading) System quality factors – RAM; design life; and transportability Design and Construction – materials, processes and parts; nameplates and product marking; workmanship, interchangeability; ES&H; and human engineering Documentation Logistics – maintenance; supply; and facilities Personnel and training Characteristics of subordinate elements – allocation of requirements down to lower level subsystems (Details in Appendix B to GRD) Verification of Requirements General overview Inspection Verification Methods Quality Conformance (Details in Appendix C of GRD) Notes Section will contain definitions and acronyms 12/3/2004 Module 3

Sample Pages from GRD 12/3/2004 Module 3

Developmental (Performance) Specifications State the requirements for the design or engineering development of a product during the developmental stage (usually preliminary design) – sometimes referred to as System Requirements Documents (SRDs) Should be of sufficient detail to describe effectively that each component within that subsystem is to achieve when it evolves into the detailed design phase Maintained current during development and subsequent production when it is desired to retain a complete statement of performance requirements for a particular subsystem Lower level developmental specifications may be prepared if deemed appropriate NCSX Engineering Web has link to format guidelines for developmental specifications OPTIONAL?? 12/3/2004 Module 3

Developmental Specification Guidelines 12/3/2004 Module 3

Product Specifications Applicable to any component below the subsystem level May be one of several types of product specifications Functional (performance) requirements where the supplier will do the detailed design Format guidelines still under development Fabrication (detailed design) where the project does the detailed design – essentially a “build to print” procurement Format guidelines available 12/3/2004 Module 3

Fabrication Product Specification Guidelines Functional Product Specification Guidelines - TBD Fabrication Product Specification Guidelines Still Out of date Web needs to be updated to reflect PRLs 12/3/2004 Module 3

Other Specifications May be other situations that might require specifications Processes Materials Format guidelines for these specifications will be develop on a case-by-case basis 12/3/2004 Module 3

Product Requirements Lists (PRLs) Used to specify minimum requirements when purchasing a catalog item when a formal specification would be overkill No sample PRL available yet Format guidelines to be developed later 12/3/2004 Module 3

Subsystem Specifications Example: Modular Coils Links to specific WBS element specifications Production Modular Coil Winding Forms 12/3/2004 Module 3

Statements of Work (SOW) Purpose of a Statement of Work (SOW) is to detail the work requirements for projects and programs that have deliverables and/or services performed SOW covers the work requirements and, in conjunction with applicable performance/design requirements contained in specifications, is used for contractual agreements The SOW defines (either directly or by reference to other documents) all non-specification requirements for the supplier effort Technical qualitative and quantitative design and performance requirements are contained in specifications and referenced standards – SOWs typically do not contain technical requirements Typically used to task a supplier to establish, implement, and control specific management programs in terms of results needed rather than “how to manage” procedures SOW also used to require a supplier to establish, implement, and control specific specialty programs (e.g., maintainbility, reliability, configuration management and control, etc.) 12/3/2004 Module 3

Statements of Work Guidelines 12/3/2004 Module 3

Statements of Work (SOW) Single page with links to all the current versions of Statements of Work (SOW) Example: VVSA 12/3/2004 Module 3

Summary This training module has focused on specifications and statements of work Specs define technical qualitative and quantitative design and performance requirements SOWs define (either directly or by reference to other documents) all non-specification requirements for the supplier effort Several types of specifications exist General Requirements Document – top level project specification Requirements and constraints allocated down to lower level subsystems and components Developmental - document design requirements at the system level Product – functional (performance based) and fabrication (“build to print” based) Other – process and material or perhaps others Product Requirements List (PRL) - specifies minimum requirements when purchasing a catalog item when a formal specification would be overkill Statement of Work – usually non-technical in content – sets management systems and specialty systems engineering processes required 12/3/2004 Module 3