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

More documents

Recommendations

Info

2.4.8 Project Planning ProcessPurpose:The purpose of the Project Planning Process is to produce and communicate effective andworkable project plans.This process determines the scope of the project management and technical activities, identifiesprocess outputs, project tasks and deliverables, establishes schedules for project task conduct,including achievement criteria, and required resources to accomplish project tasks.Implementation:Standard IO practices apply (defined and maintained by the IO Department for Administration,Project Management Division). Software management aspects are covered in the CODACsoftware project management plan [RD10].2.4.9 Project Assessment and Control ProcessPurpose:The purpose of the Project Assessment and Control Process is to determine the status of theproject and ensure that the project performs according to plans and schedules, and withinprojected budgets, and that it satisfies technical objectives.This process includes redirecting the project activities, as appropriate, to correct identifieddeviations and variations from other project management or technical processes. Redirectionmay include replanning as appropriate.Implementation:Standard IO practices apply (defined and maintained by the IO Department for Administration,Project Management Division). Software management aspects are covered in the CODACsoftware project management plan [RD10].2.4.10 Decision Management ProcessPurpose:The purpose of the Decision Management Process is to select the most beneficial course ofproject action where alternatives exist.This process responds to a request for a decision encountered during the system life cycle,whatever its nature or source, in order to reach specified, desirable or optimized outcomes.Alternative actions are analyzed and a course of action selected and directed. Decisions andtheir rationale are recorded to support future decision-making.Implementation:Standard IO practices apply (defined and maintained by the IO Department for Administration,Project Management Division).2.4.11 Risk Management ProcessPurpose:The purpose of the Risk Management Process is to identify, analyze, treat and monitor the riskscontinuously.Page 12 of 22
The Risk Management Process is a continuous process for systematically addressing riskthroughout the life cycle of a system or software product or service. It can be applied to risksrelated to the acquisition, development, maintenance or operation of a system.Implementation:Standard IO practices apply (defined and maintained by the IO Department for Administration,Project Management Division). Software management aspects are covered in the CODACsoftware project management plan [RD10].2.4.12 Configuration Management ProcessPurpose:The purpose of the Configuration Management Process is to establish and maintain theintegrity of all identified outputs of a project or process and make them available to concernedparties.Implementation:Standard IO practices apply (defined and maintained by the IO Department for ITER Project,Technical Integration Division). Software-specific procedures are covered in section 2.4.34.2.4.13 Information Management ProcessPurpose:The purpose of the Information Management Process is to provide relevant, timely, complete,valid and, if required, confidential information to designated parties during and, as appropriate,after the system life cycle.This process generates, collects, transforms, retains, retrieves, disseminates and disposes ofinformation. It manages designated information, including technical, project, organizational,agreement and user information.Implementation:Standard IO practices apply (defined and maintained by the IO Department for Administration,Document Control and Project Information System Sections). The principal instrument is IDM(see [RD6]). Standard document templates are given in reference [RD12].2.4.14 Measurement Management ProcessPurpose:The purpose of the Measurement Process is to collect, analyze, and report data relating to theproducts developed and processes implemented within the organizational unit, to supporteffective management of the processes and to objectively demonstrate the quality of theproducts.Implementation:Standard IO practices apply (defined and maintained by the IO Department for Administration,Project Management Division).Page 13 of 22
Page 2 and 3: Change LogTitle (Uid) Version Lates
Page 4 and 5: 2.4.34 Software Configuration Manag
Page 6 and 7: 1.3 DDD-45 ContextThe Design Descri
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 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?