APPLICATION PROJECT DOCUMENTATION FORMAT For ADVANCED LOGIC CIRCUIT (group) Instructions: 1.

The documentation should be computerized and conforms the following format: a. Margins : Left (1.5), Top, Bottom, Right (1) b. Font Style : Verdana c. Font Size : 10 d. Line Spacing: Single 2. Follow the correct format of the documentation. 3. Submission of Application Project in a CD (softcopy) and documentation will be on the date of your presentation. 4. The content of the CD are follows: (Compiler is not included) i. Source Code/Flowchart Diagram (All Programs created in MPLAB or C) ii. Documentation iii. Schematic diagrams and PCB layouts of all circuits board (including the trainer boards) used in this subject (Note: in PDF format please) iv. Documentation should place it in a clear book(colored coded by section) from title page personal information sheet. FORMAT OF THE APPLICATION PROJECT DOCUMENTATION Title Page Acknowledgement Abstract Table of Contents 1. Introduction 1.1 Statement of the problem -This should introduce the general problem that the designed system addresses to. 1.2 Current State of Technology -This should include the state of the current technology and the different solutions proposed so far (based on a literature survey). The discussion should include only enough detail to show the rationale for and the problems in each leading to the specific need for the designed system. 1.3 Objectives - This should contain the following: 1.3.1 General Objective 1.3.2 Specific Objectives 1.3.3. Scope and Limitation 2. Related Theories (Body of knowledge adopted)

-This section should give the theoretical background that leads to the design of the system. This may be broken into different sub-sections for logical grouping of the topics. 2.1 Introduction - This should give the relation of the section to the design solution, as well as the interrelation between the different sections of this topic. 2.2. <theory 1> 2.3. <theory 2> . . . . 2.n <theory n-1> 2.n+1. Summary 3. (PET NAME OF THE PROJECT): The Application Project 3.1 Introduction - This part gives the relation of the section to the designed solution, as well as the interrelation between different sections of this part. 3.2 (PET NAME) The System -This should describe the top-down design of the system, with emphasis on how the proponents attempted to solve the problem. This section also includes the detailed discussion of the Systems Block Diagram and also discusses in brief the designed prototype (accompanied with sketch/diagram). 3.3 Theoretical Analysis (Design Details) - This should describe how the system solved the problem given the assumptions and limitations presented in Chapter 1, and the theories discussed in Chapter 2. 3.4 Summary 4. Performance Analysis 4.1 Introduction - This should give the major objectives of the experiments. (The minor objectives of each experiment should be included in the experimental section). There should be a description of the parameters to be measured. Also, the assumption made in the analysis should be given in detail. 4.2 Experimental (hardware and software design phase) This section should describe the experiments performed in analyzing the behavior/performance of the designed system. This should include how the required parameters are quantified, i.e., what measurable parameters are used to indicate the desired

parameter if this is not directly measurable. This should also include the basis for such an assumption. The information given should be enough that the reader can repeat the experiments for evaluation. 4.3 Results and Analysis (H/W & S/W Testing, Design Verification) This should give an overview of the results from experiments. Sample raw data shall be included to explain how there are presented. The full set of data shall be included as an appendix. This shall also contain a discussion of the information derived from the results with sample raw data to support the conclusion. 5. 4.4 Summary Conclusion - The conclusion should contain a summary of the problem, the designed system, the major results of the performance analysis, and the recommendation for further work/s.

Appendices - These should contain the raw data, program listing, flowchart diagrams, personal information sheet (with recent photo attached), technical manual/s and user manual (flyertype). The technical manual for the hardware systems shall include the detailed schematic diagram/s and PCB Layouts and technical data sheets of major components used in the design. The technical manual for the software systems shall include the user-defined procedures with a short description of what each does and how these are referenced by which routines. WORK BREAKDOWN DISTRIBUTION (for the whole group) Members name
(Alphabetically Arranged, Lastname first)

Assigned Task/Area
(H/W, S/W, Doc)

Percentage of Work Contributed (%)

1. 2. 3. 4. 5. BIBLIOGRAPHY - This section contains the references cited throughout the project documentation. The sequence may either be in the order of citing or in order of the first authors surname. SUPPORTING PICTURES (Candid shots of the group while making the project) PERSONAL INFORMATION SHEET (w/ recent photo please)