Technical Documentation Coordinator

Slides:



Advertisements
Similar presentations
S Y S T E M S E N G I N E E R I N G.
Advertisements

Chapter 2 – Software Processes
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
CS 411W - Notes Product Development Documentation.
Development and Use of Architectures in System Engineering Rosalind Lewis USC-CSSE Workshop October 2007 © 2007 The Aerospace Corporation Motivated by.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
SE 555 Software Requirements & Specification Requirements Validation.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
[ §4 : 1 ] 4. Requirements Processes II Overview 4.1Fundamentals 4.2Elicitation 4.3Specification 4.4Verification 4.5Validation Software Requirements Specification.
Effective Methods for Software and Systems Integration
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
SOFTWARE REQUIREMENTS SPECIFICATION (SRS)
Lesson 7 Guide for Software Design Description (SDD)
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
1 ITS America Palm Springs, CA June 6, 2007 SunGuide SM Software – Florida's ITS Software ITS America Palm Springs, CA June 6, 2007 Trey Tillander, P.E.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Software System Engineering: A tutorial
1 Lecture 5.2.b: Requirements Specifications (IEEE 830) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Dr. Tom WayCSC Software Requirements CSC 4700 Software Engineering Lecture 2 Based on Sommerville, Chapter 6.
From Use Cases to Test Cases 1. A Tester’s Perspective  Without use cases testers will approach the system to be tested as a “black box”. “What, exactly,
Best Systems Engineering Products Drive CMMI NDIA 6th Annual Systems Engineering Supportability & Interoperability Conference October 21, 2003 Dr. Tom.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.
Lecture 7: Requirements Engineering
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
ANALYSIS - II REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Requirements Traceability Matrix
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
Requirements Analysis
Software Engineering Lecture 10: System Engineering.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1. What is Demand Management? …aims to understand, anticipate, prioritize and influence customer demand for services. Demand Management 2.
Requirement Specification SRS document is a contract between the development team and the customer How do we communicate the Requirements to others? Firm.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
1 Interfaces, Engineering and Standards. 2 Interfaces LoKI Interface document description for deliverables Elements: PBS number, Deliverable description,
 System Requirement Specification and System Planning.
The Quality Gateway Chapter 11. The Quality Gateway.
BSA 385 Week 4 Individual Assignment Frequent Shopper Program Part 3 For the items specified in the technical architecture document developed for the Frequent.
Software Process Activities.
SYSTEM ANALYSIS AND DESIGN
Session 5b Dr. Dan C. Surber, ESEP
Software Requirements
COIT20235 Business Process Modelling
DoDAF 2.x Meta Model (DM2) Conceptual Level
Lockheed Martin Canada’s SMB Mentoring Program
Systems Engineering for Mission-Driven Modeling
ESS.VIP VALIDATION An ESS.VIP project for mutual benefits
Network Architecture By Dr. Shadi Masadeh 1.
Technical Documentation Coordinator
Technical Documentation Coordinator
Ian Evans SSRL Safety Office
PSS verification and validation
ESS Management System SSM visit 24th October
Technical Documentation Coordinator
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
Technical Documentation Coordinator
Safety Readiness Review (SRR) Thomas Hansson, ESH
Requirements Engineering Lecture 6
DOE Review of the LCLS Project October 2006
Machine Protection PLC Based System Verification and Validation Plan
Bunker Project Integration/Interfaces
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
Bunker Project Interfaces introduction
Chapter 2 Software Processes
Presentation transcript:

Technical Documentation Coordinator BUNKER SYSTEM REQUIREMENTS Critical Design Review (CDR) 5 December 2017 Mark Ridgley Technical Documentation Coordinator Bunker Project europeanspallationsource.se

Bunker System Requirements ESS-0060210 - System Requirements Specification (SRS) Extracted from: Guide for Writing Requirements, INCOSE-TP-2010-006-02.1, 30 June 2017

Bunker System Requirements Stakeholders Expectations Stakeholders expectations for the Bunker System: See ESS-0123251, ConOps for the Bunker System, Section 3. (Systems Documentation folder in Material)

Bunker System Requirements Flow down of High-level System Requirements In general the high-level system requirements applicable to the Bunker System flow down from Shielding & Safety System (S&SS) as allocated by its System Architecture Description (SAD). High-level system requirements together with constraint requirements and the information presented elsewhere in ConOps for the Bunker System, are the primary source for the system requirements for the Bunker System (BS.SyR).

Bunker Subsystem Requirements High-level system requirements High-level system requirements allocated to the Bunker System by its parent system the Shielding & Safety System: See ESS-0123251, ConOps for the Bunker System, Section 4. (Systems Documentation folder in Material)

Bunker System Requirements ESS-0060210 - System Requirements Specification (SRS) All system requirements are captured and specified in the System Requirements Specification (SRS) for the Bunker System. Derived from: high-level requirements allocated by the parent system - Shielding & Safety System ConOps for the Bunker System feedback from the evolving design development of the system BS.SyR are defined according to the different categories and each is uniquely identified: Functional Requirements Constraint Requirements Seismic Safety Requirements Radiation Safety Requirements Interface Requirements BS.SyR are applied to the requirements driven development of the system design.

Bunker System Requirements ESS-0060210 - System Requirements Specification (SRS) As well as baselined BS.SyR that are transformed into the design of the system, the system design process is driven and/or guided by: ESS dedicated rules, procedures, manuals and guidelines that guide and/or drive the design process. European and International standards and norms.

Bunker System Requirements ESS-0060210 - System Requirements Specification (SRS) Before acceptance as a requirement on the Bunker System: Requirements must be achievable - reflect need or objective for which a solution is technically achievable at costs considered affordable. Requirements must be verifiable - expressed in a manner that allows verification to be objective. Requirements must be unambiguous. Requirements must be expressed in terms of need, not solution. Requirements must be consistent with other requirements without conflict. Requirements must be appropriate for the level of system hierarchy without constraining solutions for the level of design.

Bunker System Requirements ESS-0060210 - System Requirements Specification (SRS) For all Bunker System requirements (BS.SyR): See ESS-0060210, SRS for the Bunker System. (Systems Documentation folder in Material)

Bunker System Requirements ESS-0123443 - System Architecture Description (SAD) As well as describing the system architecture, SAD allocates BS.SyR to subsystems accordingly. BS.SyR are allocated to at least one subsystem. Bunker System Breakdown Structure (simplistic)

Bunker System Requirements ESS-0123443 - System Architecture Description (SAD) For allocation of Bunker System requirements (BS.SyR) to the subsystems: See ESS-0123443, SAD for the Bunker System, Section 4. (Systems Documentation folder in Material)

Bunker System Requirements ESS-0123443 - System Architecture Description (SAD) Flow of requirements

Bunker Structural Support System System Requirements For high-level requirements (BS.SyR) allocated to the Bunker Structural Support System: See ESS-0123282, ConOps for the Bunker Structural Support System. For all Bunker Structural Support System requirements (BSSS.SyR): See ESS-0123295, SRS for the Bunker Structural Support System. For allocation of Bunker Structural Support System requirements (BSSS.SyR) to the first level subassemblies: See ESS-0123445, SAD for the Bunker Structural Support System. (All available in Systems Documentation folder in Material)

Bunker Wall System System Requirements For high-level requirements (BS.SyR) allocated to the Bunker Wall System: See ESS-0123283, ConOps for the Bunker Wall System. For all Bunker Wall System requirements (BWS.SyR): See ESS-0123296, SRS for the Bunker Wall System. For allocation of Bunker Wall System requirements (BWS.SyR) to the first level subassemblies: See ESS-0123446, SAD for the Bunker Wall System. (All available in Systems Documentation folder in Material)

Bunker Roof System System Requirements For high-level requirements (BS.SyR) allocated to the Bunker Roof System: See ESS-0123286, ConOps for the Bunker Roof System. For all Bunker Structural Support System requirements (BRS.SyR): See ESS-0123297, SRS for the Bunker Roof System. For allocation of Bunker Roof System requirements (BRS.SyR) to the first level subassemblies: See ESS-0123447, SAD for the Bunker Roof System. (All available in Systems Documentation folder in Material)

Bunker Access Safety System System Requirements For high-level requirements (BS.SyR) allocated to the Bunker Access Safety System: See ESS-0123281, ConOps for the Bunker Access Safety System. For all Bunker Access Safety System requirements (BASS.SyR): See ESS-0123287, SRS for the Bunker Access Safety System. For allocation of Bunker Access Safety System requirements (BASS.SyR) to the first level subassemblies: See ESS-0123444, SAD for the Bunker Access Safety System. (All available in Systems Documentation folder in Material)