Subject

Object-Oriented Analysis and Design

1. Course Title Object-Oriented Analysis and Design
Object-oriented analysis and design
2. Code F23L2S015
3. Study Programme Software Engineering and Information Systems
4. Organizer of the study programme (unit, institute, department or division) Faculty of Computer Science and Engineering
5. Degree level (first, second, third cycle) First Cycle
6. Academic year / semester 2 / Summer
7. Number of ECTS credits 6
8. Teacher Biljana Risteska Stojkoska, Bojana Koteska, Ilinka Ivanoska, Kire Trivodaliiev, Slobodan Kajaldjiski
9. Prerequisites for enrolling in the course
10. Objectives of the course programme (competences) Introduction to techniques for analysing, designing and modelling object-oriented systems. Development of practical skills in analysing user requirements and creating effective object-oriented models as the initial stage in implementing an object-oriented system.
11. Course content Lectures:
1. Basic object-oriented concepts. Classes, objects, encapsulation, and polymorphism. Interfaces and implementation. Inheritance and composition.
2. Introduction to UML. Models and the need for modeling. Class diagrams - attributes and methods.
3. Class diagrams - relationships between classes. Object diagrams.
4. User scenarios and their modeling through use case diagrams.
5. Activity diagrams.
6. State diagrams.
7. Sequence diagrams.
8. Collaboration diagrams.
9. Interaction with other systems. Defining interfaces to other systems using UML. Component and deployment diagrams.
10. Interaction with other systems. Defining interfaces to other systems using UML. Component and deployment diagrams (continued).
11. Relationship between UML notation and other notations for systems modeling.
12. Practical examples of applying the UML standard.

Practical Classes:
1. Basic object-oriented concepts. Classes, objects, encapsulation, and polymorphism. Interfaces and implementation. Inheritance and composition.
2. Introduction to UML. Models and the need for modeling. Class diagrams - attributes and methods.
3. Class diagrams - relationships between classes. Object diagrams.
4. User scenarios and their modeling through use case diagrams.
5. Activity diagrams.
6. State diagrams.
7. Sequence diagrams.
8. Collaboration diagrams.
9. Interaction with other systems. Defining interfaces to other systems using UML. Component and deployment diagrams.
10. Interaction with other systems. Defining interfaces to other systems using UML. Component and deployment diagrams (continued).
11. Relationship between UML notation and other notations for systems modeling.
12. Practical examples of applying the UML standard.
12. Learning methods Lectures supported by slide presentations, interactive lectures, practical classes (using equipment and software packages), teamwork, case studies, guest lecturers, independent preparation and defence of a project assignment and seminar paper, and learning in an electronic environment (forums and consultations).
13. Total available time 6 ECTS x 30 hours = 180 hours
14. Distribution of available time 30 + 45 + 15 + 15 + 75 = 180 hours
15. Forms of teaching activities
15.1. Lectures - theoretical instruction 30 hours
15.2. Exercises (laboratory, auditory), seminars, teamwork 45 hours
16. Other forms of activities
16.1. Project assignments 15 hours
16.2. Independent assignments 15 hours
16.3. Home study 75 hours
17. Assessment method
17.1. Tests 10 points
17.2. Seminar paper / project (presentation: written and oral) 15 points
17.3. Activities and learning 10 points
17.4. Final exam 70 points
18. Grading criteria (points / grade)
up to 50 points5 (five) (F)
from 51 to 60 points6 (six) (E)
from 61 to 70 points7 (seven) (D)
from 71 to 80 points8 (eight) (C)
from 81 to 90 points9 (nine) (B)
from 91 to 100 points10 (ten) (A)
19. Requirement for obtaining a signature and taking the final exam completed activities 15.1 and 15.2
20. Language of instruction Macedonian and English
21. Method for monitoring the quality of teaching Internal Evaluation and Survey Mechanism
22. Literature
22.1. Required literature
1. G. Booch, J. Rumbaugh, I. Jacobson | The Unified Modeling Language User Guide | Addison Wesley Professional | 2005
2. A. Dennis, B. Haley Wixom, D. Tegarden | Systems Analysis and Design with UML | Wiley | 2007
3. M. Fowler | UML Distilled: A Brief Guide to the Standard Object Modeling Language | Addison Wesley Professional | 2003
4. Binder, R.V. | Testing Object-Oriented Systems: Models, Patterns and Tools | Addison Wesley Professional | 2000
22.2. Additional literature
No. Author Title Publisher Year