Republic of the Philippines
CAVITE STATE UNIVERSITY
CAVITE CITY CAMPUS
Pulo, Dalahican, Cavite City
Tel. No. (046) 431-35-70; Telefax: (046) 431-35-80
COURSE SYLLABUS
SECOND SEMESTER, ACADEMIC YEAR 2010-2011
Professor / Instructor :
Mark B. Bilangel
E-mail Address
:
markbilangel@gmail.com
Office Location
:
CvSU Cavite City – I.T. Department
Course Code
:
DCIT60
Course
:
Bachelor of Science in Information Technology
Course Title
:
Software Engineering
Course Description
:
Phases of software engineering, requirement analysis and design,
system development, coding, testing, debugging, deployment,
maintenance and support, configuration management, capability maturity
model and model-integrated, and software evaluation and validation.
Credit Unit
:
3
Lecture
:
2
Laboratory
:
3
Prerequisite
:
ITEC55
Course Objectives
:
Credit Hours
At the end of the semester, 70% the student should be able to:
1. Explain the mission, goals and objective of the university, college and department
2. Discuss the phases of a software process.
3. Design a software process model.
4. Prepare a solution to be followed in software creation coming from a specific problem
description.
5. Formulate requirements analysis needed in software planning.
6. Illustrate various parts needed in designing an effective program.
7. Formulate an algorithm needed to solve the problem.
*Algorithm should be implemented by means of a programming language.
8. Test the efficiency and effectiveness of generated data coming from the program
created.
9. Document the outcome of different software process model.
10. Evaluate the efficiency and effectiveness of the system by means of acceptance
testing.
Core Values
:
Students are expected to live by and stand for the following University tenets:
TRUTH is demonstrated by the student’s objectivity and honesty during examinations, class activities
and in the development of projects.
EXCELLENCE is exhibited by the students’ self-confidence, punctuality, diligence and commitment in
the assigned tasks, class performance and other course requirements.
SERVICE is manifested by the students’ respect, rapport, fairness and cooperation in dealing with
their peers and members of the community.
In addition, they should exhibit love and respect for nature and support for the cause of
humanity.
Course Content
Course Calendar
LEC
LAB
I. Introduction
A. Mission, goals and objectives of the University and Department
B. Introduction about the subject
2 hrs
II. Introduction to Software Engineering
A. Software characteristics
B. Building a system
C. Members of the development team
D. Software development steps
E. Quality and productivity factors
F. Case Study:
Problem description presentation
4 hrs
III. Modeling the Process and Life Cycle
A. Software Process Models
B. Tools and Techniques for Process Modeling
C. Case Study:
Process modeling phase
2 hrs
First Long Examination
Lecture
2 hrs
IV. Planning and Managing the Project
A. Tracking Progress
B. Project Personnel
C. Risk Management
D. Project Plan
E. Case Study:
Planning and managing phase
2 hrs
V. Capturing the Requirements
A. Requirement Process
B. Types of Requirements
C. Characteristics of Requirements
D. Prototyping Requirements
E. Participants in the Requirements Process
F. Case Study:
Requirements gathering phase
4 hrs
Midterm Examination
Lecture
2 hrs
VI. Designing the System
A. Concepts of design
B. Issues in design creation
C. Characteristics of good design
D. Design Evaluation and Validation
E. Design Reviews
F. Documenting the design
G. Case Study:
System design phase
4 hrs
VII. Writing the Programs
A. Structure Coding Techniques
B. Programming Standards and Procedures
C. Programming Guidelines
D. Documentation
2 hrs
3 hrs
6 hrs
6 hrs
6 hrs
3 hrs
E. Case Study:
Coding phase
6 hrs
VIII. Testing the Program
A. Software Faults and Failures
B. Stages of Testing
C. Kinds of Testing
D. Case Study:
Program testing phase
2 hrs
Second Long Examination
Lecture
2 hrs
IX. Delivering the System
A. Training
B. Documentation
C. Case Study:
Program implementation phase
2 hrs
X. Maintain the System
A. Types of System
B. Maintenance Activities and Roles
C. Maintenance Problems
D. Measuring Maintenance Characteristics
E. Case Study:
Program maintenance phase
2 hrs
XI. Evaluating the Products, Processes and Resources
A. Approaches to Evaluation
B. Selecting an Evaluation Technique
C. Evaluating the Products
D. Evaluating Processes
E. Evaluating Resources
F. Case Study:
Evaluation phase
2 hrs
6 hrs
3 hrs
6 hrs
3 hrs
XII. Final Project
A. Presentation of final project
6 hrs
Final Examination
Lecture
2 hrs
TOTAL
36 hrs
54 hrs
Teaching Methods / Learning Activities:
Group Work (Suggested for all Chapters)
Case Study (Suggested for all Chapters)
Reporting (Suggested for Chapters 2, 3 and 4)
Interactive Learning (suggested for all Chapters)
Problem Solving (Suggested for Chapters 2 and 3)
Research (Suggested for all Chapters)
Type study method (Suggested for Chapters 4, 5 and 6)
Simulations (Suggested for Chapters 5, 6 and 7)
Team teaching (Suggested for all Chapter)
Brainstorming (Suggested for Chapters 2 and 3)
Instructional Materials :
LCD Projector, Computer, White Board, Whiteboard Marker
Textbooks/References:
Pressman, R. (2001). Software engineering : a practitioner’s approach (5th ed).
Prentice Hall Inc.
Shari, Lawrence, Pfleeger (1991). Software engineering, the production of quality
software (2nd ed). . New York: Macmillan Publishing Company
Course Requirements:
1. Major Examinations (Midterm and Finals)
2. Case Study (For every chapter during lecture)
3. Development of a software
Note:
a. Software development should be done every laboratory.
b. The specifications of the software will come from the requirements
of the client.
4. Software Defense
Note:
a. Software defense will be conducted 2 weeks before the finals exam.
b. It should be presented with supporting documents.
c. There will be a preliminary defense that will serve as midterm project.
The general guidelines of the defense together with the format of the document will be
formulated and announce during on consortium.
Evaluation of Student Performance / Grading System
1. The lecture and laboratory are graded separately. The final grade is
based on 60% lecture and 40% laboratory. To pass the course, a student
must get a grade of 3.00 or better.
2. The grade in lecture is based on examinations, quizzes, attendance and
assignments. The laboratory grade is based on examinations, exercises,
quizzes, attendance and special projects. The distribution is as follows:
Lecture
Midterm Exam
Finals Exam
Quizzes
Long Exam
Attendance
Project
(40%)
25%
25%
15%
20%
10%
5%
Laboratory
Software Defense
individual grade
group grade
(60%)
Running Program
panel grade
50%
TOTAL
100%
TOTAL
100%
40%
10%
2. The grading scale is as follows:
96.64 – 100.00
93.31 – 96.63
89.98 – 93.30
86.65 – 89.97
83.32 – 86.64
79.99 – 83.31
76.66 – 79.98
73.33 – 76.65
70.00 – 73.32
66.67 – 69.99
Below – 66.66
1.00
1.25
1.50
1.75
2.00
2.25
2.50
2.75
3.00
4.00
5.00
Passing Grade
Conditional
Failed
Course Policies
A. Attendance
Students are not allowed to have 20% or more absences of the total class
hours, otherwise, they will be graded as follows:
Dropped (if majority of the excessive absences are excused)
Failed (if majority of the excessive absences are unexcused)
B. Classroom decorum
Students are required to:
1. wear their identification cards and observe proper dress code at all times;
2. turn off or put in silent mode their cellular phones during class hours;
3. maintain cleanliness and orderliness of the room at all times; and
4. come to class on time.
C. Examination/ Evaluation
1. Quizzes may be announced or unannounced.
2. Long examinations are always announced.
3. Cheating is strictly prohibited. A student who is caught cheating will be given a score of
”0” for the first offense. For the second offense, he/she will automatically fail the subject.
4. Examination permits are required during midterm and final examinations.
5. Students who missed exams, laboratory exercises, or quizzes may only be excused for
any of the following reasons:
a. participation in a University/College-approved field trip or activity (must be cleared
one week in advance);
b. personal illness (must present medical certificate); and
c. death or serious illness in the immediate family (must present death or medical
certificate).
Prepared by:
Recommended by:
Approved by:
Mark B. Bilangel
Professor/Instructor
Engr. Joel R. Austria
Department Chair
Cristeta M. Montano, Ph.D.
Dean