1,885
edits
Changes
no edit summary
== Week 1 ==
=== Tuesday Thursday (Jan 7Sep 4) ===
* Introduction to the Problem
** Most software is written in a '''high-level language''' which can be compiled into [[Machine Language|machine code]] for a specific architecture. However, there is a lot of existing code that contains some architecture-specific code fragments written in [[Assembly Language]](or, in some cases, machine-specific high-level code).
** Reasons for writing code in Assembly Langauge include:
*** Performance
** For more course information, refer to the SPO600 Weekly Schedule (this page), the [http://www.senecacollege.ca/ssos/findWithoutSemester/spo600/sict Course Outline], and [[SPO600 Course Policies]].
=== Friday (Jan 10) Week 1 Deliverables === # [[SPO600 Communication Tools|Set up a blog and add it to Planet CDOT]].# Add yourself to the [[Winter 2014 SPO600 Participants]] page (leave the projects columns blank).# Sign and return the [[Open Source Professional Option Student Agreement]].
=== Tuesday (Sep 9) ===
{{Admon/tip|Bring Your Laptop|Classes are held in a Active Learning Classroom. If you have a laptop or other device with a VGA or HDMI output (such as a smartphone!) please feel free to bring it.}}
* Discussion of how open source communities work
* [[SPO600 Code Review Lab]]
* Start thinking about how you want to set up your [[SPO600 Software]]
=== Week 1 Deliverables Thursday (Sep 11) ===* [[Computer Architecture]] (see also the [[:Category:Computer Architecture|Computer Architecture Category]])
# Blog your conclusion to the [[SPO600 Code Review Lab]].
<!--
==Carried Forward = Tuesday (Jan 14) ===* [[Computer Architecture]] (see also the [[:Category:Computer Architecture|Computer Architecture Category]])
=== Friday (Jan 17) ===
* [[SPO600 Compiled C Lab]]
=== Week 2 Deliverables ===
* Blog your conclusion to the [[SPO600 Compiled C Lab]]
== Week 3 ==