Project Practical 101


Enrollment for the next round of this project practical is scheduled for 14 January 2013, 5:15-6:30pm, Room B 127. If you are interested, please pre-register to be considered. The project practical maxes out at about 10 students. Currently, 4 students are working on this project practical. (Status: 21 December 2012)


If you have questions, get in touch with ed.znelbok-inu|gnaltfos#ed.znelbok-inu|gnaltfos.

Teaching stuff:

  • Ralf Lämmel
  • Andrei Varanovich

Curriculum context

This course corresponds to the module "Projektpraktikum" (project practical), part of the BSc INF/CV/WI/IM curriculum. Students are required to have moderate skills of programming and software engineering. See also the ongoing practinar for a related course format.


The project practical aims at a major push to bring up quality of code and documentation as well as infrastructural support in the 101companies Project. Students will act as developers, testers, writers, architects, and managers on the grounds of a highly agile methodology. Students will work with the distributed GitHub- and semantic Wiki-based repository of the 101companies Project. Students may choose to focus on specific contributions in the 101companies Project based on preferences, skills and expectations regarding software technologies and languages. (For instance, one student may take care of the C++ theme in the project.) Students may also choose to deal with some crosscutting concerns of the project, e.g., consistent metamodel-based documentation, diverse import/export functionality, or analysis and visualization of repository data. In this manner, students contribute to a highly visible, practically and pedagogically valuable research project; students acquire skills that directly improve their visible profiles as software engineers.


The best way to get an idea of this project, is to look at the corresponding repositories.

Specifically, have a look at github issues for these repositories:

The complexity of these issues varies dramatically. Just try to get an idea. You would never get assigned an issue, unless the team discussion establishes that you are interested in a certain issue and there is enough clarity and team support for making your success likely.

Modus operandi

Students may enroll for this project practical semi-continuously, but see the next registration date (above) for preferred concentration of enrollment. Likewise, students may operate at slightly difference pace, as long as they usefully participate in the agile process. There is a weekly scrum meeting; regular physical or virtual attendance is expected from enrolled students. The teaching stuff gives overall direction to the project practical and focuses on keeping everyone informed and productive. The students have to show sufficient commitment to identify feasible tasks, to usefully prioritize, to retrieve technical expertise from other team members, and to work out software engineering strategies for resolution of issues. Students should not expect to work on a single, well-delimited task; they should rather be prepared to work in a team on smaller, scattered, dependent, incremental, and experimental improvements that add up to an overall, substantial, and stable improvement over time.