TOPIC 1: Definition of emergent systems
Introduction: In general, when composing a complex system from subsystems (components), the overall characteristics of the resulting system cannot be derived only from summarising the characteristics of the components but occur also through interactions between them. This behaviour is broadly referred to as the concept of emergence. However, even within one discipline the concept of emergence is open to a variety of different interpretations and definitions. The goal of this seminar work is to clearly describe and compare various definitions of emergence (and emergent properties) in the context of information systems.
Goal and Objective: Overview and examples of different definitions of emergent systems in the context of information systems and comparison between them
TOPIC 2: Coordination in Multi-Agent Software Systems
Introduction: When building a software system from components which are themselves agents with their own objectives and interests, the interaction of these components can be very intricate: In order to achieve their own goals and to leverage their capabilities by joining forces, agents rely on coordinating their actions and even on negotiating with each other in case of conflicting interests.
The mechanism which enables coordination can be pre-defined by the system or emerge from more general rules of interaction, such that it appears as an emergent property of the system.
Goal and Objective: In this seminar, you will examine the concept of coordination in this context, understand existing approaches and put them into the context of emergent characteristics of a complex system.
TOPIC 3: Information extraction from source code
Introduction: In the area of computer science and software, development components are omnipresent. Thinking about (i) code dependent on third-party packages, (ii) systems composed of different components e.g. smart homes or cities, (iii) apps running on smartphones or computers in your network, or (iv) taking scenario three to the business world. It is not always the case that the information on what components do are disclosed to (potential) users of the components.
Goal and Objective: The objective of this seminar is to give an overview of techniques on how to extract information (and what kind of information) from source code.
TOPIC 4: Methodology of conducting and reporting a Case Study
Introduction: Case Studies are a popular explorative, qualitative research methodology. They are widely used to gain insights about contemporary phenomena in their natural contexts. In the context of computer science, the use of case studies was especially well studied in the field of software engineering.
Goal and Objective: Summarize and describe the methodology of conducting a case study and discuss in which cases it makes sense to conduct a case study in the context of computer science.
|Institute for Enterprise Systems||L15, firstname.lastname@example.org||Office Management|
|Schloss||68131 Mannheim||+49 621 181-3560|