Thesis Guidelines Assignment

Thesis Guidelines Assignment Words: 2885

Thesis Main Documentation Outline Title Page Dedication Acknowledgement Abstract Table of Contents List of Appendices List of Tables List of Figures Table of Contents (Arial 12) Chapter I – Introduction (Mar 2, 2010) 1. Background of the Study 2. Statement of the Problem 3. Objectives of the Study 1. General Objective 2. Specific Objectives 4. Significance of the Study 5. Scope and Limitation Chapter II – Theoretical Framework and Review of Related Studies (Mar 12, 2010) 1. Theoretical / Conceptual Framework 2. Review of Related Studies (Related Studies-10; Related Literature 5) 3.

Operational Definition of Terms Chapter III – Methodology of the Study (Mar 26, 2010) Chapter IV – Data Gathering Procedures and Outputs (Mar 31, 2010) Chapter V – Documentation of Current System (Mar 2, 2010) 1. Description of Current System 2. Hardware Set-up 3. Software and Applications being used 4. Personnel Chapter VI – Requirement Analysis Specification (Mar 26, 2010) Chapter VII – System Requirement Specification(Mar 31, 2010) 1. Hardware Requirements 2. Software Requirements 3. Human Resource Requirements Chapter VIII – Implementation (Apr 6, 2010) . Testing 2. Installation Process Chapter IX – Conclusion and Recommendation (Apr 8, 2010) 1. Conclusion 2. Recommendation Appendices Gannt Chart User’s Manual Bibliography Curriculum Vitae Resource Person Thesis Main Documentation Outline 1. All Thesis Main Documentation should follow the following standards: a. Margins |Left |Right |Top |Bottom | |1. 5″ |1. 0″ |1. 0″ |1. 0″ | b. Font |Font |Size |Font Style | |1. Text |Arial |12 |Regular | | | | |use Italics or single underline | | | | |in emphasizing some text | |Heading or Sub-headings |Arial |14 |Bold |

Don’t waste your time!
Order your assignment!


order now

NOTE: Alignment of the Headings are Center c. Spacing -Double Space d. Footer ____________________________________________________________ |Line |Black, 1 pt. | |Text |Arial, size 11, Regular | e. Pages -The page notation to be used is – Sample: Page No. Chapter II : 2-1 Appendix A : A-1 Note: There should be no page numbers for the items before Chapter 1. f. Sub-headings and text All text and sub headings should be in the following format as shown in the example below:

Chapter I Introduction (Arial 14 Bold Main Headings) 1. Background of the Study (Arial 14 Bold Sub-headings) Real Estate, in broad definition, land and everything made Permanently a part thereof, and the nature and extent of one’s interest therein. In law, the word real, as it relates to property, means land as distinguished from personal property; and estate is defined as the interest one has in property. 2. Statement of the Problem g. Bibliography (References and Citations) This section deals with the nature of reference materials (e. g.

Books, Unpublished Materials, Journals, and Periodicals, etc. ) if one wishes to read further in the area of problem or corollary areas. It also speaks of the researcher’s awareness of the literature in his field and his critical resources. Citations, as they appear within the text, should be coded to reflect the first four characters of the principal author’s last name suffixed by the year of publication. Thus, [MILL1991] refers to the publication of Faron Miller for his work published 1991. If Miller has another publication for the same year, the code is appended with an alphabet in lowercase.

Thus, a second publication of Miller should be coded as [MILL1991a], while a third publication should be coded as [MILL1991b]. Books: (). : complete name of publisher> Example: [CHIC1986]J. M. Chiclov(1986). An Introduction to Distributed and Parallel Computing. Hemel Hempstead: Prentice-Hall International (UK), Ltd. Journal: (). ”, Journal Title, volume number (issue number), Example: [BAET1988]J. C. M. Bacten & J. A. Bergstra (1988). ‘Global Renaming Operators in Concrete Process Algebra’, Information and Computation, 78(3),pp. 05-245. Conference: (year of publication>). ”, In: Conference Name(editors of the proceedings, ed), . : . Example: [PARK1981]D. H. E. Park (1981). ‘Concurrency and Automata on Infinite Sequences’. In: Fifth GI Conference (P. Deussen, ed). Pp. 167-183. Berline: Springer-Verlag World Wide Web: (year). ‘Homepage title’, URL site Example: [CRUZ1995]J. Cruz(1996). ‘The Home Page of Juan Dela Cruz’. http://www. informatics. edu. ph Note: Do not use the Traditional Style of Footnoting 2. Title Page

The first page of a thesis is the title page. The title page presents the title, the full name of the writer, and the submission statement, which includes the faculty or school, and the institution, the degree sought (granted), and the month and year in which the degree is to be (or was) granted. Thesis Title – The title of the project should be concise as well as descriptive and comprehensive. It is a distinctive name given to the project describing the work scope in a specific context and indicates the content of the paper

Generally, project titles begin with a noun or present participle form of an action verb. It is advisable to state project titles in general terms in order to bundle a number of problem areas. Humorous or catchy titles are not appropriate and is discouraged. 3. Adviser’s Recommendation Sheet No final thesis documentation will be accepted if all copies are not duly signed by the thesis adviser. The Adviser’s Recommendation Sheet provides space for the signature of the adviser of the group indicating that he/she has examined and recommended the thesis for acceptance and approval. . Thesis Coordinator and Academic Head’s Acceptance Sheet No final thesis documentation will be accepted if all copies are not duly signed by the Thesis Coordinator and Academic Head of the college indicating their acceptance of the work. The college acceptance sheet provides space for the signatures of the Thesis Coordinator and Academic Head of the college indicating their acceptance of the work. 5. Panel’s Approval Sheet No final thesis documentation will be accepted if all copies are not duly signed by all the defense panelists.

The approval sheet provides space for the signatures of the Thesis Coordinator and Academic Head of the college indicating their acceptance of the work. 6. Table of Contents Observe the following format: TABLE OF CONTENTS (in bold characters, font size 14) Chapter I – Intoduction1-1 1. Background of the Study1-1 2. Statement of the Problem1-2 3. Objectives of the Study1-3 1. General Objective1-3 2. Specific Objectives1-3 4. Significance of the Study1-4 5. Scope and Limitations1-5 Chapter II – Theoretical Framework and Review of Related Studies2-1 1.

Theoretical / Conceptual Framework2-1 2. Review of Related Studies2-2 7. List of Appendices Observe the following format: Appendices (in bold characters, font size 14) Appendix Appendix A. Project Schedule and Work Assignment (Gantt Chart) Appendix B. Certifications Appendix C. Transcript of Interview Appendix D. Survey Forms/ Questionnaires Appendix E. Sample Forms and Reports Appendix F. Screen Design Appendix G. User’s Manual Appendix H. Program Listing Appendix I. Others Project Schedule and Work Assignment Observe the following format:

Project Schedule |ACTIVITIES |5/23 | |Specific? |Yes! Because the objectives state particular, precise and definite details | | |about the project | |Measurable? |Yes! Because the objectives state weighable (80%) indicator to measure the | | |success of the project | |Attainable? |Yes!

Because the procedures, function and integration of GRS and POS is | | |feasible and within reach | |Realistic? |Yes! Because the objective states practical and viable methodology | |Time-bounded? |Yes! Because the objective states the time when the system will be | | |accomplished | 1. Significance of the Study – A discussion on who benefits from the output of the research or thesis project. Discusses the contributions/benefits of the study to: 1. Individuals 2. Corporations 3. Country 4. World or humanity in general – Enumerates the problems that may be solved by the output of the study The resources allocated for the proposed research (human, financial and material) should be justified in terms of the expected utility/ significance of the results for the following concerns: 1. Nationhood and Development • Will the research produce new technology? • Does research address current social, economic, political and cultural problems? Will innovations in natural, infra and human rescue management result from the study? 2. Scientific or Artistic Domain • Will the research contribute new information? • Are data gaps to be filled? • Is a new point of view to be applied to a previously studied phenomenon? 3. University Thrust • Will it contribute to expansion of knowledge? • Will it develop strong scientific base for national mastery • Will it develop strategies to address present socio-economic? 4. Specific Users/Beneficiaries • Will it benefit specific users? How will it benefit these users? 2. Scope and Limitation – Discusses the boundaries of the system to be developed – Enumerates items that will not be covered by the study – Gives a general view of the features/ characteristics of the output of the system – Assumptions made about certain things stated in this section – These are statements of what can be taken for granted about research project. Chapter II – Theoretical Framework and Review of Related Studies 1. Theoretical / Conceptual Framework

The Theoretical foundations in computer science that is necessary to accomplish the objectives set need to be discussed thoroughly and cited accordingly. It is a structure that holds together/ supports the fundamental principles of the study and is required to give legitimate basis defining the area of research Examples: 1. For Games Software: game trees, search algorithms 2. For Information Systems: general systems theory, transaction processing systems, human computer interface, etc. 3. For CAIs, ICAIs, ITSs: learning theories, testing theories, assessment theories, etc. 4. For Expert Systems: search engines, knowledge bases, etc. Inputs Process Output | |Knowlegde Requirements Design Thesis Title | |Software Requirements Development | |Hardware Requirements Implementation | 2. Review of Related Studies ( local – min 3 studies.

Internet – 5 studies) A. General Literature Survey – resources according to your major or area of study B. Abstracts/Compiled Abstract – crude sources of materials C. Bibliographical References – bibliographies of bibliographies D. Directories and Periodical guides E. Trade Literature • National Journals – research and development trend in the country • Information Journals – research and development at international level F. Personal Interviews – ask the following persons about the studies, conclusions, recommendations for future works, present and future rends of particular research, advice, etc. G. Persons in the same professional major H. Persons who have done research at same professional level I. Advisers/ faculty members from yours and other universities J. Go to Industry/Research Institutes/ Government Agency/ Private Corp. – interview/ visit site and inquire the following: • Inquire on their past projects, recommendations, future works that need to be done, problems encountered, limitations and coverage of works. • Inquire about present projects (if possible) • See their facilities, library and laboratory • Try to interview their staff and personnel

K. Evaluation of Existing System/Software Literature or background of the study will: • Reveal investigations similar to your study, how other researchers approach the problem • Suggest method or technique of dealing with problems… suggest approach and strategies • Reveal sources of data • Reveal significant research personalities • See your study in historical/associative perspective • Provide new ideas and new approaches • Assist you in evaluating your own research effort • Provide information on what is current in terms of similar technologies or solutions to a particular problem domain. . Operational definition of Terms Chapter III – Methodology of the Study Identifies the formal method that the proponents intend to follow in order to accomplish what have been set in the objectives. The formal methodologies are any of the software engineering systems analysis and design methodologies: 1. Waterfall Model or Software Development Life Cycle (SDLC Model) • System Engineering and Analysis • Software Requirements Analysis • Design • Coding • Testing • Maintenance 2. Prototyping • Requirements gathering and refinement • Quick Design • Building Prototype • Customer Evaluation of Prototype • Refining Prototype Engineer Product 3. The Spiral Model • Planning • Risk Analysis • Engineering • Customer Evaluation 4. 4th Generation Techniques • Requirements Gathering • Design Strategy • Implementation using 4GL • Testing 5. Rapid Application Development(RAD) 6. Joint Application Development(JAD) Chapter IV – Data Gathering Procedures and Outputs This section discusses procedures on gathering data such as interviews, survey/questionnaires, etc. It also includes try-outs and other validation procedures, observation techniques, distribution and collection of questionnaires and whichever approach(es) is/are to be employed is/are described.

At each procedure, an accompanying output should also be described. If needed, statistical treatment of data using statistical formulas and procedures are described. Chapter V – Documentation of Current System This section should provide necessary information on the current situation/ system such as its nature, its description, users/beneficiaries, etc. 1. Description of Current System 2. Hardware Set-up 3. Software and Applications being used 4. Personnel Chapter VI – Requirement Analysis Specification The Analysis part is the most important section of the document.

In some, researches, this is sometimes referred to as the Analysis and Interpretation of Data. Some important parts in this section are as follows: • Detailed discussion of the application of the research methodology on the data gathered • Detailed discussion on how the solutions to the problems stated were formulated • Detailed discussion on how the objectives of the study were met • Detailed interpretation of results Basically, all the “HOWs” of the research should be stated narratively in this section. Any questions about the validity of the conclusion should be answered by the Analysis section.

This section is an expansion of development of points raised in the introduction and methodology and consists of facts and figures translated into supportive, narrative description or explanation. The discussion should be organized and arranged in clear, associated points/ paragraphs to support the main research output. Sample organization of paragraphs are: • What did you do? • How did you do it? • What happened? A specific analysis tool should be used to illustrate the existing system and the requirements of the project. The analysis tools that may be used are: • Hierarchical Input-Output (HIPO) Charts Data Flow Diagrams • Entity-Relationship Diagram • System Flowchart Chapter VII – System Requirement Specification 1. Hardware Requirements 2. Software Requirements 3. Human Resource Requirements The requirement definition describes everything about how the system is to interact with its environment. Included are the following kinds of items: Physical Environment • Where is the equipment to function? • Is there one or several locations? • Are there any environmental restrictions, such as temperature, humidity or magnetic interference? Interfaces • Is the input coming from one or more other systems? Is the output going to one or more other systems? • Is there a prescribed way in which the data must be formatted? • Is there a prescribed medium that the data must use? Users and Human Factors • Who will use the system? • Will there be several types of user? • What is the skill level of each type of user? • What kind of training will be required for each type of user? • How easy will it be for a user to understand and use the system? • How difficult will it be for a user to misuse the system? Functionality • What will the system do? • When will the system do it? • How and when can the system be changed or enhanced? Are there constraints in execution speed, response time, or throughput? Documentation • How much documentation is required? • To what audience is the documentation addressed? Data • For both input and output, what should the format of the data be? • How often will it be received or sent? • How accurate must it be? • To what degree of precision must the calculations be made? • How much data flows through the system? • Must any data be retained for any period of time? Resources • What materials, personnel, or other resources are required to build, use and maintain the system • What skills must the developers have? How much physical space will be taken up by the system? • What are the requirements for power, heating or air-conditioning? • Is there a prescribed timetable for development? • Is there a limit on the amount of money to be spent on development or on hardware and software? Security • Must access to the system or to information be controlled? • How will one user’s data be isolated from others? • How will user programs be isolated from other programs and from the OS? • How often will the system be backed up? Chapter VIII –Implementation 1. Testing Please refer to Software Development: Testing on page 20 of the Project Student’s Manual. . Installation Process This section should present the procedure on how the final system would be installed upon implementation. Chapter IX –Conclusion and Recommendation 1. Conclusion This section should discuss what has been accomplished in the study written in the objective to see clearly all the significant aspects. It may be subdivided into those that are primarily aesthetic, those that announce the results on any investigation, and those that present a decision concerning a course of action. Also, it may be numbered with respect to problems and sub-problems in the study. 2. Recommendation

This section should furnish future undertakings based on the analysis and conclusion of the study. It may also recommend potential applications of the study, other solutions, enhancement and/or developments related to the study. Informatics International College-Eastwood (Arial 16 Bold) Thesis Title (Arial 16 Bold) A Thesis presented to Informatics International College – Eastwood Branch In partial fulfillment of the Requirements for the (Arial 12) By: (Author’s Names) (Arial 12) Ms. Jasmin A. Caliwag Thesis Adviser (Date(Month/Day/Year) Arial 12) Informatics International College-Eastwood (Arial 16 Bold) ADVISER’S RECOMMENDATION SHEET Arial 16 Bold) This Thesis entitled Thesis Title (Arial 16 Bold) Submitted in partial fulfillment of the Requirements for the And is recommended for acceptance and approval By: (Author’s Names) (Arial 12) Ms. Jasmin A. Caliwag Thesis Adviser (Date(Month/Day/Year) Arial 12) Informatics International College-Eastwood (Arial 16 Bold) THESIS COORDINATOR AND CENTER MANAGER’S ACCEPTANCE SHEET (Arial 16 Bold) This Thesis entitled Thesis Title (Arial 16 Bold) By: Author’s Names (Arial 12) After having been recommended and approved is hereby accepted by the Computer Studies Department of Informatics International College – Eastwood _________________________ Ms. Jasmin A. Caliwag Thesis Coordinator __________________________ Ms. Regina Luz B. Arquiza Center Manager (Date(Month/Day/Year) Arial 12) Informatics International College-Eastwood (Arial 16 Bold) PANEL’S RECOMMENDATION SHEET (Arial 16 Bold) This Thesis entitled Thesis Title (Arial 16 Bold) By: Author’s Names (Arial 12) After having presented is hereby approved by the following members of the panel ________________________________________________ Panelist Panelist _________________________ Lead Panelist (Date(Month/Day/Year) Arial 12) ———————– [pic]

How to cite this assignment

Choose cite format:
Thesis Guidelines Assignment. (2020, Aug 05). Retrieved September 23, 2020, from https://anyassignment.com/samples/thesis-guidelines-6002/