Practivistas India/Page template: Difference between revisions

Revision as of 09:13, 26 July 2018

Abstract

Short abstract describing the project from background to conclusion. This should be about a paragraph long and cover the main topic of each of the sections from start to finish.

Background

Describe the background of the project. Make sure to cover who, what, why, when and where. This is not the problem statement. It is the background that readers should understand before the problem. Remember that the reader does not know anything about the project, except what you covered in the abstract above.

Empathy

Describe your various processes for collecting information. Summarize the results. Include some pictures. Include some specific demonstrative anecdotes.

Interviews

Summarize the various interviews and interview processes that you utilized.

Community meetings

Summarize the various community meetings and and meeting processes that you utilized.

Observations

Summarize the various observations and and observations processes that you utilized. Feel free to add or subtract subheadings under empathy as needed.

Literature Review

I think we might skip this just this time... feel free to wait until I arrive to complete the literature review subsection. Introduce the literature review briefly and then use heading and subheadings for topics. This should focus on information… NO PLAGIARISM! ^[1] Copy and paste from this Practivistas India/literature review template.

Definition

Problem statement

Start your project objective statement in the format, "The objective of this project is to..." Feel free to include specification and considerations here, or make subsections for them.

Criteria

Include a brief intro to the criteria and then include a table with constraints and weights (0-10 highest). Edit the code below to make your table.

Criteria	Constraints	Weight (0-10)
Criterion 1	The constraint specifically on criterion 1	The weight for the criterion
e.g. cost	e.g. must cost less that $10 USD per year.	e.g. 9
Criterion 3	The constraint specifically on criterion 3	The weight for the criterion
Criterion 4	The constraint specifically on criterion 4	The weight for the criterion
Criterion 5	The constraint specifically on criterion 5	The weight for the criterion

Ideation

Describe your ideation process. Include some images of your process, and include community ideation as well. You do not need photos of everything. Feel free to describe in words, and summarize/generalize repetitive processes.

Prototyping

Describe your various processes for prototyping for function and desire. You will need to make some executive decisions on what to include and what not to include. It is important that the major prototyping tracks are described, including the ones that ended in 'failure'.

Make subsections for each of the prototypes

Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.

Describe the results of each of the prototypes.

Make subsections for each of the prototypes

Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.

Describe the results of each of the prototypes.

Make subsections for each of the prototypes

Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.

Describe the results of each of the prototypes.

Tests

Describe testing results or culminations events such as a fair. You may need to make multiple subsections here using the three equal signs on either side of the subsection name. This will include lots of photos, which may be in gallery format or using the image code and switching between left and right orientations.

Timeline

Introduce the timeline and include a table of the timeline. Briefly describe what you did each day. Alternatively, this could be a link to a google spreadsheet as long as it is one that will not go away (i.e. it should probably be shared via Meenal or Lonny.

Conclusion

Describe your tangible findings.

Instructions

This is how to make, use and/or maintain it. The step by step how to template {{How to}} is most likely best for this part as shown below:

File:Bpack bike trailer - demo 1.jpg

How to Do Something

Troubleshooting

This is only how to troubleshoot basic operation. For complex issues, the solution might just say contact ________. In addition, this might not be relevant to your project... if that is the case, just delete this section. It should be a table in this format:

Problem	Suggestion
Example issue	Example solution or suggestion
Does not turn on	Make sure it is plugged in
Another issue	Et cetera

Discussion

Lessons learned

Next steps

Discuss any next steps for the project as it goes on into the future.

Team

Introduce team and semester in the following format:

Lonny Grafman
for each team member.

References

Template:Reflist

Make sure to include other relevant categories at the bottom, e.g. [[Category:Rainater]], [[Category:Upcycling]], etc.

↑ http://www.humboldt.edu/learning/handouts/plagiarism_guide.pdf

[1] ttp://www.humboldt.edu/learning/handouts/plagiarism_guide.pdf

[1]

@@ Line 7: / Line 7: @@
 Describe the background of the project. Make sure to cover who, what, why, when and where. This is not the problem statement. It is the background that readers should understand before the problem. Remember that the reader does not know anything about the project, except what you covered in the abstract above.
-==Problem statement==
+==Empathy==
+Describe your various processes for collecting information. Summarize the results. Include some pictures. Include some specific demonstrative anecdotes.
+===Interviews===
+Summarize the various interviews and interview processes that you utilized.
+===Community meetings===
+Summarize the various community meetings and and meeting processes that you utilized.
+===Observations===
+Summarize the various observations and and observations processes that you utilized. Feel free to add or subtract subheadings under empathy as needed.
+=== Literature Review ===
+I think we might skip this just this time... feel free to wait until I arrive to complete the literature review subsection. Introduce the literature review briefly and then use heading and subheadings for topics.  This should focus on information… NO PLAGIARISM! <ref>http://www.humboldt.edu/learning/handouts/plagiarism_guide.pdf</ref> Copy and paste from this [[Practivistas India/literature review template]].
+==Definition==
+===Problem statement===
 Start your project objective statement in the format, "The objective of this project is to..." Feel free to include specification and considerations here, or make subsections for them.
 ===Criteria===
-Include a brief intro to the criteria and then include a table with constraints and weights (0-10 highest). Feel free to use the code from examples, such as [[CCAT pedal powered TV#Evaluation Criteria]].
+Include a brief intro to the criteria and then include a table with constraints and weights (0-10 highest). Edit the code below to make your table.
 {| class="wikitable sortable"
 |-
@@ Line 39: / Line 56: @@
 |}
-== Literature Review ==
+== Ideation ==
-Introduce the literature review briefly and then use heading and subheadings for topics.  This should focus on information… NO PLAGIARISM! <ref>http://www.humboldt.edu/learning/handouts/plagiarism_guide.pdf</ref> Copy and paste from this [[Practivistas India/literature review template]].
+Describe your ideation process. Include some images of your process, and include community ideation as well. You do not need photos of everything. Feel free to describe in words, and summarize/generalize repetitive processes.
-Grading criteria for Literature Review:
+== Prototyping ==
-* Formatting +1
+Describe your various processes for prototyping for function and desire. You will need to make some executive decisions on what to include and what not to include. It is important that the major prototyping tracks are described, including the ones that ended in 'failure'.
-* Spelling, grammar, etc. (even when this is not explicitly stated as a criteria, it is expected) +2
-* Credibility (at least 1 book, 1 peer reviewed journal article, and many credible web references per student) +3
-* Thoroughness and relevance (at least 3 very project relevant topics per student) +3
-** Remember engineering 215 students must use technical writing
-* Extra (e.g. amazing sources, beautiful writing, above and beyond topic coverage, etc.) +1
-==Construction==
+===Make subsections for each of the prototypes===
-Very complete description of how final project is made. This large section should have lots of pictures. Please consider making a timeline in addition or instead. Use the [[Help:Images#Galleries]] and probably [[Template:How_to]] (e.g. [[Barrel O' Fun Worm Bin Instructions]]).
+Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.
+{{gallery
+|Image:IMAGENAME.JPG|Brief description of prototype step
+|Image:IMAGENAME.JPG|Brief description of prototype step
+|Image:IMAGENAME.JPG|Brief description of prototype step
+|Image:IMAGENAME.JPG|Brief description of prototype step
+}}
+Describe the results of each of the prototypes.
-===Timeline===
+===Make subsections for each of the prototypes===
-Introduce the timeline and include a table of the timeline.
+Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.
+{{gallery
+|Image:IMAGENAME.JPG|Brief description of prototype step
+|Image:IMAGENAME.JPG|Brief description of prototype step
+|Image:IMAGENAME.JPG|Brief description of prototype step
+|Image:IMAGENAME.JPG|Brief description of prototype step
+}}
+Describe the results of each of the prototypes.
-Grading criteria for timeline:
+===Make subsections for each of the prototypes===
-* Spelling and grammar +2
+Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.
-* Completeness of timeline +4
+{{gallery
-* Table formatting +1
+|Image:IMAGENAME.JPG|Brief description of prototype step
-* Timeline introduced +2
+|Image:IMAGENAME.JPG|Brief description of prototype step
-* Separate columns for proposed and actual completion date. +1
+|Image:IMAGENAME.JPG|Brief description of prototype step
+|Image:IMAGENAME.JPG|Brief description of prototype step
+}}
+Describe the results of each of the prototypes.
-===Costs===
+==Tests==
-Description of costs, donations, the fact that this is just proposed, etc.
+Describe testing results or culminations events such as a fair. You may need to make multiple subsections here using the three equal signs on either side of the subsection name. This will include lots of photos, which may be in gallery format or using the image code and switching between left and right orientations.
-See http://www.appropedia.org/Help:Table_examples#Cost_Table for a very nice looking table format.
-Grading criteria for costs:
+==Timeline==
-* Formatting (should look good, see http://www.appropedia.org/Help:Table_examples#Cost_Table formatting) +2
+Introduce the timeline and include a table of the timeline. Briefly describe what you did each day. Alternatively, this could be a link to a google spreadsheet as long as it is one that will not go away (i.e. it should probably be shared via Meenal or Lonny.
-* Thoroughness and up-to-dateness of budget (should display necessary components, including donations, have an introduction, etc)  +4
-* Mathematical accuracy +3
-* Extra (sortable, etc) +1
-== Operation ==
+==Conclusion==
-This is how to operate. It should have a brief introduction and very useful images with labels. Also it may work best for your project to use the step by step how to template {{Tl|How to}}. See [[#Troubleshooting]] for an example.
+Describe your tangible findings.
-=== Maintenance ===
-Introduce this maintenance section.
-=== Schedule ===
-This is when to maintain what.
-;Daily
-*A daily task
-*A daily task
-;Weekly
-*a weekly task
-*a weekly task
-;Monthly
-*a monthly task
-*a monthly task
-;Yearly
-*a yearly task
-*a yearly task
-;Every __ years
-*task
-*task
 === Instructions ===
-This is how to use and maintain it. The step by step how to template {{Tl|How to}} is most likely best for this part.
+This is how to make, use and/or maintain it. The step by step how to template {{Tl|How to}} is most likely best for this part as shown below:
 {{How to
@@ Line 110: / Line 109: @@
   |File:Aleiha dish.jpg |Aleiha's parabolic solar cooker |2 |Do something really complicated but made simple, etc.
 }}
-==Conclusion==
-===Testing results===
-Describe the testing results.
-===Discussion===
-Discuss the testing results.
-===Lessons learned===
-Discuss lessons were learned during this project and what you would do different next time.
-===Next steps===
-Discuss any next steps for the project as it goes on into the future.
 === Troubleshooting ===
-This is only how to troubleshoot basic operation. For complex issues, the solution might just say contact ________. It should be a table in this format:
+This is only how to troubleshoot basic operation. For complex issues, the solution might just say contact ________. In addition, this might not be relevant to your project... if that is the case, just delete this section. It should be a table in this format:
 {| class="wikitable"
 |-
@@ Line 138: / Line 126: @@
 | Et cetera
 |}
+==Discussion==
+===Lessons learned===
+==Next steps==
+Discuss any next steps for the project as it goes on into the future.
 ==Team==
@@ Line 143: / Line 138: @@
 *[[User:Lonny|Lonny Grafman]]
 *for each team member.
-Grading criteria for the remaining sections:
-*Grammar and spelling +1
-*Formatting +1
-*Depth, breadth and accuracy of content +7
-*Project documentation's potential for impact (e.g. reproduction) +1
 ==References==