COURSE OUTLINE

Course ID Course Title Credits

Công nghệ phần mềm
SW210DE01 03
Software Engineering

(Applied to Semester: 1A, Academic year 2023-2024

Decision No. . . . ./QĐ-ĐHHS dated . . . . . .)

A. Course Specifications:
Periods Periods in classroom
Self-
Total Lecture/ Lecture
Activity study Lab room Fieldwork
periods* Seminar room
periods
(1) (2) (3) (4) (5) (6) (7)
45 45 0 120 45 0 0
(1) = (2) + (3) = (5) + (6) + (7)

B. Other related Subjects:

Related Course ID Course Title
Previous subject:
1. SW103D Lập trình hướng đối tượng
Phân tích, thiết kế và phát triển hệ
or IT208D
thống hướng đối tượng

C. Course Description:
The course aims to provide students with a background in software development processes
and steps, and to equip students with a basic understanding of how to evaluate, analyze, and
implement project according to the process.

D. Course Objectives:
No. Course Objectives
1 Provide students with software development engineering background.
Help students apply appropriate development models, analysis techniques,
2
design, programming, ... to build software projects in the right process.

E. Course Learning Outcomes:

Students that successfully complete the course will be able to:
No. Course Learning Outcomes PLOs
Present basic knowledge of principles, methodology, processes PLO4(4)
CLO1
and techniques for building software projects.
Describe the problems involved in the software development PLO4(4)
CLO2
process.
CLO3 Know software development team PLO5(3)
CLO4 Develop a project implementation plan PLO4(4)

Trang 1 / 9
F. Instructional Modes:
Room Periods
1 Lecture room 30
2 Computer Lab 30
Total 60
Requirements:
● Language used for teaching and learning: Vietnamese.

● Lecturers can ask that English be used for the following cases: learning materials;
lecture slides; multiple choice questions in quiz, quiz, or final exam questions;
project report presentation.
● Requirements for students when participating in the subject: Students are divided
into small groups to do exercises and practice on the subject.
● How to organize the teaching of the subject:

STT Teaching Short description Periods

method
1 Lecture Before going to class, students should 45
read at home the chapters of the syllabus
specified in the outline. In class, the
teacher emphasizes concepts and
important or difficult issues of each
chapter. Lecturer gives some main topics
of the subject, students divide groups and
choose topics to learn first, then discuss in
class.
2 Group Lecturer in charge of practice will divide
work students into small groups (3-5 students),
each group will receive 1 project assigned
by lecturer. Lecturer will give specific
requirements for each practice session of
the project, at the end of the session,
students will return the results to lecturer
for evaluation. At the end of the semester,
the groups must complete the project and
submit it to the teacher in charge. lecturer
will base on the results of each week and
the final results to score each group.

G. Textbooks and teaching aids:

1. Textbooks:
[1] Ian Sommerville, Software Engineering 8e, Addison-Wesley, 2007
2. References:
[2] Roger S.Pressman (Ph.D.) , Software Engineering.
3. Software:
IBM Rational Rose V7.0, MS Project, MS Word, Excel, Visual studio 2008/2010…

Trang 2 / 9
H. Assessment Methods (Requirements for Completion of the Course):
1. Description of learning outcomes assessment
Students studying the "Software Engineering" course will be assessed on 4 forms:
a) Case study
- Students are divided into groups of 3-5 each. Each group will be assigned a case study in
week 1 for in-class presentation starting week 5. The group is also required to submit to
the lecturer the materials prepared for the reporting session one week before present.
- This score will be divided into 3 parts: 40% for the group's results, 40% for the effort of
each member contributing to the group and 20% for presenting and demonstrating
understanding of the group. when answering questions from teachers and classmates. If a
member feels another team member is not contributing, he must notify the trainer to
resolve it. In extreme cases, students may ask to do it on their own. However, any
complaints about the group must be reported to the instructor no later than week 4.
- 1 point will be deducted if the submission is late. If it is more than 1 week late, the group
gets a zero.
b) Final Project
Students work in group projects (3-5 students) to apply and check the knowledge they
have learned in real projects. Each group of students will work on one topic during their
practice in the Lab. Performance and results will be evaluated by the trainer.
c) Homework Assignments
There will be regular homework assignments on the topics covered in class, with
approximately 2 homework assignments.
2. Summary of learning outcomes assessment

Component Duratio Percentag

Assessment Forms Schedule
s n e
Case study - 30 Group presentation (3-5 Week 5- 13
Seminar minutes people) about topics related
20%
to course in the theorical
time
Homework Doing homework instructed Week 5-12
30%
Assignments by lecturer
Final Doing project instructed by 50%
Project lecturer
Total 100%

I. Academic integrity
Academic integrity is a fundamental value that affects the quality of teaching, learning, and
research at a university. To ensure the maintenance of academic integrity at Hoa Sen University,
students are required to:
1. Work independently on individual assignments: Collaborating on individual assignments
is considered cheating.
2. Avoid plagiarism: Plagiarism is an act of fraud that involves the use of ideas or words of
another person without proper attribution. Students will be accused of plagiarism if they:
a. Copy in their work one or more sentences from another person without proper
citation.
b. Rephrase, paraphrase, or translate another person’s ideas or words without proper
attribution.

Trang 3 / 9
 c. Reuse their own assignments, in whole or in part, and submit them for another class.
d. Work responsibly within a working group.
3. In cooperative group assignments, all students are required to stay on task and contribute
equally to the projects. Group reports should clearly state the contribution of each group
member. Any acts of academic dishonesty will result in a grade of zero for the task at hand
and/or immediate failure of the course, depending on the seriousness of the fraud. Please
consult Hoa Sen University’s Policy on Plagiarism at http://thuvien.hoasen.edu.vn/chinh-
sach-phong-tranh-dao- van
To ensure the maintenance of academic integrity, the university asks that students report cases of
academic dishonesty to the teacher and/or the Dean. The names of those students will be kept
anonymous.

J. Teaching Staff:
STT Name Email, Phone Schedul Position
e
1 Nguyễn Văn Sơn son.nguyenvan@hoasen.edu.vn
2 Nguyễn Ngọc Tú tu.nguyenngoc@hoasen.edu.vn
3 Nguyễn Thị Thanh thanh.nguyenthi@hoasen.edu.vn

K. Outline of Topics to be covered:

For main semester:
Week/Session Title Textbook Outcome

Part 1: Overview of Software Engineering

[1]. Chapter 1,2
1/1 Chapter 01. Introduction
Page: 338
(2 periods) 1. Introduce aspects related to the software
2. General concepts
- Software
- Software technology

2/2 Chapter 02. Development Pre-Development Slide của giảng

Activities and Materials viên
(2 periods)
1. Necessity of the document
2. Process activities and corresponding
documents
3. Tools used to build documentation
4. Introduction to document templates
5. Teamwork (Teamwork)
[2]. Chapter 2
3/3 Chapter 03. Life cycle models - software
[1]. Chapter 4
process
(2 periods)
Page:6391
1. Some software lifecycle building models
1.1 Linear model

Trang 4 / 9
 1.2 Standard model
1.3 Spiral model
1.4 Components-based development model
2. Software development method
3. User role in software development stage
[1]. Chapter 5
4/4 Chapter 04. Software project management
Page 92104
(2 periods) 1. Project preparation activities
2. Project planning
3. Study the feasibility of the project
4. Select a solution
5. Installation environment
6. Methodology
7. Supervision and control
8. Human resource management
9. Risk management

Part 2: Determining the requirements

[1]. Chapter 6,7,
5/5 Chapter 05. Software Requirements
Page :119139
(2 periods) 1. Functional Requirements - Nonfunctional
2. User requirements
3. System Requirements
4. Interface specification
[1]. Chapter 7,8
6/6 Chapter 06. Process and Modeling
Page :142166
(2 periods) 1. Obtain and analyze the request
2. Confirm the request
3. Management requests Page :169189

Chapter 07. System modeling

1. Modeling context
2. Modeling behavior
3. Data Model
4. Object model

Part 3: Designing
[1]. Chapter
7/7 Chapter 8. Architectural design and
11,13
application
(2 periods)
Page :241264
1. Organize the system
2. Solution

Trang 5 / 9
 3. Controller
4. Architecture of the application
[1]. Chapter
8/8 Chapter 9. Object-oriented design and
14,16
interface
(2 periods) Page :313335
1. Object oriented design
Page :362386
2. Interface design

Part 4: Software development

[1]. Chapter 17
Chapter 10. Rapid development
Page:391412
1. Agile method
9/9
2. XP
(2 periods)
3. RAD
4. Template
[1]. Chapter 18,
10/10 Chapter 11. Software Reuse - Development
19
(2 periods) 1. Reuse
Page :415436
2. Design sample
3. Application framework
4. Component-based software

Part 5: Verification - authentication

[1]. Chapter
11/11 Chapter 12. Software testing
22,23
(2 periods) 1. Verification - authentication Page :537561
2. Test

Part 6: Evaluation, management and improvement

[1]. Chapter
12/12 Chapter 13. Evaluation and management
26,27
(2 periods) 1. Cost evaluation
Page:612637
Practical exercise
[1]. Chapter 29
13/13 2. Quality management
Page:641655
(2 periods) 3. Configuration management

[1]. Chapter 28
14/14 Chapter 14. Process Improvement
Page:665680
(2 periods) 1. Process improvement
2. Process classification
3. Measurement
4. Analysis - process model
5. CMMI

Trang 6 / 9
 15/15 Case study presentation
(2 periods)

For extra semester

Week/Session Title Textbook Outcome

Part 1: Overview of Software Engineering

[1]. Chapter 1,2
1/1 Chapter 01. Introduction
Page: 338
1. Introduce aspects related to the software
2. General concepts
- Software
- Software technology

2/1 Chapter 02. Development Pre-Development Slide của giảng

Activities and Materials viên
1. Necessity of the document
2. Process activities and corresponding
documents
3. Tools used to build documentation
4. Introduction to document templates
5. Teamwork (Teamwork)
[2]. Chapter 2
3/2 Chapter 03. Life cycle models - software
[1]. Chapter 4
process
Page:6391
1. Some software lifecycle building models
1.1 Linear model
1.2 Standard model
1.3 Spiral model
1.4 Components-based development model
2. Software development method
3. User role in software development stage
[1]. Chapter 5
4/2 Chapter 04. Software project management
Page 92104
1. Project preparation activities
2. Project planning
3. Study the feasibility of the project
4. Select a solution
5. Installation environment
6. Methodology

Trang 7 / 9
 7. Supervision and control
8. Human resource management
9. Risk management

Part 2: Determining the requirements

[1]. Chapter 6,7,
5/3 Chapter 05. Software Requirements
Page :119139
1. Functional Requirements - Nonfunctional
2. User requirements
3. System Requirements
4. Interface specification
[1]. Chapter 7,8
6/3 Chapter 06. Process and Modeling
Page :142166
1. Obtain and analyze the request
2. Confirm the request
3. Management requests Page :169189

Chapter 07. System modeling

1. Modeling context
2. Modeling behavior
3. Data Model
4. Object model

Part 3: Designing
[1]. Chapter
7/4 Chapter 8. Architectural design and
11,13
application
Page :241264
1. Organize the system
2. Solution
3. Controller
4. Architecture of the application
[1]. Chapter
8/4 Chapter 9. Object-oriented design and
14,16
interface
Page :313335
1. Object oriented design
Page :362386
2. Interface design

Part 4: Software development

[1]. Chapter 17
9/5 Chapter 10. Rapid development
Page:391412
1. Agile method
2. XP
3. RAD

Trang 8 / 9
 4. Template
[1]. Chapter 18,
10/5 Chapter 11. Software Reuse - Development
19
1. Reuse
Page :415436
2. Design sample
3. Application framework
4. Component-based software

Part 5: Verification - authentication

[1]. Chapter
11/6 Chapter 12. Software testing
22,23
1. Verification - authentication Page :537561
2. Test

Part 6: Evaluation, management and improvement

[1]. Chapter
12/6 Chapter 13. Evaluation and management
26,27
1. Cost evaluation
Page:612637
Practical exercise
[1]. Chapter 29
13/7 2. Quality management
Page:641655
3. Configuration management

[1]. Chapter 28
14/7 Chapter 14. Process Improvement
Page:665680
1. Process improvement
2. Process classification
3. Measurement
4. Analysis - process model
5. CMMI

15/7 Case study presentation

Date:…………… Date:…………… Date:……………

The lecturer Programme Chair Dean/ Vice Dean
(Signature and the full name) (Signature and the full name) (Signature and the full name)

Trang 9 / 9