Project number
26504
Organization
Honeywell Aerospace
Offering
ENGR498-S2026-F2026
#Overview
This project is to develop a comprehensive SysML model of turbine engines aligned with ARP4754B development processes (create a reference model like the ARP4754B Wheel Brake System Example in Appendix E). The model will integrate product line engineering principles for a generic turbine which could include options of afterburner, nacelle, and accessories. The model would have a deep structural/logical architectural and top-level functional decomposition. The model would incorporate executable behavioral modeling (simulation) to support requirements validation and airworthiness compliance. Given the time frame, the executable model would focus on at least one functional and logical subsystem. The model would be developed using Cameo Enterprise Modeler or Magic Systems of Systems Architect (MSOSA) and sysML 1.6 or 1.7. This project represents a real-world Systems Engineering design challenge reinforcing Systems Engineering process, principles, and difficult selection of system architectural options.
#Key Aspects of Model:
• Product Line Engineering Implementation
oEngine Family Architecture: Develop variant models for commercial, military, and industrial turbine configurations sharing common architectural elements
o Feature Model Integration: Implement configurable parameters for thrust ratings, bypass ratios, and certification basis variations
o Commonality Exploitation: Maximize reuse of safety assessments, requirements, and verification artifacts across engine variants
• Basic Model and Process Aspects
o System Development Process: Implement the aircraft and systems development processes defined in ARP4754B, adapted for turbine engine applications
o Interface Definition: Establish system interfaces, environmental conditions, and operational scenarios using the same modeling patterns
o Requirements Allocation: Demonstrate top-down requirements flow from aircraft-level functions to engine subsystem requirements following ARP4754B methodology
o Model Organization: Structure SysML packages and diagrams according to Honeywell MBSE standards
o Review Artifacts: Prepare model review packages suitable for engineering design reviews
o Behavioral model utilizes all available diagram types (State Machine, Activity, Sequency)
o Basic safety/hazard identification with links to functions and requirements
This project is to develop a comprehensive SysML model of turbine engines aligned with ARP4754B development processes (create a reference model like the ARP4754B Wheel Brake System Example in Appendix E). The model will integrate product line engineering principles for a generic turbine which could include options of afterburner, nacelle, and accessories. The model would have a deep structural/logical architectural and top-level functional decomposition. The model would incorporate executable behavioral modeling (simulation) to support requirements validation and airworthiness compliance. Given the time frame, the executable model would focus on at least one functional and logical subsystem. The model would be developed using Cameo Enterprise Modeler or Magic Systems of Systems Architect (MSOSA) and sysML 1.6 or 1.7. This project represents a real-world Systems Engineering design challenge reinforcing Systems Engineering process, principles, and difficult selection of system architectural options.
#Key Aspects of Model:
• Product Line Engineering Implementation
oEngine Family Architecture: Develop variant models for commercial, military, and industrial turbine configurations sharing common architectural elements
o Feature Model Integration: Implement configurable parameters for thrust ratings, bypass ratios, and certification basis variations
o Commonality Exploitation: Maximize reuse of safety assessments, requirements, and verification artifacts across engine variants
• Basic Model and Process Aspects
o System Development Process: Implement the aircraft and systems development processes defined in ARP4754B, adapted for turbine engine applications
o Interface Definition: Establish system interfaces, environmental conditions, and operational scenarios using the same modeling patterns
o Requirements Allocation: Demonstrate top-down requirements flow from aircraft-level functions to engine subsystem requirements following ARP4754B methodology
o Model Organization: Structure SysML packages and diagrams according to Honeywell MBSE standards
o Review Artifacts: Prepare model review packages suitable for engineering design reviews
o Behavioral model utilizes all available diagram types (State Machine, Activity, Sequency)
o Basic safety/hazard identification with links to functions and requirements