SEQA-45 - Software Engineering and Quality Assurance for ... - Iter

More documents

Recommendations

Info

1.3 DDD-45 ContextThe Design Description Document for CODAC (DDD-45, [RD2]) describes CODAC designassumptions and candidate solutions for them. Some of these topics are covered in more detailin the annex documents. This document makes a part of the DDD-45 package focusing on thesoftware engineering and QA topic.1.4 ScopeThis document describes general rules, practices and recommendations for softwareengineering in the scope of ITER CODAC activities. It defines the overall approach;technology-specific topics are described in separate reference documents.The content of this document applies to the development of the CODAC System (PBS 45).Plant system I&Cs prepared in the scope of the PCDH are also subject to these requirements.The Central Interlock System (PBS 46), the plasma control algorithms (PBS 47), and CentralSafety Systems (PBS 48) are not addressed yet.This document is primarily focused on the CODAC System (PBS 45). Chapter 2 gives astandard conformity statement for CODAC.Software for control system elements qualified as COTS devices does not have to follow theserules and should follow the engineering and quality assurance guidelines of their respectivemanufacturers and/or maintainers instead. COTS components will be selected in such a waythat their integration does not degrade the overall quality level of CODAC.1.5 DefinitionsMany terms and definitions used in this document are explained in the glossary of the ISO/IEC12207 standard ([RD3]).The ISO/IEC 12207 standard is broken down into two main parts – system engineering andsoftware engineering. By the “system” we understand hereafter a plant system I&C or a centralsystem (central systems are treated as plant systems PBS 45, PBS 46, PBS 47 and PBS 48, withsome special control features). The system includes both hardware and software. Systemengineering in the I&C context is addressed by the PCDH ([RD1]) and this annex document isfocused on software engineering. For some processes the system engineering for I&C followsthe same life cycle as for its plant system and is thus governed by overall ITER Organization(IO) practices; this is noted specifically in section 2.2.The following abbreviations and acronyms are used in this document (Table 1-1):ADMCIECISCODACCOTSCWSD-TDDDADMinistration directorateCentral Integration and Engineering directorateCentral Interlock SystemControl, Data Access and CommunicationCommercial Off-The-ShelfCooling Water SystemDeuterium-TritiumDesign Description DocumentPage 4 of 22
DOORSDRDTEPICSFDISFPGAGDHMIHPNI&CIDMIECIOISOLCCPBSPCDHPISPLCPSPSSQAR&DRDSADDSCCSCMPSCPSDMPSDPSDSDSEQASPMPSQAPSQLSQSSRCSRDSRSSSPDynamic Object Oriented Requirements SystemDocument ReviewDocument TemplatesExperimental Physics and Industrial Control SystemFinal Draft International StandardField Programmable Gate ArrayGeneric DocumentHuman-Machine InterfaceHigh Performance NetworksInstrumentation and ControlITER Document ManagementInternational Electrotechnical CommissionITER OrganizationInternational Standards OrganizationLocal Control CubiclePlant Breakdown StructurePlant Control Design HandbookPlant Interlock SystemProgrammable Logic ControllerPlant SystemPlant Safety SystemQuality AssuranceResearch and DevelopmentReference DocumentSoftware Architecture and Design DescriptionSignal Conditioning CubicleSoftware Configuration Management PlanSystem Context ProcessesSoftware Documentation Management PlanSoftware Development PlanSoftware Development Standards DescriptionSoftware Engineering and Quality AssuranceSoftware Project Management PlanSoftware Quality Assurance PlanStructured Query LanguageSafety, Quality and Security departmentSouRCe codeSystem Requirements DocumentSoftware Requirements SpecificationSoftware Specific ProcessesPage 5 of 22
Page 2 and 3: Change LogTitle (Uid) Version Lates
Page 4 and 5: 2.4.34 Software Configuration Manag
Page 8 and 9: STPSTRSUMSVNSWTBDSoftware Test Plan
Page 10 and 11: 2.3 ISO/IEC 12207 Conformity Matrix
Page 12 and 13: 2.4.1 Acquisition ProcessPurpose:Th
Page 14 and 15: 2.4.8 Project Planning ProcessPurpo
Page 16 and 17: 2.4.15 Stakeholder Requirements Def
Page 18 and 19: 2.4.23 Software Operation ProcessPu
Page 20 and 21: demonstrate that the functional and
Page 22 and 23: This process is executed in accorda
Page 24: 4 PROJECT CLASSIFICATIONProjects ex

SEQA-45 - Software Engineering and Quality Assurance for ... - Iter

Create successful ePaper yourself

Delete template?

Save as template?