Skip to content

Kiel Master Project WS 17

madcau edited this page Sep 5, 2017 · 8 revisions

In this semester's master project, we address several tasks to improve the existing code base and create new features.

Below you find the description of the tasks and further links which might be helpful. For each task, we created a separate wiki page which you should use to document your efforts, describe the requirements, the design and implementation of your software. Especially, design decisions should be documented. In case you have to perform reverse engineering you also document the old design of the software. Please make use of the ticket system to document features which realize requirements or in case of bugs. We will meet on a weekly basis; the appointment is made at the beginning of the project. After the first weeks, the team will present their planned Project in a short proposal (~30 min for the whole project) At the end of the semester a presentation takes place where every team presents their work and describe their role in the team.

These (and other) topics may also be suitable for Bachelor and Master theses or the research project for the master's degree.

Preliminary Meeting

For a first get-together we meet at 25th of October in Cap4 room 1210 to discuss the details that await you in this project. If you want to participate in the project but can't attend the meeting, please send an E-Mail to [email protected] . The task assignments will be made in our second meeting.

General Approach

  • Install an appropriate IDE, e.g. Eclipse.
  • Have a look at all the technology which is related to your task. (use your favorite search engine)
    • If there are tutorials available use them to make you familiar with the technology.
    • Sometimes there exist vlog posts on youtube which explain how to use a specific technology.
  • Setup your Eclipse development environment (in case you are using it, otherwise you have to adjust the code formatting and implementation settings of your IDE). You find the necessary information here.
  • Collect your requirements. (We will discuss them in our weekly meetings)
  • Plan the schedule with milestones for the whole project. (We will discuss that in our weekly meetings)
  • Coordinate your schedule with your teammates, especially if there are dependencies.
  • Compile a short presentation as proposal for your project.
  • Come up with a design. (we will discuss that in our weekly meetings)
  • Testing is an important element of software development. Therefore, come up with a plan to implement testing (unit-testing, e.g., JUnit4 and integration testing).
  • Write user documentation.
  • Compile a presentation at the end of the master project.

Note: In case you have trouble setting up your IDE or accessing repositories, please consult Reiner or Marc by mail or visit them in their office.

Task Descriptions WS17/18