SoleOPS 3.13.0, ©2005-2018Solenovo Oy

Opintojakson toteutussuunnitelma

Group504D10/Degree Programme in Information Technology (Rovaniemi)
Study unit504D15B Design Methods, 5.00 ECTS credits, 133 h
Compulsory Professional Studies
Time of implementationSpring1/2011-2012, Spring2/2011-2012
Responsible teacherMattila Erkki
Other teachers
Status of implementationFinished

Description status Ready
Language of instruction English
Starting and ending dates01.01.2012 - 29.05.2012
Minimum number of participants  
Maximum number of participants  
Enrolment period14.04.2011 - 31.05.2011
Implementation method
Virtuality 2 ECTS credits
R&D integration 0 ECTS credits
Resit dates of the exam
Koulutuksen aikataulu (www-linkki)
Description language English 

The student will get an understanding of object-oriented analysis and design using the UML modeling language, as well as knowledge of the best design and programming practices. The student will learn to apply some common design patterns and application frameworks in software development.

Assessment criteria  
Pedagogical arrangements

Lectures and practises 60 h, case study and presentations  73 h.


Lecture notes and examples.

Recommended reading:
Bennet S., McRobb S. & Farmer R. 2006. Object-oriented System Analysis and Design Using UML, 3rd Edtion. McGraw-Hill: Berkshire
Fowler M. 2004. UML Distilled, 3rd Edition. Addison-Wesley
McConnel S. 2004. Code Complete. Second Edition. Microsoft Press: Redmond
O'Docherty M. 2005. Object-Oriented Analysis and Design: Understanding System Development with UML 2.0. John Wiley & Sons
Pressman R. S. 2005. Software Engineering: A Practioner’s Approach, 6th Edition. McGraw-Hill
van Vliet H. 2008. Software Engineering: Principles and Practice. John Wiley & Sons
Sebesta R. W. 2008. Concepts of Programming Languages, 8th Edition. Pearson Education, Addison-Wesley
Sommerville I. 2006. Software Engineering, 8th Edition. Addison-Wesley


Introduction to design methods. Best design and programming practices. Applying into practice object-oriented analysis and design with UML. Writing software requirements specification and software design specification on the given system.

1. Translating requirements into object-oriented models of system structure and behaviour that provide a traceable route through to implementation.

2. Understanding the stages in the development cycle and appreciate why and when to apply UML.

3. Applying UML concepts and notation for representing objects, classes and interfaces; be able to specify their content and know how to represent the different relationships of association, aggregation inheritance and realisation.

4. Using appropriate UML diagrams and notation to model the work of requirements capture, analysis and design.

5. Translating analysis models, based on entity relationship diagrams into design models based around class diagrams.

6. Understanding the concepts of a use-case driven approach to object-oriented requirements modelling and the application of use-cases as a tool for incremental systems delivery.

7. Identifing and describing use cases and using CRC cards.

8. Applying  the concepts and notation for sequence diagrams during design and understanding how they relate to class diagrams and use-cases.

9. Understanding where dynamic modelling with state charts is appropriate.

10. Applying design patterns and application frameworks.


The final exam and the compulsory case study (software requirements specification, software design specification, presentations and learning diaries) will be assed on the scale from 0 to 5.