Seminar FSS 2019

Course Information:

  • Course ID: CS 704
  • Credit Points:
    • B.Sc. Wirtschaftsinformatik: 5 ECTS
    • M.Sc: Wirtschaftsinformatik: 4 ECTS
    • MMDS: 4 ECTS

Schedule:

  • Sunday, January 27, 2019: Please register for the kick-off meeting by sending an ordered list of three preferred topics and a list of your completed courses (Transcript of Records, optionally CV) via mail to Nils Wilken (wilken@es.uni-mannheim.de)
  • Monday, January 28, 2019: As we can only offer a limited number of places, you will be informed whether you can participate in this seminar.
  • Wednesday, February 20, 2019: Latest possible drop-out date without a penalty (A drop-out after this date will be graded with 5.0)
  • Wednesday, February 20, 2019: Milestone 1 – Kick-Off Meeting
  • Sunday, May 5, 2019: Milestone 2 – Seminar paper draft submission
  • Sunday, May 12, 2019: Milestone 3 – Submission of reviews
  • Sunday, May 26, 2019: Milestone 4 – Submission of final seminar paper
  • Monday, May 27 – Wednesday, May 29, 2019: Milestone 5 – Presentation of your final seminar paper

Important notes:

  • Missing a milestone will result in a final grade of 5.0
  • This seminar is open for Bachelor and Master Students focusing on “Business Informatics” and “Data Science”. Master’s students enrolled in the “Mannheim Master in Data Science” are also highly welcome to apply for this seminar.
  • Only Master Students enrolled in the program “Business Informatics”: This seminar will be held as Module “CS 704” and is thus only applicable for the Specialization Tracks “Information Technology”, “System Design and Development” and “Data and Web Science”.

Suggested Topics:

TOPIC 1: Definition of emergent systems (Supervision: Kristian Kolthoff)

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

Starting Papers:

  • Emergent Properties in Software Systems, Gerhard Chroust, 2002
  • On the Emergence of Properties in Component-Based Systems J.L. Fiadeiro, 1996
  • What’s Emergent in Emergent Computing?, Brunner, K., 200

TOPIC 2: Coordination in Multi-Agent Software Systems (Supervision: Michael Pernpeintner)

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.

Starting Papers:

  • H.S. Nwana, L. Lee and N.R. Jennings: Co-ordination in software agent systems, in BT Technology Journal, Vol. 14 No. 4, 1996.
  • S. Ossowski: Coordination in Multi-Agent Systems: Towards a Technology of Agreement, in MATES 2008, LNAI 5244, pp. 2–12, 2008.

TOPIC 3: Information extraction from source code (Supervision: Christian Schindler)

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.

Starting Papers:

  • Börger, Egon. “The abstract state machines method for high-level system design and analysis.” Formal Methods: State of the Art and New Directions. Springer, London, 2010. 79-116.
  • Tonella, Paolo. “Reverse engineering of object oriented code.” Software Engineering, 2005. ICSE 2005. Proceedings. 27th International Conference on. IEEE, 2005.
  • Corbett, James C., et al. “Bandera: Extracting finite-state models from Java source code.” Software Engineering, 2000. Proceedings of the 2000 International Conference on. IEEE, 2000

TOPIC 4: Methodology of conducting and reporting a Case Study (Supervision: Nils Wilken)

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.

Starting Papers:

  • Darke, P., Shanks, G., & Broadbent, M. (1998). Successfully completing case study research: combining rigour, relevance and pragmatism. Information systems journal, 8(4), 273-289.
  • Runeson, P., & Höst, M. (2009). Guidelines for conducting and reporting case study research in software engineering. Empirical software engineering, 14(2), 131.

Nach oben

PostanschriftBesucheradresse  EmailTelefonnummer
Institute for Enterprise Systems  L15, 1-6office-ines@uni-mannheim.de  Office Management
Schloss68131 Mannheim +49 621 181-3560
68131 MannheimGermany
Germany