Zoom Logo

Systems Thinking: A Foundation for Product Development (Dr. Hefner, Caltech) - Shared screen with speaker view
Steve Cash
01:33:50
Thinking in terms interactions and relationships
Vinarcik | INCOSE Treasurer
01:33:50
Systems thinking is considering elements, interactions, and context when framing, considering, and solving a problem.
MAG
01:33:51
Holistic view of the system considering it’s overall footprint within its environment
Dennis Tuckowski
01:33:51
systematic and whoalistic approach to understanding complex interactions
Sean Mahrt
01:33:52
Needs verses design
Warren Porter
01:33:52
taking account of all aspects
Ben Taggart
01:33:52
Thinking of all the parts of the system and the needs of everyone and everything that interacts with it
Amy Peterson
01:33:52
Requirements Analysis and Management
Mike Meakin
01:33:52
The ability to analyze a set of connected components based on their interactions
Ronald Heller
01:33:52
Looking at the BIG picture
Nathan Vinarcik
01:33:52
The ability to see the evolution of a product and the processes needed to create said product.
tm128989
01:33:52
its not systems engineering
Obi Odenigbo
01:33:52
wholistic, eagle view, high level thinking
Bob and Leslie Noel
01:33:52
Considering all perspectives and viewpoints
Rick Dombrowski
01:33:52
multi-discipline, interface focused....
Terry Fitzgerald
01:33:53
To anticipate emergence behavior and knock on effects
Steve Morrisson
01:33:54
Wholistic view of how the system interfaces with users.
V - Ray Barton
01:33:55
end-to-end thinking and view of process
Raghavendra Naik
01:33:56
It is the logical processing of a System to process the inputs and handle the task
Joe Bigelow
01:33:56
holistic approach
19 Steve Perich
01:33:56
Systems Thinking is a broad, comprehensive way of looking at the problem and the possible solutions.
Raghavendra Keshavamurthy
01:33:56
System thinking for me is overall architecture
Stephen Lamb
01:33:57
The process of considering relationships, functions in a system or system of systems
Mk Malast
01:33:59
A systems approach by design
Dan Menoher
01:33:59
The ability to consider the multiple perspectives of a systems
Alex Babut
01:33:59
Broad, multidisciplinary, full-lifecycle approach to building a system
Glenn Thibodeau
01:34:00
focus on the whole and environmentti nteraction
James Leege
01:34:06
Looking at the system as a whole and its context for requirements and behavior.
Dave Hanson
01:34:10
A holistic approach to turning customer needs into functionality
Mark Payton
01:34:15
A holistic approach to consider interfaces between system components
Paige
01:34:25
big picture but keeping focusing on internal and external interfaces
Vinarcik | INCOSE Treasurer
01:37:57
Not a great customer satisfier!
tm128989
01:51:40
how is this different from synthesis or integration?
Bob and Leslie Noel
01:52:15
This is system decomposition - so we can create components to integrate later
Raghavendra Naik
01:52:49
Do we need to consider Integration requirements in order to make sure all the subsytems are implemented per the standard earlier defined and agreed upon?
Steve Morrisson
02:00:56
Many different parts interacting.
Raghavendra Naik
02:00:58
number of systems interacting with each other
Casey
02:01:01
lots of dependencies and interfaces
Raghavendra Keshavamurthy
02:01:02
they are not organized.
Ben Taggart
02:01:02
Lots of parts that can affect one another
Michael Casper
02:01:02
many interfaces
James Leege
02:01:02
Lots of features, behaviors and interfaces.
Bob and Leslie Noel
02:01:03
Complex systems require analysis to understand
Mark Payton
02:01:03
Unpredictable interaction between the parts
Glenn Thibodeau
02:01:03
elements and connections
Sean Mahrt
02:01:03
interactions between systems/subsystems
19 Steve Perich
02:01:03
Lots of moving parts!
Mike Meakin
02:01:03
Complexity is a function of the number of interfaces and the number of artefacts exchanged across these interfaces
Rajith
02:01:03
Difficult to understand data flow / control flow
David Long-Wright Bros
02:01:04
Not knowing how a change will affect other subsystems
Chris
02:01:04
The number of elements and the interactions between them
Vinarcik | INCOSE Treasurer
02:01:04
Numerous interactions and emergent behavior.
Alex Babut
02:01:04
Many moving pieces and relationships between elements
V - Ray Barton
02:01:04
The number of components
Kristen Berger
02:01:05
Many different operations and users
Shadrak Rajkumar
02:01:05
Not able to get an output from one system makes a system complex
Terry Fitzgerald
02:01:06
Highly coupled elements
Mk Malast
02:01:06
a complex system has many interdependent parts
Stephen Lamb
02:01:06
It's dynamic and includes humans!
Steve Cash
02:01:06
Unable to predict performance
Jack Stein - Asst. Director, Americas
02:01:06
Interactions that can not be predicted
Nathan Vinarcik
02:01:11
Number of components, subsystems, and functions
Gurunandan Renjal
02:01:12
lot of interacting parts
Dave Hanson
02:01:25
many layers or pathways needing to be followed to get to final result
Mike Meakin
02:09:27
Being a good generalist is itself its own specialty :-)
Sean Mahrt
02:09:50
Jack-of-all-disciplines. :)
Terry Fitzgerald
02:12:31
'Swiss army knife' of Engineering
Terry Fitzgerald
02:16:39
Two layers up - a useful heuristic to scope the area of influence for a decision to consider
Sean Mahrt
02:17:07
Slow down today to speed up next week.
Casey
02:21:14
How do you better identify "real needs"? Or is it only important to address the expressed needs that the customer has become aware of?
Bob and Leslie Noel
02:21:57
Good idea to have a checklist of possible needs so a SE can interview customers and find them
Raghavendra Naik
02:22:17
In that case how do we really address the issue of Real Needs, since the needs had to change every stage
Bob and Leslie Noel
02:22:42
For example, does the system need to operate in various environments like cold temps
Sean Mahrt
02:22:50
Requirements validation is highly valuable (not verification)
Bob and Leslie Noel
02:23:07
Also known as eliciting needs
Bob and Leslie Noel
02:25:32
Ideally you can do the virtual certification before performing the physical one
Shadrak Rajkumar
02:26:29
Are there any common attributes for Systems Thinking approaches to Safety and Security?
Sean Mahrt
02:27:12
Safety/Security used to be part of the 'illities. I think the terms are shifting around
Rick Dombrowski
02:28:27
How do you see agile development processes such as scrum helping or hurting system thinking, system engineering? Any gaps with typical roles (product owners, scrum masters...) or activities (sprint planning, retrospectives...) that should be augmented to better support system thinking?
Casey
02:28:40
How do you see systems thinking, the V model, and particularly model based SE (which involves upfront definition of the problem/need) fitting into an Agile process?
Terry Fitzgerald
02:29:52
Question: You mentioned the heuristic of considering the influence of a design change to the system upto two layers up in the system hierarchy. In a coupled system how can you identify the relationships that matter rather than be trapped in an open ended analysis exercise.
Bob and Leslie Noel
02:31:44
Can 3D printing work for hardware agility?
Sharon Lienemann
02:39:43
thank you
Nathan Vinarcik
02:39:48
Than you.
Terry Fitzgerald
02:39:52
Thank you!
Ben Taggart
02:39:56
thank you sir
Alex Babut
02:40:01
thank you!
Gurunandan Renjal
02:40:02
Thank you Rick!
Casey
02:40:17
Great presentation, thank you!
Mk Malast
02:41:48
Thank you!