![Project Manager Questions about Systems Engineering ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Systems Engineering Architecture and Modeling Presentation
Ähnlich wie Systems Engineering Architecture and Modeling Presentation (20)
Mehr von NASAPMC
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Systems Engineering Architecture and Modeling Presentation
- 1. Systems Engineering, Architecting and Model Based SE Challenges and Opportunities Presentation to PM Challenge February 22, 2012 Brian Muirhead Chief Engineer Jet Propulsion Laboratory , California Institute of Technology © 2012 California Institute of Technology. Government sponsorship acknowledged.
- 10. Modeling Landscape Level 1 (program) Level 2 (project) Level 3 (system) Level 4 (subsystem) Level 5 (component) Architecture Science EEIS Payload Ground System Flight System S/S V&V CAD Cabling Flight S/W SMAP Component V&V System V&V S/S Models SE margins & analysis … … … Electrical SE Model-centric engineering integrates models at multiple levels Operations
- 18. Requirements Subsystem Design Electrical System Design Electrical Interface Procedures Electrical Measurements Test results and Documentation Traceability report and ECR impact generation Cabling Design Potential Manual Entry Error Points 11/11/2011 Independent DB Independent DB Independent DB Independent DB Independent DB Independent DB Independent DB Independent DB
- 19. Requirements Subsystem Design Electrical Measurements Test results and Documentations Traceability report and ECR impact generation Electrical Interface Procedures Cabling Design Electrical System Design 11/11/2011 MBSE Pilot on SMAP UNIFIED Data Repository
- 21. Conceptual
- 23. Notional Model of V&V test environment Diagram is notional – proper ontology patterns are not implemented Acts as an inventory diagram for the V&V parts list and functional purposes of GSE
- 24. Integration and Test Models Mechanical View Data Flow View Each I&T test can be viewed through multiple filters to enable a full understanding of the test configuration Diagram is notional – proper ontology patterns are not implemented
- 25. Requirement Verification and TAYF Exceptions I&T tests can be traced to requirement verification, as well as any test-as-you-fly exceptions. Diagram is notional – proper ontology patterns are not implemented
Hinweis der Redaktion
- Just one slide on AFT… extending improving the RMA and CDF, more up front thinkin gabout “why”… our quick solution to avoid SysML learning c urve…. 4X stakeholder radiation risk concern and success criteria energetic radiation view, point to in work driving scenarios RELM Viewpoint
- This slide has one step of animation. The first image shows how a system model serves as the integration component for system analysis, design, implementation, and verification. Click: now you see the names and topics of the five presentations: Alex Jimenez talking about Cable Harness Systems, etc, etc.
- Talk about in terms of ‘this is the first time doing this top down, and in early formulation these are the things we find valuable (put this comment way up in the outline)
- Provides an overview, or “road map” for where we want to be...not just for this quarter but overall roadmap.
- Together with previous slide, this slide will show the proposed process flow and how a unified data repository is what we want to achieve such that the various “stages” of this process can be addressed.
- Key point: Comparison of existing Level 1 Electrical Function Block Diagram with a model of this view, which is constructed in MD/SysML framework. One of our first assignments was to capture a “Level 1” electrical function block diagram as shown. However, it quickly became apparent in the modeling exercise that this was more difficult of a task because the existing block diagram was not very clear with respect to the type of interfaces, their connections, and being consistent showing what constitutes a “Level 1 Electrical System Functional Block Diagram”. To complete this assignment it was necessary to define what is a Level 1 Functional Block diagram, and this lead to our definition of a “Subsystem View” of the the electrical system architecture. The purpose of this view is to specify electrical signal types that are transmitted between subsystems.
- Key point: Comparison of existing Level 1 Electrical Function Block Diagram with a model of this view, which is constructed in MD/SysML framework. One of our first assignments was to capture a “Level 1” electrical function block diagram as shown. However, it quickly became apparent in the modeling exercise that this was more difficult of a task because the existing block diagram was not very clear with respect to the type of interfaces, their connections, and being consistent showing what constitutes a “Level 1 Electrical System Functional Block Diagram”. To complete this assignment it was necessary to define what is a Level 1 Functional Block diagram, and this lead to our definition of a “Subsystem View” of the the electrical system architecture. The purpose of this view is to specify electrical signal types that are transmitted between subsystems.