Samenvatting

Abstract: The Problem-Solution Chain (PSC) models proposed in this exploratory paper are conceived as describing chains of problem-solution links, thereby modelling specific multi-link ‘problem-solving’ paths, typically (but not exclusively) from a high-level business problem to lower-level functional solution components. The main elements are ‘Problems’ and ‘Solutions’. These may be selected from purpose-made, domain-specific collections of elements. Single ‘Problem-Solution links’ are comparable to compact, high-level descriptions of design patterns and can be directly related to design problem templates as used in Design Science. Coherent collections of such links would resemble boiled-down representations of pattern languages.
Instantiations of PSCs for specific situations aim to help conceptualise and discuss pre-architectural, high-level overviews, for example, of (options for) functionalities or applications representing ‘solutions’ for ‘solving’ some business need or capability ‘problem’. A useful metaphor is that PSCs help describe and discuss basic ingredients (related problems and solutions) for some specific situation, which can later (out of scope here) be developed into a recipe (e.g. an enterprise or process architecture and roadmap) and eventually into an actual dish (realisation of the architecture/solution). Thus, PSCs can, for example, be conceptualisations and conversation aids in the early stages of business-IT alignment efforts and system design. This explorative, practice-oriented paper presents our initial conceptualisation of PSCs. We also present a syntax and notation for problem-solution chains as specified for the Simplified Modelling Platform (SMP), and we briefly discuss the possibility of supporting PSC modelling with guided conversations for PSC modelling. We demonstrate and evaluate our proposed concepts by applying them in a single real case. Much work lies ahead.