The language was changed to English.

Course Type (SWS)
Lecture: 0 │ Exercise: 0 │ Lab: 2 │ Seminar: 0
Exam Number:
Exam Code:
Type of Lecture:

Group work with presentations and discussion of intermediate results.
Language: German
Cycle: WS
ECTS: 2
Exam Type
Regular and active lab participation.
Creating all required development documents, coding and testing of the software.
assigned Study Courses
assigned People
assigned Modules
Information
Beschreibung:

Unter Einsatz der in der Vorlesung "Softwaretechnik" vorgestellten Konzepte soll eine objekt-orientierte Software auf Basis zu erstellender Entwicklungsdokumente prototypisch realisiert werden.

Dies beinhaltet u.a. den Einsatz und das Verständnis von Mustern und UML Notationen zur Erzeugung der Dokumente.

Für die Analysephase
- Erhebung der Anforderungen.
- Ableitung der Spezifikation.
- Lebenszyklusmodell für Unterproblembeziehungen.

Für die Entwurfsphase
- Entwurf der Architektur unter Einsatz von Mustern.
- Zustandsmaschinen für Komponentenverhalten.

Darüber hinaus ist die Software auf Basis der zuvor erstellten Dokumente zu implementieren und zu testen.
Lernziele:

Praktische Erfahrung in der Entwicklung von Software und in Gruppenarbeit sammeln.
Literatur:

- Ian Sommerville: Software Engineering, Addison-Wesley, jeweils neueste Auflage
- Michael Jackson: Problem Frames. Analyzing and structuring software development problems. Addison-Wesley, 2001
- M. Jeckle, C. Rupp, J. Hahn, B. Zengler, S. Queins: UML 2 glasklar
- D. Coleman, P. Arnold, S. Bodoff, C. Dollin, H. Gilchrist, F. Hayes, and P. Jeremaes. Object-Oriented Development: The Fusion Method. Prentice-Hall, 1994
- Bass, L., Clements, P., and Kazman, R. (1998). Software Architecture in Practice. Addison-Wesley, Boston, MA, USA, 1st edition.
- Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides: Design Patterns. Addison Wesley, 1995

Vorleistung:
Infolink:
Bemerkung:
Description:

The concepts introduced in the lecture "Software Engineering" are applied for developing an object-oriented software prototype. All necessary development documents have to be set up. This includes the usage of patterns and UML notations.

Tasks in the the analysis phase are to
- elicitate requirements.
- derive specifications.
- create a life cycle model that relates all identified subproblems.

For the design phase:
- desing a software architecture usung patterns and
- each component‘s behavior is defined by a state machine.

Furthermore, the software has to be implemented and tested, based on the previously developed artifacts.
Learning Targets:

Gain practical experience in developing software and of working in groups.
Literature:

- Ian Sommerville: Software Engineering, Addison-Wesley, jeweils neueste Auflage
- Michael Jackson: Problem Frames. Analyzing and structuring software development problems. Addison-Wesley, 2001
- M. Jeckle, C. Rupp, J. Hahn, B. Zengler, S. Queins: UML 2 glasklar
- D. Coleman, P. Arnold, S. Bodoff, C. Dollin, H. Gilchrist, F. Hayes, and P. Jeremaes. Object-Oriented Development: The Fusion Method. Prentice-Hall, 1994
- Bass, L., Clements, P., and Kazman, R. (1998). Software Architecture in Practice. Addison-Wesley, Boston, MA, USA, 1st edition.
- Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides: Design Patterns. Addison Wesley, 1995

Pre-Qualifications:
Info Link:
Notice: