Introduction to Software Engineering€¦ · get a better grade (e.g. to get 1.0 instead of 2.0.) •Let’s further assume that you have achieved 85% of the necessary exercise points

Introduction to Software Engineering (2+1 SWS)Winter Term 2009 / 2010 Dr. Michael EichbergVertretungsprofessur Software EngineeringDepartment of Computer ScienceTechnische Universität Darmstadt

Mittwoch, 14. Oktober 2009

|Go to: http://www.es.tu-darmstadt.de/lehre/se_i to get further information.

This lecture has multiple names and the number of credit points you will get is dependent on your course of studies.

Software-Engineering - Einführung IST - Zentrales Prüfungssekretariat

Software-Engineering - Analyse und Design ETiT Bachelor

Softwaresysteme ETiT Prüfungssekretariat

Einführung in Software-Engineering Informatik

Einführung in das Software Engineering Maschinenbau

2


|Organization

The Team

Dr. Michael EichbergFachgebiet Software Engineering

Ralf MitschkeFachgebiet Softwaretechnik

Felix KlarFachgebiet Echtzeitsysteme

ContactWWW

http://www.stg.tu-darmstadt.de/teaching/courses/ws2009/eiseForum

http://www.d120.de/forum/→kanonische Einführungsveranstaltungen →Einführung in Software Engineering

Schedule http://ical.me.com/michael_eichberg/EISE

3


|OrganizationThe Tutors

TODO

4


Introduction to Software Engineering

Dr. Michael EichbergFachgebiet Software EngineeringDepartment of Computer ScienceTechnische Universität Darmstadt

Teaser


|Teaser

The goal of this lecture series is to give you a broad overview over software engineering related topics.

• “Software Engineering” as its own engineering discipline•Understanding software engineering processes•Understanding object-oriented analysis and design • Learn to use UML for analysis and design• Learn to apply design patterns•Assorted topics:• Testing• Refactoring• Software quality (assurance)...

6


|Teaser

Basic programming skills are required.

•Basic knowledge of object-oriented programming concepts is necessary.I.e., you should understand the following terms:• class, interface• object• inheritance• polymorphism

•Knowledge of the Java programming language.

7


|Background Information

The Humble ProgrammerCommunications of the ACM, Vol. 15, Issue 10, 1972

E.W. Dijkstra

As long as there were no machines, programming was no problem at all; when we had a few weak computers, programming became a mild problem, and now we have gigantic computers, programming has become a gigantic problem.

8


Introduction to Software Engineering

Dr. Michael EichbergFachgebiet Software EngineeringDepartment of Computer ScienceTechnische Universität Darmstadt

Organization


|Organization

Lecture

•Wednesdays 16:15-17:55 in S3 11 | 08• The slides are in English

(Key terms will be translated to German.)

• The slides will generally be available after the lecture(I will try hard to make a preliminary variant available the day before the lecture.)

•Slides will be available on:• our web page• https://cage.st.informatik.tu-darmstadt.de/eise (SVN)

(RBG account required)• “iwork.com” to enable you to comment the slides

10


|Organization 11


|Organization

Exercises

•Every week we will have an exercise, starting Tuesday, Oct. 27th, 13:30-14:15 in S3 11 | 08•Exercises are solved in teams of exactly 3 students; details

are available on our webpage; sign-up for the exercise until Oct. 20th.•We will have X exercises (~12)•Each exercise will have ten points• To get the full bonus you need at least (X-1)*10 = Y points

(I.e. you can miss one exercise and can still get the full bonus.)

• To get a bonus for the written exam, you need to have at least 30% of the points necessary to get the full bonus (Y)

12


|Organization

Written Exam

• The date of the exam is: Feb. 24th, 2010; 10:00 - 12:00(The room will be announced in due time. The exam will take 90min.)

• There are no prerequisites (“Everyone” can attend the exam.)

•We have not decided if the exam will be an open book or closed book exam• The maximum bonus you can get is equal to one full grade;

the bonus will reflect your relative success in the exercises • The bonus cannot be used to pass the exam• If you do not write the exam at the end of this semester

you can use the bonus for the summer term 2010 exam

13


|Organization

The bonus exemplified.

• Let’s assume you need ten points in the written exam to get a better grade (e.g. to get 1.0 instead of 2.0.)• Let’s further assume that you have achieved 85% of the

necessary exercise points to get the full bonus (E.g., if we have thirteen exercises (max. 130 points) then you need 120 points to get the maximum bonus; hence, 102 exercise points equals 85%).

• Your bonus (in exam points) will be: 10 exam points * 0.85 = 8.5 exam points•We will cut after the first digit and always round down:

10 exam points * 0.789 ≙ 7.5 exam points

14


|Organization

The effect of the bonus on your final grade may vary.

Bonus Grade Scenario IBonus: 3 pointsExam: 70 points

Scenario IIBonus: 3 pointsExam: 73 points

≥80 1,0

73 points → 1,770 points → 2,0


77-79,5 1,3


76 points → 1,773 points → 1,773-76,5 1,7 73 points → 1,7

70 points → 2,076 points → 1,773 points → 1,7

70-72,5 2,0



… …



15


|OrganizationRelated bibliography.

I do not recommend this book for this lecture.

Useful as a reference, not useful to learn to apply UML.

16


|Organization

Essential Bibliography.

•Design Patterns - Elements of Reusable Object-Oriented Software; Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides; Addison-Wesley, 1995•Applying UML and Patterns - An Introduction to Object-

oriented Analysis and Design; Craig Larman; Prentice Hall• For relevant papers and podcasts see the website and

slides• You can get a substantial discount - visit:

http://www.fachschaft.informatik.tu-darmstadt.de/forum/viewtopic.php?f=6&t=16830

17


|OrganizationVery useful podcast.

http://www.se-radio.net/

18


|Organization

Excursion to Capgemini sd&m

•Date: tba (at the end of the semester)(We will create a Doodle poll; you will have to use your full name.)

• Preliminary list of topics:• Spezifikation in der Praxis - Werkzeuge, Vorgehen,

Erfahrungen• Rechnen statt würfeln – Aufwandsschätzung• Entwicklungsprozesse und Releasemanagement• Die Rolle des Chefarchitekten im Entwicklungsprozess• Reale Projekte

19


Documents

Introduction to Software Engineering€¦ · get a better grade (e.g. to get 1.0 instead of 2.0.) •Let’s further assume that you have achieved 85% of the necessary exercise points