Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 5

SD Elective II

<Project Name>

Group <number>
Class Group: <Group A or Group B>
Submitted: <date>

Members:
<Member name 1>
<Member name 2>
<Member name 3>
<Member name 4>
SD Elective II 2

Table of Contents:

Problem:
Plan:
Design:
Build (Hardware):
Code (Software):
Testing and Results:

Revision Table

Revision Date Section / Page Remarks

A
SD Elective II 3

Problem:
- Define the problem
- Nature of the problem
- Its impact on society or any technology / applications etc.

Plan:
- Overview of the solution
- Explain in detail how this solution can really address the problem

Design:
- Project Specifications
- Hardware specifications
- Sensor/Modules specification (If used)
- Software Specifications

Build (Hardware):
- Explain the overall concept of the design (provide a sketch/diagram if necessary)
- Explain the purpose of each component.

Code (Software):
This is the “technical manual” of the program.
- Provide an overall structure of the program.
- Explain each part of the program (subprograms, modules, classes, etc.) sufficient detail such that the
reader can understand the statements, algorithmic logic, etc.
- Do not give all the explanations in a single section; instead, divide this section into subsections for ease
of reading.

Testing and Results


- Details of how you have tested the software
- Difficulties
- Real time testing, tools used, etc
SD Elective II 4

References:
- References used
SD Elective II 5

This is how to provide the information to every portion of the documents:

Headings First Draft Final Draft


(Proposal) (with actual implementation)
Table of Contains Fill in the details like the page Update if there are some
numbers and etc. changes.
Revision Table Leave it blank Indicated the changes from
the first draft
Problem To be filled in Update if there are some
changes
Plan To be filled in Update if there are some
changes
Design To be filled in Update if there are some
changes
Build (Hardware) To be filled in Update if there are some
changes
Code (Software) Leave it blank Fill in the codes with detailed
explanation for its functions
Testing and Results Leave it blank Fill in the details of test
performed and the
corresponding result
References To be filled in Update if there are some
changes

Note: Do not include this table upon submitting your proposal and final document. You need to
remove this guideline table. This only serve as your reference and not really part of this
document.

You might also like