Research Group for Applied Software Engineering
Forschungsgruppe für Angewandte Softwaretechnik

JASS 2006 AdvancedSE

Advanced Topics in Software Engineering

Gennady G. Yanovsky, St. Petersburg State University of Telecommunications

Bernd Brügge, Technische Universität München

St. Petersburg - Sunday, April 2 through Wednesday, April 12, 2006


Overview

The course is offered to 12 highly motivated students interested in learning about software project management and applying new technologies in addressing some of its challenges. Active preparation and contribution of the participants will be required. The course consists of a seminar and a project component. The seminar component focuses on some recent advances in management and technology with respect to the management of large complex software development projects. The goal of the project component is to deepen the understanding of concepts discussed in the seminar component: All course participants will work together to develop a meeting management tool for distributed global software projects. The course language is English.

To apply for this course, you must have programming experience with C++ or Java.

Download the application form and send all the required information (filled out application form, letter of intent, resume, grade certificates, list of prioritized presentation topics) in PDF format to your local course director.For more information contact Timo Wolf. Letters of notification to the 12 accepted students will be sent on February 2, 2006.

This course is offered as part of the fourth Joint Advanced Student School - JASS 2006. More information about JASS 2006 can be found under http://wwwmayr.in.tum.de/konferenzen/Jass06/


Course Information

 
Course Directors

Prof. Dr. Gennady G. Yanovsky
Course Support

 

 

Prof. Dr. Andrew Krasov


Timo Wolf


Project Component

The goal of the JASS project is the development of an agile meeting management tool for distributed software projects.

It is based on a rhetorical model of issues, proposals, resolutions and action items, enabling users to annotate UML modeling elements such as use cases, class diagrams or sequence diagrams with rhetorical elements.

Developers create system models and communication elements within a single repository, where the system models represent the system under development and the communication elements represent problems, status and tasks.

Meeting agendas are not explicitly written by a project manager, but are generated automatically from the open issues and action items in the repository.

Languages and tools used in the project:

The result of the project will be part of the JASS 2006 CD.

 

 

 

 

Seminar Component

The seminar focuses on topics in the area of

  • Agile software development
  • Agile project management
  • Agile modeling
  • Rationale management
  • System  integration and build management

Each topic will be presented by two students (one from St. Petersburg, one from Munich). The presentation about the selected topic will be included in the JASS 2006 CD.

Each applicant has to submit a prioritized list of three topics indicating his or her preferences.

Topic Literature
1. Agile software development

J. Highsmith (2002). Agile Software Development Ecosystems. Addison Wesley. See also http://www.agilealliance.org &

http://en.wikipedia.org/wiki/ Agile_software_development

 

2. Agile project management

K. Schwaber, M. Beedle (2002). Agile Software Development with Scrum. See also http://www.controlchaos.com/

 

3. Agile Modeling

S. W. Ambler (2002). Agile modeling. Wiley Computer Publishing. See also http://www.agilemodeling.com/

 

4. Extreme Programming

D. Astels, G. Miller, M. Novak. (2002). A Practical Guide to eXtreme programming. Prentice Hall.

See also  http://www.extremeprogramming.org/

 

5. Rationale Management

B. Bruegge and A. Dutoit (2003). Object-Oriented Software Engineering: Using UML, Patterns and Java, Prentice Hall, in particular Chapter 12 &

R. Fisher & W. Ury (1981). Getting To Yes, Penguin Books.

6. System Integration and Build Management

M. Fowler & M. Foemmel. Continuous Integration. See  http://www.martinfowler.com/articles/

continuousIntegration.html

For more information on CruiseControl see http://cruisecontrol.sourceforge.net/

For information on Maven see http://maven.apache.org/