Revised September 2010

Polytechnic University of the Philippines

College of Computer Management and Information Technology
Sta. Mesa Manila

COURSE SYLLABUS
(Curriculum Year 2007)

Vision
The College of Computer Management and Information Technology (CCMIT) envisions itself as a
creative and responsible catalyst of change and a dynamic Center of Excellence in the field of
Information Technology. It will produce graduates who will address the demands of the emerging
knowledge-based economy.

Mission
The College of Computer Management and Information Technology is committed to:
1. provide quality IT education relevant and responsive to the changing needs of the industry
and society;
2. produce entrepreneurial and highly employable graduates who can respond to the
challenges of globally competitive information age;
3. engage in research on technologies for effective teaching of students whose experiences
are increasingly influenced by electronic media and computers;
4. develop innovative programs with greater reliance on technology as an alternative to costly
and limited resources offered by the traditional educational system;
5. undertake outreach and extension programs which allow the utilization of the expertise of
the CCMIT human resource for the improvement of the community;
6. strengthen linkages with industry and other research and development institutions in order
to continuously upgrade and update the knowledge and skills of faculty members and
students; and
7. inculcate among administrators, faculty members, staff, and students the highest degree of
commitment and professionalism in any undertaking.

Course Description of the Program

The Bachelor of Science in Information Technology program is an integrative discipline that pulls
together the IT pillars of databases, human-computer interaction, networking, programming, and web
systems and uses a solid background in each of them to enable graduates to solve all types of
computing and informational problems, regardless of their origin.
As a discipline, IT emphasizes user centeredness and advocacy, information assurance and
security, and the management of complexity through abstraction and modeling, best practices, patterns,
standards, and the use of appropriate tools. It also provides graduates the skills to assume I.T.
positions and grow into leadership positions.

Objectives of the Program

The BSIT student is expected to:
1. explain and apply appropriate information technologies and employ appropriate
methodologies to help the individual, organization or society achieve its goals and
objectives;
2. promote innovation and creativity through research and exemplify highest level of
professionalism in work;
3. design, and manage effective and usable IT based solutions and integrate them into the
environment;
4. adapt to the rapid change in technology, identify and evaluate current and emerging
technologies, assess applicability and impact of these technologies;
5. communicate effectively and efficiently with clients, users and peers both verbally and in
writing, using appropriate terminology;
6. enhance skills through life-long professional development;
7. recognize and be guided by the social, professional and ethical standards involved in the
use of technologies.

Page 1 of 6
 Revised September 2010
Course Code : COMP3033
Course Code : Software Engineering
Course Credit : Lecture: 2 units Laboratory: 1 unit Total Units: 3 Units
Hours Equivalent : 90 hours
Lecture: 2 hrs Laboratory: 3 hrs Total Hours: 5 hrs
Pre-requisites : COSC 3063(BSCS), INTE 3023(BSIT), Programming

Course Description :

This course provides an overview of the software engineering process. The course describes the
individual phases making up the project life cycle for developing software and provides key concepts and
fundamental principles guiding the quality of the software development process. It covers detailed
discussion on software engineering principles, practices, tools and techniques and the different software
development life cycle strategies. It also includes discussion and application of object-oriented design and
development methodology.

Course Objectives :

1. Cognitive Aims:
a) To understand the different phases of system development;
b) To learn and apply fundamental principles of quality software development;
c) To identify the different practices, tools and techniques in software development;
d) To develop skills in object-oriented software design and development;
e) To design, code and document programs, going through the entire software development life
cycle.

2. Value Aims:
a) To develop in the students the value of hardship and excellence in every task that will be given
to them;
b) To instill to the students the value of fairness in the teacher-student and student-student
relationship;
c) To inculcate to the students the value of diligence and punctuality by motivating them to submit
projects on time;
d) To teach students to work collaboratively with their group mates.

Course Outline:
Lecture Laboratory
Course Outline Per Unit Topic
Time(hrs) Time(hrs)
1. Overview …………………………………………………… 2
1.1 The Nature of Software
1.1.1 Software Applications and their
Categories
1.1.2 Components of a Software Product
1.1.3 Attributes/Characteristics of Quality
Software
1.1.4 Basic Issues/Problems in Software
Development
1.1.5 Software Development Myths
Review and Clarification……………………………. 1
2. Introduction to
Software 2.1.Software Engineering………………………….. .5
Engineering 2.1.1 Software Engineering Definition
2.1.2 Generic Phases of Software Engineering
2.1.2.1 Definition Phase
- Systems Analysis
- Software Project Planning
- Requirements Analysis
2.1.2.2 Development Phase
- Software Design
Page 2 of 6
 Revised September 2010
- Coding
- Testing
2.1.2.3 Maintenance Phase
2.2.SE Related Standards & Certifications………… .5
2.2.1 Major International IT Standards
2.2.1.1 IEEE
2.2.1.2 ANSI
2.2.1.3 NIST
2.2.1.4 OMG
2.2.1.5 OSF
2.2.1 Top IT Certifications
2.2.1.1 MCSE
2.2.1.2 Certified Java Developer
2.2.1.3 Certified Java Architect
2.2.1.4 MCSD
2.3.Software Process Models………………………. 2
2.3.1 Linear Life-Cycle Models
2.3.1.1 Waterfall/Classic Life Cycle
2.3.1.2 Fountain Model
2.3.1.3 Rapid Application Dev’t
2.3.1.4 Other linear life-cycle model
2.3.2 Iterative or Prototyping
2.3.3 Evolutionary Process Model
2.3.3.1 Incremental Model
2.3.3.2 Spiral Model
2.3.3.3 Concurrent Dev’t/Eng’g
2.3.4 Other Models
2.3.4.1 Agile Methods
2.3.4.2 4th Generation Technique
2.3.4.3 Component-based Dev’t
2.3.4.4 Formal Methods
2.3.4.5 Extreme Programming
2.3.5 The Rational Unified Process
Class Examination, Evaluation, Feedback & Review. 3
3. Software Project
Management 3.1 The Project Initiation 3
Phase……………………... 1
3.1.1 Activities in Initiating The Project……….. 3
3.1.2 Building the Project Plan…………………
3.4.3.1 WBS & Baseline Plan
3.4.3.2 Gantt Chart
3.4.3.3 Task Dependencies
3.4.3.4 Lag & Lead Time
3.4.3.5 PERT/Project Network Diagram 3
3.1.3 Network Diagram Analysis……………….
3.1.4 Software Project Risk Management………
3.1.4.1 Software Development Risks
3.1.4.2 Software Risks Impact
Estimation & Assessment
3.1.4.2 Mitigating Software Risks .5
3.2 Software Metrics………………………………...
3.2.1 Quality Metrics
3.2.2 Productivity Metrics
3.2.2.1 Size-oriented/LOC
3.2.2.2 Function-oriented 1
3.2 Estimating Software Project
Resources…………
2.6.1. Problem-based Decomposition
Technique (LOC & FP)
2.6.2 Empirical Estimation Models
Page 3 of 6
 Revised September 2010
2.6.2.1. LOC-Oriented
2.6.2.2 FP-Oriented
2.6.2.3 COCOMO
2.6.2.4 Putnam Model

4. Systems Analysis ………………………………………………………. 1.5

4.1 Activities in Systems Analysis Phase
4.2 Requirements Analysis
4.2.1 Requirements Gathering Techniques
4.2.2 Requirements Modeling Tools
4.3 Requirements Specifications Document………. 3
5. Software Design
& Implementation 5.1 Software Design…………………………………. 2.5
5.1.1 3 Phases in Design
5.1.2 Architectural Models
5.1.3 Screen Design and Usability
5.1.4 Design Notation: Modeling
Languages
5.1.5 Design Specifications Document……… 3
5.2 Program Design and Coding……………………. 2 3
5.2.1 Module Partitioning Techniques
5.2.1.2 Data-oriented Techniques
5.2.1.2 Structure-oriented Techniques
5.2.2 Measuring A Module
5.2.2.1 Cohesion
5.2.2.2 Coupling
5.2.2.3 Fan-in
5.2.2.4 Fan-out
5.2.3 Program Documentation…………………..
5.3 Software Testing………………………………… 2
5.3.1 Desk Checking VS Testing
5.3.2 Types of Test
5.3.3 Testing Methods
5.3.3.1 Black Box Test
5.3.3.2 White Box Test
5.3.3.3 Bottom-up Test
5.3.3.4 Top-down Test
5.3.3.5 Big-Bang Test

Midterm Departmental Examination, Evaluation, Feedback &

Examination Review………………………………………………. 2 3

6. Essentials of 6.1 Introduction to Object Technology……………... 2.5

Visual 6.1.1. Definition of Object Technology
Modeling 6.1.2. Principles of Object Orientation
6.1.3 Objects and Classes
6.1.4 Polymorphism and Generalization
6.1.5 Organizing Model Elements thru
Packages
6.1.6 Design Patterns
6.2 Principles of Visual Modeling…………………… .5
6.2.1. Definition of Visual Modeling
6.2.2 Visual Modeling With UML
6.3 Use Case Modeling……………………………… 1.5
6.3.1 Concepts in Use Case Modeling
6.3.2 Use-Case Diagrams…………………….. 2
6.3.3 Activity Diagrams……………………… 2
6.3.4 Class Diagrams………………………… 2
6.4 Interaction Diagrams……………………………. 1 2
6.4.1 Sequence Diagrams

Page 4 of 6
 Revised September 2010
6.4.2 Communication Diagrams
6.4.3 Interaction Diagrams Comparison
6.6 Other UML Diagrams………………………….. 1
6.6.1 Object Diagrams…………………………. 1
6.6.2 State Machine Diagrams………………… 1
6.6.3 Component Diagrams…………………… 1
6.6.4 Deployment Diagrams………………….. 1
Group Case Study…………………………………… 5
Evaluation & Review………………………………... 3
7. Software
Validation and 7.1 Software Validation Techniques………………… .5
Maintenance 7.1.1 Walkthrough
7.1.2 Inspection
7.1.3 Round Robin
7.1.4 Simulation
7.2 Types of Change………………………………… .5
7.2.1 Corrective Change
7.2.2 Adaptive Change
7.2.3 Perfective Change
8. Software ………………………………………………………. 1
Configuration 8.1 Software Configuration Items(SCI)
Management 8.2 Baselining Configuration Items
8.3 Configuration Management Audit
8. 4 Version Control
9. Capability ………………………………………………………. 1
Maturity Model 9.1 Software Process Improvement (SPI)
9.2 The CMMI
9.2.1 Definition & History
9.2.2 CMMI As a Process Model
9.2.3 CMMI Model Representations
9.2.4 CMMI Process Areas
9.3 Capability Maturity Model for Software

Project Presentation, Evaluation & Feedback……….. 18

36 54
TOTAL NUMBER OF HOURS 90

Course Requirements:
MAJOR MINOR
Departmental Examination Quizzes/Examinations
Group Project Presentation Seatworks/Home Works/Laboratory Works
Software Documentation Attendance/Recitation/Reports

Evaluation Techniques:
1. Examination/Quiz
2. Recitation
3. Group Project Presentation & Submission

Course Grading System:

Midterm Final
Class Standing 70 % Class Standing 50 %
Assignment/Recitation/Exercises Software Documentation
Reports Assignment/Recitation/Exercises
Examination/Quiz Examination/Quiz
Lab Activities Lab Activities
Attendance
Mid-term Examination 30 % Group Project 50%
Page 5 of 6
 Revised September 2010
Final Grade = (Mid-term + Final)/2

Suggested Learning and Teaching MethodologiesActivities:

1. Lectures/Discussion
2. Recitation/Q & A/Review/Seminar
3. Individual & Group Exercises
4. Laboratory/Hands-on Exercises
5. Individual/Group Research & Report
6. Seminars

Textbook:
Roger S. Pressman, 2009, Software Engineering: A Practitioner’s Approach, 7th Edition, McGraw-Hill

References:
1. Ian Sommerville, 2007, Software Engineering, 8th Edition, Addison-Wesley
2. Shari Lawrence Pfleeger & Joanne Atlee, 2005,Software Engineering, 3rd Edition, Prentice Hall
3. Mastering Requirements Management with Use Cases, IBM Philippines, Inc.
4. Essentials of Visual Modeling, IBM Philippines, Inc
5. Essentials of Rational Unified Processing, IBM Philippines, Inc.

Revised by:

_____________________
Mary Jane Magno-Tan

Approved by:

__________________________ _________________________
Michael M. Dela Fuente Angelito G. Pastrana
Chairperson, BSCS Chairperson, BSIT

_________________________
Rosita M. Canlas
Dean, CCMIT

Page 6 of 6