Page 1 of 12 AY1617 – July 15, 2016 /nsalas
HOLY ANGEL UNIVERSITY
COLLEGE OF INFORMATION AND COMMUNICATIONS TECHNOLOGY COMPUTER PROGRAMMING 3
COURSE SYLLABUS
Course Code : 6COMPRO3L Prerequisite : 6COMPPRO2L
Course Credit : 3 Units (2 hours LEC, 3 hours LAB) Year Level: 2nd year Degree Program : Bachelor of Science in Computer Science (BSCS)
Course Description :
This course focuses on intermediate to advanced programming. It includes the review of basic object-oriented concepts and advanced Object Oriented approaches such as interfaces, polymorphism and inheritance. Similarly, the course provides the opportunity to learn designing their own program exception types, data structures using and implementing linked list, applying abstract data types, stacks and queues, advance Graphical User Interface programming and Database Connectivity.
At the end of the course, students will be able to:
Course Outcomes Graduate Outcomes aligned to
CO1 To design computer programming system that solves a real world computing system problems that require a combination interface, polymorphism, inheritance, packages.
BSCS03: 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.
BSCS03.1: Reach substantiated conclusions and recommendations using fundamental principles of
mathematics, computing fundamentals, technical concepts and practices in the core information technologies, and relevant domain disciplines.
BSCS03.5: Formulate test cases that represents real world scenarios that will assess the fitness to purpose and level of satisfaction of user needs of the designed and developed systems, components or processes
BSCS03.8: Recommend and introduce corrections
Page 2 of 12 AY1617 – July 15, 2016 /nsalas
(debug), improvements and modifications to existing
solutions (systems, components or processes) to improve its appropriateness and effectiveness in addressing problems and/or requirements.
CO2 To formulate a software program that requires a
combination of reading text input, reporting exceptional conditions, designing own exception types, and
efficiently manipulating elements with linked lists, stacks and queues mechanism.
CO3 To develop, evaluate and recommend computer programming system that solves a real world
computing system problems that require a combination of graphical user interface programming, the graphical applications with visual gadgets and management of database systems
Learning Evidences
As proof of achievement of the above-mentioned outcomes, students are required to submit/demonstrate the following:
LE1: Programming Project CO1, CO2, CO3
Page 3 of 12 AY1617 – July 15, 2016 /nsalas
Measurement System
To assess the level of performance in the learning evidences, the following rubrics will be used:
Unsatisfactory (5) Satisfactory (10) Good (15) Excellent (20) Delivery (1-20) Completed less than
70% of the requirements.
Not delivered on time or not in correct format (disk, email, etc.)
Completed between 70- 80% of the requirements.
Delivered on time, and in correct format (disk, email, etc.)
Completed between 80- 90% of the
requirements.
Delivered on time, and in correct format (disk, email, etc.)
Completed between 90-100% of the requirements.
Delivered on time, and in correct format (disk, email, etc.) Coding
Standards (21-40)
No name, date, or assignment title included
Poor use of white space (indentation, blank lines).
Disorganized and messy
Poor use of variables (many global
variables, ambiguous naming).
Includes name, date, and assignment title.
White space makes program fairly easy to read.
Organized work.
Good use of variables (few global variables, unambiguous naming).
Includes name, date, and assignment title.
Good use of white space.
Organized work.
Good use of variables (no global variables, unambiguous naming)
Includes name, date, and assignment title.
Excellent use of white space.
Creatively organized work.
Excellent use of variables (no global variables,
unambiguous naming).
Documentation (41-60)
No documentation included.
Basic documentation has been completed including descriptions of all
variables.
Purpose is noted for each function.
Clearly documented including descriptions of all variables.
Specific purpose is noted for each function and control structure.
Clearly and effectively documented including
descriptions of all variables.
Specific purpose is noted for each function, control structure, input requirements, and
Page 4 of 12 AY1617 – July 15, 2016 /nsalas
output results.
Runtime (61-80)
Does not execute due to errors.
User prompts are misleading or non- existent.
No testing has been completed.
Executes without errors.
User prompts contain little information, poor design.
Some testing has been completed.
Executes without errors.
User prompts are understandable, minimum use of symbols or spacing in output.
Thorough testing has been completed
Executes without errors excellent user prompts, good use of symbols, spacing in output.
Thorough and organized testing has been completed and output from test cases is included.
Efficiency (81-100)
A difficult and inefficient solution.
A logical solution that is easy to follow but it is not the most efficient.
Solution is efficient and easy to follow (i.e. no confusing tricks).
Solution is efficient, easy to understand, and maintain.
Page 5 of 12 AY1617 – July 15, 2016 /nsalas
Learning Plan:
In order to achieve the outcomes of this course, learners will go through this learning plan.
Intended Learning Outcome
Unit#
(weeks)
Course Outcome
Topic Learning
Activities
Assessment Activity Student Output To design and implement
their own classes and supply instructor for each method.
To document their programs so that other programmers can
understand and use their creation.
To use packages to organize their classes.
To reuse
software components in multiple projects using interface and
polymorphism
Implement inheritance and make use of Object class
1-5 CO1 Objects, Classes, and Methods Method Parameters and Return Values Constructing Objects Accessor and
Mutator Methods The API
Documentation Instance Variables Encapsulation Specifying the Public Interface of a Class Commenting the Public Interface Providing the Class Implementation Local Variables Implicit Parameters
Segmented Lecture
Discussion Oral Recitation
Board work
Prelim Quiz Prelim
Seatwork/Assignments
Laboratory Activity Collaborative Activity Individual Activity
Required Program Required Individual and Group Work
Page 6 of 12 AY1617 – July 15, 2016 /nsalas
Intended Learning Outcome
Unit#
(weeks)
Course Outcome
Topic Learning
Activities
Assessment Activity Student Output Cohesion and
Coupling
Immutable Classes Static Methods Static Variables Using Interfaces for Algorithm Reuse Converting Between Class and Interface Types
Polymorphism Using Interfaces for Callbacks
Inner Classes Inheritance Hierarchies Implementing Subclasses
Overriding Methods Subclass
Construction
Page 7 of 12 AY1617 – July 15, 2016 /nsalas
Intended Learning Outcome
Unit#
(weeks)
Course Outcome
Topic Learning
Activities
Assessment Activity Student Output Converting Between
Subclass and Superclass Types Polymorphism and Inheritance
6 Prelim
Examination To apply file input and
output.
To create programs that can report exceptional conditions and to recover when an
exceptional condition has occurred.
To use linked list that allows to add and remove elements
efficiently, without moving any existing
elements.
To conceptualize the distinction between concrete and abstract data types (stack and queue types)
7-11 CO2 Reading and Writing Text Files
Reading Text Input Throwing Exceptions Checked and
Unchecked Exceptions
Catching Exceptions The finally Clause Designing Your Own Exception Types Using Linked Lists Implementing Linked Lists
Abstract Data Types Stacks and Queues
Lecture
Discussion Oral Recitation
Collaborati ve Activity Individual Activity Board work
Prelim Quiz Prelim
Seatwork/Assignments
Laboratory Activity Collaborative Activity Individual Activity
Required Program Required Individual and Group Work
Page 8 of 12 AY1617 – July 15, 2016 /nsalas
Intended Learning Outcome
Unit#
(weeks)
Course Outcome
Topic Learning
Activities
Assessment Activity Student Output
12 Midterm
Examination To apply graphical user
interface programming.
and applications.
To assess Swing user- interface
toolkit.
To query and update information in a relational database, and to access database information.
13-17 CO3
Graphical
Applications and Frame Windows Drawing on a Component
Ellipses, Lines, Text, and Color
Shape Classes Events, Event Sources, and Event Listeners
Using Inner Classes for Listeners
Building Applications with Buttons
Processing Timer Events
Mouse Events Graphical user interfaces
Lecture
Discussion Oral Recitation
Collaborati ve Activity Individual Activity Board work
Prelim Quiz Prelim
Seatwork/Assignments
Laboratory Activity Collaborative Activity Individual Activity
Required Program Required Individual and Group Work LE1
Page 9 of 12 AY1617 – July 15, 2016 /nsalas
Intended Learning Outcome
Unit#
(weeks)
Course Outcome
Topic Learning
Activities
Assessment Activity Student Output (Advanced)
Processing Text Input
Text Areas
Layout Management Choices
Menus
Exploring the Swing Documentation Relational Databases (Advanced) Organizing Database Information Queries
Installing a Database Database
Programming
18 Final
Examination
Page 10 of 12 AY1617 – July 15, 2016 /nsalas
Course References:
A. Basic Readings
Big Java
By Horstmann, Cay S.
Copyright 2010
Java programming : From the Ground Up By Bravaco, Ralpf (et al)
Copyright 2010
B. Extended Readings (Books, Journals)
Java Actually : A First Course in Programming By Mughal, Khalid (et al)
Copyright 2007 C. Web References
www.java.sun.com
Oracle Technology Network for Java by the Oracle Company
http://www.scribd.com/doc/22308312/JEDI-Introduction-to-Java-programming-vol-2#scribd JEDI – Introduction to Java Programming (Vol.2 )
by Mariz, Johanna
Page 11 of 12 AY1617 – July 15, 2016 /nsalas
Grading System
The final grade in this course will be composed of the following items and their weights in the final grade computation:
Lecture Class Standing 70%
Lecture Major Exam 30%
Laboratory Class Standing 60%
Laboratory Major Exam 40%
FINAL GRADE = ((Lecture Class Standing + Lecture Exam) + (Laboratory Class Standing + Laboratory Exam))/2 Transmutation Table:
Minimum Passing Percent Average of Subject : 50
RANGE EQUIVALENTS (COMPUTED AVERAGES & TRANSMUTED VALUES)
Range of Computed Average Range of
Transmuted Values Grade General Classification
94.0000 100.0000 97 100 1.00 Outstanding
88.0000 93.9999 94 96 1.25 Excellent
82.0000 87.9999 91 93 1.50 Superior
76.0000 81.9999 88 90 1.75 Very Good
70.0000 75.9999 85 87 2.00 Good
64.0000 69.9999 82 84 2.25 Satisfactory
58.0000 63.9999 79 81 2.50 Fairly Satisfactory
52.0000 57.9999 76 78 2.75 Fair
50.0000 51.9999 75 3.00 Passed
Below Passing Average 5.00 Failed
Failure due to absences 6.00 FA
Unauthorized Withdrawal 8.00 UW
Officially Dropped 9.00 Dropped
Page 12 of 12 AY1617 – July 15, 2016 /nsalas