MATHEMATICAL AND COMPUTING SCIENCES UNIT

DEPARTMENT OF PHYSICAL SCIENCES AND MATHEMATICS

COLLEGE OF ARTS AND SCIENCES
UNIVERSITY OF THE PHILIPPINES MANILA

Course Code: CMSC 128.1 Course Title: Software Engineering I Prerequisites: CMSC 121, CMSC 127
Credit Units: 3 Lecture Unit(s): 2 units; 2 hrs/week Laboratory Unit(s): 1 unit; 3hrs/week
Course Description Application of sound engineering principles in the development of software systems; Software Development Life Cycle (SDLC); Requirements analysis
and specification, design, construction, testing, deployment, operation and maintenance. Additional topic on project management is likewise included.
Instructional Materials and References:
1. Pressman, Roger. Software Engineering: A Practitioner's Approach, 7th edition. McGraw-Hill Science/Engineering/Math, 2009
2. Sommerville, Ian, Software Engineering, 9th edition. Addison-Wesley, 2010.
3. Satzinger, J., Jackson, R., Burd, S., Systems Analysis and Design in a Changing World, 6 th edition, Course Technology, 2012
4. Grady Booch, Robert A. Maksimchuk, Michael W. Engel, and Bobbi J. Young, Object-Oriented Analysis and Design with Applications, third edition.
Benjamin/Cummings 2007.
5. Rob Pooley, Perdita Stevens, Using UML Software Engineering with Objects and Components, second edition. Addison-Wesley 2005.
6. Bernd Bruegge and Allen H. Dutoit, Object-Oriented Software Engineering Using UML, Patterns and Java, third edition. Prentice Hall, 2009.

Program/Student Outcomes

1. Incorporate the latest developments in Computer Science and Information Technology in the design of software systems for various applications
2. Create innovative solutions through research and development projects in Computer Science
3. Exhibit moral, ethical and social responsibilities as a professional and as a Filipino citizen
4. Work collaboratively in teams
5. Communicate computing solutions effectively

Course Outcomes

1. Apply sound engineering principles in the analysis, design, development, deployment and maintenance of large software systems
2. Experience how to use available CASE (Computer Aided Software Engineering) tools to support the activities associated to each phase in the SDLC.
3. Work in teams on projects that are either case studies provided by the instructor, or real-world projects.
4. Present the working system in class.
5. Produce the necessary documentation (Project Plan, Requirements Traceability Matrix, Software Requirements Specs, Design Documentation, Test Logs,
Deployment Plan, User’s Manual)
 TEACHING-
TIME METHOD OF
COURSE OUTCOMES TOPICS INTENDED LEARNING OUTCOMES LEARNING
FRAME ASSESSMENT
ACTIVITIES
Apply sound engineering Lecture: Week 1 To be able to Lecture/Class Class participation
principles in the analysis, design, Introduction to Software  Understand what is software discussion
development, deployment and Engineering engineering and appreciate Survey results
maintenance of large software the importance of Survey of open
systems Laboratory: application of sound source CASE tools
Survey of available open engineering principles in the
source tools for planning, development of software
analysis and design systems.
 Know the different myths
associated with software
development
Apply sound engineering Lecture: Week 2 To be able to Lecture/Class Recitation
principles in the analysis, design, Software Process Models  Know the different software discussions
development, deployment and development methodologies
maintenance of large software Laboratory: and identify in what Seatwork on the
systems Seatwork (Give scenarios instances should each one be most appropriate
and then let each student used SDLC methodology
group justify their choice of a given project
for the most appropriate
systems development Recitation
methodology)
Experience how to use available Lecture: Week 3 To be able to Lecture/Class Presentation of
CASE (Computer Aided Software Project Management  Appreciate the importance discussions submitted Gantt
Engineering) tools to support the Orientation re Group of good project management Chart
activities associated to each phase Project in increasing the success rate Hands-on using
in the SDLC. of a given project spreadsheet or any
Laboratory: project management
Work in teams on projects that Group Dynamics (board tool to create Gantt
are either case studies provided work) See Project Chart
by the instructor, or real-world Management Lab
projects. Exercise.docx Group Work

Use Excel or any project

management tool to
come up with a Gantt
Chart for a simple website
project
Apply sound engineering Lecture: Week 4 To be able to Lecture/Class Presentation of
principles in the analysis, design, Software Quality  Understand the role of the discussions Requirements
development, deployment and Assurance (SQA) QA team who will ensure Traceability Matrix
maintenance of large software that system features are Group discussion on Or
Course Requirements

Lecture (50%)
Midterm Exam 20%
Final Exam 20% 50%
Hands-on Exercises, Seatwork, Recitation, Assignment 10%
Laboratory (50%)
Project
Implementation of Functional and Non-functional 40% 50%
Requirements
Documentation 10%
Grand Total 100%

Classroom Policies:

1. The grade in the Lecture component should be not lower than 50% (i.e. 50% of 40%). This is to ensure that the student gains minimum understanding of the
concepts and pass not just because of high marks in the lab
2. Missed exam rule: A student is allowed to make up for only one missed exam, provided that the reason is valid. If another exam is missed, the student will get a
zero in that exam. The special exam is usually scheduled after the Finals and covers all topics of the entire course
3. Cheating during an examination is a major offense. A student caught cheating during exams will automatically be given a grade of 5.0

GRADING SCALE

≥ 93 90–92 87–89 84–86 80–83 75–79 70–74 65–69 60–64 55–59 ≤ 55

1.0 1.25 1.5 1.75 2.0 2.25 2.5 2.75 3.0 4.0 5.0

Faculty-in-charge: Prof. Ma. Sheila A. Magboo

Email: sheilaabad@yahoo.com or sheilaabad@gmail.com
Consultation Hours: