IIŞIK UNIVERSITY – Computer Engineering Department

SOFT3501 Requirements Analysis - Fall 2021

Catalog Data SOFT3501 – Requirements Analysis (3+0+0) 3, 6 ECTS

Textbook: Software Requirements, Karl Wiegers and Joy Beatty, 3rd edition (available
through Işık University Online Library, Safari Books Online)

Reference Requirements Analysis and System Design, Maciaszek, Leszek. Pearson Education, 3rd.
Book Ed.,

Instructor Asst. Prof. Emine Ekin, emine.ekin@isikun.edu.tr, Office: 331, Extension:

7144

Course Description:
Software Requirements and Types. Requirements Engineering Processes. Problem analysis and
Requirements Inception. Requirements elicitation, analysis, specification. Requirements
negotiation, prioritization. Use Case Models. Requirement analysis documentation.

Course Outcomes:
CO1. Identify the phases of requirements analysis.
CO2. Elicit requirements for a software system
CO3. Produce Requirements Analysis Document.
CO4. Verify and validate requirements
CO5. Trace and manage the changes in the requirements
CO6. Work in a team.
CO7. Model and analyze requirements, using the UML and other appropriate languages

Grading Policy:
Final Exam 20%
Midterm 20%
Homeworks (2 planned) 20%
Team project
 Completeness and correctness of work
done 40%
 Documentation
 Team working
 Tool usage

Project
As the course name implies, the project will be managing the requirements of a complex
software product. You will be using some tools to achieve this task.

You can't have great software without a great team, and most software teams behave like dysfunctional
families. --Jim McCarthy 
IIŞIK UNIVERSITY – Computer Engineering Department
SOFT3501 Requirements Analysis - Fall 2021

In general, team working doesn’t mean that one does the job, and the others have rest; or one
writes the documents, one develops the project. Instead, every group member must be involved
in any task. Since team working is one of the course outcomes, your attitudes as a team member
will also be graded.

Tentative Schedule

Week Topics
Introduction to the course

Introduction to RE, Requirements from the customer's perspective

Finding the voice of user, requirements elicitation

Understanding user requirements, documenting requirements

Data requirements

Requirements modeling

Risk reduction through prototyping

8 MIDTERM
Requirements negotiation and prioritization

Validating requirements

Requirements for specific project classes (agile, outsourced,

embedded etc.)
Tracing and Managing requirements

Project presentations

Project presentations

You can't have great software without a great team, and most software teams behave like dysfunctional
families. --Jim McCarthy