User Tools

Site Tools


2014:think_comparch

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
2014:think_comparch [2014/12/17 13:15]
skumarasena
2014:think_comparch [2014/12/18 16:58] (current)
skumarasena [What did you do?]
Line 6: Line 6:
  
 We designed our project to be readable from start to finish, but with standalone sections. The sections grow in complexity and build upon each other. This allows people to either read the entire guide, or use it as a reference manual to look up specific sections on an as-needed basis. Our explanations also include working sample code that a reader could incorporate into his/her own code and expand on. Examples were designed to be simple, with the intention of making it easier for people to generalize. We designed our project to be readable from start to finish, but with standalone sections. The sections grow in complexity and build upon each other. This allows people to either read the entire guide, or use it as a reference manual to look up specific sections on an as-needed basis. Our explanations also include working sample code that a reader could incorporate into his/her own code and expand on. Examples were designed to be simple, with the intention of making it easier for people to generalize.
 +
 +
 +The link to the public ShareLatex document: https://​www.sharelatex.com/​project/​54934cbbe2d91b2f78ae0fa5
  
 ===== Why did you do it?===== ===== Why did you do it?=====
Line 18: Line 21:
  
 =====How can someone else build on it?===== =====How can someone else build on it?=====
-Someone else could expand this guide to involve other topics in CompArch. Some of us felt confused by the timing lecture on latches and flip-flops. A section that outlines some examples of when to use different latches and when to use them would be helpful. Another nice feature to add to our guide would be exercises for people to practice different skills and concepts with. Although our guide includes code examples and helpful explanations,​ we don’t provide many opportunities for the reader to check his/her understanding of each concept. Students should get practice from homework and labs assigned throughout the semester, but if there is a concept a student finds confusing, it could be helpful for him/her to be able to do a couple of practice exercises. All the materials for continuing the project (the LaTeX files, all images, and all code examples) can be found at https://​github.com/​skumarasena/​ThinkCompArch. The .pdf document can be found {{2014:​Think_CompArch.pdf | here.}}+Someone else could expand this guide to involve other topics in CompArch. Some of us felt confused by the timing lecture on latches and flip-flops. A section that outlines some examples of when to use different latches and when to use them would be helpful. Another nice feature to add to our guide would be exercises for people to practice different skills and concepts with. Although our guide includes code examples and helpful explanations,​ we don’t provide many opportunities for the reader to check his/her understanding of each concept. Students should get practice from homework and labs assigned throughout the semester, but if there is a concept a student finds confusing, it could be helpful for him/her to be able to do a couple of practice exercises. All the materials for continuing the project (the LaTeX files, all images, and all code examples) can be found at https://​github.com/​skumarasena/​ThinkCompArch. The .pdf document can be found {{2014:​Think_CompArch.pdf | here.}} ​Download this PDF if you want to be able to use the internal links -- this will be very helpful because this document is pretty big.
  
 ====Difficulties==== ====Difficulties====
2014/think_comparch.1418840157.txt.gz · Last modified: 2014/12/17 13:15 by skumarasena