MAPÚA INSTITUTE OF TECHNOLOGY

School of EE-ECE-COE

VISION
Mapúa shall be an international center of excellence in technology education by:
 providing instructions that are current in content and state-of-the art in delivery;
 engaging in cutting-edge research; and
 responding to the big local and global technological challenges of the times

MISSION
a) The mission of Mapúa Institute of Technology is to disseminate, generate, preserve and apply scientific,
engineering, architectural and IT knowledge.
b) The Institute shall, using the most effective means, provide its students with professional and advanced
scientific and engineering, architectural and information technology education through rigorous and up-
to-date academic programs with ample opportunities for the exercise of creativity and the experience of
discovery.
c) It shall implement curricula that, while being steeped in technologies, shall also be rich in the humanities,
languages and social sciences that will inculcate ethics.
d) The Institute shall advance and preserve knowledge by undertaking research and reporting on the results
of such inquiries.
e) The Institute, singly or in collaboration with others, shall bring to bear the world's vast store of
knowledge in science, engineering and other realms on the problems of the industry and the community
in order to make the Philippines and the world a better place.

MISSION
PROGRAM EDUCATIONAL OBJECTIVES
a b c d e
1. To equip the student with a broad foundation on the basic
engineering concepts and the fundamentals of Computer    

addressed by SLHS
Engineering.
2. To develop the student’s capability to apply these learned concepts
in engineering design and to implement such in a career as a    
practicing engineer.
3. To inculate to the students the importance of lifelong learning.    

4. To develop in the student an appreciation of technology and

   
determine its use in the advancement of society.

COURSE SYLLABUS
1. Course Code : COE 125

2. Course Title : SOFTWARE ENGINEERING

3. Pre-requisite : COE124

4. Co-requisite : None

5. Credit/ Class Schedule : 3 units

6. Course Description : A course on software development processes such as project planning,

requirements engineering, software design, testing, verification and validation, and
implementation.

7. Program Outcomes and Relationship to Program Educational Objectives

Course Title: Date Effective: Date Revised: Prepared by: Approved by:
st
Page 1 of
Software Engineering 1 Quarter 2008-2009 July 1, 2008 Meo Vincent C. Caya Noel B. Linsangan 5
Lecture
 Program
Educational
Program Outcomes
Objectives
1 2 3 4
An ability to apply knowledge of mathematics, science, and
(a) √ √
engineering
An ability to design and conduct experiments, as well as to
(b) √ √
analyze and interpret data
An ability to design a system, component, or process to meet
(c) √ √
desired needs
(d) An ability to function on multi-disciplinary teams  √
An ability to identify, formulate, and solve engineering
(e) √ √
problems
(f) An understanding of professional and ethical responsibility √ √
(g) An ability to communicate effectively √ √ √
The broad education necessary to understand the impact of
(h) √
engineering solutions in a global and societal context
A recognition of the need for, and an ability to engage in life-
(i) √ √
long learning
(j) A knowledge of contemporary issues √ √ √ √
An ability to use the techniques, skills, and modern engineering
(k) √ √  √
tools necessary for engineering practice.

8. Course Objectives and Relationship to Program Outcomes:

Course Objectives Program Outcomes

The students should be able to: a b c d e f g h i j k
1. To understand the concept of software
√ √ √ √ √ √
engineering and its importance.
2. To understand and apply the processes
involved on the development life cycle of
√ √ √ √ √ √ √ √ √
software, and have an idea of the distribution of
cost over software development phases.
3. 3. To experience and appreciate the technical,
managerial and psychological aspect of software √ √ √ √ √ √ √ √ √
engineering.
4. To practice ethical disciplines in software
√ √ √ √ √
engineering.
5. To be able to apply the theoretical principles
√ √ √ √ √ √
through actual software design development.

9. Course Coverage :

METHODOLOGY &
WEEK TOPICS EVALUATION TOOL
STRATEGY
1 Orientation
Introduction to Software Engineering
Lecture Recitation
Software Life Cycle
(Waterfall, Prototyping,Incremental
Development, RAD, others…)

Course Title: Date Effective: Date Revised: Prepared by: Approved by:
st
Page 2 of
Software Engineering 1 Quarter 2008-2009 July 1, 2008 Meo Vincent C. Caya Noel B. Linsangan 5
Lecture
 2 Software Project Planning
Resource Allocation ( hardware, software,
people) Lecture Recitation
Metrics for Software Productivity and Quality
SeatWork
Estimation Method( COCOMO, Putnam)
Estimates on Return of Investment (ROI) Project Proposal
Project Scheduling ( Work breakdown
structure, task delegation)
Creation of Project Plan (Gantt Chart) QUIZ 1
3 Requirement and Analysis Planning
Requirement Gathering Tools ( interview, Company Request Letter
survey…) Lecture
Homework
Software Requirement Specification (SRS)
Recitation
Entity Relation Diagram (ERD) SRS Document
4 Design Phase Seatwork
Data Flow Diagram (DFD)
Logical DFD Lecture Recitation
Physical DFD
Context Diagram ( Diagram 0, Child DFD) Discussion of Template Final SRS Document
Use Cases
QUIZ 2
Data Dictionary
5 Object-Oriented Analysis and Design
Recitation
Design Notation
Lecture
Design Method Consultation
Project Status Report and Consultation
6 Software Testing Recitation
Verification and Validation of Planning, Design Seatwork
and Document Lecture Consultation
QUIZ 3
Project Status Report and Consultation
7 Software Maintenance Recitation
Processes and Procedures Seatwork
Lecture
Tools and Management Consultation
Software Development Document (SDD)
Project Status Report and Consultation SDD Document
8 Software Quality Metrics Homework
Software quality evaluation Recitation
Lecture Consultation
Tools and Management
Project Status Report and Consultation QUIZ 4
9 Group Presentation Project Status Report
Project Status Presentation and Consultation
Final SDD Document
10 Final Group Question and Answers
Project Presentation (SDD)
Presentation
11 Finals Final Exam

10. Course Outcomes and Relationship to Course Objectives/ Program Outcomes

Course
Program Outcomes
Course Outcomes Objectives
A student completing this course should at the
minimum be able to: 1 2 3 4 5 a b c d e f g h i j k

 Define software engineering

and describe the phases of software √ √ √ √ √ √ √
development.

Course Title: Date Effective: Date Revised: Prepared by: Approved by:
st
Page 3 of
Software Engineering 1 Quarter 2008-2009 July 1, 2008 Meo Vincent C. Caya Noel B. Linsangan 5
Lecture
  Evaluate the different models to
illustrate the structure of software √ √ √ √ √ √ √
development process.
 Understand and apply the techniques
in planning a software development √ √ √ √ √ √ √ √
project and software cost estimation.
 Identify the different requirement
gathering tools and classify the
contents of the software requirement
√ √ √ √ √ √ √ √ √ √ √ √
specification format as well as
construct an entity relationship
diagram for data modeling.
 Assess the different aspects of
software design and formulate
√ √ √ √ √ √ √ √ √ √ √
design methods and modeling
languages.
 Implement and assess object
oriented analysis and design √ √ √ √ √ √ √ √ √ √
methods.
 Classify and compare different
software techniques. √ √ √ √ √ √ √ √ √ √ √ √ √

 Distinguish the type of maintenance

task and integrate some tools to
√ √ √ √ √ √ √ √ √ √ √ √ √
organize the software maintenance
task.
 Categorize the different software
quality metrics in improving system
√ √ √ √ √ √ √ √ √ √ √ √ √ √
performance and present a document
for software engineering.

11. Contribution of Course to Meeting the Professional Component:

Engineering topics – 80%

General education component – 20 %

12. Textbook : Software Engineering Principles and Practice, 2nd ed. by Hans Van Vliet

13. Recommended Course Evaluation :

Q1 – 150 points
Q2 – 150 points
Q3 – 150 points
Q4 – 150 points
Final Exam 200 points

The minimum requirement for a passing grade is 60% final grade average from the following:

QUIZZES : 20%
Homework, Seatwork, Recitation : 5%
SRS : 20%
SDD : 20%
Project Presentation : 10%
Final Exam : 25%

Course Title: Date Effective: Date Revised: Prepared by: Approved by:
st
Page 4 of
Software Engineering 1 Quarter 2008-2009 July 1, 2008 Meo Vincent C. Caya Noel B. Linsangan 5
Lecture
14. Other References

a. Software Engineering Principles and Practice by Pressman 5th edition

b. System Analysis and Design by Kendall & Kendall 6th edition
c. MIS cases: decision making with application software by Miller, M L (2005)
d. Software architect boot camp. 2nd edition by Malveau, Raphael(2004)
e. Software engineering for real time systems by Cooling, J(2003)
f. Software system development by Britton, C(2003)
g. Object-Oriented and Classical Software Engineering by Schach, S.K.(2007)
h. Systems Analysis Design, 3rd edition by Dennis (2006)
i. Modern Software Development Using C++. NET by Wiener (2007)
j. The Road Map to Software Engineering: a standard-based guide by Moore(2006)
k. Software Quality Engineering: testing, assurance, and quantifiable improvement by Tian(2006)

15. Course Materials Made Available:

Course goals and instructional objectives

Course schedule for lectures and exams
End of course self-assessment report

16. Committee Members:

Meo Vincent C.Caya

Arlene T. Carpizo
Maribelle D. Pabiania
Mary Jane C. Quinit
Joyce M. Santos
Jumelyn L. Torres
Analyn N. Yumang

Course Title: Date Effective: Date Revised: Prepared by: Approved by:
st
Page 5 of
Software Engineering 1 Quarter 2008-2009 July 1, 2008 Meo Vincent C. Caya Noel B. Linsangan 5
Lecture