Object-Oriented Software Construction

Bertrand Meyer, Summer semester 2005

Still available: last year's page.

Announcements

23 June 2005

• Some additional information about the exam:
• no helping material is allowed (keine Hilfsmittel erlaubt)
• bring with you some blank sheets of paper on which you will solve the questions; we will provide the question sheets, but no answers written on these sheets will be taken into account
• the chapters from "Object-Oriented Software Construction" are recommended reading for the exam; no questions will be asked in the exam about topics not covered in the lectures
• the exam will last for 45 minutes (13:15 - 14:00)
• The projects will be turned in no later than 30 June 2005 by emailing me (ilinca.ciupa@inf.ethz.ch) a zip or tgz file containing all the deliverables:
  • The source code of the project – This means only the ace file and Eiffel classes (.e files). Do not use absolute paths in the ace file. Do not include any compilation output (compiled code, EiffelStudio project files, etc.) in the delivery.
  • A test suite (also only as source code)
  • Requirements document (in pdf format)
  • Documentation (in pdf format): user guide and developer guide. In the user guide, give very clear instructions for running the application.
• Also list in the email the names of the people in the project group.

22 June 2005

• The slides for lecture 21 (Agents and Tuples) are now available
• The schedule of the lectures has been updated

14 June 2005

• The slides for lecture 20 (Design Principles) are now available

13 June 2005

• The slides for lecture 19 (SCOOP: Simple Concurrent Object-Oriented Programming) are now available

8 June 2005

• Lecture 18 has been on a design example. The slides are now available.

6 June 2005

• The slides for lecture 18 (Design Principles) are now available

3 June 2005

• The slides for lecture 17 (Testing Object-Oriented Software) are now available

30 May 2005

• The slides for lectures 14 (Presentation of EiffelStudio and Ace Files), 15 (Exception Handling), and 16 (Object Persistence) are now available
• The tentative schedule for the lectures has been updated

26 May 2005

• The ace files of the example for drawing in EiffelVision 2 have been updated

25 May 2005

• The slides for lecture 13 (Design by Contract (continued)) have been updated (change on slide 4)

24 May 2005

• The slides for lecture 11 (Design by Contract) have been updated
• The slides for lecture 12 (Design by Contract (continued)) are now available
• The slides for lecture 13 (Design by Contract (continued)) are now available

12 May 2005

• An example for using drawing in Eiffel Vision 2 is available here

11 May 2005

• The slides for lecture 10 (Project Presentation) are now available

9 May 2005

• The slides for lecture 9 (Design Patterns) are now available
• The project specification has been updated (added a section on deliverables)

4 May 2005

• The slides for lecture 8 (More on inheritance) have been updated
• Please announce the project groups to the course assistant by Monday 9 May (groups of 2; it's permitted to work alone, but the amount of work is the same). Those who do not do it will be grouped randomly.

2 May 2005

• The slides for lecture 7 (Inheritance) have been updated

29 April 2005

• The new project specification is now available
• The lecture on Wednesday 11 May and the first hour of the lecture on Monday 30 May will be dedicated to discussions and questions on the project. If you have questions in the meantime, email the course assistant.
• Those who have not done so yet, please decide on the groups for the project by Wednesday 4 May and send the information by email to the course assistant.
• The slides for lecture 9 (Design by Contract) are now available

25 April 2005

• Slides for lecture 6 (Genericity) have been updated
• Updated schedule for the lectures is now available

24 April 2005

• Slides for lectures 7 and 8 (Inheritance) are now available
• Updated versions in pdf format for lecture 4 (Objects) are now available

21 April 2005

• Slides for lecture 4 (Objects) have been updated (pdf versions will be available soon)

17 April 2005

• Slides for lecture 6 (Genericity) are now available

14 April 2005

• The specification of the testing framework in the project will change. The updated version will be available next week.
• Please decide on the groups for the project by Monday 25 April and send the information by email to the course assistant. If you can't decide until then, send an email explaining the situation.

12 April 2005

• The schedule for the lectures has been updated
• Slides for lecture 5 (Project and EiffelStudio Presentation) are now available

11 April 2005

• Slides for lecture 3 (Abstract Data Types) have been updated

10 April 2005

• Slides for lecture 4 (Objects) are now available
• Project specification is available

4 April 2005

• Slides for lectures 1 and 2 (Modularity) have been updated
• Slides for lecture 3 (Abstract Data Types) are now available

31 March 2005

• Slides of the first lecture are now on-line (see Slides)

29 March 2005

• Register to the course: Please send an email
  To: oosc-course@se.inf.ethz.ch
  Subject: OOSC Course Participant
  Content:
  • Your name
  • Preferred email address
  • Status: Diplom student (what semester), Ph.D. student, other.
  • Taking the course for credit or not.
  • Attach a picture (JPEG, GIF, PNG) if you wish.

Description

Title and code

Object-Oriented Software Construction
Course code: 251-0250-00
See official ETH page on this course

Scope

This course will explore a number of issues, both practical and theoretical, raised by object technology, especially when applied to large, ambitious, long-running projects with high quality requirements.

Prerequisites

Some practice of object-oriented development and knowledge of an object-oriented language and basic design patterns. Attendance of the winter semester course 251-0239-00 Trusted Components is desirable.

Objectives

The goal is to provide students with solid knowledge of:

• Object technology principles and methods
• The practice of object-oriented analysis, design and implementation
• Some open issues
• Some recent developments
• A specific technology: Eiffel

Topics

• Review of elementary and advanced object-oriented mechanisms.
• Theoretical basis: abstract data types.
• Techniques and principles for producing reusable components and high-quality object-oriented software. Reuse issues.
• Concurrent object-oriented development: issues, constraints, existing proposals, implementations, SCOOP model.
• Typing issues. Covariance and catcalls. Language design for flexible typing.
• Encapsulating behaviours along with data.
• High-level system structuring. Role of graphical formalisms. Seamless and reversible development.
• Metrics of object-oriented development.
• Object-oriented project management. Lifecycle issues; the cluster model, seamlessness, reversibility.
• From design patterns to reusable components.

Schedule

Weekly schedule

• Monday 9.00 - 11.00, RZ F21.
• Wednesday 13.00 - 14.00, RZ F21.

Office hours: By appointment. RZ J4.

Semester schedule (tentative)

Grading

Important: No "Testat" is delivered or "mündliche Prüfung" provided for this course. The only way to get a grade is to take the exam and the project. This applies regardless of your department or status.

• 60% Project: Development of an Object Spyglass.(Deadline: 30 June 2005)
• 40% Exam: 29 June 2005

Textbook

Bertrand Meyer: Object-Oriented Software Construction, second edition. Prentice Hall, 1997.

Recommended:
Erich Gamma et al.: Design Patterns. Addison-Wesley, 1995.

Readings

Bertrand Meyer: The power of abstraction, reuse and simplicity: An object-oriented library for event-driven design . Springer-Verlag, Lecture Notes in Computer Science, 2003.

David L. Parnas: On the Criteria To Be Used in Decomposing Systems into Modules. Communications of the ACM, Communications of the ACM, 15, 12, (December 1972), p 1053 - 1058

C.A. R. Hoare: An Axiomatic Basis for Computer Programming. Communications of the ACM, 1969.

IEEE Std 1063: IEEE Standard for User Documentation

IEEE Std 1233: IEEE Guide for Developing System Requirements Specifications

IEEE Std 830: IEEE Recommended Practice for Software Requirements Specifications

Niklaus Wirth, “Program Construction by Stepwise Refinement”, Communications of the ACM, 14, 4, (April 1971), p 221-227

Karine Arnout, “EiffelStudio: A Guided Tour”

Slides

Project

Project specification: Object Spyglass

Supporting material:

• Example for using drawing in Eiffel Vision 2

Contacts

• Send all email relative to this course to oosc-course at se.inf.ethz.ch. It will reach the professor and the assistant. Do not use their personal addresses or your message may be missed.
• Contact assistant for the course: Ilinca Ciupa (http://se.inf.ethz.ch/people/ciupa, office: RZ J4)

Last modified: 23.06.2005 by Ilinca Ciupa