DATA CENTER COLLEGE OF THE PHILIPPINES

Brgy.Ubbog – Lipcan, Bangued, Abra

COURSE SYLLABUS

PROGRAM: Bachelor of Science in Computer Science (BSCS)

COURSE SUBJECT: SOFTWARE ENGINEERING
COURSE CODE: CS 324
SEMESTER: 1ST Semester
CREDIT: 3 Units
CONTACT HOURS : 54 Hours
PRE-REQUISITE: CS 221 / CS 315

I. VISION

Data Center College of the Philippines envisions itself as one of the leaders of tertiary education in the country consistently producing graduates who are
able to participate actively in local, regional and national development and who will be globally competitive to find employment here and abroad.

II. MISSION

Pursuant to its vision, Data Center College of the Philippines is committed to nurture the physical, socio-cultural, and moral potentials of its students for
their total development as human beings, and to provide them with relevant and quality education in their fields of specialization to enable their chosen professions
with honor and dignity.
III. GOALS

An unwavering advocacy for the rights of its students to quality and relevant education, Data Center College of the Philippines has adopted the following
objectives.

 To promote a culture of life-long learning

 To provide adequate and state-of-the-art instructional materials and facilities
 To develop globally competitive graduates who can address the needs and problems of the regions
 To employ qualified and competent faculty members and to continuously motivate them to upgrade their qualification

IV. BSCS PROGRAM OBJECTIVES

Graduates of BSCS program are individuals who can / have:

1. Apply knowledge of computing fundamentals, knowledge of a computing specialization, and mathematics, science, and domain knowledge appropriate for
the computing specialization to the abstraction and conceptualization of computing models from defined problems and requirements
2. Identify, analyze, formulate, research literature, and solve complex computing problems and requirements reaching substantiated conclusions using
fundamental principles of mathematics, computing sciences and relevant domain disciplines
3. Apply mathematical foundations, algorithm principles and computer science theory in the modeling and design of computer-based systems in a way that
demonstrates comprehension of the tradeoffs involved in design choices
4. Knowledge and understanding of information security issues in relation to the design, development and use of information systems
5. Design and evaluate solutions for complex computing problems, and design and evaluate systems, components, or processes that meet specified needs with
appropriate consideration for public health and safety, cultural, societal, and environmental considerations
6. Create, select, adapt and apply appropriate techniques, resources and modern computing tools to complex computing activities, with an understanding of the
limitations to accomplish a common goal
7. Function effectively as an individual and as a member or leader in diverse teams and in multidisciplinary settings
8. Communicate effectively with the computing community and with society at large about complex computing activities by being able to comprehend and
write effective reports, design documentation, make effective presentations, and give and understand clear instructions
 9. An ability to recognize the legal, social, ethical and professional issues involved in the utilization of computer technology and be guided by the adoption of
appropriate professional,, ethical and legal practices
10. Recognize the need, and have the ability, to engage in independent learning for continual development as a computing professional

(Taken from CMO No. 25, s.2015)

V. COURSE DESCRIPTION

This course introduces the software engineering process, its principles, techniques and practices to produce quality software products. Topics include
requirement analysis, analysis modeling, software design fundamentals, software testing, quality assurance and quality process and software maintenance. Principles
of object oriented programming, programming languages, object oriented modeling and ethical issues in the IT field are also discussed.

VI. COURSE LEARNING OUTCOMES

Students learning outcomes (Adapted from CMO No. 25, s.2015)

 Discuss the difference between the waterfall-based models and agile-based models, and identify the strengths and weaknesses of these models
 Extract user requirements translate these to formal models and present these using UML-based visualizations
 Design an overall architecture of the system, and justify its appropriateness
 Improve an existing software by adopting an appropriate design pattern
 Translate program designs and specifications into actual program codes
 Design test case documents applying good testing practices, run the existing program against these test cases, and report defects properly
 Update a software that requires defect fixing or has undergone some changes in specifications
 SPECIFIC OBJECTIVES, TOPICS
AND TIME ALLOTMENT
1. Software Engineering: An Overview
1.1 Discuss the history and origin of
Software Engineering
1.2 Explain the impacts of Software
Engineering in different fields
1.3 Discuss the importance of Software 1.3 Students can identify and explain
Engineering
the ethics of being a software engineer
1.4 Discuss the Software Engineering
Ethics
8 HRS
2. Software Engineering Processes
2.1 Discuss Software Engineering
Processes and their importance
(SDLC)
2.2 Discuss Waterfall-based models
and Agile-based models of software
engineering
STUDENTS LEARNING
OUTCOMES (SLO) AND
ACTIVITIES
1.1 Students can explain the
importance of software engineering
1.2 Students can identify the different
applications of software engineering in
different fields
Students are given a seatwork
regarding the topic
Students are given an additional home
assignment on the topic
2.1 Students identify several software
engineering processes and differentiate
them
2.2 Students can identify the
appropriate software process approach
for a specific system based on its needs
ASSESSMENT
STRATEGIES
Individual participation in class
discussion and presentation
Individual seatwork checking
Home assignment on the topic
Individual participation in class
discussion and presentation
Individual seatwork checking
Presentation of report assignment
on the topic
EVIDENCE OF
OUTCOMES
Rating of level and quality of
participation
Graded individual seatwork
Graded submission of individual
home assignment
Rating of level and quality of
presentation
Individual grading of students on Q
&A
Graded individual seatwork
 2.3 Illustrate the different software
engineering models
6 HRS
3. Requirements Engineering
3.1 Discuss the different activities of
requirements engineering and their
importance in Software Engineering
3.2 Discuss the different approach in
Requirements Engineering
3.3 Discuss and illustrate the different
diagraming techniques and
requirement gathering tools
6 HRS
2.3 Students can illustrate the different
software engineering processes
Students are given an additional report
assignment on the topic
Students are given a seatwork
regarding the topic
3.1 Students can explain the activities Individual participation in class Rating of level and quality of
done in requirements engineering discussion and presentation presentation
3.2 Students can identify the different
requirements needed for a specific type Individual seatwork checking Individual grading of students on Q
of software / system
&A
3.3 Students can identify and explain Presentation of report assignment
different requirement gathering on the topic
techniques and tools Graded individual seatwork
3.4 Students can explain and illustrate
the different diagrams in requirements
engineering
Students are given a seatwork
regarding the topic
Students are given reporting activity on
the topic
4. System Modeling
4.1 Explain the importance of system
modeling in regards to software
engineering
4.2 Discuss the different perspective in
creating models
4.3 Discuss and Illustrate the types of
diagrams in representing the essentials
of a system
4.4 Differentiate models used in
developing software / system
8 HRS
5. Architectural Design
5.1 Discuss Architectural design’s
concerns and advantages
5.2 Explain the importance and how
architectural design is used in software
development
5.3 Discuss how architectural design is
used in decision making
6 HRS
4.1 Students can discuss system Individual participation in class Rating of level and quality of Group
modeling perspectives discussion and presentation presentation
4.2 Students can identify the
appropriate system modeling approach Group presentation Individual grading of students on Q
in developing software / system
&A
4.3 Groups can illustrate and present a Individual seatwork checking
topic regarding system modeling Graded individual seatwork
Groups are given reporting activity on
the topic
Students are given a seatwork
regarding the topic
5.1 Students can explain Architectural Group presentation Rating of level and quality of Group
design as an important factor in presentation
software engineering
5.2 Students can create architectural
Individual grading of students on Q
design based on user specifications
&A
Groups are given reporting activity on
the topic
6. Design and Implementation
6.1 Discuss how design can affect
other stages of software development
6.2 Explain Implementation phase of
SDLC and the activities done in this
stage
6 HRS
7. Software Testing and Evolution
7.1 Discuss the intensions and goals of
software testing
7.2 Explain and differentiate
Verification and validation and their
importance
7.3 Discuss and demonstrate the
application of Test Cases in software
testing
7.4 Discuss the different types of
testing performed in the different
stages of software development
7.5 Discuss why software evolution is
important
6.1 Students can discuss the Individual participation in class Rating of level and quality of
importance of the design phase and its discussion and presentation presentation
effect on the entire software
development process
Individual seatwork checking Graded individual seatwork
6.2 Students can identify the different
activities done during implementation
stage
Students are given a seatwork
regarding the topic
7.1 Students can identify the goals of Individual seatwork checking Rating of level and quality of
software testing and evolution presentation
7.2 Students can create test cases used
in software testing and its various Group presentation Graded individual seatwork
levels
7.3 Students discuss the activities
Individual grading of students on Q
performed in software testing
&A
Students are given a seatwork
regarding the topic
Groups create test cases and present
them to the class
 7.6 Explain the different activities done
in the software evolution

6 HRS

8. Dependability and Security
8.1 Explain why dependability and
security are very important
characteristics of a software
8.2 Discuss the Sociotechnical aspects
of software / system and their impacts
8.3 Discuss Users / Customers
participation in achieving software
dependability and security
8.1 Students can discuss the Individual seatwork checking Rating of level and quality of
importance of dependability and presentation
security in software development
8.2 Students can explain sociotechnical Group presentation Graded individual seatwork
aspects and impacts in regards to
software / system
Individual grading of students on Q
8.3 Students can explain the
importance of user/customer &A
interaction in software design and
development

8.4 Discuss organizational factors and

environment effects in system design Students are given a seatwork
and development regarding the topic

8.5 Explain Sociotechnical

characteristics Groups create report regarding the
topic
8.6 Discuss Security and Formal
Specifications

8.7 Discuss Dependability Engineering

8 HRS
References:

 Sommerville, I. Software Engineering 6th Edition, Jurong Singapore, Pearson Education South Asia Pte. Ltd. 2006
 Software Engineerin, Benjamin Sommer, Ludwig-Maximilian-University
 Website: http://www.sofware-engin.com

Prepared by: Date Submitted: Checked by: Approved by:

ABEL M. INGAW, MIT JANUARY 2018 ABEL M. INGAW, MIT GENESIS ANTHONY G. DAIT, MIT
Instructor III Program Head Head for Academic Affairs