COURSE LEARNING PLAN

COLLEGE OF COMPUTER SCIENCE

SOFTWARE DEPARTMENT

COURSE TITLE COURSE CODE

SOFTWARE PROJECT SOFTPRO

COURSE PREREQUISITES/CO-REQUISITES UNITS

OOPROGR / SYSANDE 3

COURSE DESCRIPTION
This course is intended to provide the students with an overall process of software project development. It captures a software management perspective that emphasizes a balanced view of
the following elements: theory and practice, technology and people, customer value and provider profitability, strategies and tactics.

COURSE OBJECTIVE
1. To understand the concept of software project management as a practice.
2. To build a project team and create essentials plans for the project.
3. To understand the importance of tracking project progress and technical documentation
4. To create a technical document for the software project
5. To apply knowledge and skill in developing software solutions to real world problems
6. To build and present the software project

1
 METHODOLOGY/
WEEK SESSION DATE LEARNING OUTCOME TOPIC RESOURCES ASSESSMENT
ACTIVITIES
Orientation
Vision/Mission of UMAK/CCS
1
Course Requirement/Grading
System
A. What is a Project?
B. What is a Software Project?
C. Three key assets of software
1. Discuss the concepts regarding project
software project management People
1 including the knowledge areas Process
and constraints. Technology Powerpoint Seatwork
2. Explain roles and D. What Software Project Lecture/PowerPoint Reference Book Group Discussion
2 responsibilities of Project team Management Presentation Internet Article: The Quiz
3. Discuss and explain technical E. Four essential properties of Discussion Many Roles in Project Team
documentation importance, Software Software Project composition
structure and format F. Project Management
Knowledge Areas
G. Project Constraints
H. Starting and Finishing
Software Projects
I. Technical Documentation
1. Discuss and explain the phases A. Phases of Software
Lecture/PowerPoint Powerpoint
of Software Project Development Lifecycle Group Activity
1 Presentation Video Presentation
2. Discuss steps in project initiation B. Initiating Software Project Quiz
Discussion Reference/Internet
C. Identifying the Purpose
1. Discuss and explain Software A. Development-Process Software Requirement
2-3
Development Process Framework Specification
Powerpoint
Framework Users, Customers and Lecture User Stories
2 Reference Book
2. Discuss and explain Acquirers (User Stories) Discussion User Task/Profiles
Internet
components of project System requirements and Project Rationale
proposal System Design Paper (3 Proposal)

2
 3. Create a software project Verification and Validation
proposal D. Software development models
Traditional models
Iterative models
B. Project Proposal
A. Project Charter
B. Foundation elements of
1. Discuss and explain components
Software Project
of project charter Project Charter
Product Foundation
2. Create a project charter Advance Reading Powerpoint Software Project
Process Foundation
1 3. Discuss and explain elements of Lecture Video Presentation Management Plan
C. Working the Project Plan
software project Discussion Reference/Internet Baseline requirement
Architecture
4 4. Discuss and explain the purpose
Decomposition View
of Project Plan
Work Breakdown
Structure
1. Identify the project risks and A. Project schedule
Advance Reading Powerpoint
constraints. Project constraints Project Calendar
2 Lecture Video Presentation
2. Understand project Estimating product Gantt Chart
Discussion Reference/Internet
estimations. size
A. Software Design
Wire Framing
Database design
Report design Quiz
1. Discuss and explain importance B. Software Quality assurance Software Requirement
Powerpoint
of software design standard Specification
5-6 1 Video Presentation
2. Discuss standards regarding ISO/IEC 25010:2011 Lecture User Interface
Reference/Internet
software and ensuring quality. (SQuaRE) Requirement
C. Verification and Validation Specification
Acceptance Criteria Test Cases
Test Plans/UAT

3
 Milestone 1 (20% of
system)
Project Progress
1. Tracking Project Performance
Report
1. Discuss project updates and 2. Documentation Milestone Evaluation
2 Group minutes of
status. 3. Project Consultation and Form
meeting
Checking of Milestone 1
Individual assignment
and performance
rating sheet
Milestone 2 (40% of
system)
Project Progress
1. Apply concepts on proper Report
1. Consultation and Checking of Milestone Evaluation
7-8 1&2 system/software Group minutes of
Milestone 2 Form
documentation. meeting
Individual assignment
and performance
rating sheet
MIDTERM EXAM
9 (Group Progress Report and Individual Performance Rating)
includes Milestone 3 (60% of system) checking
Milestone 3 (60% of
system)
Project Progress
Report
1. Discuss project updates and A. Consultation and Checking of Milestone Evaluation
10 1 Group minutes of
status. Milestone 3 Form
meeting
Individual assignment
and performance
rating sheet
1. Discuss project updates and A. Consultation and Checking of Milestone Evaluation Milestone 4 (80% of
11-12 1&2
status. Milestone 4 Form system)

4
 Project Progress
Report
Group minutes of
meeting
Individual assignment
and performance
rating sheet
Database Requirement
Specification
Milestone 5 (100% of
system)
Project Progress
Report
Group minutes of
1. Discuss project updates and A. Consultation and Checking of Milestone Evaluation
13-14 1&2 meeting
status. Milestone 5 Form
Individual assignment
and performance
rating sheet
Testing and Validation
Specification
Defense Rating Sheet
FINALS (PROJECT DEFENSE) PowerPoint
presentation
15
Complete Software
Application of concepts learned Defense Rating Sheet
1&2 A. Defense Project
upon project presentation. (Rubric)
Software Project
A. Revision of Software and Project acceptance (revised)
16-17 1&2
Documentation and Revision Form Documentation
(revised)
A. Submission and Encoding of
18 1&2
Grades

5
REQUIRED READING (TEXTBOOK)
Software Project Management for Dummies
By: Teresa Luckey and Joseph Phillips

Managing and Leading Software Projects

By: Richard E. Fairley

SUGGESTED READING

COURSE REQUIREMENTS
*Good and working Software Project
*System Documentation
*Midterm Evaluation (Progress report and Individual performance rating)
*Groupings: minimum of 3 and maximum of 4 members
*Complete Milestone checking prior the scheduled Final Defense

I. Deliverables: (a) System and (b) Documentation

A. System based on the approved charter stipulated in Work Breakdown Structure requires 5 major system components (progressive/cumulative)
1st Milestone 20% (1st major system component)
2nd Milestone 40% (2nd major system component)
3rd Milestone 60% (3rd major system component)
4th Milestone 80% (4th major system component)
5th Milestone 100% (Complete system )

B. Document Requirements
1st Proposals (3 proposals)
2nd Project Charter (approved proposal)
3rd System Documentation 1/Project Scope Management Plan (PSMP)
4th System Documentation 2/Software Requirement Specification (SRS)
5th System Documentation 3/ Database Requirement Specification (DRS)

6
 6th - System Documentation 4/ User Interface Requirement Specification (UIRS)
7th System Documentation 5/ Testing and Validation Specification (TVS)
8th - Appendices

II. SOFTWARE PROJECT DEFENSE. System must be 80% complete/working prior the scheduled Project Defense and complete Documentation. (Completed the scheduled milestone
checking)

GRADING SYSTEM
Midterm/Final Period

Class Standing (60%)

Quizzes/Written Deliverables -20%
Attendance/ Attitude -10%
Lab. Exers / Project Milestones -30%
Major Exam/Defense (40%)
Individual -60%
Group Grade -40%

NOTE:
(a) Midterm Examination is Group Progress Report (3 Milestones) and Individual Performance Rating
(b) Final Examination is Project Defense

CLASSROOM POLICIES

Medium of Instruction
The medium of instruction is English.

Attendance
The University requires that every student to attend all classes regularly. Anyone who incurs 20 % (11 hours) of the total hours of instruction may be given a failing grade, if
majority of absences are unexcused. (University of Makati, Student Handbook)

Honor, Dress and Grooming Code

All students are required to attend classes in their prescribed uniform:

7
For Male Students
White polo with patch sewn a little above the left side of the chest
Brown Slacks
Black Shoes
ID

For Female Students

White Blouse with school patch
Brown Pants
Black closed leather shoes
ID

Students shall at all time neat, clean and decent in their clothing, orderly, respectful, and courteous in their conduct.
(University of Makati, Student Handbook)

All students of University of Makati are expected to conduct themselves properly, to respect the persons around them and the rights of their
(a) fellow students, faculty members, school administrators, school authorities and employees. Also, they should preserve human dignity and uphold the good name of the
University at all times. (University of Makati, Student Handbook)

CONSULTATION HOURS

COURSE/PROGRAM
SOFTPRO / B.S. COMPUTER SCIENCE Major in Application Development
PREPARED BY CHECKED BY APPROVED BY REVISED BY

ROMMEL L. DORIN, MIT ROEL C. TRABALLO, MSIT DANILO C. SABADO, D.T.

Faculty, College of Computer Science Chair, Software Programs Dean, College of Computer Science