Software engineering, English page

Results

• Results in intranet
• Exam point by tasks in intranet

Lecturer

Harri Laine

How to pass the course

There is one exam (Friday 15.11.2002, Teollisuuskatu Auditorium) crediting at most 48 points. You may get at most 12 points by doing the weekly exercises.

Exercises

According to current plans, there are no exercise groups in English. However, the weekly tasks will be available in English. The tasks will appear here on Thursdays. Please, send your answers (e-mail or paper) to the lecturer to get feedback on your solutions.

Instead of doing the weekly tasks you may get the credit points by doing one larger exercise.

Weekly practice tasks

• Tasks for the 1st exercise (16.9.-25.9.)
• Tasks for the 2nd exercise (23.9.-1.10.)
• Tasks for 3rd exercise (30.9.-8.10.)
• Tasks for 4th exercise (7.10.-15.10.)
• Tasks for 5th exercise (14.10.-22.10.)
• Tasks for 6th exercise (21.10.-29.10.)
• Tasks for 7th exercise
• Tasks fot 8th exercise
• That's all
-->

Contents

This course assumes the technigues taught in 'Introduction to Application Design and Analysis' as known. These include the basic UML-techniques.

The main textbook is:


Pressman Roger S.: Software Engineering - A Practioner's Approach, 5th ed. McGraw-Hill.

Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides.:Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley. October 1994 will be partly covered.

• Introduction
  • What is Software Engineering
  
  Pressman: ch 1.
• Software process
  Pressman: ch2 (not 2.7.3)
• Lectures 17.9.2002
• Software project
  • Organising the Software project
    Lectures 19.9.2002
    Pressman: ch 3.1 & 3.2
  • Project planing
  
  Lectures 24.9.2002
  Pressman: ch 3.3, 3.4, 3.5, 3.7, 5.1-5.4
  • Estimation of effort
    Lectures 26.9.2002
    Pressman: ch 4.2.2,4.3.1-4.3.2, 4.4, 4.5.4, 5.5-5.7
  • Risk Analysis. Pressman: ch 6
    Exercises 3
  • Project scheduling
    Lectures 26.9.2002
    Pressman ch 7.1-7.7
  • Controlling the project
  • Quality
    Lectures 3.10.2002
    Pressman: 8.1-8.5
• Tasks in Software engineering
  • Requirements analysis
  
  Lectures 3.10.2002
  Pressman ch 10, 11 (not 11.2.2, 11.4)
  • Techniques for Requirements analysis
    Lectures 8.10.
    • Object modeling (refreshment)
      Pressman ch 21 (not CRC)
    • state transition diagrams
      Lectures 10.10.
    • Data flow diagrams
      Lectures 15.10.
      Pressman ch 12.4, 12.6
  • Design
    • Design principles
    
    Lectures 17.10. -->
    Pressman ch 13
    • Architecture design
      Pressman ch 14.1-14.3, 22.1-22.2
    • Component design
      Pressman 22.3
    • Use case driven design
      Laine:Olioiden maihinnousu, luku 6.4
• Design Patterns
  Pressman: ch 22.4
  Strategy Pattern
  Composite Pattern
  Observer pattern
  Command Pattern
  Abstract Factory Pattern
  Visitor Pattern
• Programming
• Testing
  Pressman ch 17
• Maintenance