Course Name

1
Tên môn học
Course Code
2
Mã môn học
No of credits
3
Số tín chỉ
Degree Level
4
Cấp độ

Time Allocation
5
Phân bố giờ học

Pre-requisite
6
Điều kiện tiên quyết

Description
7
Mô tả

Learning Outcomes
Chuẩn đầu ra

LO1

LO2

LO3
8
LO4

695765681.xls
 8

LO5

LO6

LO7

LO8

LO9

Student's task
9
Nhiệm vụ của sinh viên

Teaching &
Learning
10 Materials
Tài liệu học tập và giảng
dạy

Assessment structure
11
Cấu trúc đánh giá

Scoring scale
12
Thang điểm

695765681.xls
 SYLLABUS/ ĐỀ CƯƠNG CHI TIẾT
(Under Decision No. 396/QĐ-ĐHFPT dated 12/4/2018)

SOFTWARE REQUIREMENTS

SWR302

Bachelor

Class hours: 30 slots - 1slot =90'

Lectures: 15 slots
Tutorials: 15 slots
Home study: 60 slots

SWE102

This course is a model-based introduction to RE, providing the conceptual background and
terminology on RE, addressing a variety of techniques for requirements development including
Analysis and Requirements Elicitation; Requirements Evaluation; Requirements Specification and
Documentation; Requirements Quality Assurance. To implement these frameworks, student will
be learnt how to find appropriate customer representatives, elicit requirements from them, and
document user requirements, business rules, functional requirements, data requirements, and
nonfunctional requirements.
The numerous visual models that will be represented to illustrate the requirements from various
perspectives to supplement natural-language text. Other contents recommend the most effective
requirements approaches for various specific classes of projects: agile projects developing
products of any type, enhancement and replacement projects, projects that incorporate packaged
solutions, outsourced projects, business process automation projects, business analytics projects,
and embedded and other real-time systems.

Upon successful completion of this course, students will be able to

Develop a good understanding of principles and techniques for requirement enginneering (RE)
regarding requirement inception, requirement development(elicitation, analysis, specification,
validation) and requirement management; understand main characteristics of specific projects

Identify the appropriate requirements elicitiation techniques to identify requirements

Utilize various requirements validation techniques to critically evaluate their requirements to

identify defects
Analysis of system requirements and the production of system specifications

695765681.xls
Create models of requirements using a variety of notations and techniques, including domain and
usage models
Design and plan software solutions to problems using an object-oriented strategy

Prepare and deliver coherent and structured verbal and written technical reports

Understand how to reduce risks by prototyping.

Utilize the tactic of requirements management regarding changing, tracing and improving
requirements

- Students must attend more than 80% of contact slots in order to be accepted to the final
examination.
- Student is responsible to do all exercises given by instructor in class or at home and submit on
time
- Constantly follow announcements on intranet/LMS at http://lms.fpt.edu.vn for up-to-date course
information regarding assignment submission and feedback on assignments and project work.

A) Main textbook/ resources:

1) Software Requirements Third Edition by Karl E. Wiegers, Microsoft Press, ISBN: 978-0-7356-
7966-5
2) Course slides (.pptx)
3) Document_GuideLines folder includes document template
4) COS_Document_Example folder includes Case studies illustrating the actual system.

B) Reference:
1. More About Software Requirements: Thorny Issues and Practical Advice by Karl E. Wiegers,
Microsoft Press, ISBN: 978-0-7356-2267-8

2. The Software Requirements Memory Jogger: A Pocket Guide to Help Software And Business
Teams Develop and Manage Requirements by Ellen Gottesdiener, GOAL/QPC, ISBN: 978-1-
57681-060-6 (www.MemoryJogger.org)

C) Technical facilities:
- Microsoft office for documents and presentation.
- BOUML (http://bouml.free.fr/) : UML Drawing software

1) On-going Assessment
- At least 3 progress tests: 30%
- 02 Assignments: 30%
2) Final exam (60'): 40%
3) Final Result: 100%

Completion Criteria:
1) Every on-going assessment component >0
2) Final Exam Score >=4 & Final Result >=5

10

695765681.xls
 Back to Syllabus COURSE SCHEDULE
Part Chapter Session
Topic/ Sub-topics Learning ITU level Materials
Chủ đề chính/ chủ đề con outcomes Mức ITU
Course Introduction

The essential of software requirement

1 1 - Software requirements defined LO1 Slides
- Requirements development and management I
- When bad requirements happen to good people
- Benefits from a high-quality requirements process

Requirements from the customer’s perspective

- Who is the customer?
- The customer-development partnership
LO1 I,T Chapter 2
2 2 - Creating a culture that respects requirement
- Identifying decision makers + Slides
R E Q U I R E M E N T S:
WHAT, WHY AND WHO

- Reaching agreement on requirements

I. S O F T W A R E

Assignment 1 introduction

Good practices for requirements engineering

- A requirements development process framework
- Requirements elicitation
Chapter 3
3 3 - Requirements analysis LO1, LO2 I,T
+Slides
- Requirements specification
- Requirements validation
- Requirements management

Group discussion
4
Summary and Exercises

The business analyst

- The business analyst role Chapter 4+ Business
4 - The business analyst’s tasks Analyst Job
Description.docx + Slides
- Essential analyst skills I,T, U
- Essential analyst knowledge
- The making of a business analyst
5 - The analyst role on agile projects

695765681.xls LO2,
LO4,LO5
 5

Establishing the business requirements

- Defining business requirements
- Vision and scope document LO2,
- Scope representation techniques LO4,LO5 Chapter 5 + Vision and
5 Scope Template.docx +
Slides
Establishing the business requirements (con't)
- Keeping the scope in focus
- Vision and scope on agile projects

Finding the voice of users

6 - User classes
- User personal Chapter 6 + Product
Champion
6 - Connecting with user representatives Responsibilities.docx +
- The product champion Slides
- User representation on agile project
- Resolving conflicting requirements

Requirements elicitation
- Requirements elicitation techniques: Interviews, workshops, 1. Use Case
Template.docx
Focus groups, Observations, Questionaires, System interface 2. Chapter 7 + 8
analysis, User Interface Analysis, Document Analysis +Slides
- Planning and Preparing for elicitation on your project
7 7 - Performing elicitation activities LO2, LO3
- Follow up after elicitation I,T, U
- Classifying customer input
- Some cautions about elicitation
- Assumed and implied requirements
- Finding missing requirements
Understanding user requirements
- Use cases and user stories
8 8 LO5,LO6 T,U
- The use case approach
- Benefits of usage-centric requirements

1
Playing by the rules 1.Software Requirements

T
Specification
- A business rules taxonomy Template.docx
- Documenting business rules 2. Chapter 9 + 10
- Discovering business rules N +Slides
9 9 - Business rules and requirements LO4,LO5 T,U
E

- Tying everything together

M

Progress test 1 and Review

N
E N T

695765681.xls
I
S
 E
M
N
Documenting the requirements
D E V E L O P M E N T

G
- The software requirements specification
10 10 LO7 T,U
- A software requirements specification template

I
- Requirements specification on agile projects

S
Writing excellent requirements
- Characteristics of excellent requirements

S
11
- Guidelines for writing requirements
- Sample requirements, before and after

A
11
A picture is worth 1024 words Chapter 11 + 12
- Data flow diagram; Swimlane diagram; State-transition diagram LO5 T,U + Slides
and state table ; Dialog map ;
12
A picture is worth 1024 words (con't)
12 - Decision tables and decision trees; Event-response tables ;
II. R E Q U I R E M E N T S

Modeling on agile projects

Specifying data requirements

- Modeling data relationships
1.Guidance for Data
- The data dictionary
13 13 Dictionaries.docx
- Data analysis 2.Chapter 13
- Specifying reports +Slides

Beyond functionality
- Software quality attributes LO5 T,U
- Exploring quality attributes
- Defining quality requirements
14 14 - Specifying quality requirements with Planguage Chapter 14 + Slides
- Quality attribute trade-offs
- Implementing quality attribute requirements
- Constraint
- Handling quality attributes on agile projects

Risk reduction through prototyping

- Prototyping: What and why
- Mock-ups and proofs of concept
- Throwaway and evolutionary prototypes
15 15 - Paper and electronic prototypes LO8 T,U Chapter 15 + Slides
- Working with prototypes
- Prototype evaluation
- Risks of prototyping
- Prototyping success factors

695765681.xls
 Risk reduction through prototyping
- Prototyping: What and why
- Mock-ups and proofs of concept
- Throwaway and evolutionary prototypes
15 15 - Paper and electronic prototypes LO8 T,U Chapter 15 + Slides
- Working with prototypes
- Prototype evaluation
- Risks of prototyping
- Prototyping success factors

First things first: Setting requirement priorities

- Why prioritize requirements? 1. Requirements
- Some prioritization pragmatics Prioritization
16 16 LO2 T,U Spreadsheet.docx
- Games people play with priorities
2. Chapter 16
- Some prioritization techniques + Slides
- Prioritization based on value, cost, and risk

Validating the requirements

- Validation and verification
- Reviewing requirements 1. Requirements Review
17 17 - Prototyping requirements LO3 T Checklist.docx
- Testing the requirements 2. Chapter 17
+Slides
- Validating requirements with acceptance criteria

Requirements reuse
- Why reuse requirements?
- Dimensions of requirements reuse
- Types of requirements information to reuse
18 - Common reuse scenarios
- Requirement patterns
1. Chapter 18 + 19
18 - Tools to facilitate reuse LO3, LO5 I,T,U 2. Requirements
- Making requirements reusable Estimation Tool.xlsx
- Requirements reuse barriers and success factors +Slides

Beyond requirements development

- Estimating requirements effort
19
- From requirements to project plans,designs and code, tests,
success
CLASS

19 Assignment 1 Review and Evaluation Oral test Assignment 1 documents

ECT

695765681.xls
CLASS
Assignment 2 Introduction
20 Quiz test LSM questions
Progress test 2 and Review
PROJECT

Agile projects
- Limitations of the waterfall
- The agile development approach
20
- Essential aspects of an agile approach to requirements
- Adapting requirements practices to agile projects
- Transitioning to agile: Now what?
21 LO4 I,T,U Chapter 20 + 21 +Slides
FOR SPECIFIC

Enhancement and replacement projects

- Expected challenges
- Requirements techniques when there is an existing system
21
- Prioritizing by using business objectives
- When old requirements don’t exist
ES

- Encouraging new system adoption

Packaged solution projects

- Requirements for selecting packaged solutions
22
- Requirements for implementing packaged solutions
- Common challenges with packaged solution
1. Chapter 22 + 23
III. R E Q U I R E M E N T S

22 Outsourced projects LO4 I,T,U 2. Request for Proposal

Template.docx
- Appropriate levels of requirements detail 3. Slides
23 - Acquirer-supplier interactions
- Change management
- Acceptance criteria
24 Group discussion 1. Chapter 24 + 25 +
23 Slides
25 Summary and Exercises

26
24 Assignment 2 supporting 1. Chapter 26 + Slides

2
Requirements management practices

T
- Requirements management process
- The requirements baseline
N
- Requirements version control
27 25 - Requirement attributes LO9 I,T,U
E
MANAGEMENT

- Tracking requirements status

M

- Resolving requirements issues

- Measuring requirements effort
- Managing requirements on agile projects
N
G

695765681.xls 1. Chapter 25 + 26 + 27
2. a. CCB Charter
I

Template.docx
 2
Requirements management practices

T
- Requirements management process
- The requirements baseline

N
- Requirements version control
27 25 - Requirement attributes LO9 I,T,U

E
MANAGEMENT

- Tracking requirements status

M
- Resolving requirements issues
- Measuring requirements effort
- Managing requirements on agile projects

N
G
Change happens 1. Chapter 25 + 26 + 27
2. a. CCB Charter

I
- Change control policy Template.docx
- Basic concepts of the change control process

S
b. Change Control
IV. R E Q U I R E M E N T S

- A change control process description Process.docx

28 26 - The change control board c. Impact Analysis

S
Checklist.docx
- Change control tools LO9 I,T,U

A
- Measuring change activity 3. Slides
- Change impact analysis
- Change management on agile projects

Links in the requirements chain

- Tracing requirements
- Motivations for tracing requirements
29 27 LO9 I,T,U
- The requirements traceability matrix
- Tools for requirements tracing
- A requirements tracing procedure

30 Tools for requirements engineering (self-study)

Improving your requirements processes
- How requirements relate to other project processes
V.IMPLEMENTING REQUIREMENTS

- Requirements and various stakeholder groups

- Gaining commitment to change
- Fundamentals of software process improvement 1. Chapter 31,32
31 - Root cause analysis 2. Action Plan
- The process improvement cycle Template.docx
ENGINEERING

28 LO8, LO9 I,T,U 3. Risk Management Plan

- Requirements engineering process assets
Template.docx
- Creating a requirements process improvement road map 4. Slides
Software requirements and risk management
- Fundamentals of software risk management
- Requirements-related risks
32
- Risk management is your friend

695765681.xls
 ENGINEE
V.IMPLEMENTING 32 29
Progress test 3
Assignment 2 evaluation
Oral test +
30 Assignment 2 documents
Quiz test

FINAL EXAM

695765681.xls
 Activitiy
Hoạt động dạy và học Số bài học

Ch #S PP

1 3 50 1

do homework

2 3 25 0.5
3 3 Q1 30
4 4 70

do homework

5 3 A1 30 1

Discuss what students have

to do in their Assignment 1

0.5

695765681.xls
Write Vision and Scope for 7 2 30 0.5
Assignment1

8 4 Q2 45 0.5

Practice on Assignment 1

10 II.Require 35 0.5
11 1 Q3 30

Finish Use Case document

12 3 30 1
A2

Preparing the structure of

SRS document (based on 1 0.5
student's assignment)
27

695765681.xls
Preparing the structure of
SRS document (based on
student's assignment)

0.5

Write SRS document based

on guidelines

0.5

1
Finish Data Dictionaries of
Assignment 1

Finish Requirements
Prioritization worksheet

695765681.xls
 Finish Requirements
Prioritization worksheet
1

Check Assignment 1's

requirements

Do requirements estimation

0.5

0.5
`

695765681.xls
 `

Do assignment 2 - the first 0.5

taks

0.5

Requirements for specific pro 0.5

Read and understand the
proposal template ( what are
contents and the purpose of
these ones)

0.5

Checking SRS document

695765681.xls
 1

Do assignment 2 - based on
guidelines

Finish assignment2 's

documents
1

695765681.xls
Finish assignment2 's
documents

22

695765681.xls
 ASSESSMENT STRUCTURE/ CẤU TRÚC ĐÁNH GIÁ
Scope of
knowledge
Assessment Number of and skill of
Learning Type of
Category Part Weight Duration questions questions How?
Outcomes questions
Hạng mục đánh Phần Trọng số Thời lượng Số lượng Phạm vi kiến Cách thức đánh giá?
Đầu ra Loại câu hỏi
giá câu hỏi thức và kỹ
năng của câu
hỏi
Test 1:
LO1, LO2,
LO3, LO4,
Multiple Test 1: Chapter
LO5, LO6
choices 1-> Chapter 9
Test 2:
Marked by Test 2: Chapter
Progress Test 3 30% 30'/each LO2, 30/each in class, by LMS system
Computer or a 10 ->20
LO3,LO5,L
suitable format Test 3: Chapter
O7,LO8
21 -->32
Test 3:
LO4,LO8,Teacher raise
LO9 projects,
students
practice step
by step to
Depending
complete their
on
14slots/ assignments. All subjects in
Assignment 2 30% LO1->LO8 questions in in class, by teacher
each Student could syllabus
every
base on study
assignment
guide
COS_Docume
Multiple
nt_Example to
choices
do All subjects in
Final Exam 1 40% 60'/each LO1->LO9 Marked by
assignments. 60 LSM system
syllabus
Computer

02.01a-BM/CT/HDCV/FE 1/1 19/22

Lưu ý: Khi sử dụng biểu mẫu, có thể thay thế logo tương ứng của khối.

02.01a-BM/CT/HDCV/FE 1/1 20/22

 Note
Ghi chú

Instruction and schedules for

Progress Tests must be presented in
the Course Implementation Plan
approved by director of the campus.
Progress test must be taken right
after the last lectures of required
material.
Instructor has responsibility to review
the test for students after graded.

The exam questions must be

updated or different at least 70% to
the previous ones.

02.01a-BM/CT/HDCV/FE 1/1 21/22

 ITU TERM
Introduce:
Intent: Touch on or briefly expose the students to this topic

Relationship to learning objectives: No specific learning objective of knowledge retention is linked to this t
Time: Typically less than one hour of dedicated lecture/discussion/laboratory time is spent on this topic

Relationship to assignments: No assignments/exercises/projects/homework are specifically linked to this t

Relationship to assessment: This topic would probably not be assessed on a test or other evaluation instr

Example: At the beginning of class an example is given of the operation of an engineering system to mot
aspect of the design. But, no explicit discussion of the design or analysis of operation is presented
Example: An ethical problem or dilemma is presented to the students that sets the context for an example
lecture. But, no explicit treatment of ethics or its role in modern engineering practice is presented.

Teach:
Intent: Really try to get students to learn new material
Relationship to Learning objective: is to advance at least one cognitive level (e.g. no exposure to knowled
knowledge to comprehension, comprehension to application, etc.)
Time: Typically 1 or more hours of dedicated lecture/discussion/laboratory time are spent on this topic:
Relationship to assignment: Assignments/exercises/projects/homework are specifically linked to this topic
Relationship to assessment: This topic would probably be assessed on a test or other evaluation instrume

Example: The process and methodology of product design are explicitly presented to and exercised by
students on a project or assignment.
Utilize:
Intent: Assumes the student already has a certain level of proficiency in this topic
Time: No time explicitly allotted to teaching this topic
Relationship to assessment:Tests are not designed to explicitly assess this topic
Example: When working in a laboratory session, students are expected to utilize their skills of
experimentation. But, no further explicit instruction on techniques of experimentation are given.

02.01a-BM/CT/HDCV/FE 1/1