illustration of the information model for complex system modeling: from requirement to v&v...

1
Illustration of the Information Model for Complex System Modeling: from Requirement to V&V Romaric Guillerm 1, 2 , Hamid Demmou 1, 2 , Nabil Sadou 3 [email protected], [email protected], [email protected] 1 CNRS, LAAS, 7 avenue du colonel Roche, F-31400 Toulouse, France 2 Université de Toulouse, UPS, INSA, LAAS, F-31400, Toulouse, France 3 SUPELEC / IETR, avenue de la Boulais, F-35511, Cesson-Sevigne, France 3rd Edition of the International Conference on Complex Systems Design & Management (CSDM 12) 12-14 December, 2012 – Paris, France We have defined an information model to assist the design of complex systems in a context of Model Based System Engineering (MBSE). This poster illustrates the utilization of this information model through a case study. System Engineering (SE) as framework for the design of complex system. EIA-632 standard to guide the SE approach. Information model to address requirements definition and their traceability towards the solution and the Verification and Validation (V&V) elements. The work considers especially an important system property which is safety. SysML language is used to establish the information model thanks to the different available diagrams, which make SysML as the language for systems engineering. Context The information model that we propose is adapted to the EIA-632 standard and makes a clear distinction between different requirements types. The case study illustrates the interest of the SysML information model on a complex example. It consists on an S18 aircraft that the specifications are provided by the standard ARP- 4761. Materials and Methods Illustration The involved subsystems for the decelerate function are: the thrust inverser system (or reverse), the spoiler system, and the wheel brake system. 2. Requirements The Top-level requirements diagram presents the requirements at system level. It connects those requirements to the risks they deal with the treat” link. References Conclusion 3. V&V Different concepts are handled in complex system design: requirements, design solution and V&V. An information model aims to help engineers in the expression of these concepts, and the creation of traceability links between them in order to facilitate the comprehension and/or the impacts analysis. It also helps to formalize the practice of systems engineering through the use of models. The objective is to improve quality/productivity and to reduce risks by introducing rigor, precision, and communications among stakeholders and managing complexity. 1. Guillerm R., Demmou H. and Sadou N., Safety evaluation and management of complex systems: A system engineering approach, Concurrent Engineering: Research and Application, vol.20 pp.149-159, June 2012. 2. Martin J. N., Overview of the EIA-632 Standard: Processes for Engineering a System, Digital Avionics Systems Conference, 31 Oct-7 Nov 1998. 3. Friedenthal S., Moore A., and Steiner R., A Practical Guide to SysML: The Systems Modeling Language, 576 The MK/OMG Press Series 2009. 4. ARP-4761: Guidelines and methods for conducting the safety assessment process on civil airborne systems and equipment , Society of Automotive Engineers (SAE) standard, December 1996. The study is limited to the “Decelerate aircraft on the ground” function. 1. Design Solution Blocks Diagram: Equipment Breakdown Structure . The Requirement declinations diagram shows the declination of the system requirements into subsystem requirements through the “compositionlink. The Requirement verification diagram denotes elements of V&V which satisfy the requirements with the “verify” link. Requirements Diagram: Requirement Declinations . Requirements Diagram: Requirement Verification . The Requirement satisfaction diagram indicates the system elements (system or subsytems) that meet the requirements with the “satisfy” link. Blocks Diagram: Test Cases . The Test cases diagram presents the defined V&V elements to verify the requirements. Requirements Diagram: Requirement Verification. (extract) Requirements Diagram: Top-Level Requirements . (Extract) The complexity of modern systems makes system engineering processes critical. Requirement engineering processes are important in system design. The emergence of critical proprieties like safety needs a global approach. MBSE allows to requirements definition and their traceability towards the solution elements and the V&V (Verification and Validation) elements. Information Model

Upload: felix-oliver

Post on 18-Dec-2015

216 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Illustration of the Information Model for Complex System Modeling: from Requirement to V&V Illustration of the Information Model for Complex System Modeling:

Illustration of the Information Model for ComplexSystem Modeling: from Requirement to V&V

Romaric Guillerm1, 2, Hamid Demmou1, 2, Nabil Sadou3

[email protected], [email protected], [email protected]

1 CNRS, LAAS, 7 avenue du colonel Roche, F-31400 Toulouse, France2 Université de Toulouse, UPS, INSA, LAAS, F-31400, Toulouse, France

3 SUPELEC / IETR, avenue de la Boulais, F-35511, Cesson-Sevigne, France

3rd Edition of the International Conference on Complex Systems Design & Management (CSDM 12)12-14 December, 2012 – Paris, France

We have defined an information model to assist the design of complex systems in a context of Model Based System Engineering (MBSE).This poster illustrates the utilization of this information model through a case study.

System Engineering (SE) as framework for the design of complex system.

EIA-632 standard to guide the SE approach.

Information model to address requirements definition and their traceability towards the solution and the Verification and Validation (V&V) elements.

The work considers especially an important system property which is safety.

SysML language is used to establish the information model thanks to the different available diagrams, which make SysML as the language for systems engineering.

Context

The information model that we propose is adapted to the EIA-632 standard and makes a clear distinction between different requirements types.

The case study illustrates the interest of the SysML information model on a complex example. It consists on an S18 aircraft that the specifications are provided by the standard ARP-4761.

Materials and Methods

Illustration

The involved subsystems for the decelerate function are: the thrust inverser system (or reverse), the spoiler system, and the wheel brake system.

2. Requirements

The Top-level requirements diagram presents the requirements at system level. It connects those requirements to the risks they deal with the “treat” link.

References

Conclusion

3. V&V

Different concepts are handled in complex system design: requirements, design solution and V&V.

An information model aims to help engineers in the expression of these concepts, and the creation of traceability links between them in order to facilitate the comprehension and/or the impacts analysis. It also helps to formalize the practice of systems engineering through the use of models.

The objective is to improve quality/productivity and to reduce risks by introducing rigor, precision, and communications among stakeholders and managing complexity.

1. Guillerm R., Demmou H. and Sadou N., Safety evaluation and management of complex systems: A system engineering approach, Concurrent Engineering: Research and Application, vol.20 pp.149-159, June 2012.

2. Martin J. N., Overview of the EIA-632 Standard: Processes for Engineering a System, Digital Avionics Systems Conference, 31 Oct-7 Nov 1998.

3. Friedenthal S., Moore A., and Steiner R., A Practical Guide to SysML: The Systems Modeling Language, 576 The MK/OMG Press Series 2009.

4. ARP-4761: Guidelines and methods for conducting the safety assessment process on civil airborne systems and equipment, Society of Automotive Engineers (SAE) standard, December 1996.

The study is limited to the “Decelerate aircraft on the ground” function.

1. Design Solution

Blocks Diagram: Equipment Breakdown Structure.

The Requirement declinations diagram shows the declination of the system requirements into subsystem requirements through the “composition” link.

The Requirement verification diagram denotes elements of V&V which satisfy the requirements with the “verify” link.

Requirements Diagram: Requirement Declinations.

Requirements Diagram: Requirement Verification.

The Requirement satisfaction diagram indicates the system elements (system or subsytems) that meet the requirements with the “satisfy” link.

Blocks Diagram: Test Cases.

The Test cases diagram presents the defined V&V elements to verify the requirements.

Requirements Diagram: Requirement Verification. (extract)

Requirements Diagram: Top-Level Requirements. (Extract)

The complexity of modern systems makes system engineering processes critical.

Requirement engineering processes are important in system design.

The emergence of critical proprieties like safety needs a global approach.

MBSE allows to requirements definition and their traceability towards the solution elements and the V&V (Verification and Validation) elements.

Information Model