Structured problem exploration approach for the pre-concept stage of system development

At the pre-concept stage, an architect explores the problem space together with various stakeholders, including engineers, marketing, and future users of the system. This requires competencies and tactics to communicate efficiently while maintaining a system-level scope. We present a practical Structured Problem Exploration approach to assist architects in exploring the problem space. The approach aims to ensure that involved parties are talking on the same level. The approach includes a checklist to elicit information relevant to the system-level scope and activities to warrant convergence of the results. This paper starts with an overview of soft competencies, skills, and methods. After outlining the approach, we report our experiences with applying it to investigate energy improvement opportunities of a connected system. This paper aims to inform discussions on the importance of competencies and methods for the pre-concept exploration stage when creating SoS elements.

[1]  Jonas Löwgren,et al.  Methods & tools: design methodology and design practice , 1999, INTR.

[2]  Grady Booch Draw Me a Picture , 2011, IEEE Software.

[3]  Gerrit Muller,et al.  Systems Architecting: a Business Perspective , 2011 .

[4]  Roelof Hamberg,et al.  A Design Framework for Model-based Development of Complex Systems , 2012 .

[5]  Wen-Huei Chou,et al.  Emotional Experience and Interactive Design in the Workplace , 2013, HCI.

[6]  Philippe Kruchten,et al.  Architecture blueprints—the “4+1” view model of software architecture , 1995, TRI-Ada '95.

[7]  Gerrit Muller Validation of Systems Engineering Methods and Techniques in Industry , 2012, CSER.

[8]  Ian F. Alexander,et al.  A Taxonomy of Stakeholders: Human Roles in System Development , 2005, Int. J. Technol. Hum. Interact..

[9]  Philippe Krutchen,et al.  Architectural blueprints--the '4+1' view model of software architecture , 1995 .

[10]  Henry Muccini,et al.  The Road Ahead for Architectural Languages , 2015, IEEE Software.

[11]  Gersica A. Alencar,et al.  Non-Functional Requirements In Health Information Systems: , 2019, 2019 14th Iberian Conference on Information Systems and Technologies (CISTI).

[12]  Eelco Rommes,et al.  Why They Just Don't Get It: Communicating about Architecture with Business Stakeholders , 2016, IEEE Software.

[13]  Alexandr Vasenev Structuring of Methods to Estimate Benefits of Partial Networking , 2018, VEHITS.

[14]  Eltjo Poort Just Enough Anticipation: Architect Your Time Dimension , 2016, IEEE Software.

[15]  E. Rechtin,et al.  The art of systems architecting , 1996, IEEE Spectrum.

[16]  Raghuraman Krishnamurthy Breezing My Way as a Solution Architect: A Retrospective on Skill Development and Use , 2017, IEEE Software.