Republic of the Philippines

PALAWAN STATE UNIVERSITY

College of Sciences
Puerto Princesa City

COURSE SYLLABUS

Approval Sheet

Course Title: Software Engineering

Course Code/ Number: CS 11/L

Revision Level Effective Date Details of Origination/ Revision Author/ Subject Matter Expert
001 January 11, 2021 Compliance with OBE Syllabus and QMS requirements Ailene L. Sibayan

Prepared by Recommending Approval Approved

AILENE L. SIBAYAN ________KRISTINE JOY V. MARTINEZ, MIS____ ________PROF. IMELDA LACTUAN_____

Name and Signature of Faculty Member Name and Signature of Department Chairperson Name and Signature of College Dean
Date: Date: Date:
 INSTITUTIONAL COURSE SYLLABUS

COURSE SYLLABUS IN _CS 11/L_

PSU Vision A premier State University in Southeast Asia that provides excellent and relevant higher education for sustainable development.
PSU Mission The Palawan State University is committed to upgrade the quality of life of the people by providing quality higher education opportunities
through excellent instruction, research, extension, production services and transnational collaboration.
PSU Shared Values E – Excellence ; L – Leadership ; A - Advocacy for Sustainable Development ; S – Social Responsibility ; T – Teamwork ; I – Integrity ;
C – Commitment
Institutional Outcomes The Palawan State University graduates are expected to be agents of change, creative and critical thinkers, effective communicators,
research-oriented learners, and value laden individuals.
College Goals and To advance the frontiers of knowledge, skills, and practices in the biological sciences, environmental science and management,
Program Objectives mathematics, and information and communication technology to become a premier institution of learning and scientific inquiry for
sustainable development in the region.

To produce ethical CS professional who are well-versed on application, installation, operation, development, maintenance and
administration of Information Technology Infrastructure.
Course Title Software Engineering
Course Code/ Number CS 11/L
Course Description This course is about the life cycle model of software development – requirements, specification, design, implementation, testing and
verification of large software systems. Study and use of software engineering methodologies and team programming.
This includes documentation, management, processes, requirements, design models, computer programs, validation, verification, cost
estimation, management, and other aspects of the development process.
Credit Units 2/1
Course Prerequisites IM101
SDF104
Link to Program
Outcomes Course Outcomes Program Outcomes
a b c d e f g h i j k l m
1. Discuss the difference between the I I I I

Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

waterfall-based models and agile-

based models, and identify the
strengths and weaknesses of these
models
2. Extract User Requirements translates I P I I I P
these to formal models and present these
using UML-based visualizations
3. Design an over-all architecture of the P P P P P P P
system and justify its appropriateness
4. Translate program designs and P D D D D D
specifications into actual program codes
Legend ( for program outcomes):
I- Introduced concepts/ principle P- Practiced with supervision D- Demonstrated across different settings with minimal supervision

Program Outcomes:

A graduate of BS in Information Technology should be able to:

a. Apply knowledge of computing, science, and mathematics appropriate to the discipline.

b. Understand best practices and standards and their applications.
c. Analyze complex problems, and identify and define the computing requirement appropriate to its solution.
d. Identify and analyze user needs and take them into account in the selection, creation, evaluation and administration of computer-
based systems.
e. Design, implement, and evaluate computer-based system, processes, components, or programs to meet desired needs and
requirements under various constraints.
f. Integrate IT-based solutions into the user environment effectively.
g. Apply knowledge through the user of current techniques, skills, tools and practices necessary for the IT profession.
h. Function effectively as a member or leader of a development team recognizing the different roles within a team to accomplish a
common goal.
i. Assist in the creation of an effective IT project plan.

Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

j. Communicate effectively with the computing community and with society at large about complex computing activities through logical
writing, presentations, and clear instructions.
k. Analyze the local and global impact of computing information technology on individuals, organizations, and society.
l. Understand professional, ethical, legal, security, and social issues and responsibilities in the utilization of information technology.
m. Recognize the need for and engage in planning self-learning and improving performance as a foundation for continuing professional
development.

Course Format Describe the teaching-learning strategies or activities that will be used in the course. e.g. lecture, fieldwork, research projects, laboratory
work, case analysis, problem solving, etc.

Lecture, Brainstorming, Group Reportorial, Laboratory Works, Media Elements Editing, Group Project

Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

LEARNING PLAN
Course Intended Learning
Time Course Content/ Subject Teaching and Resource Textbooks/
Outcome Outcomes Assessment Tasks
Frame Matter/ Topic Learning Activities Materials References
s
I. PSU MISSION,
VISION,
GOALS AND
1. Illustrate the PSU
OBJECTIVES
Vision, and Mission
A. Palawan State PSU
2. Interpret the CS PSU Code
University Vision and Powerpoint-Aided Code and
Week 1 CO1 Goals and Program Essay and Student
Mission. Lecture Student
Objectives with Manual
B. College of Business Manual
regards to their
and Accountancy
program
Goal and Objectives

Week 2 CO2 At the end of the unit, the II. INTRODUCTION TO Powerpoint-Aided Paper and Pencil Test: eBook Pressman
students should be able to: SOFTWARE Lecture Multiple Choice R.S.,
1. Identify unique ENGINEERING Software
features of various  What is SE? Engineering:
software application  Why is Software A
domains Engineering required? Practitioner's
 Characteristics of a Approach,
2. Classify the software good software Seventh
applications. engineer Edition, TMH
 The importance of SE Publication.
 SE Code of Ethics
3. Practice The Nature of Software https://www.t
professional, ethical  Defining a Software utorialspoint.
and social  Software Application com/uml/uml
responsibility of a Domains _quick_guide
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

software engineer  Legacy Software .htm

The Changing Nature of
Software https://www.j
 WebApps avatpoint.co
 Mobile Applications m/project-
 Cloud Computing monitoring-
Product Line Software and-control#

https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 3 CO2 III. SOFTWARE Powerpoint-Aided Paper and Pencil Test: eBook Pressman
1. Apply appropriate ENGINEERING Lecture Multiple Choice R.S.,
lifecycle model of  Defining the Discipline Software
software  The Software Process Engineering:
development. - The Process A
Framework Practitioner's
2. Describe a number - Umbrella Activities Approach,
of different process - Process Seventh
models and when Adaptation Edition, TMH
they may be used  Software Engineering Publication.
Practice
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

-The Essence of https://www.t

Practice utorialspoint.
- General Principles com/uml/uml
 Software _quick_guide
Development Myths .htm
 How It all Starts?
 SDLC “Development https://www.j
Life Cycle” avatpoint.co
Requirement Engineering m/project-
monitoring-
and-control#

https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 4 CO3 1. Describe software IV. SOFTWARE Powerpoint-Aided Paper and Pencil Test: eBook Pressman
engineering Process PROCESS Discussion Multiple Choice R.S.,
frame STRUCTURES Software
work/structure.  A General Process Engineering:
2. Use the knowledge Model A
of contemporary  The Process Flow Practitioner's
issues and emerging  The Software process Approach,
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

software Model Seventh

engineering trends,  Software Crisis Edition, TMH
models, tools, and  Program Vs. Software Publication.
techniques
MODELS https://www.t
3. Develop software  Water fall Model utorialspoint.
projects using  RAD Model com/uml/uml
modern engineering  Spiral Model _quick_guide
techniques and tools  V-Model .htm
 Incremental Model
Agile Model https://www.j
avatpoint.co
m/project-
monitoring-
and-control#

https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 5 CO3 V. MODELS Powerpoint-Aided Paper and Pencil Test: eBook Pressman
(Continuation) Discussion Multiple Choice R.S.,
1. Describe a number  Iterative Model Software
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

of different process  Bigbang Model Engineering:

models and when  Prototype Model A
they may be used.  Concurrent Model Practitioner's
 Specialized Process Approach,
2. Describe outline Models Seventh
process models for  The Unified Process Edition, TMH
requirements  Personal and Team Publication.
engineering in Process Models
scenario-based  Process Technology https://www.t
methods.  Products and Process utorialspoint.
com/uml/uml
REQUIREMENTS _quick_guide
3. Distinguish what MODELLING: SCENARIO- .htm
types of BASED METHODS
requirements are not  Requirements https://www.j
visible in these Analysis avatpoint.co
domains?  Scenario-Based m/project-
Modeling monitoring-
 UML Models That and-control#
Supplement the Use
Case https://www.g
- Developing an uru99.com/u
Activity Diagram ml-object-
Swimlane Diagrams diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

Week 6 CO2 1. Distinguish agile VI. AGILE Powerpoint-Aided Paper and Pencil Test: eBook Pressman
process model from DEVELOPMENT Discussion Multiple Choice R.S.,
other process  What is Agility? Software
models.  Agility and the Cost of Engineering:
Change A
2. Describe agile  What is an Agile Practitioner's
principles. Process? Approach,
- Agility Principles Seventh
3. Breakdown the - The Politics of Edition, TMH
difference of agile Agile Publication.
principles to other Development
software  Extreme https://www.t
development Programming utorialspoint.
process and models. - The XP Process com/uml/uml
- Industrial XP _quick_guide
 Other Agile process .htm
Models
- Scrum https://www.j
- Dynamic Systems avatpoint.co
Development m/project-
Method monitoring-
- Agile Modeling and-control#
- Agile Unified
https://www.g
Process
uru99.com/u
- A tool Set for Agile
ml-object-
Process diagram.html

https://sites.g
oogle.com/a/
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

rku.ac.in/soft
ware-
engineering/c
oursepack

Week 7 CO2 1. Use the techniques, VII. PRINCIPLES THAT Powerpoint-Aided Paper and Pencil Test: eBook Pressman
skills necessary for GUIDE PRACTICE Discussion Multiple Choice R.S.,
engineering  Software Engineering Software
practice. Knowledge Engineering:
 Core Principles A
2. Give original - Principles that Practitioner's
examples from the Guide Process Approach,
different principles - Principles that Seventh
within the framework Guide Practice Edition, TMH
activity.  Principles That Guide Publication.
Each Framework
Activity https://www.t
- Communication utorialspoint.
Principles com/uml/uml
- Planning _quick_guide
Principles .htm
- Modeling
Principles https://www.j
- Construction avatpoint.co
Principles m/project-
Deployment Principles monitoring-
and-control#

https://www.g
uru99.com/u
ml-object-
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 8 CO2 1. Analyze software VIII. UNDERSTANDING Powerpoint-Aided Paper and Pencil Test: eBook Pressman
requirements by REQUIREMENTS Discussion Multiple Choice R.S.,
applying various  Requirements Software
modeling Engineering Midterm_Recitation Engineering:
techniques.  Establishing the A
Groundwork Practitioner's
2. Describe functional - Identifying Approach,
and non-functional Stakeholders Seventh
requirements. - Recognizing Edition, TMH
Multiple Viewpoint Publication.
3. Explain how - Working toward
software Collaboration https://www.t
requirements may - Asking the First utorialspoint.
be organised in a Questions com/uml/uml
requirements - Nonfunctional _quick_guide
document. Requirements .htm
- Traceability
 Eliciting https://www.j
Requirements avatpoint.co
 Developing Use m/project-
Cases monitoring-
 Building the Analysis and-control#
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

Model
 Negotiating https://www.g
Requirements uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 9 CO2 1. Demonstrate the IX. PROJECT Powerpoint-Aided Paper and Pencil Test: eBook Pressman
ability to develop a MANAGEMENT AND Discussion Multiple Choice R.S.,
high-quality software PLANNING Software
system while  Introduction if Project Group Activity: Engineering:
working in a project Management Presentation of Midterm A
group  What is Project Project Practitioner's
Management? Approach,
2. Apply the principles,  Software Project Seventh
tools and practices Planning Edition, TMH
of IT project  Software Cost Publication.
management Estimation
 COCOMO Model https://www.t
 Putnam Resource utorialspoint.
Allocation Model com/uml/uml
_quick_guide
.htm

https://www.j
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

avatpoint.co
m/project-
monitoring-
and-control#

https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 10
Week 11 CO2 1. Develop SRS and XI. SOFTWARE Powerpoint-Aided eBook Pressman
other software REQUIREMENTS Discussion R.S.,
engineering  Software Paper and Pencil Test: Software
documents in the Requirement Multiple Choice Engineering:
project report. Specifications A
2. Explain two  Requirements Practitioner's
techniques for Analysis Approach,
describing system - Data Flow Seventh
requirements Diagrams Edition, TMH
3. To explain how - Data Publication.
software Dictionaries
requirements may - Entity- https://www.t

Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

be organised in a Relationship utorialspoint.

requirements Diagram com/uml/uml
document _quick_guide
.htm

https://www.j
avatpoint.co
m/project-
monitoring-
and-control#

https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 12 CO2 1. Explain software XII. SOFTWARE Powerpoint-Aided Paper and Pencil Test: eBook Pressman
design principles. DESIGN Discussion Multiple Choice R.S.,
 Software Design Software
2. Design a good User Principles Engineering:
Interface according  Coupling and A
to its purpose. Cohesion Practitioner's
 Function Oriented Approach,
Apply the use of Design Seventh
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

 Object Oriented Edition, TMH

Design Publication.
 User Interface
Design https://www.t
utorialspoint.
com/uml/uml
_quick_guide
.htm

https://www.j
avatpoint.co
m/project-
monitoring-
software design
and-control#
principles
https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 13 CO2 1. Use Unified XIII. UML USE CASE Powerpoint-Aided Paper and Pencil Test: eBook Pressman
Modeling Language DIAGRAM Discussion Multiple Choice R.S.,
in software  Why Use-Case Software
specification diagram? Engineering:
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

 Use-case diagram A
notations Practitioner's
 How to draw a use- Approach,
case diagram? Seventh
 Tips for drawing a Edition, TMH
use-case diagram Publication.
 An example of a use-
case diagram https://www.t
 When to use a use- utorialspoint.
case diagram? com/uml/uml
 Goals of UML _quick_guide
.htm
documents.
UML OVERVIEW
 UML Building Block https://www.j
2. Create UML Use-
 UML Architecture avatpoint.co
Case diagram for
 UML Modeling Types m/project-
identified project.
 UML Basic Notations monitoring-
 UML Standard and-control#
3. Differentiate UML
Diagrams
Diagrams.
 UML Class Diagram https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

Week 14 CO4 1. Create UML Use- XIV. UML Powerpoint-Aided Paper and Pencil Test: eBook Pressman
Case diagram for (Continuation) Discussion Multiple Choice R.S.,
identified project.  UML Object Diagram Software
 UML Component Engineering:
2. Differentiate UML Diagram A
Diagrams.  UML Deployment Practitioner's
Diagram Approach,
3. Apply Web-app  UML use Case Seventh
principles in Diagram Edition, TMH
designing web-  UML Interaction Publication.
application. Diagram
 UML Statechart https://www.t
Diagram utorialspoint.
 UML Activity Diagram com/uml/uml
_quick_guide
WEB APP DESIGN .htm
 Web App Design
Quality https://www.j
 Design Goals avatpoint.co
 A Design Pyramid for m/project-
Apps monitoring-
 WebApp Interface and-control#
Design
 Aesthetic Design https://www.g
 Content Design uru99.com/u
 Architecture Design ml-object-
 Navigation Design diagram.html
Test Strategies for
Webapps https://sites.g
oogle.com/a/
rku.ac.in/soft
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

ware-
engineering/c
oursepack

Week 15 CO4 1. Apply Web-app XV. MOBILE APP DESIGN Powerpoint-Aided Paper and Pencil Test: eBook Pressman
principles in  Challenges Discussion Multiple Choice R.S.,
designing web-  Developing Web Apps Software
application. - MobileApp Engineering:
Quality A
2. Demonstrate a good - UI Design Practitioner's
design for mobile- - Context Aware Approach,
application. Apps Seventh
 MobileApp Design Edition, TMH
Best Practices Publication.
3. Give original example  Mobility Environments
of challenges in  The Cloud https://www.t
designing mobile-  Test Strategies for utorialspoint.
applications. Webapps com/uml/uml
_quick_guide
4. Apply the techniques CODING .htm
in programming  Coding
(developing the  Programming Style https://www.j
project).  Structured avatpoint.co
Programming m/project-
 Software monitoring-
Management and-control#
- Project
Management https://www.g
- Activities uru99.com/u
 Project Management ml-object-
Tool diagram.html
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 16 CO4 1. Describe software XVI. RISK MANAGEMENT Powerpoint-Aided Paper and Pencil Test: eBook Pressman
management risks.  Risk Management Discussion Multiple Choice R.S.,
 Risk Management Software
2. Understanding on Activities Engineering:
SQA and how to  Project Scheduling Midterm_Recitation A
ensure good quality  Personnel Planning Practitioner's
software. SOFTWARE QUALITY Approach,
ASSURANCE Seventh
3. Understand the of SOFTWARE VALIDATION Edition, TMH
approaches to AND VERIFICATION Publication.
software verification
and validation. https://www.t
utorialspoint.
4. Explain the com/uml/uml
importance of _quick_guide
Software V and V. .htm

5. Understand the of https://www.j

approaches to avatpoint.co
software verification m/project-
and validation. monitoring-
and-control#

Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 17 CO4 1. Describe the causes XVII. SOFTWARE Powerpoint-Aided Group Activity: Presentation of eBook Pressman
of Software MAINTENANCE Discussion Final Project, both software R.S.,
Maintenance. AND and document. Software
REENGINEERING Engineering:
2. Differentiate Software  Software A
Maintenance and Maintenance Practitioner's
Re-engineering in  Causes of Software Approach,
Software Maintenance Seventh
Engineering.  Software Edition, TMH
Maintenance Cost Publication.
Analyze the effects of Factors
software maintenance and https://www.t
re-engineering. REENGINEERING utorialspoint.
 What is com/uml/uml
Reengineering? _quick_guide
 Software .htm
Reengineering
 Business Process https://www.j
Reengineering avatpoint.co
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

 Reverse Engineering m/project-

 Restructuring monitoring-
 Forward Engineering and-control#
The Economics of
Reengineering https://www.g
uru99.com/u
ml-object-
diagram.html

https://sites.g
oogle.com/a/
rku.ac.in/soft
ware-
engineering/c
oursepack

Week 18 FINALS
Course References
Laboratory supplies, computers, , Camera, Multimedia Authoring Tools, Film Clappers, etc.
Additional Materials
Adobe: Premiere Windows: Paint, Movie Maker , Sony Vegas Pro 10, Audacity, Adobe Photoshop CS6
Course State the nature of the requirements. Be very clear with what you would expect the students to pass, perform, or submit to pass the course.
Requirements • Students are expeted to create their own design especially of the elements of Multimedia, e.i., Text, Graphics, Animation, Audio and
Video.
• They are also expected to apply all the techniques in cinematography, especially when they’re asked to create a simple video clip, and/or
even short films.
• As individual output, a Portfolio of all the output of students of graphic editing and designing using Adobe Photoshop CS6, including some
of the photos captured as their output for photography.

Seatwork, Recitation, Assignment 5%

Quizzes 15%
Drills & Exercises 25%
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

Major Written Exam 25%

Major Hands-on Exam 30%
100%
Course Policies ATTENDANCE
a. Attendance
 All students are required to attend classes regularly and punctually
 Attendance shall be checked and counted from the first regular meeting of classes, regardless of the time the student enrolled.
 A student is held responsible for all assignments and for the entire content of the course missed, regardless of whatever reason he has for
his absence.
 Should you miss class, it is your responsibility to make up all the work done that day as well as get the notes for that class period from a
peer in the class. If you missed a quiz it is up to you to reschedule a make-up test time. Don’t expect your instructor to seek you out and
reschedule a time for you.
b. Absence
 Any student who is absent from class must obtain an excuse slip from the Dean together with other valid documentation/s (i.e. medical
certificates) to be presented to the instructor concerned not later than the second class session following the student’s return before he might be
given any considerations for taking the missed quiz or drill..
 When the number of unexcused absences reaches to 3 consecutive meetings, the student shall be warned and if he failed to attend to the
class on the four (4) successive absences, the instructor will mark “UW” (Unauthorized Withdrawal) on his class record. Given that the four
consecutive absences acquired were before the midterm or final term hence, the student shall be given a grade of “5”.
 To be considered as Officially Dropped “OD”, the student shall present the signed dropping form to the respective instructor.
c. Tardiness
 Student shall come to class on time unless of course there is an unavoidable circumstances but in the case of tardiness, the student shall
ensure that he will not miss any graded activities like quizzes, seat works, drills, etc. otherwise, he will be required to present an excuse letter
signed by the dean before he shall take the test or if in case that he come on class not later than after the quiz started, the instructor may allow
him to join the class and take the quiz/drill and may possibly repeat the missed items or the student might start on the item by the time he
comes to the class
UNIFORM
 Students are required to wear the prescribed school uniform while on campus everday, except on Wednesday, which is a free day.
 Students who have classes on Wednesdays are required to wear clothes appropriate to the academic environment. It is required to wear
business suits or Sunday’s best.
 P.E. uniforms must be worn only for P.E. classes.
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

 Students who are not in their school uniform must not be entertained to class except for some valid reasons but they must first secure an
excuse letter signed by the dean stating the reason why they are not in uniform.
MISSED EXAMS OR ASSIGNMENTS
 All assignments must be completed on or before the given date. Late assignments should not be entertained unless of course for some
considerable reasons. But there is a corresponding deduction for that.
 Any student absent on an examination date may be given a make-up exam and earn 100% credit, only if they submit documentation of an
illness, doctor’s visit, mandatory business appointment, jury duty, etc.
 Students who do not submit appropriate documentation will not be permitted to take a make-up examination and the score will be
recorded as zero (0).
PLAGIARISM /INTELLECTUAL DISHONESTY
 This occurs when you knowingly submit someone else's ideas or words as your own. Plagiarism is an act of intentional deception that not
only is dishonest; it robs you of the most important product of education---the actual learning. This will not be tolerated in any form. All work will
be checked for individuality. If a student is found to have copied another's work, that student will receive a zero for that day's attendance and
assignment. If you are found guilty of academic dishonesty, you will automatically fail that assignment. If you are caught plagiarizing again in the
same quarter, you will fail this class.
Examples of academic dishonesty are, but not limited to:
 Letting someone copy your assignment/test.
 Substituting for another student, or permitting another student to substitute for oneself, to take a test.
 Knowingly using another person’s disk and submitting work from the disk as your own.
 Giving your data disk to someone for whatever reason to look at or use your work.
 Working on an assignment/test with a classmate or someone else. You must complete your own work.
 Copying someone’s file and changing a few items and submitting it as your own.
CELLULAR PHONES/LAPTOPS/OTHER GADGETS
 In order to ensure a productive learning environment, you are required to set your personal communication device to silent contact or in a
lowest volume level during class time especially if your instructor is giving a lecture. Use of cell phones and other similar communication device is
not allowed during classes unless such activity supports class activities. Since these same communication devices are now being use for
emergency purposes your instructor permitted you to just put it on a silent mode but do not entertain unimportant call or text during class hours. If
in case there is an important call, just answer it in a manner that the class will not be disturbed.
 Laptops may be used in class but only for class related activities (e.g., taking notes, completing in-class or group writing assignments). If it
becomes apparent you are using the computer for non-class activities (checking your email, playing games, Facebooking, etc.) you should ask
first your instructor if it is allowed then that’s the only time you may access those computer programs. But if you are not allowed to open those
Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number:
 INSTITUTIONAL COURSE SYLLABUS

programs and you will be caught the instructor will ask you to turn off your computer and refrain from bringing it into class in the future.
Other Important Rules inside the Lecture/Laboratory Room:
 Maintain the cleanliness of the room and of the computer units
 Always turn off the computer units, lights, aircondition units and fans before leaving
 No combing of hair, no nail cutting inside the laboratory room
 No vandalism on the walls and on the furniture and equipment
 Do not forget to bring flashlights (for those students who has night classes)
 Always show discipline, respect, honesty and good behavior inside the class.
An Invitation: If you have any questions or concerns about your progress in this course, please arrange a time to speak with your instructor
immediately. There are few problems that can’t be worked around, but it is necessary that you initiate a discussion about the issue at hand in
order for any action to result.
Supplementary Include supplementary material to help students succeed in the course.
Material/s • Online tutorials on graphics designing.
• Book about multimedia such as Cinematography, films in the Philippines and the likes.
• IT-CS Building Computer Laboratory, PSU-New Library Building where students can develop and enhance their knowledge as well as
their skills when it comes to project management especially Production Team.
Consultation Period Tuesday: 10:30-11:30
Tuesday: 6:00-6:30
Friday:6:00-6:30

Doc Ref. No.: Revision Level: Effective Date: November 2018 Page Number: