F17: Red Link - Revision history

Proj user5: Blanked the page

2017-09-28T06:24:14Z

Blanked the page

Proj user5 at 06:22, 28 September 2017

2017-09-28T06:22:31Z

Proj user5: Created page with "=== Grading Criteria === * How well is Software & Hardware Design described? * How well can this report be used to reproduce this project? * Code Quali..."

2017-09-28T06:20:04Z

Created page with "=== Grading Criteria === <font color="green"> * How well is Software & Hardware Design described? * How well can this report be used to reproduce this project? * Code Quali..."

New page

=== Grading Criteria ===
<font color="green">
* How well is Software & Hardware Design described?
* How well can this report be used to reproduce this project?
* Code Quality
* Overall Report Quality:
** Software Block Diagrams
** Hardware Block Diagrams
**: Schematic Quality
** Quality of technical challenges and solutions adopted.
</font>

== Meow Meow ==

== Abstract ==
This section should be a couple lines to describe what your project does.

== Objectives & Introduction ==
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

=== Team Members & Responsibilities ===
* Yaron Alexandrovich
**
* Emil Kurian
**
* Gerard Ramos
**
* Fred Sun
**

== Schedule ==
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 10/8
| Task list
| Completed? Problems Encountered?
|}

== Parts List & Cost ==
Give a simple list of the cost of your project broken down by components. Do not write long stories here.

== Design & Implementation ==
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

=== Hardware Design ===
Discuss your hardware design here. Show detailed schematics, and the interface here.

=== Hardware Interface ===
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.

=== Software Design ===
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

=== Implementation ===
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

== Testing & Technical Challenges ==
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again?
Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

=== <Bug/issue name> ===
Discuss the issue and resolution.

== Conclusion ==
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

=== Project Video ===
Upload a video of your project and post the link here.

=== Project Source Code ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== References ==
=== Acknowledgement ===
Any acknowledgement that you may wish to provide can be included here.

=== References Used ===
List any references used in project.

=== Appendix ===
You can list the references you used.

← Older revision		Revision as of 06:24, 28 September 2017
Line 1:		Line 1:
−	~~=== Grading Criteria ===~~
−	~~<font color="green">~~
−	* How well is Software & Hardware Design described?
−	* How well can this report be used to reproduce this project?
−	* Code Quality
−	* Overall Report Quality:
−	** Software Block Diagrams
−	** Hardware Block Diagrams
−	**: Schematic Quality
−	** Quality of technical challenges and solutions adopted.
−	~~</font>~~

−	~~== Meow Meow ==~~
−
−	~~== Abstract ==~~
−	~~This section should be a couple lines to describe what your project does.~~
−
−	~~== Objectives & Introduction ==~~
−	~~Show list of your objectives. This section includes the high-level details of your project. You can write about the various sensors or peripherals you used to get your project completed.~~
−
−	~~=== Team Members & Responsibilities ===~~
−	* R Nikfar
−	**
−	* Jason Tran
−	**
−	* Ahsan Uddin
−	**
−	* Yuyu Chen
−	**
−
−	~~== Schedule ==~~
−	Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
−
−	~~{\| class="wikitable"~~
−	\|-
−	~~! scope="col"\| Week#~~
−	~~! scope="col"\| Date~~
−	~~! scope="col"\| Task~~
−	~~! scope="col"\| Actual~~
−	\|-
−	~~! scope="row"\| 1~~
−	~~\| 10/8~~
−	~~\| Task list~~
−	~~\| Completed? Problems Encountered?~~
−	\|}
−
−	~~== Parts List & Cost ==~~
−	~~Give a simple list of the cost of your project broken down by components. Do not write long stories here.~~
−
−	~~== Design & Implementation ==~~
−	~~The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.~~
−
−	~~=== Hardware Design ===~~
−	~~Discuss your hardware design here. Show detailed schematics, and the interface here.~~
−
−	~~=== Hardware Interface ===~~
−	In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high-level workings rather than the inner workings of your project.
−
−	~~=== Software Design ===~~
−	Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show pseudocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
−
−	~~=== Implementation ===~~
−	This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
−
−	~~== Testing & Technical Challenges ==~~
−	~~Describe the challenges of your project. What advice would you give yourself or someone else if your project can be started from scratch again?~~
−	~~Make a smooth transition to testing section and described what it took to test your project.~~
−
−	~~Include sub-sections that list out a problem and solution, such as:~~
−
−	~~=== <Bug/issue name> ===~~
−	~~Discuss the issue and resolution.~~
−
−	~~== Conclusion ==~~
−	Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learned from this project. How has this project increased your knowledge?
−
−	~~=== Project Video ===~~
−	~~Upload a video of your project and post the link here.~~
−
−	~~=== Project Source Code ===~~
−	* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
−
−	~~== References ==~~
−	~~=== Acknowledgement ===~~
−	~~Any acknowledgement that you may wish to provide can be included here.~~
−
−	~~=== References Used ===~~
−	~~List any references used in project.~~
−
−	~~=== Appendix ===~~
−	~~You can list the references you used.~~

@@ Line 17: / Line 17: @@
 == Objectives & Introduction ==
-Show list of your objectives.  This section includes the high level details of your project.  You can write about the various sensors or peripherals you used to get your project completed.
+Show list of your objectives.  This section includes the high-level details of your project.  You can write about the various sensors or peripherals you used to get your project completed.
 === Team Members & Responsibilities ===
-*  Yaron Alexandrovich
+*  R Nikfar
 **
-*  Emil Kurian
+*  Jason Tran
 **
-*  Gerard Ramos
+*  Ahsan Uddin
 **
-*  Fred Sun
+*  Yuyu Chen
 **
@@ Line 55: / Line 55: @@
 === Hardware Interface ===
-In this section, you can describe how your hardware communicates, such as which BUSes used.  You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.
+In this section, you can describe how your hardware communicates, such as which BUSes used.  You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high-level workings rather than the inner workings of your project.
 === Software Design ===
-Show your software design.  For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level.  Do not show the details of the code.  For example, do not show exact code, but you may show psuedocode and fragments of code.  Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
+Show your software design.  For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level.  Do not show the details of the code.  For example, do not show exact code, but you may show pseudocode and fragments of code.  Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
 === Implementation ===
@@ Line 64: / Line 64: @@
 == Testing & Technical Challenges ==
-Describe the challenges of your project.  What advise would you give yourself or someone else if your project can be started from scratch again?
+Describe the challenges of your project.  What advice would you give yourself or someone else if your project can be started from scratch again?
 Make a smooth transition to testing section and described what it took to test your project.
@@ Line 73: / Line 73: @@
 == Conclusion ==
-Conclude your project here.  You can recap your testing and problems.  You should address the "so what" part here to indicate what you ultimately learnt from this project.  How has this project increased your knowledge?
+Conclude your project here.  You can recap your testing and problems.  You should address the "so what" part here to indicate what you ultimately learned from this project.  How has this project increased your knowledge?
 === Project Video ===