Difference between revisions of "S16: Sprinkler"

From Embedded Systems Learning Academy
Jump to: navigation, search
(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...")
 
(→‎Schedule)
Line 30: Line 30:
  
 
== Schedule ==
 
== 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.
+
The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
 
! scope="col"| Week#
 
! scope="col"| Week#
−
! scope="col"| Date
+
! scope="col"| Start Date
 +
! scope="col"| End Date
 
! scope="col"| Task
 
! scope="col"| Task
−
! scope="col"| Actual
+
! scope="col"| Status
 +
! scope="col"| Completion Date
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
| 10/8
+
| 04/03/2016
−
| Task list
+
| 04/09/2016
−
| Completed?  Problems Encountered?
+
| Project Idea confirm, ordering project parts
−
|}
+
| In process
 +
| 04/11/2016
 +
|-
 +
! scope="row"| 2
 +
| 04/10/2016
 +
| 04/16/2016
 +
| Begin conceptual design of code and schematic
 +
| In process
 +
| 04/16/2016
 +
|-
 +
! scope="row"| 3
 +
| 04/17/2016
 +
| 04/23/2016
 +
| Work on designing codes for basic sprinkler system ans set up physical sprinkler system.
 +
| In process
 +
| 04/23/2016
 +
|-
 +
! scope="row"| 4
 +
| 04/24/2016
 +
| 04/30/2016
 +
| Enhance sprinkler system codes to work with internet, refine the physical sprinkler system.
 +
| In process
 +
| 04/30/2016
 +
|-
 +
! scope="row"| 5
 +
| 05/01/2016
 +
| 05/07/2016
 +
| Develop a symbol web app to view information about the sprinkler system.
 +
| In process
 +
| 05/07/2016
 +
|-
 +
! scope="row"| 6
 +
| 05/08/2016
 +
| 05/14/2016
 +
| Debug and refine project and demo.
 +
| In process
 +
| 05/14/2016
 +
|-
  
 
== Parts List & Cost ==
 
== Parts List & Cost ==

Revision as of 17:35, 6 April 2016

Grading Criteria

  • 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.

Project Title

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

The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

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:

My Issue #1

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

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.

Week# Start Date End Date Task Status Completion Date
1 04/03/2016 04/09/2016 Project Idea confirm, ordering project parts In process 04/11/2016
2 04/10/2016 04/16/2016 Begin conceptual design of code and schematic In process 04/16/2016
3 04/17/2016 04/23/2016 Work on designing codes for basic sprinkler system ans set up physical sprinkler system. In process 04/23/2016
4 04/24/2016 04/30/2016 Enhance sprinkler system codes to work with internet, refine the physical sprinkler system. In process 04/30/2016
5 05/01/2016 05/07/2016 Develop a symbol web app to view information about the sprinkler system. In process 05/07/2016
6 05/08/2016 05/14/2016 Debug and refine project and demo. In process 05/14/2016
Retrieved from "http://socialledge.com/sjsu/index.php?title=S16:_Sprinkler&oldid=23112"