Skip to main content
Fachgebiete
Automobil + Motoren Bauwesen + Immobilien Business IT + Informatik Elektrotechnik + Elektronik Energie + Nachhaltigkeit Finance + Banking Management + Führung Marketing + Vertrieb Maschinenbau + Werkstoffe Versicherung + Risiko
DE
EN
Bücher
Zeitschriften
Themenseiten
Organisationspsychologie Projektmanagement Marketing Smart Manufacturing
Weitere Formate
Podcasts Webinare Technik Webinare Wirtschaft Kongresse Veranstaltungskalender Awards
Jetzt Einzelzugang starten
Zugang für Unternehmen
Referenzkunden
SLX-Digitalkonferenz: Zukunftswerkstatt 2024

Mehr Umsatz mit Top-Kontakten

Am 7. Mai erfahren Sie, wie Vertriebsteams Leadgenerierung, Leadnurturing und Leadstrategien effizient steuern können.
Erweiterte Suche
Anmelden
nach oben
Erschienen in:
What Automated Planning Can Do for Business Process Management Kapitel lesen Erstes Kapitel lesen

2018 | OriginalPaper | Buchkapitel

A Pattern-Based Question Checklist for Deriving Requirements from BPMN Models

verfasst von : Bernhard M. Turban, Johannes Schmitz-Lenders

Erschienen in: Business Process Management Workshops

Verlag: Springer International Publishing

Einloggen

Aktivieren Sie unsere intelligente Suche, um passende Fachinhalte oder Patente zu finden.

search-config
loading …

Abstract

Concerning the realization of planned Business Processes through IT-Systems (IT Alignment), Requirement Elicitation is of central importance. One decisive factor for success is the experience knowledge of the Requirement Engineers, especially concerning the know how to ask the right questions for eliciting unknown requirements as early as possible in a project. This article presents an approach how this experience knowledge can be captured in a Pattern-based Question Checklist providing a structured set of questions to derive requirements from Business Processes modeled in BPMN. This captured knowledge can thus be provided to less experienced Requirement Engineers supporting them in their Requirement Elicitation activities.

Sie haben noch keine Lizenz? Dann Informieren Sie sich jetzt über unsere Produkte:

Springer Professional "Wirtschaft+Technik"

Online-Abonnement

Mit Springer Professional "Wirtschaft+Technik" erhalten Sie Zugriff auf:

  • über 102.000 Bücher
  • über 537 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Maschinenbau + Werkstoffe
  • Versicherung + Risiko

Jetzt Wissensvorsprung sichern!

Jetzt informieren

Springer Professional "Technik"

Online-Abonnement

Mit Springer Professional "Technik" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 390 Zeitschriften

aus folgenden Fachgebieten:

  • Automobil + Motoren
  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Elektrotechnik + Elektronik
  • Energie + Nachhaltigkeit
  • Maschinenbau + Werkstoffe




 

Jetzt Wissensvorsprung sichern!

Jetzt informieren

Springer Professional "Wirtschaft"

Online-Abonnement

Mit Springer Professional "Wirtschaft" erhalten Sie Zugriff auf:

  • über 67.000 Bücher
  • über 340 Zeitschriften

aus folgenden Fachgebieten:

  • Bauwesen + Immobilien
  • Business IT + Informatik
  • Finance + Banking
  • Management + Führung
  • Marketing + Vertrieb
  • Versicherung + Risiko




Jetzt Wissensvorsprung sichern!

Jetzt informieren
Vorheriges Kapitel Variability Patterns for Analyzing Flexible Processes
Nächstes Kapitel Minimal Effort Requirements Engineering for Robotic Process Automation with Test Driven Development and Screen Recording
Fußnoten
1
[14; Ch. I.6.2.4] provides a comprehensive description of the basic ideas behind the pattern approach and the diverse types of patterns, its effects, disadvantages and the connections to other design theories in computer science.
 
2
SE = Start Event, T = Task/Activity, IE = Intermediate Event, ICE = Intermediate Cancel Event, IEE = Intermediate Error Event, EE = End Event, DS = Data Store, P = Pool, L = Lane.
 
3
The example assumes that certain decisions concerning which IT-system is used for which task have already been made before and the BPMN diagram has been modeled accordingly. In the BPMN-standard, Pools are originally dedicated for expressing organizations. However, in the authors’ experience Pools can and are also used in practice to model the break-down of BPs to involved systems.
 
4
E.g., a GUI form (GUI = Graphical User Interface), or a part of a GUI form, or a GUI control, or something else (e.g. a steering gesture, voice command, …).
 
5
See also [3; p. 156f] where modeling the flow of GUI forms and BPMN is described.
 
6
As much as needed for the level of detail wanted for the intended purpose of the requirements specification; not every requirement specification needs to address the user interface, this might be done later in the process; this also applies to all other questions in the PQC.
 
7
This and the following questions address the requirements for the logical structure/the logical design of UI-E’s. The concrete UI design depends –in addition to the chosen level of detail– on concrete targeted technologies, e.g. web browser(s), desktop, mobile devices.
 
8
Here and concerning question block R2.Q4, overlaps to the questions of R1 do exist. In requirement analysis, it has proven successful to ask questions from different perspectives in order to elicit possibly still undiscovered aspects and requirements (cf. e.g. [13; p. 101f]).
 
9
Concerning Intermediate Events at the border of tasks consult the next chapter discussing Intermediate Error and Cancel Events.
 
10
It is assumed here that the technical system boundaries have already been determined. In general, areas of responsibility (pools) can also be used to split a planned larger system into logical subsystems. During implementation, each area can result in a technical system boundary, or not in case the logical subsystems are merged into a common technical system.
 
11
In Fig. 1, instead of the end-start-event-relationship EE9 → SE6 and the message flow T2 → T3, developers might come to the idea to model a direct sequence flow T2 → T3, because L1.2 and L2.1 denote the same user role. This would violate the BPMN standard, however. These situations are addressed by R5.Q1 and must be resolved as shown in Fig. 1.
 
Literatur
1.
Alexander, C., Ishikawa, S., Silverstein, M.: A Pattern Language: Towns, Buildings. Construction. Oxford University Press, New York (1977)
2.
Fowler, M.: Analysis Patterns: Reusable Object Models. Addison-Wesley, Reading (1997)
3.
Freund, J., Rücker, B.: Praxishandbuch BPMN. Hanser Verlag, München (2017)
4.
Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, Reading (1995)MATH
5.
Jacobson, I., Christerson, M., Jonsson, P., Övergaard, G.: Object Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, Wokingham (1992)MATH
6.
7.
8.
Moro, M.: Modellbasierte Qualitätsbewertung von Softwaresystemen. Books on Demand GmbH (2004)
9.
Ouyang, C., van der Aalst, W., Dumas, M., ter Hofstede, A.: From business process models to process-oriented software. In: ACM Transactions on Software Engineering and Methodology (TOSEM), vol. 19, no. 1, pp. 1–37. ACM, New York (2009)
10.
11.
Prechelt, L., Unger, B.: Methodik und Ergebnisse einer Experimentreihe über Entwurfsmuster. In: Informatik Spektrum, vol. 14, no. 3 (1999)
12.
Rohfleisch, F.: Geschäftsprozessorientierte Anforderungsanalyse – Business Analyse mit ARIS und UML. MV-Verlag, Münster (2011). Edition Octopus
13.
Rupp, C.: Sophist Group: Requirements-Engineering und Management, 6th edn. Hanser Verlag, München (2014)
14.
Turban, B.: Tool-Based Requirement Traceability between Requirement and Design Artifacts. Vieweg + Teubner Verlag, Wiesbaden (2013)CrossRef
15.
Withall, S.: Software Requirement Patterns. Microsoft Press, WA (2007)
16.
Maiden, N., Manning, S., Jones, S., Greenwood, J.: Generating requirements from systems models using patterns: a case study. Requirements Eng. 10(4), 276–288 (2005)CrossRef
17.
Laue, R., Koop, W., Gruhn, V.: Indicators for open issues in business process models. In: Requirements Engineering: Foundation for Software Quality (REFSQ), Gothenburg, Sweden (2016)
Metadaten
Titel
A Pattern-Based Question Checklist for Deriving Requirements from BPMN Models
verfasst von
Bernhard M. Turban
Johannes Schmitz-Lenders
Copyright-Jahr
2018
Buch
Business Process Management Workshops

Print ISBN: 978-3-319-74029-4

Electronic ISBN: 978-3-319-74030-0

Copyright-Jahr: 2018

DOI
https://doi.org/10.1007/978-3-319-74030-0_50

Premium Partner

    Bildnachweise