1. Course Title |
Design and Analysis of Information Systems | |||||||
2. Code | 4ФЕИТ07Л001 | |||||||
3. Study program | КТИ | |||||||
4. Organizer of the study program (unit, institute, department) | Faculty of Electrical Engineering and Information Technologies | |||||||
5. Degree (first, second, third cycle) | First cycle | |||||||
6. Academic year/semester | III/6 | 7. Number of ECTS credits | 6 | |||||
8. Lecturer | D-r Katerina Raleva | 9. Course Prerequisites | ||||||
10. Course Goals (acquired competencies): Modelling software solutions using UML diagrams and introduction to XML. After finishing this course, the students will be able to understand and design software solutions using UML and XML.
– Understanding and analyzing UML diagrams |
||||||||
11. Course Syllabus: Introduction to system design. Introduction to modelling. Modelling concepts in UML. Class diagram and Object diagram. Use Case diagrams. Activity diagrams. State diagrams. Sequence and collaboration diagrams. Component and implementation diagram. Mapping user requests into UML models. Semi-structured databases. Introduction to XML and definition of types of documents. Introduction to XML Schema. Description of XML documents. Mapping of structured databases in XML. Semi-structured question concepts. Asking questions. Asking questions with the help of XPATH. Asking questions with the help of XQUERY. | ||||||||
12. Learning methods: Lectures, exercises and laboratory exercises | ||||||||
13. Total number of course hours | 2 + 2 + 1 + 0 | |||||||
14. Distribution of course hours | 180 | |||||||
15. Forms of teaching | 15.1. Lectures-theoretical teaching | 30 | ||||||
15.2. Exercises (laboratory, practice classes), seminars, teamwork | 45 | |||||||
16. Other course activities | 16.1. Projects, seminar papers | 25 | ||||||
16.2. Individual tasks | 20 | |||||||
16.3. Homework and self-learning | 60 | |||||||
17. Grading | 17.1. Exams | 0 | ||||||
17.2. Seminar work/project (presentation: written and oral) | 0 | |||||||
17.3. Activity and participation | 0 | |||||||
17.4. Final exam | 100 | |||||||
Grading criteria (points) | up to 50 points | 5 (five) (F) | ||||||
from 51to 60 points | 6 (six) (E) | |||||||
from 61to 70 points | 7 (seven) (D) | |||||||
from 71to 80 points | 8 (eight) (C) | |||||||
from 81to 90 points | 9 (nine) (B) | |||||||
from 91to 100 points | 10 (ten) (A) | |||||||
19. Conditions for acquiring teacher’s signature and for taking final exam | Laboratory exercises and homework | |||||||
20. Forms of assessment | During the semester, a theoretical and practical exams are scheduled. The theoretical exam is consisted of short questions from the curriculum, whereas, the practical exam is taken by doing a home project assignment. Each student chooses a different assignment for the practical exam, which upon completion, has to present it. The theoretical part is taken during exam week. To pass the exam, both theoretical and practical exams have to be completed. If the student obtains more than 50% of the points from the theoretical part, it is considered as passed. The final grade is consisted from 70% of the practical part and 30% from the theoretical part. | |||||||
21. Language | Macedonian and English | |||||||
22. Method of monitoring of teaching quality | Internal evaluation and survey | |||||||
23. Literature | ||||||||
23.1. Required Literature | ||||||||
No. | Author | Title | Publisher | Year | ||||
1 | Arthur M. Langer | Analysis and Design of Information Systems 3rd Edition | Springer | 2007 | ||||
2 | Raymond Frost | Business Information Systems: Design an App for That | Saylor Foundation | 2011 | ||||
3 | Alan Dennis, Barbara Wixom, David Tegarden | Systems Analysis and Design: An Object-Oriented Approach with UML, 6th Edition | Wiley | 2020 |