CS504 Advanced Software Engineering
CS504 Advanced Software Engineering
Syllabus | International University of Sarajevo - Last Update on Mar 03, 2026
Syllabus Quick Jump
Search and navigate to any syllabus instantly
Computer Sciences and Engineering
Khaldoun Al Khalidi
Course Lecturer
Course Objectives
1. Understand object-oriented analysis and design basics. 2. Be able to distinguish between problems and solutions and know how to map object oriented analysis to object oriented design. 3. Employ fundamental design principles and patterns in the development of a software system and its supporting documents. 4. Analyze architectural factors and use design mechanisms to select appropriate design technique and design patterns. 5 Be introduced to the Service Oriented Architecture (SOA) and the Microservices.
Learning Outcomes
After successful completion of the course, the student will be able to:
Course Materials
Required Textbook
Applying UML and Patterns, 3rd/Edition, Graig Larman,, Pearson.
Additional Literature
UML Distilled, 3rd Edition, Martin Fowler, Addison-Wesley. K. E. Wiegers and J. Beatty, Software requirements, Third edition. Redmond, Washington: Microsoft Press, s division of Microsoft Corporation, 2013. Robert Martin, Clean Code: A Handbook of Agile Software Craftsmanship, Pearson, M. Richards, Software Architecture Patterns: Understanding Common Architecture Patterns and when to Use Them. O’Reilly Media, 2015. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, 2nd ed. Addison-Wesley, 2003.Teaching Methods
Reports on readings
Use of modeling tools and Computer Assisted Software Engineering (CASE) tools
Projects following the standards (UML, UP,
)
Real life project development guided by the different concepts presented in the course
Weekly Topics
| Week | Topic | Readings / References |
|---|---|---|
| 1 | Overview; Introduction to OOA-OOD and the Unified Process | Handouts |
| 2 | Requirements Modeling - Technical Requirements | Handouts |
| 3 | OOA and OOD Using the Unified Modeling Language (UML) and the Unified Process (UP) - Inception | Handouts |
| 4 | OOA and OOD Using the Unified Modeling Language (UML) and the Unified Process (UP) - Elaboration 1 | Handouts |
| 5 | OOA and OOD Using the Unified Modeling Language (UML) and the Unified Process (UP) - Elaboration 2 | Handouts |
| 6 | Architectural Analysis, Design Mechanisms | Handouts |
| 7 | Midterm | |
| 8 | Architectural Patterns | Handouts |
| 9 | Component Based Development (CBD) | Handouts |
| 10 | Service Oriented Architecture (SOA) | Handouts |
| 11 | Microservices | Handouts |
| 12 | Project follow up | |
| 13 | Research paper Presentations | |
| 14 | Projects Demo | |
| 15 | Final review |
Course Schedule (All Sections)
Office Hours & Room
Assessment Methods and Criteria
Assessment Components
Final Exam
AI: Not AllowedAlignment with Learning Outcomes :
Project
AI: Not AllowedAlignment with Learning Outcomes :
Research paper
AI: Not AllowedAlignment with Learning Outcomes :
Participation
AI: Not AllowedAlignment with Learning Outcomes :
IUS Grading System
| Grading Scale | IUS Grading System | IUS Coeff. | Letter (B&H) | Numerical (B&H) |
|---|---|---|---|---|
| 0 - 44 | F | 0 | F | 5 |
| 45 - 54 | E | 1 | ||
| 55 - 64 | C | 2 | E | 6 |
| 65 - 69 | C+ | 2.3 | D | 7 |
| 70 -74 | B- | 2.7 | ||
| 75 - 79 | B | 3 | C | 8 |
| 80 - 84 | B+ | 3.3 | ||
| 85 - 94 | A- | 3.7 | B | 9 |
| 95 - 100 | A | 4 | A | 10 |
Late Work Policy
Information about late submission policies will be shared during class and posted in this section. Please check back for official guidelines.
ECTS Credit Calculation
📚 Student Workload
This 6 ECTS credit course corresponds to 150 hours of total student workload, distributed as follows:
Lecture hours
42 hours ⏳ (14 week × 3 h)
Project
48 hours ⏳ (12 week × 4 h)
Research
36 hours ⏳ (12 week × 3 h)
Home study
14 hours ⏳ (14 week × 1 h)
Final exam study
10 hours ⏳ (1 week × 10 h)
150 Total Workload Hours
6 ECTS Credits
Course Policies
Academic Integrity
All work submitted must be your own. Plagiarism, cheating, or any form of academic dishonesty will result in disciplinary action according to university policies. When in doubt about citation practices, consult the instructor.
Attendance Policy
Students are expected to adhere to the attendance requirements as outlined in the International University of Sarajevo Study Rules and Regulations. Excessive absences, whether excused or unexcused, may impact academic performance and eligibility for assessment. Mandatory sessions (e.g., labs, workshops) require attendance unless formally exempted. For detailed policies on absences, documentation, and penalties, please refer to the official university regulations.
Technology & AI Policy
Laptops/tablets may be used for note-taking only during lectures. Phones should be silenced and put away during all class sessions. Audio/video recording requires prior permission from the instructor.
Artificial Intelligence (AI) Usage: The use of AI tools (e.g., ChatGPT, Copilot, Gemini) varies by assessment component. Please refer to the AI usage indicator next to each assessment item in the Assessment Methods and Criteria section above. Submitting AI-generated content as your own work, where AI is not explicitly allowed, constitutes an academic integrity violation.
Communication Policy
All course-related communication should occur through official university channels (institutional email or SIS). Emails should include [CS504] in the subject line.
Academic Quality Assurance Policy
Course Academic Quality Assurance is achieved through Semester Student Survey. At the end of each academic year, the institution of higher education is obliged to evaluate work of the academic staff, or the success of realization of the curricula.
Learning Tips
Be prepared to contribute thoughtfully during class discussions, labs, or collaborative work. Active participation deepens understanding and encourages critical thinking.
Complete assigned readings or prep materials before class. Take notes, highlight key ideas, and jot down questions. Aim to grasp core concepts and their applications—not just facts.
Use course frameworks or methodologies to analyze problems, case studies, or projects. Begin early to allow time for reflection and refinement. Seek feedback to improve your work.
Don’t hesitate to reach out when something is unclear. Use office hours, discussion boards, or peer networks to clarify concepts and stay on track.
Syllabus Last Updated on Mar 03, 2026 | International University of Sarajevo
Print Syllabus
Referencing Curricula Print this page
| Course Code | Course Title | Weekly Hours* | ECTS | Weekly Class Schedule | ||||||
| T | P | |||||||||
| CS504 | Advanced Software Engineering | 3 | 0 | 6 | Monday 17:00 - 19:50 | |||||
| Prerequisite | None | It is a prerequisite to | - | |||||||
| Lecturer | Khaldoun Al Khalidi | Office Hours / Room / Phone | Currently not available |
|||||||
| kalkhalidi@ius.edu.ba | ||||||||||
| Assistant | Assistant E-mail | |||||||||
| Course Objectives | 1. Understand object-oriented analysis and design basics. 2. Be able to distinguish between problems and solutions and know how to map object oriented analysis to object oriented design. 3. Employ fundamental design principles and patterns in the development of a software system and its supporting documents. 4. Analyze architectural factors and use design mechanisms to select appropriate design technique and design patterns. 5 Be introduced to the Service Oriented Architecture (SOA) and the Microservices. |
|||||||||
| Textbook | Applying UML and Patterns, 3rd/Edition, Graig Larman,, Pearson. | |||||||||
| Additional Literature |
|
|||||||||
| Learning Outcomes | After successful completion of the course, the student will be able to: | |||||||||
|
||||||||||
| Teaching Methods | Reports on readings. Use of modeling tools and Computer Assisted Software Engineering (CASE) tools. Projects following the standards (UML, UP,..) . Real life project development guided by the different concepts presented in the course. | |||||||||
| Teaching Method Delivery | Face-to-face | Teaching Method Delivery Notes | ||||||||
| WEEK | TOPIC | REFERENCE | ||||||||
| Week 1 | Overview; Introduction to OOA-OOD and the Unified Process | Handouts | ||||||||
| Week 2 | Requirements Modeling - Technical Requirements | Handouts | ||||||||
| Week 3 | OOA and OOD Using the Unified Modeling Language (UML) and the Unified Process (UP) - Inception | Handouts | ||||||||
| Week 4 | OOA and OOD Using the Unified Modeling Language (UML) and the Unified Process (UP) - Elaboration 1 | Handouts | ||||||||
| Week 5 | OOA and OOD Using the Unified Modeling Language (UML) and the Unified Process (UP) - Elaboration 2 | Handouts | ||||||||
| Week 6 | Architectural Analysis, Design Mechanisms | Handouts | ||||||||
| Week 7 | Midterm | |||||||||
| Week 8 | Architectural Patterns | Handouts | ||||||||
| Week 9 | Component Based Development (CBD) | Handouts | ||||||||
| Week 10 | Service Oriented Architecture (SOA) | Handouts | ||||||||
| Week 11 | Microservices | Handouts | ||||||||
| Week 12 | Project follow up | |||||||||
| Week 13 | Research paper Presentations | |||||||||
| Week 14 | Projects Demo | |||||||||
| Week 15 | Final review | |||||||||
| Assessment Methods and Criteria | Evaluation Tool | Quantity | Weight | Alignment with LOs | AI Usage |
| Final Exam | 1 | 35 | Not Allowed | ||
| Semester Evaluation Components | |||||
| Project | 1 | 40 | Not Allowed | ||
| Research paper | 1 | 20 | Not Allowed | ||
| Participation | 1 | 5 | Not Allowed | ||
| *** ECTS Credit Calculation *** | |||||
| Activity | Hours | Weeks | Student Workload Hours | Activity | Hours | Weeks | Student Workload Hours | |||
| Lecture hours | 3 | 14 | 42 | Project | 4 | 12 | 48 | |||
| Research | 3 | 12 | 36 | Home study | 1 | 14 | 14 | |||
| Final exam study | 10 | 1 | 10 | |||||||
| Total Workload Hours = | 150 | |||||||||
| *T= Teaching, P= Practice | ECTS Credit = | 6 | ||||||||
| Course Academic Quality Assurance: Semester Student Survey | Last Update Date: 27/03/2026 | |||||||||