Full Menu and site Navigation

Program meetings typically 2nd Tuesday of month
Time: 6:00-7:00 CST
Food & networking at 5:30

Physical Locations

*Bell Helicopter
*L-3- Arlington
*L-3- Greenville
*Lockheed Martin Aero- Fort Worth
*Lockheed Martin MFC- Grand Prairie
*Raytheon- McKinney

Check out presentations from previous North Texas INCOSE Chapter Meetings!

Presentations can be found here

Board meetings typically 1st Tuesday of month
Time: 5:30-6:00 CST

Chapter Event Calendar

Remote Program Access
Teams (Video/Audio) - Click here to join the meeting. 
Contact INCOSE North Texas Chapter  ntxinfo @ incose dot net to be added to our meeting emails.
The meetings are not recorded. Presentation are posted in the library and resources during the following weekend if we receive the presentation.

Upcoming Chapter Events

Chapter Meeting April 13

Digital Engineering (DE): The Next Chapter of MBSE by Paul White

Remote Program Access: Teams (Video/Audio)
Join on your computer or mobile app


What is digital engineering (DE)? How does DE relate to MBSE? In this presentation, we will show how DE is the next chapter of MBSE. We will talk about the Office of the Secretary Defense’s (OSD) Digital Engineering Strategy, released in June 2018. We will discuss the goals of the DES and how you can implement DE in your current and future systems engineering efforts. This presentation is for those who would like an introduction to DE.  


Paul White is the ICBM GBSD Digital Engineering Branch Lead for BAE Systems at Hill Air Force Base, Utah. He has worked previously at Kihomac, Astronautics Corporation of America, L-3 Harris, and Raytheon. He has 20 years of experience in the aerospace industry.

Paul has been an INCOSE member since 2007 serving in various top leadership roles in the North Texas (Dallas - Fort Worth) Chapter, Chicagoland Chapter, and Wasatch (Utah) Chapter.  He is the current president of the Wasatch Chapter.  Paul has been a leader in the annual Great Lakes Regional Conference (GLRC) since 2012 including conference chair for the 6th and 8th conferences.  He served as the conference chair for the first annual Western States Regional Conference (WSRC) in Ogden in 2018; and he serves on the WSRC Steering Committee for 2019 and beyond. He was awarded the INCOSE Outstanding Service Award in 2019. He serves as the Deputy Assistant Director of Technical Events in INCOSE's Technical Operations organization.

He has a graduate certificate in Systems Engineering and Architecting from the Stevens Institute of Technology, a Master of Science degree in Computer Science from Texas A&M University-Commerce, and a Bachelor of Science degree in Computer Science from Texas A&M University.  He is a Certified Systems Engineering Professional (CSEP) through INCOSE. 


Chapter Meeting March 9

Using Architecture and MBSE to Develop Validated Requirements by Dr. Ron Carson

Remote Program Access: Teams (Video/Audio)
Join on your computer or mobile app

Abstract:  Requirements incompleteness and ambiguity continue to plaque many organizations.  The introduction of MBSE provides an opportunity to relate the structure of the architecture model to the structure of requirements, and synchronize the data between them.
In this presentation we demonstrate how to use model-based systems engineering and the related architecture to develop and validate requirements of all types. We first describe the structure of different types of requirements and map the requirements elements, e.g., function, to elements of the architecture in the MBSE model. We show how these requirements elements map to specific data elements in a particular MBSE tool for all possible types of requirements. Finally, we show how this method enables validation of the requirements from the architecture.
Attendees will gain an understanding of how to integrate their organizational requirements development and MBSE architecture activities by mapping the data elements between them and integrating these into their MBSE tools.  

:  Dr. Ron Carson is an Adjunct Professor of Engineering at Seattle Pacific University, an Affiliate Assistant Professor in Industrial and Systems Engineering at the University of Washington, a Fellow of the International Council on Systems Engineering and a certified Expert Systems Engineering Professional. 
He retired in 2015 as a Technical Fellow in Systems Engineering after 27 years at The Boeing Company. He is the author of numerous articles regarding requirements analysis and systems engineering measurement. He has been issued six US patents in satellite communications, and two patents regarding “Structured Requirements Generation and Assessment”.


Chapter Meeting February 9

Innovation and national security by Dr. Tina P. Srivastava

Remote Program Access: Teams (Video/Audio)
Join on your computer or mobile app

Abstract: Dr. Srivastava will discuss innovation and national security, focusing on two key challenges: participation and secrecy. The participation challenge is about providing adequate incentives to potential innovators, and we will discuss challenges to incentivizing participants and how to overcome them. We will discuss IP policies, innovation contests, and incentivizing employees within a company, so business leaders can learn how to incentivize their own employees, and also how they can open up the innovation process to enable broader diversity in innovation by applying open innovation strategies to overcome technology hurdles. The secrecy challenge is about technology innovation for national security where secrecy can be an obstacle. Dr. Srivastava is passionate about technology innovation and in particular, how we can harness it to further national security and competitiveness -- for example, targeted innovation to land an astronaut on the moon, or develop stealth machinery for cyber defense. But secrecy in classified environments sometimes makes it hard to recruit and innovate. We will discuss how to navigate various contracting and legal channels. We will also discuss government programs and policies related to technology innovation and government contracting.

:  Dr. Tina P. Srivastava has served on INCOSE’s Board of Directors and received the INCOSE Inaugural David Wright Leadership Award in 2014 for technical and interpersonal competencies in the practice of system engineering as a means for solving the great challenges of our planet. She is a lecturer at MIT in the areas of aerodynamics, aviation, complex systems, and technology road mapping and selection. She is also the author of Innovating in a Secret World, featured by MIT. Dr. Srivastava co-chairs the PM-SE Integration Working Group and is one of the authors and editors of the book Integrating Program Management and Systems Engineering. As an innovator, entrepreneur, and technology expert, Tina’s experience spans roles as Chief Engineer of electronic warfare programs at Raytheon to cofounder of a venture-backed security startup. She is an FAA-certified pilot and instructor of MIT’s Pilot Ground School course. Dr. Srivastava earned her PhD in Strategy, Innovation, and Engineering, a Masters in System Design and Management, and a Bachelors in Aeronautics and Astronautics, all from MIT.


Chapter Meeting January 12

North Texas 2021 by Justin C' de Baca

Location: Virtual (see chapter newsletter and top of this page for connection information)

Abstract: I will be using this meeting to cover a number of things for the 2021 year. Material will include:

  • Promotion of INCOSE IW2021
  • Impact of INCOSE 2020 report
  • INCOSE NTX's Road to Gold Status in 2021
  • Overview of TEAMS for members
We are hoping to get this year off to a great start, and this meeting will be a great place to discuss where we are heading and take any questions from our members.

Bio: Justin is our chapter president this year.


All Events

Interview with Stephen Guine, CSEP

Courtney Wright

Sep 08, 2021

SEP Interview 17 - Stephen Guine photoThe following questions are from an interview in 2014:

Q1: Describe your current position/role.

Stephen is a Systems Engineering Integrated Product Team (IPT) Manager for the B2 platform and a functional manager for B2 Systems Engineers in Palmdale, CA. He has been doing this work for about eight years and is currently adding new capabilities to the platform while ensuring backward compatibility. He is in charge of a team of about 30 engineers.

Q2: What are one or two of your proudest professional accomplishments?

As a Systems Engineer and Analyst with the Metropolitan Water District of Southern California, Stephen developed a model of systems operation, power operation, and taxation relationships. This involved metrics and modeling, detailed understanding of the phenomenology to include fluid dynamics, and understanding of environmental and budgetary constraints across the entire life cycle. This model showed a Systems Engineering approach to understand and provide solutions to a very complex and interrelated problem. Another project Stephen is proud of is providing education/training to new engineers at Northrup Grumman Corporation (NGC) with processes and tools that provide background and insight into the program. This approach ensures that an evolving workforce can be assured for future program success.

Q3: What is the biggest challenge you face as a Systems Engineer?

Stephen is challenged by the product and the environment which acutely affect the role of the Systems Engineer. Engineers at the lowest levels do not appreciate system level implications of development and how it affects other subsystems. On the business side of the house, quality Systems Engineering is not always an integral part of every program as it is not usually appreciated as value added. On the customer side, there is a similar issue of implementation.

Q4: What advice do you have for individuals starting their career as a Systems Engineer?

Steven advises to have respect for all disciplines involved in the development cycle of a system while appreciating that Systems Engineering provides a very valuable input to the system design. Systems Engineering needs to be viewed as an evolving practice that grows with experience, tool development, and new processes. Systems are becoming more and more interrelated as systems of systems leading to infinite complexity which requires a very disciplined approach. One needs to understand that this discipline is a moving target.

Q5: How do you continue to learn about SE? What professional development activities do you do?

Stephen continues to learn by involvement with associations. Being the vice president of the INCOSE LA Chapter provides him with opportunities to meet other engineers from many industries and exchange ideas. Teaching the practice of Systems Engineering forces him to look at problems in a variety of different ways and learn from others. Getting involved in areas outside of his primary role in the aerospace industry allows Stephen to learn from other field applications and challenges. Stephen reads several Systems Engineering papers a year from publications such as INSIGHT and conference publications to stay abreast of recent developments.

Q6: What are the next career goals you want to achieve?

One of Stephen’s goals is to move upward in the organization to a Systems Engineer leader and on to multi-program roles. Stephen would also like to be able to promote Systems Engineering research and participate in panels that discuss various aspects of Systems Engineering and design.

Q7: What are some of your hobbies/interests outside of work?

Stephen enjoys finish carpentry of furniture to blend the use of tools, planning of the design, and implement the process with artistic insights and ergonomic use.

Q8:  Are there any other final comments you would like to make?

The joy received from Stephen’s involvement in Systems Engineering is in the hard work and the rewards of a successful program where one can point and say that the process really led to the success.

In 2021, we reached out to Mr. Guine to answer more questions:

Q9: Why did you decide to get the SEP certification?

I got the certification for a couple of different reasons. First off, while I generally don’t believe in the value of a certification certificate, I deeply believe in the value of the knowledge that you are forced to gain or reacquaint yourself with to get a certification. In my case, I was transitioning into a new company, into a new industry. And although I had done systems engineering for quite a while, because I was coming from a different domain, I felt that certification would be a stamp of “approval” and give me a greater amount of “street cred” in my new organization and not having to spend so much time re-proving my bona fides. Additionally, I knew that some of the systems engineering knowledge that I had was kind of stale. I saw getting certification as a useful approach to relearning, refreshing, reacquainting myself with that core knowledge, not only for my long-term benefit, but also for my immediate benefit in a new organization by being able to show that not only did I understand systems engineering in practice, but I also understood it in theory and I understood how to apply that theory to the practice.

Q10: How does the SEP certification impact your professional career?

The SEP is a hell of a calling card. When I meet new people from new organizations, whom I may not have worked with or I’ve worked with lightly, having a SEP is my entree into other system engineering environments and conversations. Additionally, for situations where it is necessary to regress the conversation to discussing the fundamentals of the practice of systems engineering and then extrapolating to how we might best implement it for the system at hand, having that SEP lends credence to my words, especially if someone is not familiar with my previous work.

Q11: What has surprised you in the past five years related to systems engineering?

I would say that the rise of easy-to-build software or low-cost software has unduly influenced some into thinking that robust systems engineering may not be necessary, because the cost of implementing and iterating through multiple software builds of a system – let’s just say an app – is relatively low. And this has tricked some individuals and organizations into thinking: “Well, let’s just go.” Very similar to the old practice of “just start coding” and we’ll see where we go. I think that many organizations, especially, with the rise of cybercrime have realized or have started to realize that in a modern cyber physical world, having an incredibly strong understanding of the system under design, the environment into which it will be deployed, the varied and myriad of user’s needs – especially, when we’re talking commercial systems – and the nearly endless number of malicious actors, actually highlights the need and the value of strong systems engineering. I feel that, maybe, we’re starting to turn the corner on that.

Q12: What job titles have you had other than “Systems Engineer?”

Integrated Functional Capability Manager, Incremental Verification Engineer, Mission Engineer, System Architect, Model Based Systems Engineer. But probably, the one that I think I appreciate most is, he’s the guy who gets problems solved.