SE211 Software Construction
SE211 Software Construction
Syllabus | International University of Sarajevo - Last Update on Apr 04, 2026
Syllabus Quick Jump
Search and navigate to any syllabus instantly
Software Engineering
Mohammed Saeed Jawad
Course Lecturer
Course Objectives
Catalog description: Knowing programming does not make you a software engineer. The objective of this course is to introduce the enabling techniques and design principles necessary to build high quality software, in the context of the object-oriented paradigm. The students’ knowledge in object-oriented programming is enhanced by explaining the advantage of the object-oriented technology in that it promotes good design by its inherent nature through the mechanisms of abstraction, information hiding, encapsulation, and polymorphism. Students will learn how to become good designers by integrating design patterns and test cases upfront in the development cycle.
Learning Outcomes
After successful completion of the course, the student will be able to:
Course Materials
Required Textbook
No specific text book.
Additional Literature
A1• Fowler M., UML Distilled, 3rd ed., Addison Wesley, 2003. A2• Martin R. and Martin M., Agile Principles, Patterns, and Practices in C#, 1st ed., Prentice Hall, 2006. A3• Gamma E., Helm R., Johnson R., and Vlissides J., Design Patterns: Elements of Reusable Object-Oriented Software, 1st ed., Addison-Wesley, 1994.Teaching Methods
Class discussions with examples
Active tutorial sessions
Weekly Topics
| Week | Topic | Readings / References |
|---|---|---|
| 1 | Introduction | Notes |
| 2 | The object-oriented paradigm. | Notes |
| 3 | Object-oriented programming concepts.- foundations | Notes |
| 4 | Object-oriented programming concepts.- | Notes |
| 5 | UML diagrams - class diagrams, interaction diagrams | A1 |
| 6 | UML Diagrams - activity diagrams, state-machine diagrams | A1 |
| 7 | Midterm Exam | |
| 8 | Design Principles - Single-Responsibility Principle, Open-Closed Principle, Liskov-Substitution Principle | A2 |
| 9 | Design Principles - Dependency-Inversion Principle, Interface Segregation Principle | A2 |
| 10 | Exception Handling, Debugging, | Notes |
| 11 | Test-Driven development | A2 |
| 12 | Design Patterns - Adapter, Factory, Singleton | A2,A3 |
| 13 | Design Patterns - Strategy, Composite, Observer | A2,A3 |
| 14 | Basic Software Architectures | Notes |
| 15 | General Review |
Course Schedule (All Sections)
| Section | Type | Day 1 | Venue 1 | Day 2 | Venue 2 |
|---|---|---|---|---|---|
| SE211.1 | Course | Monday 12:00 - 14:50 | A F2.14 - Amphitheater II | - | - |
| SE211.1 | Tutorial | Wednesday 14:00 - 15:50 | A F1.24 - Amphitheater I | - | - |
Office Hours & Room
Assessment Methods and Criteria
Assessment Components
Final Exam
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3 4 5
Quizzes
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3 4 5
Midterm
AI: Not AllowedAlignment with Learning Outcomes : 1 2 4
Labs-Assignments
AI: Not AllowedAlignment with Learning Outcomes : 2 3 5
Group Projects
AI: Consult InstructorAlignment with Learning Outcomes : 1 2 3 4 5
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
45 hours ⏳ (15 week × 3 h)
Assignments
20 hours ⏳ (4 week × 5 h)
In-term Exam Stud
11 hours ⏳ (1 week × 11 h)
Quizzes
16 hours ⏳ (4 week × 4 h)
Home Study
42 hours ⏳ (14 week × 3 h)
Final Exam Study
16 hours ⏳ (1 week × 16 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 [SE211] 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 Apr 04, 2026 | International University of Sarajevo
Print Syllabus
Referencing Curricula Print this page
| Course Code | Course Title | Weekly Hours* | ECTS | Weekly Class Schedule | ||||||
| T | P | |||||||||
| SE211 | Software Construction | 3 | 2 | 6 | ||||||
| Prerequisite | CS103 | It is a prerequisite to | SE401, SE406 | |||||||
| Lecturer | Mohammed Saeed Jawad | Office Hours / Room / Phone | Currently not available |
|||||||
| msjawad@ius.edu.ba | ||||||||||
| Assistant | Amina Hrustic | Assistant E-mail | ahrustic@student.ius.edu.ba | |||||||
| Course Objectives | Catalog description: Knowing programming does not make you a software engineer. The objective of this course is to introduce the enabling techniques and design principles necessary to build high quality software, in the context of the object-oriented paradigm. The students’ knowledge in object-oriented programming is enhanced by explaining the advantage of the object-oriented technology in that it promotes good design by its inherent nature through the mechanisms of abstraction, information hiding, encapsulation, and polymorphism. Students will learn how to become good designers by integrating design patterns and test cases upfront in the development cycle. | |||||||||
| Textbook | No specific text book. | |||||||||
| Additional Literature |
|
|||||||||
| Learning Outcomes | After successful completion of the course, the student will be able to: | |||||||||
|
||||||||||
| Teaching Methods | Class discussions with examples. Active tutorial sessions. | |||||||||
| Teaching Method Delivery | Face-to-face | Teaching Method Delivery Notes | ||||||||
| WEEK | TOPIC | REFERENCE | ||||||||
| Week 1 | Introduction | Notes | ||||||||
| Week 2 | The object-oriented paradigm. | Notes | ||||||||
| Week 3 | Object-oriented programming concepts.- foundations | Notes | ||||||||
| Week 4 | Object-oriented programming concepts.- | Notes | ||||||||
| Week 5 | UML diagrams - class diagrams, interaction diagrams | A1 | ||||||||
| Week 6 | UML Diagrams - activity diagrams, state-machine diagrams | A1 | ||||||||
| Week 7 | Midterm Exam | |||||||||
| Week 8 | Design Principles - Single-Responsibility Principle, Open-Closed Principle, Liskov-Substitution Principle | A2 | ||||||||
| Week 9 | Design Principles - Dependency-Inversion Principle, Interface Segregation Principle | A2 | ||||||||
| Week 10 | Exception Handling, Debugging, | Notes | ||||||||
| Week 11 | Test-Driven development | A2 | ||||||||
| Week 12 | Design Patterns - Adapter, Factory, Singleton | A2,A3 | ||||||||
| Week 13 | Design Patterns - Strategy, Composite, Observer | A2,A3 | ||||||||
| Week 14 | Basic Software Architectures | Notes | ||||||||
| Week 15 | General Review | |||||||||
| Assessment Methods and Criteria | Evaluation Tool | Quantity | Weight | Alignment with LOs | AI Usage |
| Final Exam | 1 | 40 | 1,2,3,4,5 | Not Allowed | |
| Semester Evaluation Components | |||||
| Quizzes | 2 | 10 | 1,2,3,4,5 | Not Allowed | |
| Midterm | 1 | 20 | 1,2,4 | Not Allowed | |
| Labs-Assignments | 4 | 10 | 2,3,5 | Not Allowed | |
| Group Projects | 1 | 20 | 1,2,3,4,5 | Consult Instructor | |
| *** ECTS Credit Calculation *** | |||||
| Activity | Hours | Weeks | Student Workload Hours | Activity | Hours | Weeks | Student Workload Hours | |||
| Lecture Hours | 3 | 15 | 45 | Assignments | 5 | 4 | 20 | |||
| In-term Exam Stud | 11 | 1 | 11 | Quizzes | 4 | 4 | 16 | |||
| Home Study | 3 | 14 | 42 | Final Exam Study | 16 | 1 | 16 | |||
| Total Workload Hours = | 150 | |||||||||
| *T= Teaching, P= Practice | ECTS Credit = | 6 | ||||||||
| Course Academic Quality Assurance: Semester Student Survey | Last Update Date: 16/04/2026 | |||||||||