November 11, 2015
Combating Uncertainty in the Workflow of Systems Engineering Projects
Presenter: Barry Papke
Life Without Systems Engineering - Is It an Option?
Presenter: Kelly DeFazio, Professional Engineer, Director of F-35 Production/Producibility Engineering
Abstract: Systems Engineering is still a baby. Born around the 1940’s by Bell laboratories, as a result of their need for the system of products and industry in communication. Other traditional forms of engineering design as a science have been around for centuries upon centuries, so why is systems engineering so important now? NASA quickly adopted this new approach to engineering. They saw the need for integrating a system of systems in order to get a man to the moon and back to earth safely. So is Systems Engineering a technical solution need or just a government born project created to spread commerce across a varied team of contractors? Often, program management cuts this function off after completing the program’s Systems Requirements Review (SRR) treating systems engineering budget as a source of discretionary funds. After all, “the requirements are complete – now - on to hardcore design”, so why not cut systems engineering budget? Hmmmmm, is Systems Engineering really a requirement?
SAFe with MBSE for System Engineers by Peter Luckey
Abstract: It is only within the last five years that the Scaled Agile Framework has accommodated Systems Engineering. A focus of the accommodation is on incorporating Model Based System Engineering (MBSE) into the Framework.
Systems Engineering Transformation Surrogate Pilot Experiments: Doing Everything in Models to Demonstrate the Art-of-the-Possible by Dr. Mark Blackburn
Abstract: This presentation provides an overview of the NAVAIR Systems Engineering Transformation (SET) Surrogate Pilot Experiments and discusses how these experiments provide implementation examples that align with the goals of the DoD Digital Engineering Strategy. It provides an overview to set the context of the SET Framework concept and Functional Areas. The experiments are demonstrating the “Art-of-the-Possible” by doing “Everything in Models,” to show we can, while operating in a collaborative environment using an
Hardware-Inclusive DevOps: Applying DevOps Principles and Practices to Cyber-Physical System Engineering
Presenter: Marguerite Bryan
Abstract: DevOps has become the rallying cry of organizations looking to improve time-to-market, quality and other strategic business outcomes. However, much like the Agile Manifesto itself, DevOps surfaced and was developed with a strong software-centric focus. Our more recent frontier is the scaling of DevOps practices to the engineering of large, complex cyber-physical systems composed of hardware, firmware, and software.
Welcome to SysML, the Language for MBSE!
Presenter: Paul White
Abstract: Would you like to learn about the Systems Modeling Language (SysML)? Each year, more systems engineers are advancing their careers by learning about SysML, Model-based Systems Engineering (MBSE), and modeling tools. In this presentation, we will provide an introduction to SysML, present some modeling tools and techniques, and discuss how you can use SysML to benefit your company and advance your career.
Application of MBSE in AGILE Development
Presenter: Jason Forth, NAVAIR
Abstract: NAVAIR’s latest program goal is to deploy, integrate, and sustain significant interoperable technology upgrades to increase the mission profile of the aircraft system in the coming years. The Northrop Grumman MBSE Agile Team has been establishing a system model for the as is product baseline, to be designed baseline, and the processes for each technical discipline with modeling approaches to transition into a digital technical baseline for the program. In the last two releases, the team has been developing modeling approach activity diagrams and style guide diagrams within the architecture modeling application, CAMEO Enterprise Architect®, to meet the Systems Engineering Modeling and Architecture Plan (SEMAP). The approach diagram provides each sprint team the “tasks, work products, and flow” to complete each type of modeling domain (e.g. behavioral) while the style guide diagrams are unique example diagrams with aligning requirements for each definition and usage of objects compliant with UAF and best practices from industry following Object-Oriented System Engineering Methodology (OOSEM). The team is also extending current NAVAIR profiles like classification of each element and view while developing new profiles for data rights and approval. Other MBSE efforts in the corporate portfolio will be able to leverage these style guides, approach diagrams, and profiles to establish system modeling methods for applying system engineering models to streamline digital technical reviews, submit digital deliverables, and increase technical competencies integration into generating their modeling approaches within the broader system model.
Exposing and Controlling Emergent Behaviors in a System of Systems (SoS) Model
Presenter: Dr. Kristin Giammarco
Abstract: This presentation shows how to segment and extend a SysML activity model for emergent behavior analysis using Monterey Phoenix (MP). MP generates sets of behavior scenarios that are exhaustive up to a user-defined scope (number of iterations). After summarizing relevant definitions, we present, discuss and analyze examples of emergent behaviors found in the extended model, some of which contradict stakeholder intent and inspire consideration of SoS-wide consequences if they were to occur in reality. We also show how emergent behaviors may be classified as weak, strong, positive or negative. We conclude with some key takeaways and lessons learned for repeating these types of discoveries in other SoS models.