Fachbereich Wirtschaftsinformatik (WI): Difference between revisions
Created page with "Category:Fachbereiche" |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:Fachbereiche]] | [[Category:Fachbereiche]] | ||
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 | |||
Latest revision as of 13:11, 21 April 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