SOFTWARE TECHNOLOGY DEPARTMENTCOLLEGE OF COMPUTER STUDIESDE LA SALLE UNIVERSITYThesis Guidelines, Policies andManual of StyleAs of 20 September 2007

These policies and guidelines were formulated with theobjective of helping the students of the Software TechnologyDepartment to successfully deliver thesis projects on time.Comments and suggestions are continually welcome for thebetterment of the department.Effectivity Term: 2nd Trimester, SY 2007-2008This document is subject to change without prior notice. Always check the ST bulletin boardfor announcements and updates. Consult the Thesis Coordinator & Adviser regularly forclarifications.

Table of Contents1.0 OBJECTIVES............................................................................................................................... 12.0 THESIS PROJECTS.............................................................................................................. 12.1. Categories .......................................................................................................................... 12.1.1. Basic Research........................................................................................................12.1.2. Applied Research....................................................................................................22.2. Scope of the Thesis Work................................................................................................ 23.0 THESIS STAGES................................................................................................................... 33.1. ST Methods of Research (STRESME) .......................................................................... 33.2. THSST-1............................................................................................................................. 53.3. THSST-2............................................................................................................................. 63.4. THSST-3............................................................................................................................. 74.0 DUTIES AND RESPONSIBILITIES.................................................................................. 104.1. The Thesis Group ........................................................................................................... 104.1.1. Group Size..............................................................................................................104.1.2. Responsibilities......................................................................................................104.1.3. Disbanding Thesis Groups...................................................................................114.2. The Thesis Adviser ......................................................................................................... 124.2.1. Selection .................................................................................................................124.2.2. Responsibilities......................................................................................................124.3. The Thesis Panel Committee........................................................................................ 144.3.1. Selection .................................................................................................................144.3.2. Responsibilities......................................................................................................144.4. The Thesis Coordinator.................................................................................................. 154.5. The ST Chair.................................................................................................................... 165.0 DEFENSE GUIDELINES........................................................................................................... 165.1 STRESME Defense Process and Suggested STRESME Defense Outline................ 165.1.1 Defense Process........................................................................................................165.1.2. Suggested Defense Outline....................................................................................18

5.2 THSST-1 Defense Process and Suggested Defense Outline....................................... 185.2.1 Defense Process ......................................................................................................185.2.2 Suggested Defense Outline .....................................................................................195.3 THSST-2 Defense Process ................................................................................................ 205.4 THSST-3 Defense Process and Suggested THSST-3 Defense Outline..................... 205.4.1 Defense Process........................................................................................................205.4.2 Suggested Defense Outline .....................................................................................226.0 OUTSTANDING THESIS NOMINATION GUIDELINES...................................................... 227.0 THESIS MANUAL OF STYLE.................................................................................................. 247.1 Thesis Proposal Outline and Contents ............................................................................. 247.2 Thesis Document for Basic Research Outline and Contents........................................ 277.3 Thesis Document for Applied & Application-Based Research Outline and Contents 288.0 FORMAT FOR REFERENCES, CITATIONS, AND QUOTATIONS.................................. 308.1 Handling Quotations in your Text ...................................................................................... 308.2 Short Quotations .................................................................................................................. 308.3 Long Quotations ................................................................................................................... 318.4 Bibliography/Reference List................................................................................................ 318.5 Basic Forms for Sources in Print ....................................................................................... 318.6 Basic Forms for Electronic Sources .................................................................................. 328.7 A Note on Footnotes and Endnotes .................................................................................. 348.8 References/Bibliography..................................................................................................... 349.0 TECHNICAL MANUAL ............................................................................................................. 3510.0 USER’S MANUAL ................................................................................................................... 3611.0 FORMS ..................................................................................................................................... 38Title Page.................................................................................................................................... 38Adviser’s Recommendation Sheet ........................................................................................... 39Panel’s Approval Sheet.............................................................................................................. 40College Acceptance Sheet ........................................................................................................ 4112.0 ADDITIONAL GUIDELINES ON DOCUMENT WRITING................................................. 4312.1 Developing an Outline....................................................................................................... 4412.2 Quoting, Paraphrasing, and Summarizing..................................................................... 4712.3. Paraphrase: Write it in Your Own Words ...................................................................... 4812.4 Avoiding Plagiarism........................................................................................................... 4913.0 STTHES FINAL DELIVERABLES ........................................................................................ 54SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 1

1.0 ObjectivesThe undergraduate thesis is a non-classroom learning environment in which students may apply theskills, methods, and theories learned throughout their stay in the College of Computer Studies.It has the goal of adequately preparing students for their respective careers by involving them in largegroup project that extends over several months; the undergraduate thesis is put in place with thefollowing specific objectives:a. to subject the students to a self-directed, non-classroom learning environment;b. to provide students with a venue to correctly integrate and apply the various skills, methods, andtheories learned in class;c. to refine the student’s oral and written communication skills; andd. to sharpen the student’s inter-personal and work-related skills.

The Software Technology (ST) program aims to prepare the students for graduate studies andresearch in Computer Science, while training them in the engineering of software. In line withthis three-pronged thrust, the objective of the ST Thesis is to enable the ST students to use concepts,principles and techniques learned in ST courses in the design and development of software or newalgorithms.

2.0 Thesis Projects2.1. CategoriesST thesis projects may fall under one of the following categories: basic research and applied research.In both categories, every thesis project must have the following characteristics:

The thesis project is aligned with the research thrusts of the ST department, the College ofComputer Studies and/or the government;

The project is feasible and can be finished within one school year; and The amount of effort and work involved is substantial to span a period of one-year project. .

New designs, tools and methodologies, as well as unique and useful enhancements or modifications ofexisting systems are encouraged. Re-engineering of an existing system will be considered on a caseto-case basis, but the differences in the approach to the solution should be emphasized and illustrated.Collaborations between thesis projects are also allowed. These may be theses under the sameprogram; between different programs (within or across colleges). However, it is necessary that theoverall thesis project is still substantial in scope and that each group can develop, test, and defend itsparticular module independently from others. Failure of one group causing other groups not tocomplete their work will not be accepted as an excuse. In the event that a thesis group plans tocollaborate with another thesis group handled by another department (i.e. CT and IT Departments) orfrom other colleges, the thesis group must inform both the ST Thesis Coordinator and the thesiscoordinator of the department/college concerned.2.1.1. Basic ResearchThis kind of research typically involves systematic inquiry directed towards a more complete knowledgeand understanding of a particular subject without regard to practical applications or specific applicationsin mind. It is exploratory and often driven by the researcher’s curiosity, interest or hunch. It isconducted without a practical end in mind although it can have unexpected results that point to practicalapplication. The basic research provides the foundation for further research, often in applied research.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 2

Thesis projects falling under this category may have no or minimal software output although in mostcases, there will be a need to develop a prototype to illustrate the concepts at hand. The bulk of theresearcher’s work will be on the design of a system model, a framework, an algorithm, or investigation

(empirical study) of different approaches and techniques for a certain domain and a correspondingproof of correctness (and possibly, an analysis of other properties). Statistical measures or softwaresimulation may be used as empirical support to this type of research.2.1.2. Applied Researcha. Breadboard Software (Exploratory/ Experimental Research)This involves the development of prototype software systems. The product to be developed mayalready exist, but in terms of analysis, design and implementation, the students conduct the analysis bythemselves, prepare a design of their own (perhaps patterned after an existing design), and write asubstantial portion (not necessarily all) of its source code.The use of relevant software libraries is allowed provided that there are sufficient design andimplementation problems that remain to be solved or addressed. These projects may also attempt todemonstrate that a certain theory/algorithm/design might work. In general, the output of this type ofthesis projects are by nature experimental and/or exploratory, and are considered at an initial stage ofdevelopment, and will require further investigation or development to mature into usable technologies.b. Commissioned SoftwareThis involves the development of application programs tailored to fit the needs of a specific institutionand it may be funded and/or used by them. Such thesis projects maybe extensions of the students’practicum projects and can be classified as externally-funded projects (i.e. supported by a company oran individual who may or may not be from outside of the College). However, the members of the thesisgroups must ensure that the support goes all the way until the completion of the project. Failure of thefunding party to support the thesis project throughout the entire duration of the thesis will not beaccepted as an excuse for the non-completion of the thesis project. Any thesis group wishes to workon this type of thesis project should inform the ST Thesis Coordinator before making any agreementwith the company or any individual to resolve issues like ownership of the thesis project, confidentialityagreement and memorandum of agreement.It should be noted in this type of thesis project that CS theories and principles should be used.c. Application-Based ProjectThis type of thesis project is similar to that of commissioned software wherein the development ofapplication programs are tailored to fit the needs of a specific organization, industry, or government andthat it may be paid for and/or used by them. However, the emphasis on this type of thesis project is onthe software engineering processes and methodologies.2.2. Scope of the Thesis Work

The thesis panel committee and the thesis adviser must ensure that the thesis is feasible and/orattainable within one school year. The major activities include:

Analysis and Design Developmental Work Concluding Work

SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 3

3.0 Thesis StagesThe entire thesis program officially starts with the thesis proposal (STRESME) and ends with thesubmission of an approved thesis document and other deliverables (THSST-3). The ST thesis iscomposed of four (4) thesis courses: STRESME (thesis proposal), THSST-1, THSST-2, and THSST-3.At the end of every stage, each thesis group submits specific deliverables for evaluation andacceptance by the thesis adviser and the thesis panel committee.For all the stages of the thesis project, the criteria used when deliberating the defense verdict include:

complete and acceptable deliverables; a well-prepared and delivered presentation; and a productive Question and Answer session.

At the end of any defense activity in a particular thesis course, the thesis group is given a RevisionsList and Verdict Form which contains a list of items the thesis group is expected to fulfill. Thecontents of this form are assumed valid and final if they are agreed upon by both the thesis group andthe thesis panel committee. This validation is by affixing the signature of the lead panelist and arepresentative from the thesis group. The thesis group must photocopy the form, which serves as thegroup’s copy and return the original copy to the ST Thesis Coordinator on the same day no later than1700H. In the event that the defense goes beyond the said time, the thesis group is allowed to submitthe original copy on the following open campus/working day. Failure to do so would result in a failingmark.3.1. ST Methods of Research (STRESME)STRESME involves in the identification of a thesis project. This stage consists of the followingactivities:

forming of thesis groups; identification of the research problem; specification of research objectives, scope and limitations; search and review of related literature; and evaluation of the thesis proposal through a proposal defense

The only deliverable at the end of this stage is an approved thesis proposal. It is expected thatbefore proceeding to the next thesis stage, the proponents have demonstrated during the proposaldefense that they have understood the thesis project and they know what they will do in the succeedingstages. However, other requirements for this thesis course may be defined by the STRESMEinstructor. The grade for the STRESME course may be independent of the outcome of a thesis group’s

proposal defense.Once a thesis proposal is submitted, the proponents will undergo a proposal defense to present theirtopic to a thesis panel committee.There will be four (4) possible verdicts after the defense:1. CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS. This verdict is given if the thesis panelcommittee has approved the general objective of the thesis project with some minor revisions, and thestudents are able to show that they understand the project. Once accepted, the thesis topic, generalSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 4

objective, specific objectives, and scope and limitations of research can no longer be changed.The research objectives established at this stage must be accomplished during the THSST-1 stage.Thesis groups are expected to comply with all the revisions and recommendations stated in theRevisions List and Verdict Form. Failure to do so would result to the change of verdict fromCONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS to FAIL. Moreover, failure to comply with anyrequirements and/or deliverable set forth by the STRESME Instructor, thesis panel committee and theST Thesis Coordinator would result in a failing mark.2. RE-PRESENTATION OF THE PROPOSED TOPIC. This verdict is given if the thesis panel committee hasapproved the general objective of the thesis project. However, the students need to conduct furtherstudy and clarify the proposed topic. This verdict is also given if students are not able to show theirunderstanding of the proposed topic. In this case, the students will undergo anotherdefense/presentation of the same topic. There are four (4) possible verdicts from here: CONDITIONAL

PASS WITH REVISIONS/RECOMMENDATIONS; RE-PRESENTATION OF THE PROPOSED TOPIC

1; CHANGE TOPIC;and FAIL.3. CHANGE TOPIC. This verdict is given if the general objective of the thesis project is unclear and thestudents are not able to show they understand the project. Specific objectives of their research and aswell as its scope are questionable. This verdict is also given if the thesis project is not aligned with thedepartment’s thrust. The group has the option to present2 another thesis proposal or improve theircurrent proposal based on the recommendations given to them by the thesis panel committee. Thereare four (4) possible verdicts from here: CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS; REPRESENTATIONOF THE PROPOSED TOPIC3; CHANGE TOPIC; and FAIL.4. FAIL. This verdict is given if the general objective of the thesis project has been rejected. More so,the thesis group, who has initially been given a verdict of CONDITIONAL PASS WITH

REVISIONS/RECOMMENDATIONS, RE-PRESENTATION OF THE PROPOSED TOPIC or CHANGE TOPIC, fails tosubmit the required defense deliverables on or before the deadline set by the STRESME Instructor.The verdict is a unanimous decision among the members of the thesis panel committee. Once issued,it is final and irrevocable. However, in meritorious cases (i.e. after further research, the thesis grouphas seen some objectives are no longer feasible), thesis groups before proceeding to THSST-1 areallowed by the department to change the following: specific objectives, scope and limitations ofresearch. In this case, thesis groups are required to submit 4 copies of letter of Request for Changesat least one (1) month before the first day of the target defense week to the ST Thesis Coordinator.The letter is addressed to all members of the thesis panel committee (cc the ST Thesis Coordinator),and should contain, but will not be limited to the following:

Original items stated in the proposal document Suggested/Recommended changes in the proposal document Justifications and/or reasons for such changes (i.e. lack of time, easier implementation or

reducing the scope of research work are not valid excuses)All copies of the letter should be signed by all members of the thesis group and noted by the group’sadviser. Once the letter is received by the ST Thesis Coordinator, he/she will convene with the thesispanel committee in coordination with the group’s thesis adviser, if necessary, to discuss the changes.The thesis group will be notified of the decision through the thesis adviser.1 Allowed only if within the schedules defined by the STRESME Instructor2 Allowed only if within the schedules defined by the STRESME Instructor3 Allowed only if within the schedules defined by the STRESME InstructorSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 5

The following table lists down the important activities of STRESME and its corresponding week ofdefenses and deliverables:Table 1: Important STRESME Schedule of Activities (Per Trimester)Deliverable: Thesis Proposal Document3.2. THSST-1Entry into the THSST-1 stage requires a passing mark in STRESME4 successful thesis proposaldefense and the completion of all THSST-1 prerequisite courses as specified in the appropriate STflowchart. THSST-1 involves the following activities:a. search and review of related literatureb. investigation of existing solutions to the identified problem(s) in STRESMEc. evaluation of existing solutionsd. application of methods and theories in the design of a solution to the problem(s)The deliverable at the end of this stage is a partial thesis document (see the Thesis Manual of Stylesection for required chapters). A thesis group is eligible for THSST-1 defense if and only if thethesis adviser recommends it by signing the partial thesis document’s title page. During the

THSST-1 defense, a thesis group is expected to present a prototype of the projected thesis project tothe thesis panel committee. The prototype is implemented using the target language identified by thethesis group. At the minimum, the prototype should illustrate the complete system function flow.There will be three (3) possible verdicts after the defense:1. CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS. The thesis defense panel accepts theobjectives, scope and limitations of the system with possible revisions to the document. These revisionsare necessary but they do not have to be presented again before the thesis defense panel. Initialsoftware implementation is acceptable to the thesis panel committee. Consultations with any of themembers of the thesis panel committee are highly encouraged to verify the correctness of the revisions.Thesis groups are expected to comply with all the revisions and recommendations stated in theRevisions List and Verdict Form. Failure to do so would result to the change of verdict fromCONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS to FAIL. Moreover, failure to comply with anyrequirements and/or deliverable set forth by the thesis adviser, thesis panel committee and the STThesis Coordinator would result the group to receive a failing mark.2. REDEFENSE. This verdict is given if the partial thesis document and/or the system’s objectives,functions, and scope and limitations need to be clarified and revised. In addition, the initial softwareimplementation is questionable. In this case, the group will undergo another defense and present tothe thesis panel committee the revised thesis document. Only two verdicts are possible after theredefense: CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS or FAIL.4 Proposal defense is the not the only grade for STRESME course.Submission of Documents for the 1st Defense Week Monday of the 8th week1st Defense 9th weekSubmission of Documents for the 2nd Defense Week Monday of the 10th week2nd Defense Week 11th weekSubmission of Documents for the 3rd Defense Week 12th week3rd Defense Week 13th weekSubmission of approved thesis proposal document 14th weekSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 6

3. FAIL. The group failed to achieve the objectives of the research established in STRESME.The verdict is a unanimous decision among the members of the thesis panel committee. Once issued,it is final and irrevocable.Once approved, no item may be modified or removed from the thesis and software objectives,scope and limitations. In very rare and extreme cases, the thesis panel committee may allowmodifications in the software objectives and scope prior to the THSST-3 defense. For this, thesisgroups are required to submit 4 copies of letter of Request for Changes at least one (1) month beforethe first day of the target defense week to the ST Thesis Coordinator. The letter is addressed to the STThesis Coordinator, and should contain, but will not be limited to, the following:

Original items stated in the partial thesis document

Suggested/Recommended changes in the partial thesis document and/or for final thesisdeliverable

Justifications and/or reasons of such changes (i.e. lack of time, easier implementation orreducing the scope of research work are not acceptable excuses)All copies of the letter should be signed by all members of the thesis group and endorsed by thegroup’s adviser and thesis panel committee.The following table shows the activities for THSST-1 and its corresponding defense week anddeliverables:Table 2: Important THSST-1 Schedule of Activities (Per Trimester)Deliverable: Partial Thesis Document (THSST-1) and THSST-2 Agreement Form3.3. THSST-2Entry into the THSST-2 stage requires a successful completion of all THSST-1 requirements andprerequisite courses as specified in the appropriate ST flowchart. This stage involves theimplementation of major system functions in the target programming language and/or environment.The proponents are expected to perform the following activities as discussed to them by their adviserand/or collaboration with the thesis panel committee:a. development and implementation of the solution identified in THSST-1;b. documentation of design and implementation issues; andc. regular consultation with the thesis adviser to resolve any issues and monitor the group’s progress.The expected deliverable for this stage is identified by the adviser in consultation and coordination withthe thesis panel committee. Such is written in the form (THSST-2 Agreement Form) that will beprovided by the ST Thesis Coordinator. The deliverable as well as the grading scheme will bediscussed with the thesis group before the enrollment of THSST-2.Submission of Documents for the 1st Defense Week Wednesday of the 8th week1st Defense 9th weekSubmission of Documents for the Redefense Wednesday of the 11th weekRedefense 12th weekSubmission of Final Deliverable 13th weekSubmission of THSST-2 Agreement Form 14th weekSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 7

The contents in the THSST-2 Agreement Form are assumed valid and final if signatures of allmembers of the thesis group, thesis panel committee5 and the thesis adviser are affixed. The thesisgroup must photocopy the said form, which serves as the group’s copy and return the original copy tothe ST Thesis Coordinator on the same day (the day it was agreed and signed) no later than 1700H. Inthe event that the meeting goes beyond the said time, the thesis group is allowed to submit the originalcopy on the following open campus/working day. Failure to do so would result in a failing mark.In very rare and extreme cases (after the signing the THSST-2 Agreement Form), the thesis panelcommittee may allow modifications in the software objectives and scope prior to the THSST-3 defense.For this, thesis groups are required to submit four (4) copies of the letter of Request for Changes at

least two (2) months before the first day of the target defense week to the ST Thesis Coordinator.The letter is addressed to the ST Thesis Coordinator, and should contain, but will not be limited to, thefollowing:

Original items stated in the partial thesis document Suggested/Recommended changes in the final thesis deliverable Justifications and/or reasons for such changes (i.e. lack of time, easier implementation or

reducing the scope of research work are not acceptable excuses)All copies of the letter should be signed by all members of the thesis group and endorsed by thegroup’s adviser and thesis panel committee.Deliverable: Depending on the listed requirements written in the THSST-2 Agreement Formand Accomplished and Signed THSST-2 Grade Form.3.4. THSST-3During this stage, the proponents are expected to perform the following activities:a. development of minor system functions (i.e. online help, system enhancements)b. system testing and analysis of test resultsc. documentation of testing activities and test resultsd. finalization of the thesis deliverables (i.e. main document, technical manual, user’s manual,software)e. preparation for the thesis defenseThe following are the deliverables required at the end of this stage (kindly see the Thesis Manual ofStyle for the complete details):a. the complete thesis document including appendicesb. for thesis involving software support systems or applications:the Technical Manual6;the User’s Manual7; andthe running software.A thesis group is eligible for THSST-3 defense (final thesis defense) only if the thesis adviserrecommends it by signing the Adviser’s Recommendation Sheet or the document’s title page (for allcopies). There are four (4) possible verdicts and these are:5 Members of the thesis panel committee affix their signatures if they will evaluate the groups’ THSST-2 deliverables at the end of the enrolledterm.6 Required if the Adviser sees it applicable7 Required if the Adviser sees it applicableSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 8

1. CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS. This verdict is given if the followingconditions (minimum requirements) are met:All objectives are met and satisfied;The software is working properly;System testing and analysis of test results are sufficient;The proponents are able to answer the questions of the thesis panel committeeconvincingly;Sufficient preparation for the defense;The thesis main document, technical manual, user’s manual and other required thesisdeliverables are well-written; andProponents have a good grasp of the objectives of the thesis and CS principles andmethods.

However, minor revisions are necessary to enhance the document and/or software, but they do nothave to be presented again before the thesis panel committee. Consultations with any members of thethesis panel committee are highly encouraged to make sure that all the required revisions areperformed before the panel signs the Panel’s Approval Sheet. Thesis groups can receive a failing markif they fail to comply with any of the requirements expected from them by the thesis panel committee,adviser and the ST Thesis Coordinator.2. REDEFENSE. Another formal defense is necessary because the group failed to present their thesisproperly and/or the documentation and/or software contain major errors. It is expected that thethesis group is able to resolve any major issues found in their work and that minimal revisions canbe found. Only two verdicts are possible after the redefense: CONDITIONAL PASS WITH

REVISIONS/RECOMMENDATIONS or FAIL.3. REDEMO. Presentation of the software/system to the thesis panel committee with minimal revisionson the thesis group’s documentation. Only two verdicts are possible after the Redemo:CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS or FAIL.4. FAIL. Either the objectives of the study have not been met or the group cheated.The verdict is a unanimous decision among the members of the thesis panel committee. Once issued,it is final and irrevocable.The following table shows the important activities in THSST-3 and its corresponding week of defensesand deliverables:Table 3: Important THSST-3 Schedule of Activities (Per Trimestral)Deliverable: Thesis Document and/or Requirements stated at the Thesis Manual of Style(STTHES3/THSST-3)Submission of thesis documents for the early defense Wednesday of the 4th weekEarly Defense 5th weekSubmission of thesis documents for the early redefense Wednesday of the 7th weekEarly Redefense 8th weekSubmission of thesis documents for regular defense Wednesday of the 9th weekRegular Defense 10th weekSubmission of thesis documents for redefense Wednesday of the 12th weekRedefense 13th weekSubmission of Final Deliverables 14th weekSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 9

Thesis groups may also be nominated for the Outstanding Thesis Award. The guidelines for theOutstanding Thesis Award are presented in this document.Table 4 summarizes the guidelines discussed in this section:Table 4: Thesis stages guidelinesSTAGE PREREQUISITES DELIVERABLES POSSIBLE VERDICTSSTRESME None Thesis Proposal Accept withRevisions/Recommendations;Re-Presentation of the ProposedTopic;Change TopicFailThe numeric grade is specified

by the STRESME instructor.THSST-1 Approved STRESMEproposal;Completion of allprerequisite courses asspecified in theappropriate ST flowchartFor Basic Research type ofthesis: Chapters 1-4For Applied Research type ofthesis: Chapters 1-4Appendices (if any)System PrototypeTHSST-2 Agreement FormAccept withRevisions/Recommendations;Redefense;FailThe numeric grade of 4.0 isgiven if the thesis groupcomplies with all therequirements; otherwise, 0.0 willbe given to them.THSST-2 Approved THSST-1partial thesis document;Completion of allprerequisite courses asspecified in theappropriate ST flowchartSpecified by the adviser andthe thesis panel committee8

THSST-2 Grade FormPassFailThe numeric grade is dependenton the agreement among thepanelists, adviser and the thesisgroupTHSST-3 Completion of THSST-2;Adviser’sRecommendation SheetComplete thesis document;If applicable, running softwarewith the following documents:Technical Manual & User’sManualProperly labeled CD containingthe thesis documents, software(if applicable), brochure, poster,flash presentation, etc.Printout of CCS AlumniInformation SheetAccept withRevisions/Recommendations;Redefense;Redemo;

FailThe numeric grade of 4.0 isgiven if the thesis groupcomplies with all therequirements; otherwise, 0.0grade is given.8 OptionalSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 10

Below is a flowchart of the thesis process that summarizes the discussions above.

4.0 Duties and ResponsibilitiesThe development and defense of the ST thesis involves the following key parties: thesis group, thesisadviser, thesis panel committee, ST Thesis Coordinator, and ST Chairperson.4.1. The Thesis GroupThe thesis group will be composed of a minimum of three (3) and a maximum of four (4) students, all ofwhom should have successfully passed the prerequisite courses prior to taking THSST-1, and all ofwhom should enroll in THSST-1, THSST-2 and THSST-3 at the same time.4.1.1. Group SizeThere will normally be three or four members in a thesis group. If a student, by any specialcircumstances, is unable to work with a group, the ST Chair may allow him/her to work alone,regardless of his/her cumulative GPA. However, the student is expected to submit a letter to the STChair, through the ST Thesis Coordinator stating the reason of such possible arrangement.4.1.2. ResponsibilitiesThe following are the responsibilities of the thesis group:a. Keep informed of the ST Thesis Guidelines, Policies and other thesis-related information. Failure todo so will not be considered as an excuse.b. Keep informed of the schedule of thesis activities, required deliverables and deadlines posted byST Thesis Coordinator.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 11

c. Submit on time all deliverables specified in this document as well as those to be specified by the STThesis Coordinator.d. Submit on time all requirements identified by the thesis panel committee during the defense.e. Submit on time the requirements identified by the thesis adviser throughout the duration of thethesis.f. When indirectly submitting deliverables to the ST Thesis Coordinator (i.e. submitting deliverablesthrough ST Secretary and/or other staff and faculty members of the College of Computer Studies),the group must make sure that the accepting party signs his/her name and indicate the current dateand time on all the copies of the documents and deliverables.g. Schedule regular meetings (at least twice a month or based on the schedule agreed upon by thethesis adviser and the thesis group) with the thesis adviser throughout the duration of the thesis

project. The meetings serve as a venue for the proponents to report the progress of their work, aswell as raise any issues or concerns. Take note that it is as much a responsibility of the advisees asthe adviser in scheduling and following up on the meetings especially because each has their ownresponsibilities aside from the thesis.h. Inform the thesis adviser of any delinquent member/s in the group.i. Any member of a thesis group may clarify issues arising during a defense before the verdict isissued.All group members should be present during the defense and all are required to present parts of thethesis. However, in extreme cases, the thesis adviser and thesis defense panel can excuse certainmembers from the defense or from presenting during the defense.A delinquent thesis proponent may receive a FAIL mark in THSST-1, THSST-2 or THSST-3. Thethesis adviser, thesis defense panel, thesis coordinator and ST Chair will decide upon the possiblecourses of action on a case-to-case basis.4.1.3. Disbanding Thesis GroupsIn extreme cases, a thesis group may be allowed by the ST Chair to disband, based on informationand/or recommendation provided by the ST Thesis Coordinator and the thesis adviser. If needed,consultation with the thesis panel committee will be convened to discuss issue(s) and the possiblecourse of actions. A subset of the group can take any of the following actions:a. Convince the thesis defense panel that it (i.e., the subset) can still complete the approvedrequirements. Note that only one subset of the original group may opt to continue with the originalthesis proposal. Normally, this subset is the one, which has contributed the most to the project.b. Join another thesis group on the following conditions:The transfer is done before the THSST-1 defense. In some cases, upon the approval of the STChair (in consultation with the thesis panel committee), the transfer can be done sometimewithin the period of THSST-2 and THSST-3The new group (whose new members came from the disbanded group) will not disband.The total members of the new group will not exceed four.c. Defend a new thesis proposal (i.e., restart from STRESME activities).Other situations not covered in this section will be handled in a case-to-case basis.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 12

In the event that due to irreconcilable issues the group is breaking up into separate groups (or somemembers will be joined to another group), the process below should be followed:i. The group should discuss the situation with their Thesis Adviser.ii. If the adviser concurs with the decision of the group, each subgroup has to informthe ST Thesis Coordinator in writing about the break-up and the letter should beendorsed by the Thesis Adviser. It should be clearly and explicitly explained in theletter of the situation/reasons of break-up.iii. A meeting of all the members of the group, together with the Thesis Adviser will be

set by the ST Thesis Coordinator in order to discuss the situation and plan out thepossible courses of action.iv. The ST Thesis Coordinator will handle each request on a case-to-case basis inconsultation with the ST Chair.v. In the event that splitting the original group into subgroups is approved, students whowill take the original approved thesis topic should inform the ST Thesis Coordinatorof such in writing; whereas students who are no longer working on the original topicwill have to present a new thesis proposal or join to another group as the casemaybe. As for the latter, a letter discussing such should be submitted to the STThesis Coordinator.4.2. The Thesis AdviserEach thesis group is assigned an adviser, who should be a full-time faculty member of the STdepartment. In special cases, the adviser can come from another department of the College, providedthat the selection criteria discussed in the next section are observed. A co-adviser, if absolutelynecessary, may come from another department or institution.4.2.1. SelectionThe main adviser will be chosen by the STRESME instructor during the STRESME stage inconsultation with the ST Chair. In some cases where the thesis group’s topic is given by a facultymember, that faculty member will assume the group’s thesis adviser. However, the ST ThesisCoordinator can recommend and select a thesis adviser, upon consultation with the thesis panelcommittee, from the College’s pool of faculty based on the following factors:a. the faculty member’s research area and projects;b. the thesis advising and administrative load of the facultyOnce completed, the list of thesis advisers will be submitted to the ST Chair for approval, and thenreleased to the thesis advisers and students.4.2.2. ResponsibilitiesThe thesis adviser has the following responsibilities:a. Keep informed of the ST Thesis Guidelines, Policies and other thesis-related information andresponsible for informing his/her advisees for changes on them and ensuring that these arefollowed throughout the thesis process.b. Keep informed of the schedule of thesis activities, required deliverables and deadlines posted byST Thesis Coordinator and responsible for informing his/her advisees for changes on them andensuring that these are followed throughout the thesis process.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 13

c. Meet the thesis groups regularly to answer questions, help resolve conflicts and conduct mockdefenses. The adviser must be aware of the progress of the thesis and help the group resolvewhatever issues they encountered (topic-wise or group-wise).The meeting should be held at least twice a month or based on agreed schedules with the thesisgroups. In meritorious cases, the adviser may request for the removal of a delinquent proponentfrom the thesis group. A letter detailing failed attempts to resolve the issue, and justification forhis/her decision must be submitted to the ST Chair.d. Ensure that the thesis project is feasible and can be implemented within one school year (i.e. fromProposal to THSST-3). The thesis adviser sees to it that the objectives, scope and limitations, and

methodology of the project are well-defined.e. Ideally, the adviser personally conducts (or has conducted) research in parallel with his/her thesisadvisees on the thesis topic. At the least, the adviser must be familiar with the topic to be able togive sound advice to his/her advisees.f. Point out deficiencies and errors in the review of related works and theories; in the developmentwork, testing activities and analysis of test results; or in the documentation. The adviser mustremind the proponents to do their work properly.g. Review thoroughly all deliverables at every stage of the thesis, to ensure that they meet thedepartment’s standards. The adviser may also require his/her thesis groups to submit progressreports regularly.h. Ensure the thesis deliverables conform to the guidelines, format and standards stated in the STThesis guidelines and policies.i. If it is applicable and necessary, the adviser should ensure that the workload is equally distributedamong the proponents.j. Recommend the group for oral defense. The adviser should not sign the thesis document and theAdviser’s Recommendation Sheet if he/she believes that the group is not yet ready for oral defense.k. Clarify points during the oral defense.l. Ensure that all required revisions are incorporated into the appropriate documents and/or software.m. Recommend to the thesis defense panel the nomination of his/her thesis group for an award.n. With the consent of the majority of the thesis group, the thesis adviser may opt to drop a groupmember anytime before the defense schedule on the following tangible grounds andconsiderations:The group member shows blatant neglect of the tasks measured through clear taskspecifications (input – output with respect to time allotment) given to him/her.The group member does not show up in meetings (in this case, proof of such meetings must bepresented to the adviser if the adviser is not the one who called the meeting)In this situation, the Thesis Adviser should inform the ST Thesis Coordinator and the member(s)will be removed from the original group in writing.o. Must ensure that all deliverables are complete prior to submission to the ST Thesis CoordinatorThe adviser can also request, on behalf of the group, for the modification or elimination of certainrevisions/requirements and defend such requests before the final verdict is issued.A faculty member assigned to be the adviser of a particular thesis group would remain in that capacityfor as long as he/she is a full-time member of the ST department or College.In meritorious cases, the ST Chair may allow faculty members to drop their thesis group in the eventthat students failed to comply with any requirements set forth by the faculty member &/orresponsibilities of the group stated in section 4.1.2. In this case, the process should be followed by the

faculty adviser:SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 14

i. Submit a letter to the ST Thesis Coordinator and state clearly of the reason ofdropping a thesis group. The letter should be copy furnished to the thesis groupconcerned.ii. A meeting of all the members of the group, together with the Thesis Adviser will beset by the ST Thesis Coordinator in order to discuss the situation and plan out thepossible courses of action.iii. The ST Thesis Coordinator will handle each request on a case-to-case basis incollaboration with the ST Chair.4.3. The Thesis Panel CommitteeEach thesis group will have a thesis defense panel, which is composed of three faculty members of thecollege. In special cases, the ST thesis coordinator, in consultation with the ST Chair and the thesisadviser, can recommend additional members to the panel.4.3.1. SelectionThe panel is composed of faculty members of the College. In special cases, a member of the panelmay come from an external unit. They will be chosen by the ST Thesis Coordinator and approved bythe ST Chair, based on the following constraints:a. At least one member of the panel is a senior faculty who belongs to the same research area as thethesis project,b. At least two members of the panel belong to the same research area as the thesis project; andc. The thesis adviser need not be the lead panelist or may opt not to be part of the panel on a pergroup basis with valid reason(s). If this is the case, the thesis adviser should inform the ST Chair orthrough the ST Thesis Coordinator in writing the reason of not being part of the panel andrecommend a faculty member on his behalf to the ST Thesis Coordinator.The composition of the thesis defense panel must be retained, as much as possible, throughout all thestages of the thesis.4.3.2. ResponsibilitiesThe thesis defense panel has the following responsibilities:a. Validate the endorsement of the thesis adviser. The panel serves as the “internal auditors”, puttingsome form of check and control on the kinds of thesis being approved by the ST department.b. Review and evaluate the deliverables.c. Recommend a verdict.d. Listen and consider the request of the thesis adviser and/or the proponents.e. Nominate a thesis for the Outstanding Thesis Award. The guidelines for the Outstanding ThesisAward are found in this document.The lead panelist has the following additional responsibilities:a. Brief the thesis group about the defense program during the actual defense.b. Issue the required revisions and the verdict. The verdict is a unanimous decision among themembers of the thesis defense panel. Once issued, it is final and irrevocable.

SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 15

4.4. The Thesis CoordinatorThe ST Thesis Coordinator, appointed by the ST Chair, has the following responsibilities:a. Announces/Informs the research areas, before the beginning of the thesis proposal stage (i.e.STRESME) to the students.b. Conducts general meetings with the students at every stage of the thesis project to discuss theThesis Guidelines, Policies and Deliverables, and to allow the students to raise and clarify issues.This however, may be replaced by announcements and inquiries through emails.c. Coordinates and consults with the STRESME instructor in identifying the composition of the thesispanel committee for each thesis group based on the guidelines in Section 4.3 and selecting a thesisadviser for each thesis group. The list is submitted to the ST Chair for approval.d. Schedule thesis activities, such as the deadlines of deliverables and defense sessions.e. Post schedules, defense guidelines, requirements guidelines, and other announcements for thestudents and faculty members.f. Furnish every member of the thesis defense panel with all the necessary thesis documents a fewdays before the defense.g. File at least one copy of the thesis defense panel’s evaluation (including revisions) and the Revisedand Approved Deliverables at every stage of the ST thesis.h. Document issues and special cases as they arise.i. Convene the necessary body (composition: thesis adviser, thesis panel committee, thesiscoordinator, and/or ST Chair) to resolve issues and handle special cases as they arise.j. Collect deliverables and other thesis requirements submitted on-time. However late deliverablesand other thesis requirements that are not submitted on time will not be accepted. The ST ThesisCoordinator can give a grade of Fail for an ST Thesis Course to a thesis group if the group fails tosubmit any deliverables or other requirements on the deadline set by the ST Thesis Coordinatorand/or the thesis panel committee.k. The ST Thesis Coordinator must disallow a thesis group, whose thesis proposal/document is notsigned by their thesis adviser, to defend before the thesis panel committee.l. The ST Thesis Coordinator, in consultation with the ST Chair and other faculty members of the STDepartment, must decide in cases not covered by the ST Thesis Guidelines and Policies.m. Prepare reports necessary for the department or concerned offices.n. Streamline procedures. In this case the ST Thesis Coordinator may revise or change the contentsof the ST Thesis Guidelines and Policies as long as it has the approval of the ST Chair.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 16

4.5. The ST ChairThe ST Chair has the following responsibilities:a. Ensure that the responsibilities of the ST Thesis Coordinator are fulfilled.

b. Approve the thesis adviser selected by the STRESME instructor in coordination with the ThesisCoordinator for each thesis group.c. Approve the thesis panel committee selected by the STRESME instructor in coordination with theThesis Coordinator for each thesis group.d. In extreme cases, allow thesis groups to disband based on the guidelines in Section 4.1.3.e. In special cases, allow thesis groups to take THSST-1 together with a prerequisite.

5.0 Defense GuidelinesA thesis group will be allowed to defend their thesis only if all members are enrolled in STRESME,THSST-1, THSST-2 and THSST-3 at the same time. Furthermore, all members should be presentduring the defense. If any one member will not be able to join the defense, any of the followingsituations will apply9:I. If the missed defense is a regular defense:a. The group is automatically scheduled for redefenseII. If the missed defense is a redefense:a. Submit a letter to the ST Thesis Coordinator stating the reason why a member (ormembers) failed to attend the said defense;b. The ST Thesis Coordinator will deliberate the case with the ST Chair;c. After the deliberation, the Thesis Coordinator will inform the group directly or throughthe group’s adviser of the decision.The thesis group should be in the prescribed defense room at least 15 minutes before the actualdefense. This will give the group ample time to set up their machines, presentations, etc (providedthe defense room is available for use). If the thesis group feels that they need more time for theset-up of the machines, then they should be in the defense room earlier. More over, if the thesisgroup mightDo not serve food/snacks for the panelists10.Each proponent is required to be in business attire during the thesis defense. Furthermore,proponents are required to answer all/any questions raised by the panelists during the defenseThe STRESME instructor is responsible for the STRESME (Thesis Proposal) defenses andscheduling. Only the THSST-X defenses and scheduling will be handled by the ST ThesisCoordinator.5.1 STRESME Defense Process and Suggested STRESME Defense Outline5.1.1 Defense ProcessThere are at most 3 defenses a group can take during the STRESME course in presenting their thesisproposal to a thesis panel committee. The STRESME Instructor is responsible for scheduling the 1st,2nd and 3rd defense as required for the group. Moreover, it is the responsibility of the STRESME9 This is with the condition that the thesis group has submitted the required documents for the defense.10 Effective on June 2001-2002.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 17

Instructor in choosing the appropriate panelists and adviser for the group. The proponents of the thesison the other hand, must prepare the necessary presentation materials for the defense11.The following schedule will be followed for the defenses:

8th week (W) – submission of document (for 1st defense). Three (3) copies of the proposal

document. 9th week – 1st defense week 10th week (W) – submission of document (for 2nd defense). Three (3) copies of the proposal

document. 11th week (W) – 2nd defense week 12th week (W) – submission of document (for 3rd defense). Three (3) copies of the proposal

document. 13th week – last defense week 14th week – submission of approved thesis proposal document. One (1) copy with Panel’s

Approval Sheet, with signatures of the all the members of the thesis panel committee.Students have the option to have their defense during the 1st defense schedule by passing three (3)copies of their thesis proposal documents by the 8th week. If they will not be able to do so, they mustsubmit their documents by the 11th week to defend during the 2nd defense schedule. If the group stillfails to pass their documents, these must be passed by the 12th week to defend during the 3rd

defenseschedule. Failure to pass documents and defend on the 1st, 2nd or 3rd defense schedule will result in afailing mark for the thesis proposal defense.The group will undergo defense on either the 1st, 2nd or 3rd defense week depending on the time theywere able to pass their documents. It is highly recommended that the probable adviser is guiding thegroup in conceptualizing their thesis project. Section 3.1 lists down the possible verdicts a thesis groupcan receive.If the verdict received is CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS, the proponents mustperform the necessary changes required by the panelists12. These must then be submitted to theSTRESME Instructor together with a copy of the list of revisions requested by the panelists and thepages where the revisions have been made. The STRESME Instructor will forward the documents tothe other panelists. All the panelists will check the document and forward the document back to theSTRESME Instructor. The STRESME Instructor will be responsible for returning the documents to thegroup. If there are further revisions on the documents, the group will continue to modify themaccordingly. The group, the STRESME Instructor and panelists will continue to exchange the groups’documents for revisions until no more revisions are needed. The final version must be prepared andsigned by the panelists on or before the due date and time specified on the syllabus. The approveddocument must then be passed to the STRESME Instructor. The STRESME Instructor will then submitthe approved proposal to the ST Thesis Coordinator and will recommend an adviser for the group in

coordination with the ST Thesis Coordinator and ST Chair. The STRESME Instructor will then post thelist of advisers at the ST bulletin board, and informs the students. A copy of the list is also given to theST Thesis Coordinator in preparation for the succeeding thesis stages.If the verdict received is RE-PRESENTATION OF THE PROPOSED TOPIC or CHANGE TOPIC and the grouphas undergone at most 2 defenses and it is still not yet beyond the 12th week, the group will be allowedto submit a new proposal or revise their proposal based on the recommendations suggested by thepanelists to the STRESME Instructor. They must pass their new or revised proposal13 by the nextdefense week and defend their thesis on the scheduled date. If the verdict received is CONDITIONAL11 It should be noted that the outcome of the thesis proposal defense is independent of the STRESME course requirement. The latter’srequirement is dictated by the STRESME Instructor.12 Only one (1) revised document is submitted unless specified by the thesis panel committee on the number of revised documents.13 Three (3) copies of the proposal document are to be submitted for the defenseSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 18

PASS WITH REVISIONS/RECOMMENDATIONS, the process in the previous section will be repeated untilthere will be no more revisions. The approved document must then be submitted to the STRESMEInstructor with signatures of all panelists on or before the due date and time specified in the syllabus.The STRESME Instructor will then submit the approved proposal to the ST Thesis Coordinator and willrecommend an adviser for the group in coordination with the ST Thesis Coordinator and ST Chair. TheSTRESME Instructor will then post the list of advisers at the ST bulletin board, and informs thestudents.However, in the event that the group receives CHANGE OF TOPIC at the 3rd defense or is not able todefend on any of the 3 defense schedules, they will receive a failing mark14.It should be noted that failure to meet any requirements set by the thesis panel committee, or by the STThesis Coordinator will result the group to receive a failing mark.5.1.2. Suggested Defense OutlineThe thesis proposal defense is an-hour exercise subdivided as follows:First 5 minutes:Opening prayer, Introduction of the Thesis Proponents and Overview of the ResearchNext 20 minutes:Discuss the proposed research, Research objectives, Scope and Limitations, Significance of theresearchLast 35 minutes:Clarifications, Question and Answer portion and deliberation of the thesis proposal.Students may be asked to step out the room while the panel deliberates on their presentation.5.2 THSST-1 Defense Process and Suggested Defense Outline5.2.1 Defense Process

The ST Thesis Coordinator is responsible for scheduling the regular defense and redefenses. Thepanelists for either of the defenses will be based on the thesis group’s panelists during STRESME. Theproponents of the thesis must prepare the necessary presentation materials and prototype of systemflow that they will be using for the defense.The following schedule will be followed for the defenses:

8th week (W) – submission of partial thesis document. Three (3) copies of the partial thesisdocument, signed at the title page by the thesis adviser.

9th week – regular defense 11th week (W) – submission of partial thesis document for redefense. Three (3) copies of the

partial thesis document, signed at the title page by the thesis adviser. 12th week – redefense week

14 In the event that a successful defense is necessary as one of the STRESME requirements, then if the group receives a failing mark in theproposal defense, then they have to enroll STRESME in the following term. Otherwise, the group will be asked to go through the thesisproposal activities in the following term.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 19

13th week – submission of final approved partial thesis document. One (1) copy of the partialthesis document, with Panel’s Approval Sheet, with signatures of all members of the thesispanel committee.

14th week – submission of the THSST-2 Agreement FormStudents have the option to have their defense during regular defense schedule by passing theirdocuments by the 8th week. If they will not be able to do so, they must submit their documents by the11th week to defend during the redefense schedule. All documents must be signed by the group’sadviser (at the title page of the partial thesis document) to be accepted by the ST Thesis Coordinator.Failure to pass documents and defend on either regular or redefense schedule will result in a failingmark.The group will undergo defense on regular defense week or redefense week depending on the timethey were able to pass their documents. Section 3.2 lists down the possible verdicts a thesis group canreceive for THSST-1.If the verdict received is CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS, the students mustperform the necessary changes required by the panelists. These must then be submitted to the thesisadviser15 together with a copy of the list of revisions requested by the panelists and the pages wherethe revisions have been made. The adviser will then check the document and forwards the saiddocument to the other panelists. All the panelists will check the document and return them back to theadviser. The adviser is responsible for returning the documents to the group. If there are furtherrevisions on the documents, the group will continue to modify them accordingly. The group, the adviser

and the thesis panel committee will continue to exchange the groups’ documents for revisions until nomore revisions are needed.The final version of the partial thesis document will then be prepared. The thesis adviser and thepanelists must sign the PANEL’S APPROVAL SHEET and the thesis adviser must also sign thedocument’s title page. All the required forms and the partial thesis document must be passed to the STThesis Coordinator on or before the date and time set by the latter.If the verdict received is REDEFENSE, the group must revise their document16 accordingly. It must bepassed, and should have the signature17 of the thesis adviser at the title page by the 11th week. Failureto do so will result in a failing mark for the group. If the documents are received on time, the group willhave their redefense. If the verdict received during the redefense is CONDITIONAL PASS WITH

REVISIONS/RECOMMENDATIONS, the process in the previous section will be repeated until there will beno more revisions. The final document will then be passed to the ST Thesis Coordinator on or beforethe date and time set by the latter.If a group receives a failing mark at any time during defense, they will have to enroll THSST-1 in thefollowing term or later term. In addition, it should be noted that failure to meet any requirements set bythe thesis panel committee, thesis adviser or by the ST Thesis Coordinator will result the group toreceive a failing mark.5.2.2 Suggested Defense OutlineThe thesis proposal defense is an-hour exercise subdivided as follows:First 5 minutes:15 Only one (1) revised document is submitted unless specified by the thesis panel committee on the number of revised documents16 Three (3) copies of the document are to be submitted for the defense17 Adviser’s signature signifies that the Adviser sees the group is ready to defend their thesis or the group is highly recommended for a thesisdefense.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 20

Opening prayer, Introduction of the Thesis ProponentsNext 5 minutes:Overview of the Research, Research Objectives, Scope and LimitationsNext 20 minutes:Discuss the Proposed System, Objectives, Scope and Limitations, System’s Screen Flows or WalkThroughLast 30 minutes:Clarifications, Question and Answer portion and deliberation.Students may be asked to step out the room while the panel deliberates their presentation.5.3 THSST-2 Defense ProcessA THSST-2 Agreement Form will be given by the ST Thesis Coordinator to each group’s thesis adviser.Before the admission of the group to THSST-2, the thesis adviser along with the thesis panelcommittee and the thesis group defines the expected deliverables and corresponding deadlines for

THSST-2. In addition, the form indicates under what conditions the group will pass THSST-2 andproceeds to THSST-3 or receive a failing mark. The contents of the agreement form are deemed to bevalid if all signatures of the concerned people (i.e. thesis adviser, proponents and thesis panelcommittee) are present. At the minimum, the thesis adviser validates the deliverables submitted by thegroup. The thesis adviser submits the THSST-2 Grade Form to the ST Thesis Coordinator containingthe group’s grade and signed by the panel committee on or before the date and time specified by theST Thesis Coordinator.If a group receives a failing mark, they will have to enroll THSST-2 in the following term or later term.5.4 THSST-3 Defense Process and Suggested THSST-3 Defense Outline5.4.1 Defense ProcessThe ST Thesis Coordinator is responsible for scheduling the early regular defense, early redefense,regular defense and redefenses. It should be noted that there is no difference between the early regulardefense and the regular defense. Also, there is no difference between the early redefense andredefense. Thesis groups opt for early defense (early redefense) mean they would finish their thesisearly during the term they are enrolled in THSST-3.The members of the thesis panel committee are based on the thesis group’s panelists during THSST-1and THSST-218. The proponents of the thesis must prepare the necessary presentation materials, thefinal thesis document19, the software20, the technical manual21 and the user’s manual22.The following schedule will be followed for the defenses:

4th week (W) – submission of thesis documents for early defense. Three (3) copies withsignature of the thesis adviser at the title page.18 Due to some situations beyond the department’s control (i.e. faculty members go on-leave), some members of the thesis panel committeemay change.19 To be submitted on the date and time specified by the ST Thesis Coordinator20 To be presented during the scheduled defense21 To be presented during the scheduled defense22 To be presented during the scheduled defenseSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 21

5th week – early regular defense week 7th week (W) – submission of thesis document for early redefense. Three (3) copies with

signature of the thesis adviser at the title page. 8th week – early redefense week 9th week (W) – submission of thesis documents for regular defense. Three (3) copies with

signature of the thesis adviser at the title page. 10th week – regular defense week 12th week (W) – submission of thesis document for redefense. Three (3) copies with

signatureof the thesis adviser at the title page.

13th week – redefense week 14th week – submission of final deliverables. See section 13.0 for the details.

Students opt to present their thesis project during the early regular defense should submit their

documents23 by the 4th week of the trimester. If they will not be able to do so, they can submit theirdocuments either on the 7th week (for early redefense)24 or on the 9th week (for regular defense). If theywill still not be able to pass their documents, these should be submitted by the 12th week to defend onthe redefense schedule. All documents must be signed by the group’s adviser (at the title page of themain thesis document) 25 to be accepted by the ST Thesis Coordinator. Failure to pass documents anddefend on early regular, early redefense, regular or redefense schedule will result in a failing mark.Section 3.4 lists down the possible verdicts a thesis group can receive.If the verdict received is CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS, the students mustperform the necessary changes required by the panelists. The revised document26 and/or software (ifnecessary) must be submitted to the adviser together with a copy of the list of revisions requested bythe panelists and the pages where the revisions have been made. The adviser will then check thedocument and/or software, and forward them to the other panelists. All the panelists will check thedocument and return them back to the adviser. The adviser is responsible for returning the documentsto the group. If there are further revisions on the documents and/or software, the group will continue tomodify them accordingly. The group, the adviser and panelists will continue to exchange the groups’documents and/or software for revisions until no more changes are needed. If there are no morerevisions, the group must prepare the final deliverables set by the ST Thesis Coordinator on or beforethe date and time set by the latter.If the verdict received is REDEFENSE, the group must revise their documents accordingly. These mustbe passed27, duly signed by the adviser (at the title page of the main thesis document) 28 by the 8th weekif the defense undergone was early regular defense and 12th week if the defense undergone wasregular defense. Failure to do these will result in a failing mark for the group. If the documents arereceived on time, the group will have their redefense. If the verdict received is CONDITIONAL

PASS WITH

REVISIONS/RECOMMENDATIONS, the process in the previous section will be repeated until there will beno more revisions. The documents will then be passed to the ST Thesis Coordinator on or before thedate and time set by the latter.If the group receives as verdict of REDEMO, the group must prepare the requirements set by thepanelists. They will then undergo a redemo on the date specified by the panelists. If the group receives

a verdict of CONDITIONAL PASS WITH REVISIONS/RECOMMENDATIONS, the process in the previous section23 Three (3) copies of the main thesis document are to be submitted.24 It should be noted that students opt for early defense (or early redefense) are not qualified for regular defense (or redefense)25 Adviser’s signature signifies that the Adviser sees the group is ready to defend their thesis or the group is highly recommended for a thesisdefense.26 Only one (1) copy is submitted unless specified by the thesis panel committee on the number of copies.27 Three (3) copies of the main thesis document are to be submitted.28 Adviser’s signature signifies that the Adviser sees the group is ready to defend their thesis or the group is highly recommended for a thesisdefense.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 22

will be repeated until there are no more revisions and the necessary requirements will be passed to theST Thesis Coordinator on or before the date and time set by the latter.If a group receives a failing mark at any time during defense, they will have to enroll THSST-3 in thefollowing term or later term. In addition, it should be noted that failure to meet any requirements set bythe thesis panel committee, thesis adviser or by the ST Thesis Coordinator will result the group toreceive a failing mark.5.4.2 Suggested Defense OutlineFor STHES3, the thesis defense is a two-hour exercise subdivided as follows:First 2 minutes:Opening prayer, Introduction of the Thesis ProponentsNext 5 minutes:Overview of the ResearchNext 30-45 minutes:Overview of the Proposed System, Design and Implementation Issues of Major System Components,Demo of System Features, Testing Results and Observation, Conclusion and RecommendationNext15 minutes:The proponents are requested to step out of the room. (this may take longer)Next 30 minutes:Question and Answer portion.Next 15 minutes:Thesis Committee Deliberation.Next 15 minutes:Presentation of defense verdict and the required revisions.

6.0 Outstanding Thesis Nomination Guidelines A thesis group can be recommended for an outstanding thesis award by the thesis panel

committeeif it has completed the thesis project in one school year from the time they successfully defendedtheir Thesis proposal.

There are three (3) types of awards: gold medal, silver medal and bronze medal for outstandingthesis

Once a thesis group is nominated, there will be a separate defense and another set of panelists. Aset of guidelines will be given and used for this special defense.

Groups nominated for outstanding thesis does not automatically ensure that the group receives anaward. It is possible that none of the nominated groups receives the outstanding thesis award.

The selection for the Most Outstanding Thesis Award Committee is based on the following criteria:o Minimum of three (3) and a maximum of five (5) members for the committeeo The lead panelist should be the senior and/or administrator of the ST department and/orCollege of Computer Studieso The thesis adviser and the original panelists cannot be members of the MOTA committeeunless needed.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 23

Nomination Process:The adviser submits a recommendation letter to the ST Thesis Coordinator nominating his/heradvisees for MOTA. The thesis panel members should all endorse the recommendation letter. Theletter should state the reasons for doing so.The ST Thesis Coordinator informs the students of their nomination. In some cases, the adviser maybe tasked to relay the nomination to his advisees.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 24

7.0 Thesis Manual of Style7.1 Thesis Proposal Outline and ContentsTitle PageIf the title of the thesis is an acronym, provide a line description of the said acronym. This one-linedescription provides the reader a general idea of what the thesis is all about.Example: ITS-C: An Intelligent Tutoring System for C ProgrammingAbstractFrom 150 to 200 words of short, direct and complete sentences, the abstract should be informativeenough to serve as a substitute for reading the thesis itself. It states the rationale and the objectives ofthe research. Do not put citations or quotes in this section. Avoid beginning the abstract with “Thispaper/document/thesis/study/ project/…”The abstract should include at least five keywords that are relevant to the thesis project. For example:Keywords: agent, collaboration, communication, multi-agent systems, and distributed artificialintelligence.For possible keywords and/or classification recommended by the Association of Computing Machinery(ACM) and Institute of Electrical and Electronics Engineers (IEEE), please see the following sites,respectively:http://www.acm.org/class/;http://code.ucsd.edu/keywords.html;http://code.ucsd.edu/ieee_keywordsTable of ContentsObserve the following format:1.0. Research Description ……………………………………………….………….…1-1

1.1. Overview of the Current State of Technology ……………………………….…1-21.2. Research Objectives………………………………………………….…….……..1-31.2.1. General Objective…………..………………………………………………………1-31.2.2. Specific Objectives ……………………………………………………………...…1-3Note that the page number notation is as follows:<chapter/appendix> – <page number>Thus the first page of Chapter 2 is 2-1, while the first page of Appendix A is A-1.1.0. Research Description<provide a sentence or two describing this section>1.1. Overview of the Current State of TechnologyThis section gives the reader an overview of the specific technology or field in the international or localsetting. The information regarding the technology or field should be contemporary and not based onoutdated sources. Discussion must not be too technical or too detailed.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 25

This section ends with a discussion on the problems faced by or that still exist in the specific technologyor field (e.g., limitations of existing software or algorithms). The problem statement would lead to theresearch objectives.1.2. Research Objectives1.2.1 General ObjectiveThis section states the overall goal that must be achieved to answer the problem.1.2.2 Specific ObjectivesThis subsection is an elaboration of the general objective. It states the specific steps that must beundertaken to accomplish the general objective. These objectives must be specific, measurable,attainable, realistic, and time-bounded. Each specific objective may start with “todesign/survey/review/analyze…”Studying a particular programming language or development tool (e.g., to study Windows/Object-Oriented/Graphics/C++ programming) to accomplish the general objective is inherent in all thesis and,therefore, must not be included here.1.3 Scope and Limitations of the ResearchThis section discusses the boundaries (with respect to the objectives) of the research and theconstraints within which the research will be developed.1.4 Significance of the ResearchThis section explains why research must be done in this area. It rationalizes the objective of theresearch with that of the stated problem. Avoid including here sentences such as “This research will bebeneficial to the proponents/department/college” as this is already an inherent requirement of all STthesis projects. Focus on the research’s contribution to the Computer Science field.2.0. Review of Related LiteratureThis section discusses the features, capabilities, and limitations of existing research, algorithms, orsoftware that are relevant and related/similar to the thesis. The reviewed work and software must be

arranged either in chronological order, or by area (from general to specific). Observe a consistentformat when presenting each of the reviewed works. In this section, the maximum number of pages is20. At the end of this section, a table of summary should be included discussing the different systemsdiscussed so far.3.0. Research MethodologyThis section lists and discusses the specific steps and activities that will be performed by theproponents to accomplish the project. The discussion covers the activities from Thesis Proposal toTHSST-3.Examples of activities include inquiry, survey, research, brainstorming, canvassing, consultation,review, interviews, observe, experiment, design, test, document, etc. The methodology also includesthe following information:SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 26

What will be doneHow it will be doneWhen and how long will the activity be doneWhere will it be doneWhy should be activity be done4.0. Calendar of ActivitiesThis section contains the Gantt chart showing schedule of the activities outlined in the previous section(Research Methodology). The following table is an example of a Gantt chart:ACTIVITY JAN FEB MAR APR …Data Gathering **** **Software Requirements Analysis **** **** ****Initial Architectural Design **5.0. BibliographyAppendix A. Resource PersonsFor each resource person, specify the following items:<Full name and title, e.g., Dr. Juan de la Cruz><Profession, e.g., faculty><Department, e.g., College of Computer Studies><Name of institution, e.g., De La Salle University><E-mail address>Appendix B. Personal VitaeFor each proponent, specify the following items:<Full name and title, e.g., Mr. Juan de la Cruz><Residence address><Contact numbers><E-mail address>Note:(a) Font size = 10 pts(b) Font type = ArialSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 27

7.2 Thesis Document for Basic Research Outline and ContentsTitle Page

Adviser’s Recommendation Sheet*Panel’s Approval SheetCollege Acceptance Sheet*Acknowledgement*AbstractTable of ContentsList of TablesList of Figures1.0. Research Description1.1 Overview of the Current State of Technology (Thesis Proposal section 1.1)1.2 Research Objectives (Thesis Proposal section 1.2)1.3 Scope and Limitations of the Research (Thesis Proposal section 1.3)1.4 Significance of the Research (Thesis Proposal section 1.4)1.5 Research Methodology (Based on Thesis Proposal section 3.0 but modified to reflect what wasactually done while developing the project)2.0. Review of Related LiteraturePart of the contents of this section is lifted from Chapter 2 of the Thesis Proposal. Additional materialsgathered during the different thesis stages must also be included. It is highly recommended that allexisting systems being studied and reviewed are recent. This chapter should contain at most 20pages, thus the discussion must be clear and concise.3.0. Theoretical FrameworkThis section discusses relevant theories and concepts to be used in the course of designing ordeveloping the thesis. Include only those concepts that you feel will be needed. Do not copy thewhole source material. Use the topics stated in the Thesis Proposal Research Objectives as a guidein determining the contents of this section.4.0. The System Model, Algorithm, and Design*5.0. Analysis*

6.0. Conclusion and Recommendations*

7.0. Bibliography (follow the format in the Thesis Proposal)Appendix A …Appendix xxx …Appendix (xxx)+1 Resource Persons (follow the format in the Thesis Proposal)Appendix (xxx)+2 Personal Vitae (follow the format in the Thesis Proposal)* Included in the THSST-1 document discussing the preliminary design, model and algorithms. Final design and implementation should bedocumented and part of the THSST-3 document. Take note that this section in THSST-1 is subject to change depending on the researchoutput of the proponents, and advices coming from the thesis adviser &/or thesis panel committee.* To be submitted in the final THSST-3 document only.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 28

TECHNICAL MANUAL (if there is a software support system and depends on the nature of the basicresearch output, see Section 5.0)*

USER’S MANUAL (if there is a software support system and depends on the nature of the basicresearch output, see Section 6.0)*

7.3 Thesis Document for Applied & Application-Based Research Outline and ContentsTitle PageAdviser’s Recommendation Sheet*Panel’s Approval Sheet

College Acceptance Sheet*Acknowledgement*AbstractTable of ContentsList of TablesList of Figures1.0. Research Description1.1 Overview of the Current State of Technology (Thesis Proposal section 1.1)1.2 Research Objectives (Thesis Proposal section 1.2)1.3 Scope and Limitations of the Research (Thesis Proposal section 1.3)1.4 Significance of the Research (Thesis Proposal section 1.4)1.5 Research Methodology (Based on Thesis Proposal section 3.0 but modified to reflect what wasactually done while developing the project).2.0. Review of Related LiteraturePart of the contents of this section is lifted from Chapter 2 of the Thesis Proposal. Additional materialsgathered during the different thesis stages must also be included. This chapter should contain at most20 pages, thus the discussion must be clear and concise.3.0. Theoretical FrameworkThis section discusses relevant theories and concepts to be used in the course of designing ordeveloping the thesis. Include only those concepts that you feel will be needed. Do not copy thewhole source material. Use the topics stated in the Thesis Proposal Research Objectives as a guidein determining the contents of this section.4.0. The <XYZ> SystemThis section gives the overall specifications and functional requirements of the software to bedeveloped.4.1. System OverviewThis section gives an overall view of the main features and capabilities of the software.4.2. System ObjectivesThis section states the specific requirements that must be met by the system.4.3. System Scope and Limitations* To be submitted in the final THSST-3 document only.* To be submitted in the final THSST-3 document only.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 29

This section discusses the scope and limitations (i.e., the level of capability or extent of power) of eachmajor function listed in section 4.2 above. This means that operations, which are beyond the identifiedlimits, will simply be invalidated/ignored, and will not cause the system to malfunction, but insteadcause the system to respond with error messages.Justifications for the identified limitations and assumptions must be included here. Assumptions are theconditions that must be satisfied or things that must be existing/available/followed in order for thesystem to function properly. Ignoring such assumptions might result in system malfunction, which willnot be the responsibility of the proponents.4.4. Architectural Design

This section presents the initial internal design of the system, by discussing its major components andtheir interactions. These components include the software components (e.g., modules, databasesystems, etc.), as well as the hardware components (e.g., processors, devices, etc.). The componentsand their interactions are graphically represented using design tools, such as hierarchical charts,structure charts or object models. Data flow diagrams may also be included to show how informationpasses among processes. In addition, discussions on why certain alternative and trade-offs werechosen must be included (e.g., issues on software decomposition, cost of hardware). Take note thatthis section can be modified as the thesis group sees fit during the development.4.5. System FunctionsThis section provides a listing of all the functions that must be performed or delivered by the system,and a description of each. Screen designs may be included, to help visualize the function beingdiscussed. Usually, the functions are based on the menu and toolbar options. If a function generatesreports, the report formats must be included in this section. Take note that this section can be modifiedas the thesis group sees fit during the development.4.6. Physical Environment and ResourcesThis section discusses the hardware and software resources needed to implement and to execute thesystem. If the system has a special set of target users, this section also includes the user specification(e.g., educational level, experience, and technical expertise). For certain uncommon resources, adiscussion of why such resources are necessary must also be included.5.0. Design and Implementation Issues*This section discusses the design and implementation of the major data structures and algorithms usedin the software. It included a discussion on the major issues and problems encountered, and thecorresponding solutions and alternatives employed by the proponents. Parts of the design tools in theTechnical Manual may be lifted as figures in this section.6.0. Results and Observations*

This section presents the analysis, interpretation and implications of the summarized test results, aswell as observations on the limits of the system’s capabilities. It also discusses the type(s) of testingperformed on the system, the test data used, and the results of the tests.The type(s) of tests performed varies depending on the system developed. For instance,commissioned software would require a detailed acceptance test and system response time analysis,while software implementing an algorithm would require an analysis of the performance of the algorithmon different machines or on different test data.

7.0. Conclusion and Recommendations*

* To be submitted in the final STTHES3 document only.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 30

This chapter gives an assessment of what happened in this project. It presents explanations andjustifications on how the objectives of the thesis were met, to what extent and why some objectiveswere not met.8.0. Bibliography (follow the format in the Thesis Proposal)This chapter also includes a discussion of possible improvements that can be made on the software, aswell as future directions of the research topic in general. This serves as a springboard for projects thatmay be done by future thesis groups.Appendix A …Appendix xxx …Appendix (xxx)+1 Resource Persons (follow the format in the Thesis Proposal)Appendix (xxx)+2 Personal Vitae (follow the format in the Thesis Proposal)TECHNICAL MANUAL (see Section 5.0)*

USER’S MANUAL (see Section 6.0)*

8.0 Format for References, Citations, and QuotationsThe following discussions are based from the American Psychological Association (APA) format*.8.1 Handling Quotations in your TextWhen using APA format, the author-date method of citation is being followed. This means that theauthor's last name and the year of publication for the source should appear in the text, and a completereference should appear in the reference list.Examples:Smith (1970) compared reaction times . . .In a recent study of reaction times (Smith, 1970) . . . *In 1970, Smith compared reaction times . . .8.2 Short QuotationsTo indicate short quotations (fewer than 40 words) in your text, enclose the quotation within doublequotation marks. Provide the author, year, and specific page citation in the text, and include a completereference in the reference list. Punctuation marks such as periods, commas, and semicolons shouldappear after the parenthetical citation. Question marks and exclamation points should appear within thequotation marks if they are a part of the quotation but after the parenthetical citation if they are a part ofyour text.Examples:She stated, "The placebo effect disappeared when behaviors were studied in this manner" (Miele,1993, p. 276), but she did not clarify which behaviors were studied.*According to Miele (1993), "the placebo effect disappeared when behaviors were studied in thismanner" (p. 276).

Miele (1993) found that "the placebo effect disappeared" in this case (p. 276), but what will the next* From the book entitled The Publication Manual of the American Psychological Association (4th Edition)* Highly recommended to use.* Highly recommended to use.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 31

step in researching this issue be?8.3 Long QuotationsPlace quotations longer than 40 words in a freestanding block of typewritten lines, and omit quotationmarks. Start the quotation on a new line, indented five spaces from the left margin. Type the entirequotation on the new margin, and indent the first line of any subsequent paragraph within the quotationfive spaces from the new margin. Maintain double-spacing throughout. If you choose to use singlespacing,then it has to be consistent all throughout the document/essay. The parenthetical citationshould come after closing punctuation mark.Example:Miele's 1993 study found the following:The placebo effect disappeared when behaviors were studied in this manner. Furthermore, thebehaviors were never exhibited again, even when real drugs were administered. Earlier studiesconducted by the same group of researchers at the hospital were clearly premature in attributing theresults to a placebo effect. (p. 276)8.4 Bibliography/Reference ListThe reference list should appear at the end of your essay/document. It provides the informationnecessary for a reader to locate and retrieve any source you cite in the essay. Each source you cite inthe essay must appear in your reference list; likewise, each entry in the reference list must be cited inyour text.Basic RulesAuthors' names are inverted (last name first); give last name and initials for all authors of aparticular work. Your reference list should be alphabetized by authors' last names. If you have morethan one work by a particular author, order them by publication date, newest to oldest (thus a 1996article would appear after a 1991 article). When an author appears as a sole author and as the firstauthor of a group, list the one-author entries first. If no author is given for a particular source,alphabetize by the title of the piece and use a shortened version of the title for parenthetical citations.Use "&" instead of "and" when listing multiple authors of a single work.The first line of each entry in your reference list should be indented one-half inch from the leftmargin. Subsequent lines should be flush with the left margin.All references should be single-spaced.Capitalize only the first word of a title or subtitle of a work. Underline titles of books andjournals.Note that the underlining in these entries often continues beneath commas and periods.Each entry is separated from the next by a single space (thus the entire reference list issingle-spaced, with no extra returns added).

List all the references according to the authors (1st author) or title (if there is no authorsmentioned) in alphabetical, ascending order. The reference list contains all the sourcescoming from books, articles, technical papers and journals. Sources coming from the WEBshould be placed at the last section of the reference list.8.5 Basic Forms for Sources in Print8.5.1 An article in a periodical (such as a journal, newspaper, or magazine)Author, A. A., Author, B. B., & Author, C. C. (Year of Publication, add month and of publication for daily,weekly, or monthly publications). Title of article. Title of periodical, Volume Number, pages.N.B. You need list only the volume number if the periodical uses continuous pagination throughout aSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 32

particular volume. If each issue begins with page 1, then you should list the issue number as well: Titleof Periodical, Volume (Issue), and pages.8.5.2 A non periodical (such as a book, report, brochure, or audiovisual media)Author, A. A. (Year of Publication). Title of work: Capital letter also for subtitle. Location: Publisher.N.B. For "Location," you should always list the city, but you should also include the state if the city isunfamiliar or if the city could be confused with one in another state.8.5.3 Part of a non-periodical (such as a book chapter or an article in a collection)Author, A. A., & Author, B. B. (Year of Publication). Title of chapter. In A. Editor & B. Editor (Eds.), Titleof book (pages of chapter). Location: Publisher.N.B. When you list the pages of the chapter or essay in parentheses after the book title, use "pp."before the numbers: (pp. 1-21). This abbreviation, however, does not appear before the page numbersin periodical references.8.6 Basic Forms for Electronic Sources8.6.1 A web pageAuthor, A. A. (Date of Publication or Revision). Title of full work [online]. Available: full web address.(Date of access).N.B. "Date of access" should indicate the date you visited the website. This is important because onlineinformation is frequently altered.Example:Daly, B. (1997). Writing argumentative essays. [online]. Available:http://www.eslplanet.com/teachertools/argueweb/frntpage.htm. (May 12, 1998)8.6.2 An online journal or magazineAuthor, A. A., & Author, B. B. (Date of Publication). Title of article. In Title of full work [online]. Available:full web address (Date of access).Examples:Journal article, one authorHarlow, H. F. (1983). Fundamentals for preparing psychology journal articles. Journal of Comparativeand Physiological Psychology, 55, 893-896.Journal article, more than one author

Kernis, M. H., Cornell, D. P., Sun, C. R., Berry, A., & Harlow, T. (1993). There's more to self-esteemthan whether it is high or low: The importance of stability of self-esteem. Journal of Personality andSocial Psychology, 65, 1190-1204.Work discussed in a secondary sourceColtheart, M., Curtis, B., Atkins, P., & Haller, M. (1993). Models of reading aloud: Dual-route andparallel-distributed-processing approaches. Psychological Review, 100, 589-608.N.B. Give the secondary source in the references list; in the text, name the original work, and give acitation for the secondary source. For example, if Seidenberg and McClelland's work is cited inColtheart et al. and you did not read the original work, list the Coltheart et al. reference in theSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 33

References. In the text, use the following citation: Seidenberg and McClelland's study (as cited inColtheart, Curtis, Atkins, & Haller, 1993)Magazine article, one authorHenry, W. A., III. (1990, April 9). Making the grade in today's schools. Time, 135, 28-31.BookCalfee, R. C., & Valencia, R. R. (1991). APA guide to preparing manuscripts for journal publication.Washington, DC: American Psychological Association.An article or chapter of a bookO'Neil, J. M., & Egan, J. (1992). Men's and women's gender role journeys: Metaphor for healing,transition, and transformation. In B. R. Wainrib (Ed.), Gender issues across the life cycle (pp. 107-123).New York: Springer.A government publicationNational Institute of Mental Health. (1990). Clinicaltraining in serious mental illness (DHHS PublicationNo. ADM 90-1679). Washington, DC: U.S. Government Printing Office.A book or article with no author or editor namedMerriam-Webster's collegiate dictionary (10th ed.). (1993). Springfield, MA: Merriam-Webster.New drug appears to sharply cut risk of death from heart failure. (1993, July 15). The Washington Post,p. A12.N.B. For parenthetical citations of sources with no author named, use a shortened version of the titleinstead of an author's name. Use quotation marks and underlining as appropriate. For example,parenthetical citations of the two sources above would appear as follows: (Merriam-Webster's, 1993)and ("New Drug," 1993).A translated work and/or a republished workLaplace, P. S. (1951). A philosophical essay on probabilities (F. W. Truscott & F. L. Emory, Trans.).New York: Dover. (Original work published 1814)A review of a book, film, television program, etc.Baumeister, R. F. (1993). Exposing the self-knowledge myth [Review of the book The self-knower: Ahero under control]. Contemporary Psychology, 38, 466-467.An entry in an encyclopedia

Bergmann, P. G. (1993). Relativity. In The new encyclopedia britannica (Vol. 26, pp. 501-508).Chicago: Encyclopedia Britannica.An online journal articleKenneth, I. (1995). A Buddhist response to the nature of human rights. [9 pars.] Journal of BuddhistEthics [online serial], 2. Available: http://www.cac.psu.edu/jbe/twocont.html. (June 15, 1998)8.6.3 EmailBecause e-mail is a personal communication, not easily retrieved by the general public, no entryappears in your reference list. When you cite an email message in the body of your paper,acknowledge it in your parenthetical citation: The novelist has repeated this idea recently (SalmanRushdie, email to author, May 1, 1995).SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 34

Example:The Publication Manual of the APA provides extensive examples covering a wide variety of potentialsources. Below are some of the most commonly cited kinds of sources. If your particular source is notlisted below, use the basic forms (above) to determine the correct format, check the PublicationManual, or call or email the Writing Lab for help at (765) 494-3723 or owl@cc.purdue.edu. (Many ofthese examples are taken from the Publication Manual.)8.7 A Note on Footnotes and EndnotesBecause long explanatory notes can be distracting to readers, most academic style guidelines(including MLA and APA) recommend limited use of footnotes/endnotes. An exception is Chicago-styledocumentation, which relies on notes for all citations as well as explanatory notes. But even in thatcase, extensive discursive notes are discouraged. Proper use of notes include:1. Evaluative bibliographic comments, for example:1 See Blackmur (1995), especially chapters three and four, for an insightful analysis of this trend.2 On the problems related to repressed memory recovery, see Wollens (1989) pp. 120-35; for acontrasting view, see Pyle (1992).2. Occasional explanatory notes or other brief additional information that would seem digressive ifincluded in the main text but might be interesting to readers, for example:3 In a recent interview, she reiterated this point even more strongly: "I am an artist, not a politician!"(Weller, 1998, p. 124).Footnotes in APA format are indicated by consecutive superscript Arabic numbers in the text. Thenotes themselves are listed by consecutive superscript Arabic numbers and appear single-spaced inregular paragraph format (a new paragraph for each note) on a separate page under the wordFootnotes (centered, in plain text without quotation marks).8.8 References/BibliographyThe listing of references used in the document should be listed and arranged alphabetically accordingto the first author. In cases where the author is the same, the most recent publication should beindicated first.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 35

9.0 Technical ManualFor those using the object-oriented methodology, kindly use the following CLASS DICTIONARYFORMAT for your technical manual and as well as the UML package diagram. Moreover classdiagrams; file and module specifications are included in the technical manual. Use case diagrams andits description are highly encouraged. However, if structured programming is applied, HIPO/IPO orDFD are necessary in this document.For each class that you have created:CLASSSUPERCLASSPROPERTIES 1. <Property name> -- <purpose and constraint>2.3.METHODS 1. <Method name> -- <description, parameters, result type, andconstraint>2.If you are creative enough, you may want to come up with your own table format. Just make sure thatyou have the minimum requirements outlined above for each class.The design and implementation issues of your class’ methods are discussed in the Design andImplementation chapter (which can include the pseudo code). There is no pseudo code needed in yourTechnical Manual, nor are you required to do IPO.For each class in MFC or Windows environment that you have used, kindly explain them in yourTheoretical Framework chapter.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 36

10.0 User’s ManualAll software systems are required by the department to have ONLINE HELP and a USER’S MANUAL.Most of the contents of the User’s Manual are based from Chapter 4 of the main thesis document(specifically on the system functions and features). The difference lies in the manner of presentation.Chapter 4 of the main thesis document is oriented towards highly technical systems designer, thus itgives an overview of the major modules of the system and their interactions.On the other hand, the User’s Manual is oriented towards end users, who might be naïve users.Therefore, it gives a detailed step-by-step instruction on how to use each function and feature of thesystem.The suggested outline of the User’s Manual is as follows:Title Page (similar to the thesis title page but add the line USER’S MANUAL below the thesis title)Table of Contents1.0. INTRODUCTIONThis section gives an overview of the system. It includes the following subsections:1.1. SYSTEM REQUIRMENTSThis section lists the minimum hardware and software requirements needed to properly execute the

system.1.2. INSTALLATIONThis subsection contains instructions on how to install the system, and the list necessary files and theirrespective directories.1.3. CONVENTIONThis subsection presents the convention used in the manual, e.g., text in boldface for emphasis onimportant concepts, text in italics are inputs from the users, etc.2.0. GETTING STARTEDThis section tarts with instructions on how to run the system, and the initial screen that will bedisplayed. It then explains the major components of the system, e.g., tool bars, menu options, statusbar, etc.3.0. <MODULE / FEATURE 1>Succeeding sections, from 3.0 to N-1, focus on the major modules or features of the system. Eachsection contains detailed instructions on how to use the particular modules, the available features andlimitations of the module.::N.0. MessagesThis section lists all system messages – error message, status message, information, and instructionmessage – that the user may encounter while using the system. For each message, include a briefdescription and the possible courses of action that the user may take in response to the message.Below is a sample format:<Message Text>Description:SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 37

Action:The messages must be arranged in ascending order, and may be grouped into subsections (e.g., N.1Error Messages, N.2 Status Messages, etc.).SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 38

11.0 FormsTitle Page<Title of Thesis>A [Partial]29 Thesis [Proposal]Presented tothe Faculty of the College of Computer StudiesDe La Salle UniversityIn Partial Fulfillmentof the Requirements for the Degree ofBachelor of Science in Computer Scienceby<lastname, firstname, middle initial of proponent 1>30

<lastname, firstname, middle initial of proponent 2><lastname, firstname, middle initial of proponent 3><lastname, firstname, middle initial of proponent 4><adviser’s signature><adviser’s name>Faculty Adviser<date of submission>29 A Thesis Proposal is used for students working on the STRESME requirements; A Partial Thesis is used for THES1 document and AThesis is used for THES3 document.30 Proponents’ names are arranged according to the last nameSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 39

Adviser’s Recommendation SheetThe [partial] thesis [proposal] entitled<title of thesis>developed by:<lastname, firstname, middle initial of proponent 1><lastname, firstname, middle initial of proponent 2><lastname, firstname, middle initial of proponent 3><lastname, firstname, middle initial of proponent 4>and submitted in partial fulfillment of the requirements of the Bachelor of Science in ComputerScience degree, has been examined and recommended for acceptance and approval.____________________________, Adviser______________________________, DateSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 40

Panel’s Approval SheetThe [partial] thesis [proposal] entitled<title of thesis>after having been reviewed, is hereby approved by the following members of the thesiscommittee:___________________________<name of lead panelist>Lead Panelist__________________________Date_____________________ ___________________<name of panelist> <name of panelist>Panelist Panelist____________________ ____________________Date DateSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 41

College Acceptance SheetThe thesis entitled<title of thesis>after having been recommended and reviewed, is hereby approved by the SoftwareTechnology Department, College of Computer Studies, De La Salle University:_____________________ __________________<name of chairperson> <name of dean>

Chairperson DeanSoftware Technology Department College of Computer Studies_____________________ ___________________Date DateSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 42

THSST-2 Agreement Form(Front page)(Back page)SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 43

THSST-2 Grade Form(front page)(back page)SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 44

12.0 Additional Guidelines on Document WritingThe following discussions are based from the American Psychological Association (APA) format*.12.1 Developing an OutlineAn outline is:A logical, general descriptionA schematic summaryAn organizational patternA visual and conceptual design of your writingAn outline reflects logical thinking and clear classification.PurposeGenerally:Aids in the process of writingSpecifically:Helps you organize your ideasPresents your material in a logical formShows the relationships among ideas in your writingConstructs an ordered overview of your writingDefines boundaries and groupsProcessBefore you begin:Determine the purpose of your paper.Determine the audience you are writing for.Develop the thesis of your paper.Then:Brainstorm: List all the ideas that you want to include in your paper.Organize: Group related ideas together.Order: Arrange material in subsections from general to specific or from abstract to concrete.Label: Create main and subtonic headings, and write coordinate levels in parallel form.TheoryAn outline has a balanced structure based on the following principles:ParallelismCoordinationSubordinationDivisionParallelismWhenever possible, in writing an outline, coordinate heads should be expressed in parallel form. That

is, nouns should be made parallel with nouns, verb forms with verb forms, adjectives with adjectives,and so on (Example: Nouns: computers, programs, users; Verbs: to compute, to program, to use;Adjectives: home computers, new programs, experienced users). Although parallel structure is desired,logical and clear writing should not be sacrificed simply to maintain parallelism. (For example, there are* From the book entitled The Publication Manual of the American Psychological Association (4th Edition)SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 45

times when nouns and gerunds at the same level of an outline are acceptable.) Reasonableness andflexibility of form is preferred to rigidity.CoordinationIn outlining, those items which are of equal significance have comparable numeral or letterdesignations: an A is equal to a B, a 1 to a 2, an a to a b, etc. Coordinates should be seen as "havingthe same value." Coordination is a principle that enables a writer to maintain a coherent and consistentdocument.Example:Correct coordinationA. Word processing programsB. Database programsC. Spreadsheet programsFaulty coordinationA.Word processing programsB. Microsoft WordC. Page MakerExplanation: Word is a type of word processing program and should be treated as a subdivision. PageMaker is a type of desktop publishing program. One way to correct coordination would be:A. Types of programs1. Word processing2. Desktop publishingB. Evaluation of programs1. Word processinga. Wordb. Word Perfect2. Desktop Publishinga. Page Makerb. Quark ExpressSubordinationIn order to indicate levels of significance, an outline uses major and minor headings. Thus in orderingideas, you should organize it from general to specific or from abstract to concrete- the more general orabstract the term, the higher the level or rank in the outline. This principle allows your material to beordered in terms of logic and requires a clear articulation of the relationship between component parts

used in the outline. Subdivisions of each higher division should always have the same relationship tothe whole.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 46

Example:Correct subordinationA. Word processing programs1. Microsoft Word2. Word PerfectB. Desktop publishing programs1. PageMaker2. Quark ExpressFaulty subordinationA. Word processing programs1. Word2. Useful3. ObsoleteExplanation: There is an A without a B. Also 1, 2, and 3 are not equal; Word is a type of wordprocessing program, and useful and obsolete are qualities. One way to correct this faulty subordinationis:A. Word1. Positive features2. Negative featuresB. Word Perfect1. Positive features2. Negative featuresDivisionTo divide you always need at least two parts; therefore, there can never be an A without a B, a 1without a 2, an a without a b, etc. Usually there is more than one way to divide parts; however, whendividing use only one basis of division at each rank, and make the basis of division as sharp aspossible.Correct divisionA. Personal computers: hardware1. Types2. Cost3. MaintenanceB. Personal computers: softwareFaulty divisionA. Computers1. Mainframe2. Microa. Floppy diskb. Hard diskB. Computer uses1. Institutional2. PersonalSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 47

Form

The most important rule for outlining form is to be consistent!An outline can use topic or sentence structure.A topic outline uses words or phrases for all entries; uses no punctuation after entries.Advantages: presents a brief overview of work; is generally easier and faster to write than a sentenceoutline.A sentence outline uses complete sentences for all entries; uses correct punctuation.Advantages: presents a more detailed overview of work including possible topic sentences; is easierand faster for writing the final paper.An outline can use Roman numerals/Letters or Decimal form.Roman NumeralI.A.B.1.2.a.b.Decimal1.01.11.21.2.11.2.21.2.2.11.2.2.212.2 Quoting, Paraphrasing, and SummarizingThis section is intended to help you become more comfortable with the uses of and distinctions amongquotations, paraphrases, and summaries. The first part of the handout compares and contrasts theterms, while the second part offers a short excerpt that you can use to practice these skills.12.2.1 What are the differences among quoting, paraphrasing, and summarizing?These three ways of incorporating other writers' work into your own writing differ according to thecloseness of your writing to the source writing. Obviously, a quotation must be identical to the original,using a narrow segment of the source. Paraphrased material is usually shorter than the originalpassage, taking a somewhat broader segment of the source and condensing it slightly. Summaries aresignificantly shorter than the original and take a broad overview of the source material.Quotations must match the source document word for word and must be attributed to the originalauthor.Paraphrasing involves putting a passage from source material into your own words. A paraphrasemust also be attributed to the original source.Summarizing involves putting the main idea(s) into your own words, including only the mainpoint(s). Once again, it is necessary to attribute summarized ideas to the original source.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 48

9.2.2 Why use quotations, paraphrases, and summaries?Quotations, paraphrases, and summaries serve many purposes. They are used to:provide support for claims or add credibility to your writingrefer to work that leads up to the work you are now doinggive examples of several points of view on a subjectcall attention to a position that you wish to agree or disagree withhighlight a particularly striking phrase, sentence, or passage by quoting the originaldistance yourself from the original by quoting it in order to cue readers that the words are not yourownexpand the breadth or depth of your writingWriters frequently intertwine summaries, paraphrases, and quotations. As part of a summary of anarticle, a chapter, or a book, a writer might include paraphrases of various key points blended withquotations of striking or suggestive phrases as in the following example:In his famous and influential work On the Interpretation of Dreams, Sigmund Freud argues that dreamsare the "royal road to the unconscious" (page), expressing in coded imagery the dreamer's unfulfilledwishes through a process known as the "dream work" (page). According to Freud, actual butunacceptable desires are censored internally and subjected to coding through layers of condensationand displacement before emerging in a kind of rebus puzzle in the dream itself (pages).9.2.3. How to use quotations, paraphrases, and summariesPractice summarizing the following essay, using paraphrases and quotations as you go. A good way tostart is to read the entire text, noting the key points and main ideas. Then, summarize in your ownwords what the single main idea of the essay is. Next, paraphrase important supporting points thatcome up in the essay. Also consider any words, phrases, or brief passages that you believe should bequoted directly. There are several ways to integrate quotations into your text. Often, a short quotationworks well when integrated into a sentence. Longer quotations can stand-alone. Remember thatquoting should be done only sparingly; be sure that you have a good reason to include a directquotation when you decide to do so.12.3. Paraphrase: Write it in Your Own WordsLearn to borrow from a source without plagiarizing. A paraphrase is...your own rendition of essential information and ideas expressed by someone else, presented in anew form.one legitimate way (when accompanied by accurate documentation) to borrow from a source.a more detailed restatement than a summary, which focuses concisely on a single main idea.Paraphrasing is a valuable skill because...it is better than quoting information from an undistinguished passage.it helps you control the temptation to quote too much.the mental process required for successful paraphrasing helps you to grasp the full meaning of theoriginal.

6 Steps to Effective Paraphrasing1. Reread the original passage until you understand its full meaning.2. Set the original aside, write your paraphrase on a note card.3. Jot down a few words below your paraphrase to remind you later how you envision using thismaterial. At the top of the note card, write a key word or phrase to indicate the subject of yourparaphrase.4. Check your rendition with the original to make sure that your version accurately expresses all theessential information in a new form.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 49

5. Use quotation marks to identify any unique term or phraseology you have borrowed exactly fromthe source.6. Record the source (including the page) on your note card so that you can credit it easily if youdecide to incorporate the material into your paper.Some examples to compare:The original passage:Students frequently overuse direct quotation in taking notes, and as a result they overuse quotations inthe final [research] paper. Probably only about 10% of your final manuscript should appear as directlyquoted matter. Therefore, you should strive to limit the amount of exact transcribing of source materialswhile taking notes. Lester, James D. Writing Research Papers. 2nd ed. (1976): 46-47.A legitimate paraphrase:In research papers students often quote excessively, failing to keep quoted material down to adesirable level. Since the problem usually originates during note taking, it is essential to minimize thematerial recorded verbatim.An acceptable summary:Students should take just a few notes in direct quotation from sources to help minimize the amount ofquoted material in a research paper.A plagiarized version:Students often use too many direct quotations when they take notes, resulting in too many of them inthe final research paper. In fact, probably only about 10% of the final copy should consist of directlyquoted material. So it is important to limit the amount of source material copied while taking notes.12.4 Avoiding PlagiarismAcademic writing in any institutions is filled with rules that writers often don’t know how to follow. Aworking knowledge of these rules, however, is critically important; inadvertent mistakes can lead tocharges of plagiarism, or the unacknowledged use of somebody else’s words or ideas. A charge ofplagiarism can have severe consequences, including expulsion from the university. This handout, whichdoes not reflect any official university policy, is designed to help writers develop strategies for knowing

how to avoid accidental plagiarism.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 50

The Contradictions of American Academic WritingShow you havedone your research---But---Write somethingnew and originalAppeal to expertsand authorities---But---Improve upon, ordisagree withexperts andauthoritiesImprove yourEnglishBy mimicking whatyou hear and read---But---Use your ownwords, your ownvoiceGive credit wherecreditIs due---But---Make your ownsignificantcontributionSince teachers and administrators may not distinguish between deliberate and accidental plagiarism,the heart of avoiding plagiarism is to make sure you give credit where it is due. This may be credit forsomething somebody said, wrote, emailed, drew, or implied.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 51

Choosing When to Give CreditNeed to Document No Need to DocumentWhen you are using or referring tosomebody else’s words or ideas from amagazine, book, newspaper, song, TVprogram, movie, Web page, computerprogram, letter, advertisement, or any othermediumWhen you use information gainedthrough interviewing another personWhen you copy the exact words or a"unique phrase" from somewhereWhen you reprint any diagrams,illustrations, charts, and picturesWhen you use ideas that others have

given you in conversations or over emailWhen you are writing your ownexperiences, your own observations, yourown insights, your own thoughts, your ownconclusions about a subjectWhen you are using "commonknowledge" — folklore, common senseobservations, shared information withinyour field of study or cultural groupWhen you are compiling generallyaccepted factsWhen you are writing up your ownexperimental resultsMaking Sure You Are SafeAction during the writing process Appearance on the finishedproductWhen researching,note-taking, andinterviewingMark everything that is someoneelse’s words with a big Q (for quote)or with big quotation marksIndicate in your notes which ideasare taken from sources (S) and whichare your own insights (ME)Record all of the relevantdocumentation information in yournotesProofread and check with yournotes (or photocopies ofsources) to make sure thatanything taken from your notesis acknowledged in somecombination of the ways listedbelow:In-text citationFootnotesBibliographyQuotation marksIndirect quotationsWhen paraphrasingand summarizingFirst, write your paraphrase andsummary without looking at theoriginal text, so you rely only on yourmemory.Next, check your version with theoriginal for content, accuracy, andmistakenly borrowed phrasesBegin your summary with astatement giving credit to the

source: According to JonathanKozol, ... Put any unique wordsor phrases that you cannotchange, or do not want tochange, in quotation marks: ..."savage inequalities" existthroughout our educationalsystem (Kozol).SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 52

When quoting directly Keep the person’s name near thequote in your notes, and in your paperSelect those direct quotes thatmake the most impact in your paper –too many direct quotes may lessenyour credibility and interfere with yourstyleMention the person’s nameeither at the beginning of thequote, in the middle, or at theend Put quotation marks aroundthe text that you are quotingIndicate added phrases inbrackets ( [ ] ) and omitted textwith ellipses ( . . . )When quotingindirectlyKeep the person’s name near thetext in your notes, and in your paperRewrite the key ideas usingdifferent words and sentencestructures than the original textMention the person’s nameeither at the beginning of theinformation, or in the middle, orat that end Double check tomake sure that your words andsentence structures are differentthan the original textDeciding if something is "Common Knowledge"A material is probably common knowledge ifYou find the same information undocumented in at least 5 other sourcesYou think it is information that your readers will already knowYou think a person could easily find the information with general reference sources.9.5 Writing Research Papers: A Step-by-Step Procedure*The Preliminaries1. Choose a topic2. Begin preliminary reading3. Restrict the subject4. Develop a preliminary thesis statementGathering Data1. Compile the working bibliography

2. Prepare the bibliography on cards in correct form (3" x 5" cards)3. Begin extensive work in the library reference room; be sure to check:a. general bibliographiesb. trade bibliographiesc. indexes (books and collections, literature in periodicals, newspaper indexes, pamphlet indexes)d. library electronic catalogueTaking Notes1. Develop a preliminary outline2. Evaluate your source material; which is primary material and which is secondary material?3. Begin note-taking on cards (4" x 6" cards)4. Avoid plagiarismWriting the Paper* Most of this format is based on the process described by James D. Lester in Writing Research Papers: A Complete Guide, 2nd ed. (1971; rpt. Glenview,Illinois: Scott, Foresman, 1976).SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 53

1. Develop the final outline; test your outline2. Prepare to write:a. Put your note cards in the order that your outline is inb. Consider your (real and imagined) readers and how their expectations may affect your tone and style3. Write the rough draft4. Check your documentation carefully5. Revise and rewrite6. Check the format of the text, citations, notes, and bibliography7. ProofreadSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 54

13.0 STTHES Final DeliverablesIf a thesis group received a verdict of PASS WITH MINOR REVISIONS, this does not guarantee thegroup that they have passed the thesis. They are required to accomplish all the revisions given bythe panelists. Furthermore, the group has to submit all the requirements imposed by the thesiscoordinator. If any of the requirements is not received by the thesis coordinator with the condition thatthe software is running perfectly will automatically receive a FAIL mark for THSST-3.The following are the guidelines and requirements for THSST-3 final deliverables:All thesis groups must submit the following:One (1) hardbound (GREEN color) copy of the thesis documentation. Must be an original copy.The main document must be printed on thesis paper, using 10-size font, single-spaced, Arial.Include in the main thesis document the Panel’s Approval Sheet and the Adviser’sRecommendation Sheet (with complete signatures of every member in the thesis panel committeeand the thesis adviser)Appendices, Technical Manual, and User’s Manual must be printed on letter-sized (8” x 11”) bondpaper.The source codes need not be printed.Documents (i.e technical and user’s) must be bound along with the thesis main document as one

volume.The front cover of the hardbound document should follow the same format as the thesis title page.The side cover of the hardbound document should contain the thesis title, term and year ofcompletion.Three (3) properly labeled CD-copies of the source codes, thesis documentation (includingtechnical and user’s manuals), defense presentation and the executable files.Each CD should be placed inside a thin, clear, plastic case.A label should be inserted into the slot of the clear plastic case. The front label must contain thefollowing information: Thesis title, Term and School year of completion, proponents, and adviser/s.The back label should indicate the software requirements and the installation instructions in bulletform. The CD label should be the same as the front label. The fonts used should be at least Arial7pts.The CD(s) must be subdivided into the following directory structure:ROOT[SOURCE] [APP] [DOC] [PRESENTATIONS]<EXE> <HLP> <DLL> ... <MAIN> <USER> <TECH>where:[SOURCE] contains the source code (*.CPP, *.H, *.JAVA, *.JSP, *.FRM, *.BAS, *.HTM, *.VBS, etc)[PRESENTATION] contains the PowerPoint presentation used for the final defense, continuous Flashpresentation of a run/flow of your program, HTML and etc.[DOC] contains the thesis documentation and is subdivided into main document (<main>), user’smanual (<user>), technical manual (<tech>), and other documents (<others>) which include thetechnical paper/s (if applicable), poster, and brochure. The technical paper refers to a document inACM format intended to be submitted to a conference. The poster is a 1-page short description of thethesis (or a component in the thesis) outlining the major features, intended for a poster presentation ina conference. The brochure is 1-page back-to-back document for marketing purposes, so the intendedSOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 55

reader would be end-users. The actual editable document (<DOCS>) and its PDF format files (<PDF>)should be stored.[EXE] contains the executable file (*.EXE) and its necessary components, including DLL (*.DLL), helpfiles (*.HLP), data files (*.DAT, *.TXT), components, activex, etc needed to execute your software.Include also a sample file.Both CDs must also contain the following files at the root directory:SETUP.EXE. Any one of these files will install the executable file and other necessary components(e.g., data files, system files, help files, DLL files) needed to run your software.

FILES.LST. This file contains the list of files found on each of the CDs, as well as a brief description ofeach file.READ.ME. This file contains instructions on how to install the executable files, the systemrequirements, your main user name and password, personal vitae of all proponents, and any lastminute information.CD containing the HTML file with the following contents:Heading: Software Technology DepartmentUndergraduate Thesis ProgramThesis TitleOptional picture file(s)Thesis Proponents (with picture and contact info) and Thesis AdviserThesis AbstractDocument Outline (i.e., Table of Contents and links to the documents in the CD)Research OverviewSystem OverviewMajor Modules and System FeaturesCD should also contain flash presentation demonstrating the thesis project (i.e. features andfunctionality). This flash presentation should be a self-demo showing the functionality and featuresof the software.CD should also contain the PowerPoint presentation used during the final defense.The Adviser should affix his signature at the front label and the CD label signifying that the CDshave been checked; the contents are complete; and the programs are working properly includingthe installation.Printout of CCS Alumni Information Sheet of each of the proponentsCourse cards with a grade of PASS will be released only upon receipt of all the aboverequirements on course card distribution day.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 56

THSST-0 (STRESME) * THSST-1 * THSST-2 * THSST -3 ProcessTHSST-0 (STRESME)Requirement:1. Students enroll a 2-unit course, STRESMEScope:

Identification of the research problem Specification of the objectives of the research; and Search and review of related literature

Activities: Proposal Defense

o Scheduling STRESME Instructoro Selection of Panelists STRESME Instructoro Selection of Adviser STRESME Instructoro Students Prepare presentation materials.

Stages: (a) Regular Defense; (b) Re-ProposeProvisions:

Students can under go at most 3 Defenses Defense weeks/Submission weeks are as follow:

8th week (W) – submission of document (for 1st defense) 9th week – 1st defense week 10th week (W) – submission of document (for 2nd defense) 11th week – 2nd defense week 12th week (W) – submission of document (for 3rd defense) 13th week – last defense week 14th week – submission of approved thesis proposal document No further defense beyond the 13th week. If students fail at this point, then they enroll STRESME on

the following term.Verdicts:

Pass with Revisions Re-Propose Fail

Process:1. Students submit thesis proposal document to the STRESME instructor based on the date stated in thesyllabus.a. It is highly recommended that when students do their thesis proposal, their probable thesis adviser isguiding them.2. Students undergo Proposal Defense3. If students received a verdict of Conditional Pass with Recommendations/Revisions, then:a. Students perform the revisions required by the panelists;b. As soon as they are done with the revisions, students submit their revised document to theSTRESME Instructor. Attached in the document is a copy of revisions requested by the panelistsand pages where these revisions can be found in the revised document;c. STRESME Instructor routes the document to the panelists.d. Panelists check and return the document back to the STRESME Instructor.e. STRESME Instructor returns the document back to the proponentsf. Students check their documents to see if there are further revisions. If there are, go back to Step3.a. If there are no further revisions, then go to Step g.g. Submit the approved document to the STRESME Instructor with panelists’ signatures on/beforethe date and time specified in the syllabus.h. STRESME Instructor forwards all (submitted) approved proposal to ST Thesis Coordinator.i. The STRESME Instructor recommends an adviser for each thesis group and coordinates with theThesis Coordinator and the ST Chair. Once approved, the STRESME Instructor posts the list ofadvisers at the ST bulletin board, and informs the students.j. If Step 4.a is not applicable to the students, then students fail THSST-0 and retake THSST-0 thefollowing term.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 574. If students received a verdict of Representation/Re-Propose, then:a. If (the number of defenses gone through by the students ≤3) and (the current term week is ≤12th

week) thenb. Submit a new proposal or revised proposal based on the recommendations set by the panelists tothe STRESME Instructor;c. STRESME Instructor sets a redefense schedule.d. If students received a verdict of Conditional Pass with Recommendations/Revisions, then go toStep 3.a. If students received a verdict of Reject/Re-propose, then go to Step 4.a.Deliverables:o Thesis ProposalTHSST-1STRESME – hard pre-requisite of THSST-1Requirements:1. Approved STRESME proposal;2. Enrolled in a 2-unit course, THSST-1Scope:

Search and review of related literature;

Investigation of existing solutions to the identified problem(s) in STRESME; Evaluation of existing solutions; and Application of methods and theories in the design of a solution to the problem(s)

Activities:1. Partial thesis defenseo Scheduling for regular and redefenses ST Thesis Coordinatoro Selection of Panelists based from STRESME panelo Students Prepare presentation materials; and prototype of system flow2. Stages: (a) Regular Defense; (b) RedefenseProvisions:

If students fail to submit documents for the Regular Defense, they will automatically be scheduled forRedefense.

Scheduling/Submission weeks are as follow: 8th week (W) – submission of partial thesis document 9th week – regular defense 11th week (W) – submission of partial thesis document for redefense 12th week – redefense week 13th week – submission of final approved partial thesis document 14th week – submission of THSST-2 Agreement Form

Verdicts: Pass with Revisions Redefense Fail

Process:1. Students have the option to choose the following: (a) regular defense; and (b) redefense. If studentschoose regular defense, go to Step 2; if students choose redefense, go to Step 32. If regular defense, then:a. Students submit partial thesis document to the ST Thesis Coordinator on/before the date and timeset by the ST Thesis Coordinator.b. The Adviser should sign the partial thesis document’s title page before the submission.c. Students undergo partial thesis defense.d. If students received a verdict of Conditional Pass with Recommendations/Revisions, then:i. Students perform the revisions required by the panelists;ii. Students submit the revised document to their adviser. Attached in the document is a copyof revisions requested by the panelists and pages where these revisions can be found inthe revised document;iii. Adviser checks their work and pass the document to other panelists;iv. Other panelists check the document and once done, pass the document back to theadviser.SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 58v. Students get the document from the adviser.vi. If there are further revisions needed to be done by the students, go back starting from Step2.d.ivii. If there are no more revisions needed, students prepare the final version of their partialthesis document.viii. The adviser and panelists should sign the panel’s approval sheet.ix. The adviser should sign the document’s title page.x. Students submit the signed document to the ST Thesis Coordinator on/before the date andtime set by the latter.e. If students received a verdict of Redefense, then go to Step 3.3. If Redefense, then:a. Perform Steps 2.a to 2.c.b. If verdict is Conditional Pass with Recommendations/Revisions, then perform starting from Step2.dc. If verdict is Fail then, go to Step 4.4. If students received a verdict of Fail, then:

a. Students enroll THSST-1 in the following term.Deliverables:

Partial Thesis Document THSST-2 Agreement Form

THSST-2THSST-2 – hard pre-requisite of THSST-1Requirements:1. Approved THSST-1 document;2. THSST-2 Agreement Form3. Enrolled in a 2-unit course, THSST-2Scope:

Implementation of major system functions &/or modules in the target programming language and/orenvironment;

Development and implementation of the solution identified in THSST-1; Documentation of development and implementation issues; Regular consultation with the thesis adviser; Public presentation in a duly organized symposium or congress by the College and/or University, or

local/national conferences, if applicable and agreed by the thesis adviser and the thesis panelcommittee.Verdicts:

Pass Fail

Process:1. A THSST-2 Agreement Form will be supplied by the Thesis Coordinator to the group’s thesis adviser.2. Before the admission of the group to THSST-2, the thesis adviser along with the thesis panelcommittee and the thesis group defines the expected deliverables and the corresponding deadlines forTHSST-2. In addition, the form indicates under what conditions the group will pass THSST-2 andproceeds to THSST-3 or receives a failing mark.3. The contents of the Agreement form are deemed to be valid if all signatures of the concerned people(i.e. thesis adviser, proponents and thesis panel committee) are present.4. At the minimum, the thesis adviser validates the deliverables submitted by the group.Deliverables:

Deliverables stated in the THSST-2 Agreement form THSST-2 Grade Form

THSST-3Requirements:1. Approved THSST-1 document and received a passing mark in THSST-2;2. Enrolled in a 2-unit course, THSST-3Scope:

Development of minor system functions (i.e. online help, system enhancements) System testing and analysis of test results;

SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 59 Documentation of testing activities and test results; Finalization of the thesis deliverables (i.e. main document, technical manual, user’s manual, software);

and Preparation for the thesis defense

Activities: Thesis Defense

o Scheduling of early, regular and redefenses ST Thesis Coordinatoro Selection of Panelists based from THSST-1 panelo Students Prepare presentation materials; final thesis document; software; technical manual anduser’s manual.

Stages: (a) Regular Defense; (b) Redefense; and (c) RedemoVerdicts:

Pass with Revisions Redefense

Redemo Fail

Provisions: Scheduling/Submission weeks as follow: 4th week (W) – submission of thesis document for early defense 5th week – early regular defense week 7th week (W) – submission of thesis document for early redefense 8th week – early redefense week 9th week (W) – submission of thesis document for regular defense 10th week – regular defense week 12th week (W) – submission of thesis document for redefense 13th week – redefense week 14th week – submission of final deliverables

Process:1. Students have the option to choose the following: (a) early defense; (b) regular defense; and (c)redefense. If students choose early defense, then go to Step 2 ; if students choose regular defense,then go to Step 3 and if students choose redefense, go to Step 4.2. If early defense, follow the process/procedures in Step 3 and Step 4.3. If students choose regular defense, then:b. Students submit the complete thesis document with adviser’s signature on the title page to the STThesis Coordinator on the date and time set by the latter.c. Students undergo thesis defense.d. During the defense, students should present their technical manual, user’s manual and theirsystem/SW.e. If students received a verdict of Conditional Pass with Recommendations/Revisions, then:i. Students make necessary revisions based on the recommendation of the panelists;ii. Students submit their revised documents &/or SW to their adviser on the date set by thepanelists during the defense;iii. Adviser checks their work; and once done, forward the materials to the other panelists;iv. Other panelists check students’ work and once done forward it back to the Adviser;v. Adviser returns the materials to his studentsvi. If there are further revisions, then perform Steps 3.d.i to 3.d.v.vii. If there are no more revisions, students prepare the final deliverables set by the ST ThesisCoordinator. Look at the DELIVERABLES SECTION of this document for THSST-3f. If students received a verdict of Redefense, then go to Step 4.g. If students received a verdict of Redemo, then go to Step 6.4. If students choose redefense, then:a. Perform Steps 3.a, to 3.c.b. If students received a verdict of Conditional Pass with Recommendations/Revisions, then performStep 3.dc. If students received a verdict of Fail, then perform Step 5.5. If students received a verdict of Fail, then students enroll THSST-3 in the following term.6. If students received a verdict of Redemo, then:SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 60a. Students prepare any requirements set by the panelists.b. Students undergo the redemo activity on the date specified by the panelistsc. If students received a verdict of Conditional Pass with Recommendations/Revisions, then, performStep 3.ed. If students received a verdict of Fail, then perform Step 5.Deliverables:

Requirements set by the Thesis Coordinator and the requirements are as follow (kindly refer tosection 13.0 for the details):

One (1) hardbound (GREEN color) copy of the thesis documentation. This document mustbe an original copy printed using the DLSU paper, 10-size font, single-spaced, Arial. Moreso the document should include the Panel’s Approval Sheet and Adviser’sRecommendation Sheet. Both should be signed. Included also the Appendices, Technical

Manual, and User’s Manual and all of these can be printed on a letter-sized (8”x 11”) bondpaper

The main document, Technical and User’s Manual must be bound as a single volume. 3 CDs properly labeled and the contents include (a) the main document; (b) technical

manual; (c) user’s manual; (d) source codes; (e) installation procedure and utilities; (f)libraries; 3rd-party software and the like.

A flash-presentation or demonstration of the final thesis product. Brochure and poster Printout of CCS Alumni Information Sheet

SOFTWARE TECHNOLOGY DEPARTMENT Thesis Guidelines: page 61

Thesis Defenses SchedulingAS OF SEPTEMBER, 2007STTHES0/STRESM1st Defense 9th week2nd Defense 11th week3rd Defense 13th weekSubmission of approved thesis proposal 14th weekSTTHES1/THSST-1Regular Defense 9th weekRedefense Week 12th weekSubmission of approved partial thesis document 13th weekSubmission of THSST-2 Agreement Form 14th weekSTTHES2/THSST-2THSST-2 Grade Form 14th weekSTTHES3/THSST-3Early Defense Week 5th weekEarly Redefense Week 8th weekRegular Defense Week 10th weekRedefense Week 13th weekSubmission of Final Deliverables 14th week