Fachbereich Wirtschaftsinformatik (WI): Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
Types of Artefacts being gathered: | Types of Artefacts being gathered: | ||
1. Algorithm: Systematic procedure for solving a problem, often in pseudo-code or | 1. ' ' 'Algorithm' ' ': Systematic procedure for solving a problem, often in pseudo-code or | ||
mathematical notation, step-by-step instructions. | mathematical notation, step-by-step instructions. <br /> | ||
2. Method: Structured process for solving a specific problem, clear organization of | 2. Method: Structured process for solving a specific problem, clear organization of | ||
phases and their purpose; often contains techniques or algorithms. | phases and their purpose; often contains techniques or algorithms. | ||
Latest revision as of 14:49, 30 June 2026
BPM - International Conference on Business Process Management
Types of Artefacts being gathered:
1. ' ' 'Algorithm' ' ': Systematic procedure for solving a problem, often in pseudo-code or
mathematical notation, step-by-step instructions.
2. Method: Structured process for solving a specific problem, clear organization of
phases and their purpose; often contains techniques or algorithms.
3. Technique: A specific procedure for carrying out a particular task; detailed descriptions
of the implementation steps, but not complex enough to be considered
as a method.
4. Framework: Structured framework for solving a class of problems with specific methods,
described by components, their relationships and contexts of use.
5. Language: Formal notation systems for modeling or analyzing processes; syntax
and semantics, often illustrated by examples and diagrams.
6. Taxonomy: Systematically classifies and organizes elements of a specific area, hierarchical
structures, and categorization criteria.
7. Model: Theoretical or conceptual tool used to describe, analyze, or predict aspects,
the systematic representation of components, and relationships.
8. Design: Concept Theoretical foundations and structures of a system or product; conceptual
models and their discussion.
9. Report: a general strategy or view of how to approach a problem: Interesting observations,
rules of thumb, innovative ideas, but not sufficiently general
or systematic to rise to the level of a descriptive model; usually includes
a discussion of the relevant litera
Schemas being used:
1. ACM Computing Classification
Schemas:
The following concepts can be only applied to other venues:
1. Research Problem
2. Research Question
3. Hypothesis
4. Data Collection
5. Data Analysis
6. Result
7. Threat to Validity
8. Research Object