AMERICAN INTERNATIONAL UNIVERSITY-BANGLADESH

Faculty of Science & Information Technology

Department of Computer Science
Undergraduate Program

COURSE OUTLINE

I- Course Code and Title: CSC4126: Software Requirement Engineering

II - Credit: 3
III - Nature: Major Course for CSSE, SE; Elective for CSE, CS, CIS
IV- Prerequisite: CSC3114: Software Engineering

V- Course Description:
Despite the wealth of development knowledge, experience, and tools available today, a substantial
percentage of software projects fail, often because requirements are not correctly determined and
defined at the outset, or are not managed correctly as the project unfolds. This course focuses on this
critical cause of failure and offers a practical, proven approach to building systems that meet
customers' needs on time and within budget.

In this course the students will learn how analysts and developers can effectively identify, analyze,
prioritize, document, and validate requirements by applying a variety of techniques.

VI – Objectives:
The objective of the course is to introduce students with the basic of software requirements, the
various perspectives of requirements, business modeling and system engineering, techniques for
eliciting requirements, establishing and managing project scope, product management, transitioning
from requirements to design and implementation and agile requirements methods.

1
VII – Topics to be covered
TOPICS Specific Time Suggested Teaching
Objective(s) Frame Activities Method(s)
 Mission and Make the student Week 1 Lecture Informative
Vision of AIUB. understand about how this and
 Introduction to course adjust with the Interactive
the course. mission and vision of session
AIUB and the
corresponding Faculty
 Software Understand the essentials Week 1 Lecture Lecture
Requirements of software requirement Delivery &
Basics Interactive
session
 Who are Requirements perspective Week 2 Lecture Lecture
involved with from customer’s view Delivery &
Software point, the good practices Interactive
Requirements and the role of Business session
and the Analyst
associated
practices
 Software Establishing the business Week 2 & 3 Lecture Lecture
Requirements requirements, identifying Delivery &
Elicitation users, requirements Interactive
elicitation and session
understanding user
requirements
 Documenting Understanding business Week 3 & 4 Lecture Lecture
Requirements rules, how to document Delivery &
requirements and how to Interactive
specify data requirements. session
Midterm Week
Week 5
 Finalizing Requirements Week 6 Lecture Lecture
Requirements prototyping, setting Delivery &
Development priorities, validating Interactive
requirement, requirements session
reuse and application of
requirements to other
phases of software
development
 Project Class Agile Projects, Week 7 and 8 Lecture Lecture
Specific Evolutionary Projects, Delivery &
Requirements Packaged Projects, Interactive
Outsourced Projects, session
Business process
automation, Embedded
and real-time systems

2
TOPICS Specific Time Suggested Teaching
Objective(s) Frame Activities Strategy(s
)
 Requirements Management practices, Week 9 & 10 Lecture Lecture
Management requirement engineering Delivery &
tools Interactive
session

 Implementing Improvement of Week 11 Lecture Lecture

Requirement requirement process, Risk Delivery &
Engineering management Interactive
session

Final Week
Week 12
PROJECT SUBMISSION & PRESENTATION
Week 15

VIII - Course Requirements

1. Student Attendance
All students are expected to attend all scheduled classes as well as mandatory counselling, and
to read all assigned chapters / materials before coming to class. 80% Attendance is mandatory
to pass the course.

2. Class Participation & Peer Evaluation

Students are expected to participate actively in the class. Your contribution towards your team
will be counted.

3. Quiz & Exam

For both terms, there will be at least 2 quizzes of which the best quiz performance will be
counted for term grading. The details will be announced in due time.

4. Assignments
For both terms, there will be assignments based on the given project proposal. Groups will be
created and members will be assigned by the instructor.

5. Final Project
Software Requirements Specification (SRS) Document on the Assigned Projects and
Presentation after the final weeks of the semester.

3
IX – Evaluation
Attendance and mandatory counselling 10%
Quizzes 40%
Assignments/Project 10%
Examination 40%
TOTAL 100%
Semester Grade: 40% midterm + 40% final term + 20%
project

X – Textbook/ Reference Materials

1. Software Requirements, Third Edition, by Karl E. Wiegers, ISBN: 978-0-7356-7966-5,

Microsoft Press © 2013.

2. Managing Software Requirements: A Use Case Approach, Second Edition, By Dean

Leffingwell, Don Widrig. Publisher: Addison Wesley (Object technology Series), Pub Date:
May 05, 2003, ISBN: 0-321-12247-X.

3. Managing Software Requirements: A Unified Approach, Second Edition, By Dean

Leffingwell, Don Widrig, Publisher: Addison Wesley (Object technology Series), Pub Date:
Nov 2000, ISBN: 0-321-12247-X.

4. Software Requirement Patterns, by Stephen Withall, ISBN: 978-81-7853-124-3, Microsoft

Press © 2007.

5. Software Engineering – A practioners approach, Latest Edition, by Pressman.

6. Software Engineering, Latest Edition, by Ian Sommerville.

7. http://www.agilemodeling.com/artifacts/userStory.htm

8. http://www.romanpichler.com/blog/10-tips-writing-good-user-stories/

9. https://help.rallydev.com/writing-great-user-story

10. https://www.mountaingoatsoftware.com/presentations/introduction-to-user-stories