SE322 Software Requirements Analysis
Syllabus | International University of Sarajevo - Last Update on Oct 10, 2025
Syllabus Quick Jump
Search and navigate to any syllabus instantly
Software Engineering
Mohammed Saeed Jawad
Course Lecturer
Course Objectives
Understand the purpose and processes of software requirements engineering in the software development lifecycle. Apply structured techniques to elicit and clarify stakeholder and business needs. Model and document functional and non-functional requirements within a Software Requirements Specification (SRS). Analyze and validate requirements for clarity, completeness, consistency, and feasibility. Prioritize, negotiate, and manage changing requirements in traditional and agile projects. Demonstrate effective teamwork and communication in the requirements process.
Learning Outcomes
After successful completion of the course, the student will be able to:
Course Materials
Required Textbook
Pohl, K., & Rupp, C. (2022). Requirements Engineering: Fundamentals, Principles, and Techniques (3rd ed.). Springer. ISBN 978-3-030-87328-0
Additional Literature
Beatty, J., & Wiegers, K. (2022). Software Requirements Essentials: Core Practices for Successful Business Analysis. Addison-Wesley. Larman, C. (2004). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd ed.). Pearson Education. (Reference for modeling.)Teaching Methods
Lectures
Interactive discussions
Case-based exercises
Guided elicitation workshops
Group SRS project
Peer review
And oral presentation.
Weekly Topics
| Week | Topic | Readings / References |
|---|---|---|
| 1 | Introduction to requirements engineering; overview of the course and SRS process | Ch. 1–2 |
| 2 | Requirements engineering concepts, roles, and stakeholders | Ch. 3 |
| 3 | Stakeholder goals and requirement categories (functional vs non-functional) | Ch. 4–5 |
| 4 | Business analysis and project vision; problem definition and scope | Ch. 6 |
| 5 | Requirements elicitation techniques (interviews, workshops, observation) | Ch. 7 |
| 6 | Documenting and modeling requirements (use cases, UML, textual templates) | Ch. 8–9 |
| 7 | MIDTERM | |
| 8 | Validation and negotiation of requirements; conflict resolution | Ch. 10 |
| 9 | Quality attributes and prioritization methods | Ch. 11–12 |
| 10 | Modeling and use cases for requirement clarification | Ch. 13 |
| 11 | Requirements management and traceability | Ch. 15 |
| 12 | Requirements in agile and hybrid projects | Ch. 16 |
| 13 | Project presentations – SRS walk-through and peer review | Project documentation |
| 14 | Final presentations and course wrap-up | Project documentation |
| 15 | Final Review before Final | Review |
Course Schedule (All Sections)
| Section | Type | Day 1 | Venue 1 | Day 2 | Venue 2 |
|---|---|---|---|---|---|
| SE322.1 | Course | Tuesday 09:00 - 11:50 | B F1.23 - Amphitheater I | - | - |
| SE322.1 | Tutorial | Friday 16:00 - 17:50 | B F1.23 - Amphitheater I | - | - |
| SE322.2 | Tutorial | Thursday 18:00 - 19:50 | B F2.17 | - | - |
Office Hours & Room
Assessment Methods and Criteria
Assessment Components
Final Exam
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3
Quizzes
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3 4 5
In-term examination
AI: Not AllowedAlignment with Learning Outcomes : 1
Project
AI: Not AllowedAlignment with Learning Outcomes : 1 2 3 4 5
Labs
AI: Not AllowedAlignment 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)
Project
36 hours ⏳ (12 week × 3 h)
Home studies
42 hours ⏳ (14 week × 3 h)
In-term Exam study
12 hours ⏳ (1 week × 12 h)
Final Exam Study
15 hours ⏳ (1 week × 15 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 [SE322] 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 Oct 10, 2025 | International University of Sarajevo
Print Syllabus
Referencing Curricula Print this page
| Course Code | Course Title | Weekly Hours* | ECTS | Weekly Class Schedule | ||||||
| T | P | |||||||||
| SE322 | Software Requirements Analysis | 3 | 2 | 6 | ||||||
| Prerequisite | CS105 | It is a prerequisite to | - | |||||||
| Lecturer | Mohammed Saeed Jawad | Office Hours / Room / Phone | Currently not available |
|||||||
| msjawad@ius.edu.ba | ||||||||||
| Assistant | Hamza Sušić | Assistant E-mail | ||||||||
| Course Objectives | Understand the purpose and processes of software requirements engineering in the software development lifecycle. Apply structured techniques to elicit and clarify stakeholder and business needs. Model and document functional and non-functional requirements within a Software Requirements Specification (SRS). Analyze and validate requirements for clarity, completeness, consistency, and feasibility. Prioritize, negotiate, and manage changing requirements in traditional and agile projects. Demonstrate effective teamwork and communication in the requirements process. |
|||||||||
| Textbook | Pohl, K., & Rupp, C. (2022). Requirements Engineering: Fundamentals, Principles, and Techniques (3rd ed.). Springer. ISBN 978-3-030-87328-0 | |||||||||
| Additional Literature |
|
|||||||||
| Learning Outcomes | After successful completion of the course, the student will be able to: | |||||||||
|
||||||||||
| Teaching Methods | Lectures, interactive discussions, case-based exercises, guided elicitation workshops, group SRS project, peer review, and oral presentation. | |||||||||
| Teaching Method Delivery | Face-to-face | Teaching Method Delivery Notes | ||||||||
| WEEK | TOPIC | REFERENCE | ||||||||
| Week 1 | Introduction to requirements engineering; overview of the course and SRS process | Ch. 1–2 | ||||||||
| Week 2 | Requirements engineering concepts, roles, and stakeholders | Ch. 3 | ||||||||
| Week 3 | Stakeholder goals and requirement categories (functional vs non-functional) | Ch. 4–5 | ||||||||
| Week 4 | Business analysis and project vision; problem definition and scope | Ch. 6 | ||||||||
| Week 5 | Requirements elicitation techniques (interviews, workshops, observation) | Ch. 7 | ||||||||
| Week 6 | Documenting and modeling requirements (use cases, UML, textual templates) | Ch. 8–9 | ||||||||
| Week 7 | MIDTERM | |||||||||
| Week 8 | Validation and negotiation of requirements; conflict resolution | Ch. 10 | ||||||||
| Week 9 | Quality attributes and prioritization methods | Ch. 11–12 | ||||||||
| Week 10 | Modeling and use cases for requirement clarification | Ch. 13 | ||||||||
| Week 11 | Requirements management and traceability | Ch. 15 | ||||||||
| Week 12 | Requirements in agile and hybrid projects | Ch. 16 | ||||||||
| Week 13 | Project presentations – SRS walk-through and peer review | Project documentation | ||||||||
| Week 14 | Final presentations and course wrap-up | Project documentation | ||||||||
| Week 15 | Final Review before Final | Review | ||||||||
| Assessment Methods and Criteria | Evaluation Tool | Quantity | Weight | Alignment with LOs | AI Usage |
| Final Exam | 1 | 25 | 1,2,3 | Not Allowed | |
| Semester Evaluation Components | |||||
| Quizzes | 2 | 10 | 1,2,3,4,5 | Not Allowed | |
| In-term examination | 1 | 25 | 1 | Not Allowed | |
| Project | 1 | 30 | 1,2,3,4,5 | Not Allowed | |
| Labs | 6 | 10 | 1,2,3,4,5 | Not Allowed | |
| *** ECTS Credit Calculation *** | |||||
| Activity | Hours | Weeks | Student Workload Hours | Activity | Hours | Weeks | Student Workload Hours | |||
| Lecture Hours | 3 | 15 | 45 | Project | 3 | 12 | 36 | |||
| Home studies | 3 | 14 | 42 | In-term Exam study | 12 | 1 | 12 | |||
| Final Exam Study | 15 | 1 | 15 | |||||||
| Total Workload Hours = | 150 | |||||||||
| *T= Teaching, P= Practice | ECTS Credit = | 6 | ||||||||
| Course Academic Quality Assurance: Semester Student Survey | Last Update Date: 26/10/2025 | |||||||||