Академический Документы
Профессиональный Документы
Культура Документы
Angeles City
V. Core Value(s) : Zeal (Conscientious effort in fulfilling capstone project requirements independently within schedule); Community Service (Proper
application of computerized systems within the community)
VI. Grading System :
Preliminary Grade (PG) = ((CS * 2) + Prelim Exam) / 3
Midterm Grade (MG) = ((((CS * 2) + Midterm Exam) / 3) + PG) / 2
Final Grade = (((CS + (Final Exam * 2)) / 3) + MG) / 2
Notes: CS – class standing composed of project deliverables, quizzes, internet research, and other related course work
AUF-SYL-CCS-34
June 8, 2009 - Rev. 2
SPECIFIC OBJECTIVES CONTENTS TIME TABLE INSTRUCTIONAL MODE
At the end of each lesson, the students shall I. Overview of the Capstone Course 3 hours Class Discussion
st
have: A. Introduction 1 week Recitation
a. Definition of a Capstone. Group Discussions
1. realized the importance of the course; b. Importance of the Course in the field of Library Research
2. identified the components of a capstone Information Technology
Project. • Activity No. 1 – Research on examples of
existing Capstone Projects in Information
Technology.
B. Capstone Project Details
a. Major Components.
b. Sub Components
• Activity No. 2 - Identify a potential development
project and its major components.
At the end of each lesson, the students shall II. Initial System Requirements 6 hours Class Discussion
nd
have: A. Initiating a Project 2 – 3rd weeks Recitation
a. Assessing the size, complexity and Post exams
1. described the activities for a project scope of the project. Group Discussions
during the initial phase; b. Establishing procedures to support the Consultations
2. determined the importance of defining project activities. Library Research
the scope and size of a project. • Activity No. 3 – Determine the complexity and
scope of a particular system within the school.
B. Planning a Project
a. Describing Project Scope, Alternatives
and Feasibility.
AUF-SYL-CCS-34
June 8, 2009 - Rev. 2
b. Determining Project Standards and
Procedures.
• Activity No. 4 - Discuss the procedures and the
standards of system discussed in activity no. 3.
• Activity No. 5 – Group discussion of possible
projects.
At the end of each lesson, the students shall III. Project Methodology. 6 hours Class Discussion
th th
have: A. Project Methodology synopsis 4 – 5 weeks Recitation
a. Definition of Methodology Post exams
1. explained the advantages and b. Types of Methodology. Group Discussions
disadvantages of the different • Activity No. 6 – Compare and contrast the Library Research
methodologies; different project methodologies discussed.
2. selected the best methodology B. Determining System Requirements
appropriate for a system. /Deliverables and Outcomes
a. Traditional Methods
b. Modern Methods
• Activity No. 7 – Survey the literature and
other related works for citations and
references
• Activity No. 8 – Analysis of the Existing
System
At the end of each lesson, the students shall IV. Capstone Guidelines and Policies 3 hours Class Discussion
th
have: A. Discussion of Guidelines, Policies, Format 6 week Recitation
for the Capstone Project Proposal Defense Post exams
1. mastered the necessary guidelines a. Cover Page Group Discussions
AUF-SYL-CCS-34
June 8, 2009 - Rev. 2
and policies pertaining to the b. Chapter Contents Library Research
development of a capstone project; c. Oral Defense
2. understood the importance of • Activity No. 9 -Grouping Assignments
outlining a proposal as a precursor B. Discussion of Proposal Outline (Chapters
to the final project. 1- 4)
a. Introduction
b. Existing system
C. Develop a prototype consisting of (at least)
screen layouts.
At the end of each lesson, the students shall V. Proposal Defense 3 hours Class Discussion
th
have: A. Presentation of Chapters 1 to 4 7 week Library Research
a. Introduction Proposal Defense
1. Finalized all requirements for the b. Survey of Current or Existing
proposal defense; Technology
2. Defended their proposal before a set of c. The Existing System
panelists; d. The Proposed System
3. Revised their proposal in line with the
panelists’ recommendations in the
oral defense.
At the end of each lesson, the students shall VI. Design of the Proposed System 6 hours Consultation with adviser
th th
have: • Activity No. 10 – Assignment of Advisers. 8 – 9 weeks Programming
Group Discussions
1. captured all the necessary data, defined • Activity No. 11– Identify System Objectives Library Research
all processes, inputs, and outputs of the • Activity No. 12 – Determining the scope
AUF-SYL-CCS-34
June 8, 2009 - Rev. 2
existing system based on the Data Flow • Activity No. 13 – UML, DFD, etc.
Diagram;
1. determined all necessary requirements
for developing the proposed system.
At the end of each lesson, the students shall VII. Software Development 3 hours Consultation with adviser
th
have: • Activity No. 14- Enhancement of Initial 10 week Programming
Prototype vis-à-vis Design Issues and Group Discussions
1. developed all the requirements such as considerations Library Research
pseudocodes, UML definitions, database
design, etc.
At the end of each lesson, the students shall VIII. Coding 6 hours Consultation with adviser
th th
have: • Activity No. 15 – Programming & Debugging 11 = 12 weeks Programming
Group Discussions
1. developed all the modules for the Library Research
proposed system’s software.
At the end of each lesson, the students shall IX. Implementation of the Proposed System 6 hours Consultation with adviser
th th
have: • Activity No. 16- Resource Requirements 13 – 14 week Programming
a. Software Requirements Group Discussions
1. finalized the checklist of resource b. Hardware Requirement Library Research
requirements necessary for implementing c. Human Resources Requirements
the proposed system. • Activity No. 17 – Group discussions on the
AUF-SYL-CCS-34
June 8, 2009 - Rev. 2
proposed system resource requirements.
At the end of each lesson, the students shall XI. Final Defense 6 hours Final Defense
th th
have: • Activity No. 21 – Final oral defense 17 - 18 week
and submission of proposed system’s
1. defended the proposed system final documentation and installation
software
2. submitted the final documentation and
installation software.
FINAL EX AM INATION
AUF-SYL-CCS-34
June 8, 2009 - Rev. 2
VII. References
A. Books
th
Schwalbe, Kathy. 2006. Information Technology Project Management, 4 Edition. Thomson, Course Technology.
Cabanizos, Gladie Natherine G. 2006. How to Write a Successful Science Thesis: The Concise Guide for Students.
st
Phillips, Joseph. 2002. IT Project Management On Track from Start to Finish, 1 Edition. McGraw Hill.
th
O Brien, James A. Introduction to Information System. 2001. 13 Edition. Boston, McGraw Hill.
th
Stair, Ralph M. Fundamentals of Information System : A Managerial Approch. 4 Edition. Boston, McGraw Hill.
B. Website
AUF-SYL-CCS-34
June 8, 2009 - Rev. 2