051659 - Ministerstvo obrany
051659 - Ministerstvo obrany 051659 - Ministerstvo obrany
ČOS 051659 1. vydání Příloha C Architectural Design requirement. Maintain throughout the system life cycle the set of system requirements together with the associated rationale, decisions and assumptions. Manage system requirements in accordance with the Configuration Management Process. Description Activities Architectural design synthesises a solution Identify and explore one or more that satisfies system requirements, expressed implementation strategies at a level of detail as a set of separate problems of manageable, consistent with the system’s technical conceptual and, ultimately, realisable requirements and risks. proportions and ensure that a defined design Define a design solution in terms of the standard of materiel meets the requirements requirements for a complete set of of the contract specification. technically viable components from which the system is configured. Plan and devise an assembly and test strategy that will detect and diagnose faults during the integration steps. Define areas of solution and establish a basis for detection/correction of errors throughout the system life cycle. Establish traceability of architectural design to system requirements. Implementation Description The purpose of the Implementation Process is to produce a specified system element. Integration Activities Define implementation strategy. Identify implementation strategy/technology constraints on the design. Realize system element. Record objective evidence that system element meets supplier agreements, legislation, and organizational policy. Package and store system element appropriately. Description Activities The Integration Process is to assemble a Define an assembly sequence and strategy system that is consistent with the that minimizes system integration risk. architectural design. This process combines Identify the constraints on the design arising system elements to form complete or partial from the integration strategy. system configurations in order to create a Obtain integration enabling systems and 140
product specified in the system requirements. Verification ČOS 051659 1. vydání Příloha C specified materials according to the defined integration procedures. Obtain system elements in accordance with agreed schedules. Assure that the system elements have been verified against acceptance criteria specified in an agreement. Integrate system elements in accordance with applicable interface control descriptions and defined assembly. Create procedures, using the specified integration facilities. Record integration information. Description Activities The purpose of the Verification process is to Define the strategy for verifying the systems confirm that the specified design throughout the life cycle. requirements are fulfilled. Define a verification plan based on system requirements. Identify and communicate potential constraints on design decisions. Ensure that the enabling system for verification is available and associated facilities, equipment and operators are prepared to conduct the verification. Conduct verification to demonstrate compliance to the specified design requirements. Make available verification data on the system. Analyze, record and report verification, discrepancy and corrective action information. Transition Description Activities The Transition Process establishes an Prepare the site of operation in accordance integrated and verified system to provide with installation requirements. services specified by stakeholder Deliver the system for installation at the requirements in the operational correct location and time. environment. Install the system in its operational location and interfaced to its environment according to its system specification. Demonstrate proper installation of the system. 141
- Page 89 and 90: název a krátký popis programu, v
- Page 91 and 92: pro odhad a s posouzením nejistot
- Page 93 and 94: ČOS 051659 1. vydání Zabezpečen
- Page 95 and 96: ČOS 051659 1. vydání 7.2 Shroma
- Page 97 and 98: velkou rozmanitost dat, která se m
- Page 99 and 100: vyžaduje důkladný analytický od
- Page 101 and 102: specifické účely, jako je: - nas
- Page 103 and 104: ČOS 051659 1. vydání Vážené i
- Page 105 and 106: 9. Měna. 9. The currency. 10. Meto
- Page 107 and 108: vytvořily výrazy interpretovateln
- Page 109 and 110: dat, vztahy mezi nimi a funkce, kte
- Page 111 and 112: ČOS 051659 1. vydání PLCS Refere
- Page 113 and 114: ČOS 051659 1. vydání P Ř Í L O
- Page 115 and 116: ČOS 051659 1. vydání Příloha A
- Page 117 and 118: 13. Testování, hodnocení, zkouš
- Page 119 and 120: chybí díky ztrátám na živé s
- Page 121 and 122: ČOS 051659 1. vydání Příloha B
- Page 123 and 124: ČOS 051659 1. vydání Příloha C
- Page 125 and 126: Podnikové procesy Management podni
- Page 127 and 128: System Life Cycle Processes Managem
- Page 129 and 130: zahrnuje přesměrování projektov
- Page 131 and 132: Project Processes Project Planning
- Page 133 and 134: Information Management ČOS 051659
- Page 135 and 136: Popis Návrh architektury sjednocuj
- Page 137 and 138: Validace Popis Proces validace posk
- Page 139: Technical Processes Stakeholder Req
- Page 143 and 144: Maintenance ČOS 051659 1. vydání
- Page 145 and 146: ČOS 051659 1. vydání (VOLNÁ STR
- Page 147 and 148: ČOS 051659 1. vydání (VOLNÁ STR
ČOS <strong>051659</strong><br />
1. vydání<br />
Příloha C<br />
Architectural Design<br />
requirement.<br />
Maintain throughout the system life cycle<br />
the set of system requirements together with<br />
the associated rationale, decisions and<br />
assumptions.<br />
Manage system requirements in accordance<br />
with the Configuration Management<br />
Process.<br />
Description<br />
Activities<br />
Architectural design synthesises a solution Identify and explore one or more<br />
that satisfies system requirements, expressed implementation strategies at a level of detail<br />
as a set of separate problems of manageable, consistent with the system’s technical<br />
conceptual and, ultimately, realisable requirements and risks.<br />
proportions and ensure that a defined design Define a design solution in terms of the<br />
standard of materiel meets the requirements requirements for a complete set of<br />
of the contract specification.<br />
technically viable components from which<br />
the system is configured.<br />
Plan and devise an assembly and test<br />
strategy that will detect and diagnose faults<br />
during the integration steps.<br />
Define areas of solution and establish a basis<br />
for detection/correction of errors throughout<br />
the system life cycle.<br />
Establish traceability of architectural design<br />
to system requirements.<br />
Implementation<br />
Description<br />
The purpose of the Implementation Process<br />
is to produce a specified system element.<br />
Integration<br />
Activities<br />
Define implementation strategy.<br />
Identify implementation strategy/technology<br />
constraints on the design.<br />
Realize system element.<br />
Record objective evidence that system<br />
element meets supplier agreements,<br />
legislation, and organizational policy.<br />
Package and store system element<br />
appropriately.<br />
Description<br />
Activities<br />
The Integration Process is to assemble a Define an assembly sequence and strategy<br />
system that is consistent with the that minimizes system integration risk.<br />
architectural design. This process combines Identify the constraints on the design arising<br />
system elements to form complete or partial from the integration strategy.<br />
system configurations in order to create a<br />
Obtain integration enabling systems and<br />
140