Derek Bridge

This core module was taught five times between 1998 and 2003 to second-year undergraduates on the main B.Sc. computing degrees in UCC's Computer Science Department.

The workload is 6 hours per week for the whole year, and is divided roughly as follows:

• Lectures: 2 lectures per week, each lasting 1 hour.
• Practicals: 1 practical per week, lasting 2 hours, starting in week 3.
  (Three practicals will appear on the timetable: students attend one of the three.)
• Private study: At least 2 hours of private study per week.

Every student should have passed first-year programming.

• Written exam: A three-hour paper in the Summer term, worth 80% of the overall mark.
• Year's work: All of the exercises tackled during the practicals should be submitted. A subset will be corrected and handed back to give feedback. A (probably different) subset will be graded, their grades will be combined by a weighted average, and this will be included in the final mark, where it will be worth 20% of the overall mark.

The course will introduce students to object-oriented design & programming. The design notation used will be based on parts of the UML. The programming language used will be Java.

Little attention will be paid to requirements analysis. But there will be coverage of high-level (architectural) design, low-level design, coding, testing and debugging.

In judging student work, considerable attention will be paid to issues of good design and good style.

• Students should learn most of the constructs of the core of the Java language.
• They should become adept at using parts of the standard Java library (sufficient to enable them to write programs with simple graphical user interfaces & event-driven programs).
• They should learn some of the principles of good object-oriented program design.
• They should learn the elements of good coding style.

• Teaching Materials
• Books
• WWW Resources
• Style File
• Glossary
• Acknowledgments