Download
1 / 10
100 likes | 250 Views
Concept Documents. Concept of Operations (IEEE Standard 1362-1998)An operationally oriented description of user's needs, including qualitative and quantitative characteristics, that communicates how the system is expected to operate in its environment.Service or Sub-Service Level Concept of Operations (NAS SEM)More insight, detail, in-depth informationElaborates on capabilities and useConcept of Use (NAS SEM)Extension of the ConOps, more detail, more elaborationNarrative describing functional characteristics.
E N D
1. Seamless V&V: Concept Validation
2. Concept Documents Concept of Operations (IEEE Standard 1362-1998)
An operationally oriented description of user’s needs, including qualitative and quantitative characteristics, that communicates how the system is expected to operate in its environment.
Service or Sub-Service Level Concept of Operations (NAS SEM)
More insight, detail, in-depth information
Elaborates on capabilities and use
Concept of Use (NAS SEM)
Extension of the ConOps, more detail, more elaboration
Narrative describing functional characteristics
4. Action Plan 5: Validation & Verification Strategies
To determine a common strategy for validating and verifying the performance, reliability, and safety of ATM systems. The strategies provide guidance for validation and verification of operational concepts during R&D phases of ATM sub-system development.
5. Action Plan 5: Validation & Verification Strategies
Concept Validation
is an iterative process by which the fitness-for-purpose of an operational concept being developed is established. 1. Figure depicts the development of a concept to implementation is depicted as an iterative process.
2. The complementary mechanism to validation is the process of verification. The relationship between verification and validation during the early phases of concept development is not as well defined as it is in other domains such as software engineering; nonetheless, verification has a constant role in these phases.
3. Verification and validation have to happen at the end of each significant step.
1. Figure depicts the development of a concept to implementation is depicted as an iterative process.
2. The complementary mechanism to validation is the process of verification. The relationship between verification and validation during the early phases of concept development is not as well defined as it is in other domains such as software engineering; nonetheless, verification has a constant role in these phases.
3. Verification and validation have to happen at the end of each significant step.
6. V&V Discuss validation & verification of concepts within the context of the AMS and Concept Lifecycle Model (CLM) – AP5. The CLM is equivalent to the system development activity progression. Within AP5 the emphasis is on the product.
This strategy is focused on validating operational needs and requirements that are derived from the concept.
Discuss validation & verification of concepts within the context of the AMS and Concept Lifecycle Model (CLM) – AP5. The CLM is equivalent to the system development activity progression. Within AP5 the emphasis is on the product.
This strategy is focused on validating operational needs and requirements that are derived from the concept.
7. Different Perspectives on V&V Emphasis is 1) determining if the requirements are correct and complete – validation and
2) is that the design solution has met the system requirements and is ready for use in an operational environment
Validation process is conducted to demonstrate that the reqmts for a system are clearly understood and that it’s possible to satisfy the reqmts though the design work. Follows the development of system requirements.
Verification has 2 components – T&E and System Engineering Assessment
**need to cleanup***Emphasis is 1) determining if the requirements are correct and complete – validation and
2) is that the design solution has met the system requirements and is ready for use in an operational environment
Validation process is conducted to demonstrate that the reqmts for a system are clearly understood and that it’s possible to satisfy the reqmts though the design work. Follows the development of system requirements.
Verification has 2 components – T&E and System Engineering Assessment
**need to cleanup***
8. Perspectives on V&V
T&E V&V Handbook
“The purpose of Verification is to ensure that selected work products meet their specified requirements.”
“The purpose of Validation is to demonstrate that a product of product component fulfills it intended use when placed in its intended environment.” The same view is echoed in T&E Handbook (inserted text).
***need to clean up***The same view is echoed in T&E Handbook (inserted text).
***need to clean up***
9.
Are we building the right system?
Are we building the system right?
In short, all definitions/perspectives ask the following questions…In short, all definitions/perspectives ask the following questions…
10. V&V: Big Picture Conclusion….This slide shows the varying dimensions of V&V: 1) validation & verification of the product (e.g., system) itself and 2) validation and verification (V&V) of the work product (e.g., the requirements document and the process/method used to develop it – quality check).
Verification and validation have to happen at the end of each significant step.
AP5’s Spring workshop objective is to develop a verification strategy which would lend itself to looking at system development from the idea to implementation.
Conclusion….This slide shows the varying dimensions of V&V: 1) validation & verification of the product (e.g., system) itself and 2) validation and verification (V&V) of the work product (e.g., the requirements document and the process/method used to develop it – quality check).
Verification and validation have to happen at the end of each significant step.
AP5’s Spring workshop objective is to develop a verification strategy which would lend itself to looking at system development from the idea to implementation.
11. Questions/Comments
