A Wargame-Augmented Knowledge Elicitation Method for the Agile Development of Novel Systems

Abstract

There are inherent difficulties in designing an effective Human–Machine Interface (HMI) for a first-of-its-kind system. Many leading cognitive research methods rely upon experts with prior experiences using the system and/or some type of existing mockups or working prototype of the HMI, and neither of these resources are available for such a new system. Further, these methods are time consuming and incompatible with more rapid and iterative systems development models (e.g., Agile/Scrum). To address these challenges, we developed a Wargame-Augmented Knowledge Elicitation (WAKE) method to identify information requirements and underlying assumptions in operator decision making concurrently with operational concepts. The developed WAKE method incorporates naturalistic observations of operator decision making in a wargaming scenario with freeze-probe queries and structured analytic techniques to identify and prioritize information requirements for a novel HMI. An overview of the method, required apparatus, and associated analytical techniques is provided. Outcomes, lessons learned, and topics for future research resulting from two different applications of the WAKE method are also discussed.

Where the Cognitive Engineering Rubber Meets the Systems Development Road

“…For one program we used wargaming to concurrently elicit requirements and design seeds for a first-of-its-kind intelligent system and design the workflow for employment of the system (Dorton et al, 2020). A challenge for this particular program was that there was no existing user community, creating an impasse for various approaches reliant on existing users and their experiences.…”

“…program managers, software engineers, and data scientists). Further, trends in more iterative, rough, and rapid, SD methods like Agile/Scrum can add time pressure for CE practitioners to translate their findings to actionable SD inputs (Dorton et al, 2020).…”

A Qualitative Study on Non-Functional Requirements in Agile Software Development

“…The most common practices such as interviews [46], user stories [47], observations [48], workshops [49] are frequently embedded in iteration-based agile methods. Moreover, the course toward promoting active user participation and involvement has been frequently documented in recent reports and reviews that discuss agile requirements engineering [47], [49], [50].…”

A Case for User-Centered Design in Satellite Command and Control

“…Design thinking is espoused for its ability to solve relatively intractable, or "wicked" problems, where a high degree of component interdependency precludes a more linear engineering approach [13]. Recent efforts have shown success in fusing more rough and rapid design thinking methods with methodologically rigorous HFE methods for agile development of DoD systems [14]. As such, we employed a UCD approach that leveraged a blend of both HFE and design thinking methods and best practices.…”