States and Modes with Charles Wasson
Ғылым және технология
Vitech is pleased to welcome special guest Charles Wasson, author, instructor, and consultant, as he explores the finer aspect of States and Modes in Systems Engineering.
System Phases, Modes, and States are often one of the most controversial concepts in System Engineering due to a lack of definition and implementation standards. In fact, Modes & States are addressed AFTER the design is completed when User Manuals are being developed. The reality is: Modes & States serve as a key analytical framework early in System Development, especially in Conceptual Design.
Four issues contribute to the challenges of implementing System Phases, Modes, and States:
• Issue #1 - What is the difference between a "mode" and a "state."
• Issue #2 - Do "modes" contain "states" or do "states" contain "modes"?
• Issue #3 - Should specifications specify "modes and states"?
• Issue #4 - Should specifications flow down "modes and states" as explicit requirements?
This webinar presents a Statement of the Problem, identifies sources of the problem, proposes clarifying definitions, and provides illustrative examples of "modes" and "states". Building on the foundational definitions, the presentation explores the entity relationships (ERs) between System Phases, Modes, and States. Then, illustrates how Modes & States serve as linking mechanisms between System or Entity specification requirements and the conceptual design to Command & Control (C2) sets of a System Architecture’s capabilities to produce the specified performance-based outcomes.
Based on solutions to Issues #1 and #2 that fuel the controversy, this webinar addresses the final two issues - i.e., Issues #3 and #4 - concerning specifying and flowing down "modes and states" in specifications. We conclude with a summary of recommendations concerning the four issues and provide suggestions for effective SE leadership to properly apply and implement System Phases, Modes, and States.
Пікірлер: 4
At 14 minutes or so in this presentation - the speaker has developed what I believe to be a VERY sound definition of Modes. I love it.
Valuable information - looking forward to your 2015 textbook! Cheers!
Thank You. I really appreciate that you are moving to standardize the way that State and Modes are defined in a system; there is so much time wasted arguing over what the difference is. Referencing Slide 1-64: Avoiding the development of States and Modes centric specification is NOT a good idea from a systems perspective. Orchestration of States and Modes is necessary if you want the outcome of the operation of a system to be deterministic. Yes, planning States and Modes may limit your architecture choices. When you are creating a system specification you are providing the basis and definition for an architecture of a system; limiting your possible design outcome. But avoiding these requirements could lead to an outcome that the user did not want.
For the definition skip to 20:40 you're welcome