CS308 Software Engineering
CS308 Software Engineering
Syllabus | International University of Sarajevo - Last Update on Apr 04, 2026
Syllabus Quick Jump
Search and navigate to any syllabus instantly
Computer Sciences and Engineering
Özge Büyükdağlı
Course Lecturer
Course Objectives
"The aims of this course are to: • demonstrate the key elements of software development process as practiced in the industry • demonstrate the process of planning and writing documentation relevant to the development of software applications • present the tools used in making of quality software"
Learning Outcomes
After successful completion of the course, the student will be able to:
Course Materials
Required Textbook
Software Engineering, Ian Sommerville, 10E. ISBN-10: 0134572793 • ISBN-13: 9780134572796
Additional Literature
HandoutsTeaching Methods
Class discussions with examples
Active tutorial sessions for engaged learning and continuous feedback on progress
Weekly Topics
| Week | Topic | Readings / References |
|---|---|---|
| 1 | Introduction | 1 |
| 2 | Software Processes | 2 |
| 3 | Agile Software Development, (Project Proposal submission) | 3 |
| 4 | Requirements Engineering (Project pitch) | 4 |
| 5 | Systems Modelling | 5, 7 (parts of chap 7) + Hand-outs |
| 6 | Design and Implementation (Requirements submission) | 7, + Hand-outs |
| 7 | MIDTERM EXAM | |
| 8 | Design and Impementation (cont). Design Patterns | 7, + Hand-outs |
| 9 | Architectural Design; (Design doc submission) | 6, + Hand-outs |
| 10 | Software Testing; Iteration I (Functional prototype Presentations and | 8 + Hand outs |
| 11 | Project Management; Project Planning, Quality Management, Configuration Management | 22,23,24,25 |
| 12 | Software Evolution, Dependable systems, Reliability Engineering (Project Discussion) | 9,10,11 |
| 13 | Working on projects, consultations | |
| 14 | Project Presentations and submission of final report and code | |
| 15 | Review for the Final Exam |
Course Schedule (All Sections)
| Section | Type | Day 1 | Venue 1 | Day 2 | Venue 2 |
|---|---|---|---|---|---|
| CS308.1 | Course | Thursday 10:00 - 11:50 | B F1.23 - Amphitheater I | Tuesday 12:00 - 12:50 | B F1.23 - Amphitheater I |
| CS308.1 | Tutorial | Thursday 12:00 - 13:50 | B F1.8 | - | - |
| CS308.2 | Tutorial | Wednesday 09:00 - 10:50 | A F1.4 - Class/Laboratory | - | - |
| CS308.3 | Tutorial | Friday 09:00 - 10:50 | B F1.25 Computer Lab | - | - |
Office Hours & Room
| Day | Time | Office | Notes |
|---|---|---|---|
| Tuesday | 09:00 - 12:00 | A F2.28 | |
| Thursday | 14:00 - 17:00 | A F2.28 |
Assessment Methods and Criteria
Assessment Components
Final Exam
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3 4
Project
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3 4 5
Midterm exam
AI: Not AllowedAlignment with Learning Outcomes : 1 3 4
Lab
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3 4
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)
Active Tutorials
26 hours ⏳ (13 week × 2 h)
Home Study
26 hours ⏳ (13 week × 2 h)
In-term Exam Study
8 hours ⏳ (1 week × 8 h)
Final Exam Study
9 hours ⏳ (1 week × 9 h)
Term Project / Presentation
36 hours ⏳ (12 week × 3 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 [CS308] 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 | |||||||||
| CS308 | Software Engineering | 3 | 2 | 6 | ||||||
| Prerequisite | CS306 | It is a prerequisite to | CS426 | |||||||
| Lecturer | Özge Büyükdağlı | Office Hours / Room / Phone | Tuesday: 9:00-12:00 Thursday: 14:00-17:00 |
|||||||
| obuyukdagli@ius.edu.ba | ||||||||||
| Assistant | Adna Dedic | Assistant E-mail | 250302287@student.ius.edu.ba | |||||||
| Course Objectives | "The aims of this course are to: • demonstrate the key elements of software development process as practiced in the industry • demonstrate the process of planning and writing documentation relevant to the development of software applications • present the tools used in making of quality software" |
|||||||||
| Textbook | Software Engineering, Ian Sommerville, 10E. ISBN-10: 0134572793 • ISBN-13: 9780134572796 | |||||||||
| 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 for engaged learning and continuous feedback on progress. | |||||||||
| Teaching Method Delivery | Online | Teaching Method Delivery Notes | ||||||||
| WEEK | TOPIC | REFERENCE | ||||||||
| Week 1 | Introduction | 1 | ||||||||
| Week 2 | Software Processes | 2 | ||||||||
| Week 3 | Agile Software Development, (Project Proposal submission) | 3 | ||||||||
| Week 4 | Requirements Engineering (Project pitch) | 4 | ||||||||
| Week 5 | Systems Modelling | 5, 7 (parts of chap 7) + Hand-outs | ||||||||
| Week 6 | Design and Implementation (Requirements submission) | 7, + Hand-outs | ||||||||
| Week 7 | MIDTERM EXAM | |||||||||
| Week 8 | Design and Impementation (cont). Design Patterns | 7, + Hand-outs | ||||||||
| Week 9 | Architectural Design; (Design doc submission) | 6, + Hand-outs | ||||||||
| Week 10 | Software Testing; Iteration I (Functional prototype Presentations and | 8 + Hand outs | ||||||||
| Week 11 | Project Management; Project Planning, Quality Management, Configuration Management | 22,23,24,25 | ||||||||
| Week 12 | Software Evolution, Dependable systems, Reliability Engineering (Project Discussion) | 9,10,11 | ||||||||
| Week 13 | Working on projects, consultations | |||||||||
| Week 14 | Project Presentations and submission of final report and code | |||||||||
| Week 15 | Review for the Final Exam | |||||||||
| Assessment Methods and Criteria | Evaluation Tool | Quantity | Weight | Alignment with LOs | AI Usage |
| Final Exam | 1 | 30 | 1,2,3,4 | Not Allowed | |
| Semester Evaluation Components | |||||
| Project | 1 | 35 | 1,2,3,4,5 | Not Allowed | |
| Midterm exam | 1 | 20 | 1,3,4 | Not Allowed | |
| Lab | 3 | 15 | 1,2,3,4 | Not Allowed | |
| *** ECTS Credit Calculation *** | |||||
| Activity | Hours | Weeks | Student Workload Hours | Activity | Hours | Weeks | Student Workload Hours | |||
| Lecture Hours | 3 | 15 | 45 | Active Tutorials | 2 | 13 | 26 | |||
| Home Study | 2 | 13 | 26 | In-term Exam Study | 8 | 1 | 8 | |||
| Final Exam Study | 9 | 1 | 9 | Term Project / Presentation | 3 | 12 | 36 | |||
| Total Workload Hours = | 150 | |||||||||
| *T= Teaching, P= Practice | ECTS Credit = | 6 | ||||||||
| Course Academic Quality Assurance: Semester Student Survey | Last Update Date: 16/04/2026 | |||||||||