DESIGN PROJECT 1 - CPE 511

GENERAL REQUIREMENTS/GUIDELINES:
• Students who would take this subject are assumed to be ready with the Design Proposal as an application with
their technical knowledge acquired in the entire course. Writing capabilities are of course expected to each
individual.
• The class of Design Project should be divided into Groups with a MAXIMUM OF 3 MEMBERS PER GROUP
• The Group should pass a CONCEPTUAL DESIGN PROPOSAL.
• The Group will present this CONCEPTUAL DESIGN PROPOSAL must be approved by the member of the PANEL on
the last week of June.
• Upon the Instructor’s recommendation, the students can choose a TECHNICAL ADVISER for the group who will
guide them for entire remaining months of developing the PROPOSAL BOOK. Depending on the TECHNICAL
ADVISER’S availability, the group will be having an informal session with the technical adviser. The group must
secure an activity log-book for the adviser to sign during informal session and consultation.
• Parts of the FORMAL PROPOSAL should be passed not later than the deadline set by the SUBJECT
COORDINATOR.
• Late submission of such part shall still be accepted, except that; 2 points will be deducted from the Score each
day.
• The proponents of the group should have their individual designations, namely SYSTEMS ANALYST/SYSTEMS
PROGRAMMER, SYSTEMS HARDWARE/PROTOTYPE DESIGNER and RESEARCH & DOCUMENTATION
SPECIALIST.
• Format of the PROPOSAL should be strictly followed. Contents of the proposal parts should be based on these
guidelines and must also be based on the consultation with the group’s technical adviser.
• Procedures of Submission and Proposal Presentation should be strictly observed.
• In order to pass the subject, the group (complete attendance) should be able to satisfactorily defend their
Project Proposal.
• The group shall NEVER KNOW who their PANELISTS would be, not until the day of their DEFENSE SCHEDULE.
• Three days before the Defense Schedule, the group should pass 3 copies of their proposal document to the
Instructor for the PANELIST. It should be placed in a blue transparent folder.
• The members of the group should be in BUSINESS/FORMAL ATTIRE during the Proposal Presentation.
• The group should use a presentation tools (LCD or MULTIMEDIA PROJECTOR) during the presentation schedule.
• Final Grade will not be uniform per member of the group, since there will be individual examinations, and oral
exams.
• During the proper research and development stage of the Proposal Book, there will be modular sessions. The
group must keep posted on the Computer Engineering Bulletin (Dean’s Office/Faculty/Digital
Laboratory/Bulletin Boards) to attend any announced meeting/session with at least one member of the group
is present so that discussions could be relayed to the group. The group sessions with its TECHNICAL ADVISER will
also be arranged.
• For the Presentation Grading System, please refer to DESIGN PROJECT GRADING SYSTEM.
• Any Conflicts/Problems pertaining to the Group should be conveyed immediately to the Instructor/Coordinator
to resolve it.
• PROJECT CATEGORIES: PC Interfacing Systems, Microprocessor-Based Systems, PIC-Based Systems and
Combinations, FPGA/HDL, any Computer Engineering Related Projects.
• The Instructor will set the minimum requirement of the DESIGN PROJECT.
DESIGNATIONS AND FUNCTIONS:
Systems Analyst / Systems Programmer
• @ He is a leader. He must have a sharp knowledge of Analysis.
• @ He settles conflicts among the members of the Group before bringing it to the Instructor.
• @ He formulates the Overall Systems Flow. He creates the Systems Block Diagram and the Program Flow chart.
• @ He is fluent in at least any of the following programming languages that have interfacing capabilities (VB,
C/C++, Java or any High Level Language).
• @ He can trace bugs in the programs. He must be present during the planning stage of the project.
• @ He integrates the software and the hardware systems.
• @ He provides the schedule of the activities of the entire time frame and assigns them to his members. He
always initiates the group to work.
• NOTE: In every changes and enhancement of the programs to suite the applications of the project, He should
always back up his program. He should name his new filename the latest version and retain the older files.
Systems Hardware/Prototype Designer
• @ He has the technical knowledge about the digital systems. He designs the PROTOTYPE of the system.
• @ He designs and implements the circuit in accordance to the systems block diagrams and systems flow given
by the systems analyst to him.
• @ He troubleshoots and solves problems relating to hardware. His expertise, is tracing circuit bugs and low-level
programming.
• @ He is familiar with the properties and characteristics of the digital Integrated Circuits and the behavior of I/O
devices.
• @ He must be present during the planning stage of the project.
• @ He must coordinate with the systems programmer so that his program is developed in accordance to the
specifications set by the systems programmer.
Research & Documentation Specialist
• @ He must be technically knowledgeable in terms of documentation and legal issues.
• @ He caters the needs of the analyst, programmer and hardware when there is a need to research for some
technical information and prepares the legal permission letter when there is a need to visit a related plants or
companies. He keeps the scratch and blue prints of the design for documentation purposes. He keeps any
receipts and record all financial transaction involved in the developing of the project.
• @ He must have the quick access to the Information resources.
• @ He must also be present during the planning stage of the project. He is in-charged of the financial budgeting.

REVIEW, READINGS AND ASSESSMENTS

• FACTORS AFFECTING DESIGN PROPOSAL / PC INTERFACING, I/O and MEMORIES/INTERFACING TECHNIQUES
• INTERFACING IC’s CHARACTERISTICS AND TRUTH TABLE / MICROPROCESSOR BASED SYSTEMS
• MICROCONTROLLER BASED SYSTEMS / SOFTWARE ENGINEERING/SCHEDULING (GANTT CHART and PERT/CPM)
• TEAM WORK/DESIGN PROJECT DESIGNATIONS AND FUNCTIONS / PROGRAMMING (C, JAVA, ASSEMBLY)
• FLOWCHARTING / DIGITAL SYSTEMS DESIGN. DECODING TECHNIQUES
• OTHER MAJOR SUBJECTS OF COMPUTER ENGINEERING

DOCUMENTATION FORMAT
• Bond paper Size: Short
• Margin: Left 1.5”, Right 1.0”, Top 1.0”, Bottom 1.0”
• Font Face: (Book Suitable), Font Size 12,
• The Informal Proposal should be in at least 1 Bond Paper.
• Line Spacing 1.5 or Double
CRITERIA OF THE CHOICE OF PROPOSAL

1. TIME FRAME – The group should consider the allotted time to finish the project during the implementations.
2. COST – The group should foresee and arrive with the payoff of such proposal project. However, the group must
also consider the pocket’s capacity of the members in proposing a project.
3. KNOWLEDGE – The knowledge of the members of the group should also be reflected before choosing a certain
proposal.
4. MATERIALS AVAILABILITY – The group should also anticipate the availability of the materials that will be utilized
during the implementations.
5. RELEVANCE TO THE SOCIETY – The group should choose a proposal project that would be helpful to the society.
It will somehow help raise the standard of living. It should provide easiness, comfort and other benefits to the
people who will benefit such project. However, for the purpose of the course’s application, the Group can also
propose a mere technical design but it can somehow foretell its usefulness in the future if developed or
enhanced.
6. PROJECT COMPLEXITY – The group should be able to see and determine the difficulty of the project in order to
anticipate any other alternatives available. Members’ limitations should be considered.
NOTE:
1. There are two types of DESIGN PROPOSAL – The first one is a mere APPLICATION OF THE TECHNICAL
KNOWLEDGE ACQUIRED in his/her professional major Computer Engineering Subjects (TECHNICAL-
APPLICATION-BASED PROPOSAL). The other one is a Proposal that is mainly focused on its relevance and
usefulness to the society in real life (COMMUNITY-BASED).

2. There are two things to consider in the DESIGN IMPLEMENTATION – THE REALISTIC NATURE and THE
PROTOTYPE of the design. This should be internalized intensely by each individual to avoid misconception most
especially during the DEFENSE.

THE PROPOSAL HEARING

• The purpose of the Project Proposal Hearing is to determine whether both the student and the written plan are
ready to move into the operational stage.
• The committee should ascertain that:
– The topic of the investigation/project is suitable
– The student is competent to undertake the study
– The study would constitute a contribution to the profession
– The topic is manageable in relation to the student’s time
– The study would be a relevant learning experience for the student
• Time frame of the Proposal Hearing
– Presentation 10-15 minutes
– Defense 20-40 minutes
– Panel Deliberation 10 minutes
• The Proposal Hearing concludes in one of the three ways:
– Unconditional approval of the proposed project
– Approval with conditions as set by the evaluation committee
– Rejection of the propose project
THE PROPOSAL HEARING REQUIREMENTS

• Documentation (Chapters 1, 2 and 3)

• Complete Attendance
• Attire – Formal
• Support Group
• Food
• Token

FINAL PROJECT REQUIREMENTS

• The students are required to have an approved proposal.

• The students shall submit, upon the approval of their adviser, the final draft of their project at least one week
before the scheduled period of the Project Defense.
• The students must be able to join the Project Exhibit, which is scheduled one week before the Project Defense.
• The Project Defense is the final procedural step of the project. It concentrates on the study, the findings and
their interpretation.
• The schedule of the Project Defense is shown in the table.
• The oral defense allows the student to defend the way the study was conducted, the validity of the findings and
the importance if the conclusions and their implications.
• Time frame of the Project Oral Defense
• Presentation 15-20 minutes
• Defense 25-60 minutes
• Panel Deliberation 20 minutes

THE PROJECT ORAL DEFENSE

• Decision making regarding the Project Oral Defense concludes in three ways:
– Passed
– Conditional Passing with
• Minor Revision – minor revision requires the students to incorporate the recommendations of
the evaluation committee in the study.
– Re-defense is not necessary.
• Major Revision – major revision requires the students to re-examine the way how the project
was conducted and assess the validity of the results. Further experimentation, data gathering
and analysis is required.
– In extreme cases, change or modification in methodology maybe necessary if the
validity of the results presented is not satisfactory.
– Re-defense is necessary and is schedule one week after the oral defense.
– The students must be able to comply all the requirements so that a re-defense is
possible.
– There is a possibility that the students might not be able to join the graduation.
– Failed
Schedule of Design Project Activities:

Date Activity Time Group

September 9, 2019 Submission of Documents 12:00 Noon All Groups
for Propossal

September 12-13, Project Propossal 9:00 – 10:30 All Groups

2019 10:30 – 12:00
October 25, 2019 Submission of Corrected 12:00 Noon All Groups
Documents
December 2019 (2nd st
1 Preliminary Checking To be scheduled All Groups
Week)
January 2020 (3rd nd
To be scheduled All Groups
2 Preliminary Checking
Week)
Tentative: Feb 14, Project Exhibit Whole Day All Groups
2020 (College Days) (College Days)
Feb 17, 2020 Submission of Documents Whole Day All Groups
for Defense
Feb 20-21, 2020 Project Presentation Whole Day All Groups

Date Activity Time Group

July 26, 2019 Submission of 12:00 Noon All Groups
Chapter 1
August 9, 2019 Submission of 12:00 Noon All Groups
Chapter 2
August 23, 2019 Submission of 12:00 Noon All Groups
Chapter 3
September 9, 2019 Submission of Documents 12:00 Noon All Groups
for Proposal

September 12, 2019 Project Proposal Whole day Groups

September 13, 2019 Project Proposal Whole day Groups

October 25, 2019 Submission of Corrected 12:00 All Groups

Documents

GRADING SYSTEM:

• Refer to Grading sheets and Rubrics

DESIGN PROJECT FORMAT

[PROJECT TITLE in bold & capital letters]

A Design Project
Presented to the Faculty of College of Engineering
University of Cebu – Lapulapu and Mandaue
Mandaue City

In Partial Fulfilment
of the Requirements for the Degree
Bachelor of Science in Computer Engineering

By

[Complete name(s) of student(s) in bold & capital letters]

[first name]
[second name]
[others]

[Month &Year of submission]

COVER PAGE for HARD BOUND
TITLE PAGE (FRONT COVER)
APPROVAL SHEET
ABSTRACT
TABLE OF CONTENTS
LIST OF FIGURES
LIST OF TABLE/CHARTS

CHAPTER
I THE PROBLEM AND ITS SCOPE

Rationale
Theoretical Background
Statement of the Problem (or Objectives of the Study)
Significance of the Study
Research Methodology
Research Environment
Research Subjects or Respondents
Research Instrument
Research Procedure
Gathering of Data
Treatment of Data
Definition of Terms

II PRESENTATION, ANALYSIS AND INTERPRETATION OF DATA

Presentation, Analysis and Interpretation of Data

Conceptual Framework
Block Diagram / System Flowchart / Program Flowchart / Charts in SAD
Design Layouts
Prototype Design
System Schematic Diagram
Hardware Specifications
Hardware Components
Software Specifications
Software Description
Back-up Strategies (Optional)

V SUMMARY, FINDINGS, CONCLUSION AND RECOMMENDATIONS

Summary
Findings
Conclusion
Recommendations
BIBLIOGRAPHY (References)
Books
Journals
Unpublished Materials
Online Resources

APPENDICES
Appendix A Transmittal Letter
Appendix B Research Instrument
Appendix C Research Environment Map
Appendix D Gantt chart / Timetable of Activities
Appendix E Data Sheets
Appendix D Source Codes
Appendix E Curriculum Vitae
Appendix F User’s Manual
Appendix G Videos and Pictures
Appendix H Statement of Expenses