1 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Technical Reviews – Contents – 1.

Slides:



Advertisements
Similar presentations
Radiopharmaceutical Production
Advertisements

Requirements Specification and Management
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
System Integration Verification and Validation
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
EQUIPMENT VALIDATION.
GAI Proprietary Information
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
Process Engineer’s Role in Project Management Dr Abdullah Malik.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
The Software Development Life Cycle: An Overview
Web Development Process Description
S/W Project Management
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
Introduction to Software Quality Assurance (SQA)
Chapter 6 Software Implementation Process Group
ISO Tor Stålhane IDI / NTNU. What is ISO ISO 9001 was developed for the production industry but has a rather general structure ISO describes.
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
Software Configuration Management
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Project Life Cycles.
© Mahindra Satyam 2009 Configuration Management QMS Training.
ISO 9001 – an overview Tor Stålhane IDI / NTNU. ISO 9001 and software development ISO 9001 is a general standard – equally applicable to software development.
Hall 180 Cryogenic test facility: Project management: Project Change Request, EVM and Interface Sheet L. Serio.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
Systems Development Life Cycle
Software Engineering Lecture # 1.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
CS3320-Chap21 Office Hours TR 1:00-2:15 PM W 2:30-3:30 PM By appointment.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
CS646: Software Design and Architectures Introduction and Overview †  Definitions.  The general design process.  A context for design: the waterfall.
Getting Ready for the NOCTI test April 30, Study checklist #1 Analyze Programming Problems and Flowchart Solutions Study Checklist.
Installation and Commisioning SE view point Romuald Duperrier ESS SE manager.
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
PRODUCT VERIFICATION Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
SQA project process standards IEEE software engineering standards
Project Planning: Scope and the Work Breakdown Structure
SQA project process standards IEEE software engineering standards
Systems Analysis and Design
FIVE PROJECT PHASES 5C-3 Sun. 8:00-10:00am 21/ 2/2016.
Quality Management Systems – Requirements
Engineering Processes
Lockheed Martin Canada’s SMB Mentoring Program
Software life cycle models
ISO/IEC IEEE/EIA Software Life Cycle Processes Supporting Life Cycle Processes IEEE Supporting Processes.
How to conduct Effective Stage-1 Audit
Engineering Processes
PSS verification and validation
Information Systems Development (ISD) Systems Development Life Cycle
Machine Protection PLC Based System Verification and Validation Plan
Presentation transcript:

1 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Technical Reviews – Contents – 1

2 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator 3C Technical Reviews shall ensure for all deliverables: Completeness Compatibility Compliance Generating deliverables is a long(er)-term process. –> In order to ensure final 3C it is recommendable to subdivide this process into so-called Product Lifecycle Phases and perform intermediate 3C checks when moving from one phase to the subsequent. This has two aspects: 1.Backward 2.Forward That means: 1.A project lifecycle phase can be concluded because all belonging outputs are generated 2.The subsequent lifecycle phase can be started because all necessary inputs are available

3 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Output Input Product Lifecycle Phases Requirements definition CDR Conceptual design Detailed design Fabrication planning DRPRR Reviews timing must leave time for corrective actions Technical Reviews shall be scheduled as milestones Fabrication

4 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator XFEL Central Tasks WP A WP B InstallationFabrication Planning Conceptual Design Detailed Design Conceptual Design Detailed Design Independent and concurrent WPs contribute different parts of the facility. Reviews, resp. milestones create follow-up activities at integrated facility integrate -> Approval Reviews (MS) are coupling WP and central activities by sets of mandatory deliverables QA place holder A,B Inter- face proof CDR QA as-built doc’s B Review Accept for installation in XFEL QA QC doc’s B Review Accept for production tendering Reviews link WPs & Central Tasks QA review & Approval detailed design B DR Every deliverable is QA-ed on reception according to QA standards

5 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Reviews -> To be scheduled as milestones Reviewing is a QA measure of eminent importance Different Reviews are required at different times They couple WP activities and Central Tasks by sets of mandatory inputs & outputs They provide sureness to the WPs & PM They initiate ‘Follow-Up Activities’ in the project Concerns all major deliverables and sub-systems Timing must leave time for corrective actions

6 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Mandatory Outputs / Inputs (Deliverables) Deliverables / System Description Requirements Analysis Target Specifications Design (conceptual –> detailed) Fabrication Planning Quality Management Plan (QMP) Tendering Documents Further Mandatory Technical Documents Reviews Contents –> To be reviewed by all requesting & interfacing parties (WPLs, Coordinations) –> Changes to be incorporated (coordinated updating of all concerned docs) –> Finally to be approved by the Project Board

7 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Deliverables / System Description The Deliverables / Systems Description shall clarify: 1.Purpose What shall the system effect (Zweck –> Was soll das System leisten) General technical context Which needs of other systems shall be satisfied Which functionalities shall be delivered, provided to other systems What do they mean for the performance of the 2.Scope What shall the system achieve and what not anymore (Abgrenzung) Which performance extent is needed, which not anymore 3.Concept & Layout How shall the system achieve it General layout (segmentation, subcomponents, hardware, software, assembly steps)

8 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Requirements Analysis Requirements Elicitation Problem: Beside formulated requirements there are usually non-formulated expectations – They might be as important! Requirements Analysis shall ensure: 1.Completeness (product lifecycle, interfaces at each lifecycle phase) 2.Consistency (eliminated contradictions = negotiation results) 3.Prioritisation (must, nice to have, must not) 4.Verifiability (req. must be formulated such that their fulfilment can be verified / measured

9 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Target Specifications Target Specifications shall define: 1.Set of Requirements that shall be satisfied finally (issuers) Functional req. (= capabilities) Non-functional req. (= constraints; incl. regulations, standards & norms) 2.Exact technical specification how the deliverable shall be built Design choices (e.g. technologies, materials …) Self-produced parts Purchase parts Software (features & structure) Interfaces (mechanics, signal levels & structure) 3.Explanation how that technical layout will satisfy the requirements

10 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Design conceptual –> detailed The Design shall comprise: (conceptual –> detailed; high level –> low level; feasibility study –> shop drawings) 1.System Model ("Architecture": 3D, UML, written documents …) 2.Calculations (analytical, numerical) 3.Simulations (FEM, Start-to-End, Monte Carlo …) 4.Safety analysis (written documents, prototype tests …) 5.Interface Definitions (e.g. 3D Placeholders -> confirmed ‘Collision Free’, documents approved by requesting & interfacing parties like WPLs, Coordinations … )

11 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Fabrication Planning Fabrication Planning shall comprise: 1.Envisaged methods (description and reasoning, incl. advantages, constraints, disadvantages) 2.Fabrication adaptation (adapted models, drawings, plans …) 3.Side Conditions (availability/readiness of subsequent issues, e.g. test or storage environments, trained personnel …)

12 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator QMP Concluding a lifecycle phase requires two QM measures: 1.Verification (= Requirements coverage check; "Is the right thing done?") 2.Validation (= Compliance check; "Was it done right?") The Quality Management Plan* shall stipulate all QM measures for all product lifecycle phases The QMP shall therefore pre-define (pre-identify) all: 1.Verification criteria, methods, tools 2.Regulations, standards, norms Finally the QMP shall provide for each phase a complete specification of all needed inputs and resources, as well as planned outputs –> However, it will be a living document as understanding grows –> Nevertheless, it must be appropriate at any time * The QMP shall follow in general the recommendations of the EN ISO 9001 standard as much as possible

13 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Tendering Documents Tendering Documents shall comprise: 1.Technical part (written specs, fabrication models, shop drawings, QM measures …) 2.Commercial part (terms of contract, awarding matrix …) –> Both must be complete, consistent, compliant (3C) –> Criteria etc. to be pre-defined and are part of the QMP

14 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator Further Technical Documents Further Mandatory Technical Documents are: 1.Instructions / Manuals (assembly, installation, maintenance …) 2.Drawings (circuit diagrams, operation flow charts …) 3.Safety & Health Plans (for installation/integration activities at XFEL conducted under the own WP responsibility) 4.… (to be defined for each WP)

15 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator CDR – Review Content Deliverables / System Description Requirements Analysis Target Specifications Conceptual Design Quality Management Plan (QMP) Conceptual Design Review Requirements definition DRPRRCDR Conceptual design Fabrication planning Detailed design –> To be reviewed by all requesting & interfacing parties (WPLs, Coordinations) –> Changes to be incorporated (coordinated updating of all concerned docs) –> Finally to be approved by the Project Board Fabrication

16 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator DR – Review Content Deliverables / System Description Requirements Analysis Target Specifications Detailed Design Fabrication Planning Quality Management Plan (QMP) Design Review –> To be reviewed by all requesting & interfacing parties (WPLs, Coordinations) –> Changes to be incorporated (coordinated updating of all concerned docs) –> Finally to be approved by the Project Board Requirements definition DRPRRCDR Conceptual design Fabrication planning Detailed design Fabrication

17 Thomas HottTechnical Reviews Contents, 2 nd CDE-WS, 12 th & 13 th May 09 XFEL Technical Coordinator PRR -> Required Information Deliverables / System Description Requirements Analysis Target Specifications Design (conceptual –> detailed) Fabrication Planning Quality Management Plan (QMP) Tendering Documents Further Mandatory Technical Documents Production Readiness Review –> To be reviewed by all requesting & interfacing parties (WPLs, Coordinations) –> Changes to be incorporated (coordinated updating of all concerned docs) –> Finally to be approved by the Project Board Requirements definition DRPRRCDR Conceptual design Fabrication planning Detailed design Fabrication