This event is free and open to all – including non-members
Model-Based Systems Engineering: A Practical Approach
Date: Wednesday, September 25th 2019. 5:30-7pm (presentation starts at 6pm).
Location: Filippi’s Restaurant in Kearny Mesa, 5353 Kearny Villa Rd, San Diego, CA 92123 (Google Maps)
Optional buffet: The option buffet dinner starts at 5:30pm, presentation starts at 6pm. Cost for the optional buffet is $10 members/$15 non-members. The buffet includes pizza, spaghetti, salad, bread, and soft drinks
This event will be webcast.
Access Code: 859-043-445
New to GoToMeeting? Get the app now and be ready when your first meeting starts:
Model-based system engineering is a methodology that focuses on creating and exploiting domain models as the primary means of information exchange between engineers, rather than relying on document based information exchange. In fact, the audience for MBSE artifacts is not just engineers, but also organizational leadership and even the customer, which means systems engineers need to speak each target audience’s native language. In the push to expand implementation of MBSE methods, various tools have been introduced to create the associated artifacts, but to date, no single product offers a comprehensive solution that meets the communication, coordination, and collaboration needs of every target audience. Just as one model does not fit all, one tool does not model all. In this presentation, you will learn how to establish an end-to-end modeling approach that creates views appropriate for each of your audiences.
Charley Patton, CSEP, is a systems engineering lead for Northrop Grumman, which he joined in 2004. He has a B.S. in Electrical Engineering and Computer Science from the University of Colorado, Boulder, an M.S. in Business Management from SDSU, and several certificates, including a Systems Engineering certificate from UCSD and a Model-Based Systems Engineering certificate from Caltech. Charley transitioned from software engineering to systems engineering the old-fashioned way – his boss directed him to derive the system requirements because he was the most experienced member of the project team. From this first excursion into systems engineering, he learned increasingly disciplined methods for determining and documenting requirements and architectures; planned and executed system test and deployment activities; eventually joined the ranks of functional management leading a group of mostly software, integration, and test engineers; and even managed a hardware development team for a year. Today he splits his time performing systems engineering lead functions, responding to proposals, executing technical systems engineering tasks, and trying to get his dachshund to understand the value of properly documented CONOPS.
49 signed up so far.