Teaching Plan

FAKULTI TEKNOLOGI MAKLUMAT DAN KOMUNIKASI

UNIVERSITI TEKNIKAL MALAYSIA MELAKA

SOFTWARE ENGINEERING
BITP 2213 SEMESTER II SESI 2 2017/2018

BITP 2213 SOFTWARE ENGINEERING [3, 2, 2]

TYPE OF COURSE: P
EDITION: 3
UPDATED: 25-02-2018

1.0 LEARNING OUTCOMES

At the end of the lesson, students should be able to:
i. Explain the concept, principles and practices of software engineering for
system development. (C2, LL1)
ii. Apply the concept, principles and practices of software engineering in the
system development. (C3, A3, CTPS3)
iii. Follow the standard guideline to produce formal specifications and software
modeling in a collaborative team environment for the purpose of system
development. (P3, TS1)

2.0 SYNOPSIS
This subject introduces the basic concept of software engineering to the student.
It covers all the software development process which includes analysis,
requirement, design, implementation and testing. This subject also covers
support areas such as project management and quality management. This
subject exposes the student to structured approach and object oriented
approach.

3.0 PRE-REQUISITE
None

4.0 PRACTICAL
The students will practice the software engineering concepts in the laboratories.
They will proposed, develop and managed the mini project. The student will go
through all the software development phases in the lab. Reviews will be

1/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
 conducted at the end of every phase. At the end of the lab, the student will
present and demonstrate their system to the lecturer.

5.0 REFERENCES
[1] Pressman, Roger S., 2015, Software Engineering: A Practitioner's
Approach, Eighth (8th) Edition, McGraw-Hill.
[2] Sommerville, I., 2015, Software Engineering, 10th Edition, Addison-
Wesley.
[3] Pfleeger, S.L and Atlee, J.M, 2010, Software Engineering, 4th Edition,
Pearson.
[4] Dennis, A., Wixom, B.H., & Roberta, M. R., 2012, System Analysis
Design, 5th Edition, Wiley.
[5] Chemuturi, M. And Caghley, T. M. J., 2010, Mastering Software Project
Management: Best Practices, Tools and Techniques, J. Ross
Publishing.
[6] Bruegge, B. and Dutoit, A. H., 2010, Object-oriented Software
Enginering: Using UML, patterns and Java, Prentice Hall
[7] Ahmad, S. et al, (2013), A Student’s Guide: UML for Software
Engineering, Penerbit UTeM.

6.0 COURSE IMPLEMENTATION

i. Lecture
 2 hours per week for 14 weeks (Total = 28 hours)

ii. Laboratory Activities

 2 hours per week for 14 weeks (Total = 28 hours)

2/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
7.0 COURSE EVALUATION
Assessment Method LO1 LO2 LO3 Scheme, Rubric/ guideline
Mini Project (1) = 25% MP1(5%) RubricMP1.docx
MP2(5%) RubricMP2.docx
MP3(5%) RubricMP3.docx
MP4(5%) RubricMP4.docx
MP5(5%) RubricMP5.docx
Mid-Sem Exam (1) = 25% MT-1(15%) MT-2(10%) SchemaMT.docx
Assignments (2) = 10% A1(5%) RubricA1.docx
A2(5%) RubricA2.docx
Laboratory Test (1) =10% LBT-1(10%) SchemaLT.docx
Final Examination (1) = 30% PA-1(10%) PA-2(20%) SchemaPA.docx
Total 25% 50% 25%

8.0 STUDENT LEARNING TIME (SLT)

STUDENT LEARNING TIME (BITP 2213)

LEARNING GUIDED LEARNING TIME INDEPENDENT LEARNING TIME

ACTIVITIES
OFFICIAL GUIDED SELF
ASSESSMENT
CONTACT FREQ TOTAL LEARNING FREQ TOTAL STUDY FREQ TOTAL FREQ TOTAL
TIME
HOURS HOURS HOURS

Lecture 2 12 24 - - - 2 12 24 - - -

Lab 2 8 16 3 5 15

Assignment - - - - - - 5.5 2 11 0.25 2 0.5

Mid-Sem Exam - - - - - - 6 1 6 1.5 1 1.5

Lab Test - - - - - - 6 1 6 1.5 1 1.5

Mini Project - - - - - - 5 1 5 0.5 1 0.5

Final
- - - - - - 8 1 8 2 1 2
Examination

TOTAL 24 16 75 6

GRAND
121
TOTAL

TOTAL
3.025
CREDIT

3/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
 9.0 DETAILED SYLLABUS AND TEACHING PLAN
Week Session Contents References Delivery
Method &
*Remark

1 Lecture Software and Software Engineering Chapter 1

[Pressman]
1
Lecture content LECTURE
 Nature of software
 Software engineering definition
 The software process Method: Role-
play
 Practice and principles
 Software myths

Laboratory content
 Software Development Plan (SDP):
 Group formation of mini project
 Mini project discussion
Lab 1

2 Lecture Software Development Process Chapter 2, 3

[Pressman]
2
Lecture content LECTURE
 Software process model
 Process iteration *A1 given
 Process activities
 The Rational Unified Process (RUP)
 Agile Software Process
 Computer-Aided Software Engineering Tool
(CASE).

Lab 2 Laboratory content

 Software Development Plan (SDP):
 Mini project discussion – development
process model

4/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
3 Lecture Project Management and Cost Estimation Chapter 24 &
26 [Pressman]
3
,
Lecture content Chapter 3 LECTURE
 What is software project management? [Sommerville]
 Project management activities ,
 Project planning and scheduling Chapter 14
[Bruegge and
 Project tracking
Dutoit]
 Risk management. &
 Estimation technique Chapter 2
 Algorithmic cost modeling [Dennis, et al]

Lab 3 Laboratory content

 Software Development Plan (SDP):
 Develop mini project schedule using Gantt
chart.
 Project tracking and document review
 Estimate project cost using the selected
software cost estimation technique
 Task: MP1 – prepare SDP documentation of
mini project
 Template to use:
(SDP_Software_Development_Plan_Template.docx)

4 Lecture Requirement And Specification Part 1 Chapter 4

[Pfleeger and
4
Atlee]
Lecture content , LECTURE
 What is software requirement and software Chapter 4
specification? [Sommerville] *Submission of
 Functional and Non Functional requirements , A1
Chapter 4
 Types of requirements – user, system,
[Bruegge and
interface Dutoit]
&
Lab 4 Laboratory content Chapter 4
 Software Requirement Specification (SRS): [Dennis, et al]
 Context model
 Mini project discussion
 Model requirement using structured approach.
 Analyze requirement of mini project **Submission
of MP1 (SDP)

5/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
5 Lecture Requirement And Specification Part 2 Chapter 4
[Pfleeger and
5
Atlee]
Lecture content , LECTURE
 Requirement documents – SRA, SRS Chapter 4
 Requirement engineering [Sommerville] *A2 given
 Requirement modeling. ,
Chapter 5
[Bruegge and
Lab 5 Laboratory content Dutoit]
 Software Requirement Specification (SRS): &
 Analyze functional and non-functional Chapter 3
requirement of mini project [Dennis, et al]
 Model requirement using Object-Oriented
approach
 Introduction to StarUMLTM – Interactions
model
 User Requirement Analysis of Mini Project
discussion

6 Lecture UML and System Modeling in Software Chapter 5

[Sommerville]
6 Engineering
,
Chapter 2
Lecture content [Bruegge and LECTURE
 Introduction to UML Dutoit]
 UML Diagrams &
Chapter 5
 Object oriented principles.
[Dennis, et al]
 Data Flow Diagram (DFD) – Logical and
physical diagram

Lab 6 Laboratory content

 Software Requirement Specification (SRS):
 Creating and validating DFD.
 Structural models
 Behavioral models
 Task: MP2 – prepare SRS documentation of
mini project
 Template to use:
(SRS_Software_Requirement_Specification_Template
and guideline.docx)

7  MID SEMESTER EXAMINATION* *Covers

Lecture 1-6
 LABORATORY TEST **
6/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
 **Covers Use
Case & DFD

***Submission
of A2

8 MID SEMESTER BREAK

9 Lecture Software Design Chapter 5 & 6

[Pfleeger and
7 Atlee]
Lecture content , LECTURE
 What is software design Chapter 6 & 7
 Software architecture [Sommerville]
 Data design ,
Chapter 12 &
 User interface design
13
 Software design documents. [Pressman]

Lab 7 Laboratory content

 Software Design Document (SDD):
 Mini project discussion & development
 Task: MP3 – prepare Software Design
Document (SDD) for mini project
 Template to use: **Submission
(SDD_Software_Design_Document_LIPS1.pdf) of MP2 (SRS)

10 Lecture Software Testing Chapter 8 & 9

[Pfleeger and
8 Atlee]
Lecture content , LECTURE
 Verification and Validation Chapter 8
 Planning [Sommerville]
 Inspection ,
Chapter 22
 What is software testing [Pressman]
 Types of testing
 Designing test cases

Lab 8 Laboratory content

 Software Test Plan (STP):
 Mini project discussion & development
 Developing Test Cases
 Task: MP4 - Developing Unit Test Plan and
Integration Test Plan (Software Test Plan
(STP) documentation)

7/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
  Template to use:
(STP_Software_Test_Plan_LIPS1.pdf)

11 Lecture Software Maintenance Chapter 11

[Pfleeger and
9 Atlee]
Lecture content , LECTURE
 Program evolution dynamics Chapter 9
 What is software maintenance [Sommerville]
 Evolution processes
 Legacy system evolution

Lab 9 Laboratory content **Submission

 Mini project discussion & development of MP3 (SDD)

12 Lecture Quality Management Chapter 24

[Sommerville]
10
Lecture content LECTURE
 Quality assurance and standards
 Quality planning
 Quality control
 Software measurements and metrics.

Lab 10 Laboratory content

 Mini project discussion & development

13 Lecture Configuration Management. Chapter 13

[Bruegge and
11
Dutoit]
Lecture content & LECTURE
 What is configuration management Chapter 25
 Configuration management planning [Sommerville]
 Change management
 Version and release management.

Lab 11 Laboratory content

 Change management **Submission
 Mini project discussion & development of MP4 (STP)

14 Lecture Ethics In Software Engineering and Software Chapter 14

12 Engineering for Real-time application and [Pfleeger and
Atlee]
embedded system &
8/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
 Chapter 20
Lecture content [Sommerville] LECTURE
 Professional Ethics
 Real-time application
 Embedded system

Lab 12 Laboratory content

 Mini project discussion & development
 Pre Demonstration.

15 Task: MP5 – Presentation of Mini Project

9/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
10.0 MATRIX OF LEARNING OUTCOMES

SUBJECT vs PROGRAM OUTCOME (PO) LEARNING OUTCOME (LO)

PROGRAM OUTCOME (PO) Explain the concept, principles and practices of software
Subject PO PO PO PO PO PO PO PO PO LO1 engineering for system development. (C2, LL1)
1 2 3 4 5 6 7 8 9
BITP Apply the concept, principles and practices of software
2213 X X X LO2 engineering in the system development. (C3, CTPS3)

LEARNING OUTCOME (LO) vs PROGRAM OUTCOME (PO)

PROGRAM OUTCOME (PO) Follow the standard guideline to produce formal specifications
LO PO PO PO PO PO PO PO PO PO LO3 and software modeling in a collaborative team environment for
1 2 3 4 5 6 7 8 9 the purpose of system development. (P3, TS1)
LO1 X
LO2 X
LO3 X

SUBJECT vs SOFT SKILLS

SOFT SKILLS
Subject entrepreneurship Ethics & moral leadership
communication skill critical thinking & problem solving team work lifelong learning
skills professionalism skills
L L L
CS CS CS CS CS CTPS CTPS CTPS CTPS CTPS TS TS TS LL LL LL ES ES ES EM EM EM S S S
1 2 3 4 5 1 2 3 4 5 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3
BITP
2213 X X X

10/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka
 LEARNING OUTCOME (LO) vs SOFT SKILLS
SOFT SKILLS
lifelong entrepreneurship ethics & moral leadership
communication skill critical thinking & problem solving team work
learning skills professionalism skills
LO
CS CS CS CS CS CTPS CTPS CTPS CTPS CTPS TS TS TS LL LL LL ES ES ES EM EM EM L L L
1 2 3 4 5 1 2 3 4 5 1 2 3 1 2 3 1 2 3 1 2 3 S S S
1 2 3
LO1 X
LO2 X
LO3 X

SUBJECT vs TAXONOMY
Taxonomy
Subject Affective Cognitive Psychomotor
A1 A2 A3 A4 A5 C1 C2 C3 C4 C5 C6 P1 P2 P3 P4 P5 P6 P7
BITP
2213 X X X X X X X X X

LEARNING OUTCOME (LO) vs TAXONOMY

Taxonomy
LO
Affective Cognitive Psychomotor
A1 A2 A3 A4 A5 C1 C2 C3 C4 C5 C6 P1 P2 P3 P4 P5 P6 P7
LO1 X X
LO2 X X X X X X
LO3 X X X

11/ 13

Fakulti Teknologi Maklumat dan Komunikasi

Universiti Teknikal Malaysia Melaka