Lab46 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<WRAP round box>
<WRAP centeralign bigger><WRAP bigger fgred>Corning Community College</WRAP>
<WRAP muchbigger>HPC Fundamentals</WRAP> 
\\ 
End of Course Experience
</WRAP>
</WRAP>
~~TOC~~
======Rules======
Presented within will be various questions evaluating your knowledge and experience gained this semester. In places where you are able, the more you write and explain topics the better the chance you will have of receiving full credit (and alternatively, the more credit you will receive should something be incorrect).

The questions on this experience are open resource with the exception of other individuals. In that respect, it is CLOSED PERSON. This means you are not to communicate with other people (either in the class or otherwise), in real life or electronically. Use your own knowledge, use your skills, and use your ability to access the allowed resources to aid you in coming up with your well thought out answers to each question.

You are allowed, and expected, to ask me questions, so that a problem can be better clarified.

You are to do **all** questions. Submission is to be in an organized and easy to read format in a plain text file, such as in an e-mail with attachments on Lab46, sent to **wedge@lab46.corning-cc.edu** and yourself.

You have until 11:59:59pm (that's 23:59:59 in 24-hour time) Wednesday, May 18th, 2011 to complete and submit this to me.

Our scheduled finals week meeting time is **Wednesday, May 18th** from **11:15am-2:15pm** in Room **B003** at the BDC (Our regular room). Additionally, you are also welcome to come to the BDC, Room **B003** for questions/to work on projects on:

  * Tuesday, May 17th from 8am-2:15pm
  * Wednesday, May 18th from 11:15am-2:15pm

Good luck!

======0x0: Replication======
A big focus of the course was the creation of documentation as you performed the various projects- ultimately assembled on your portfolio page.

The project documentation needs to be process complete and accurate- the original author, or someone else (either in the class or another individual in the future) should be able to reference that documentation and replicate that project.

To put this to the test, choose to perform a project performed by another person in the class, and follow their documentation through to project completion.

Answer the following:

  * Who was the author, what was the project, and where is the URL to the project documentation you chose? (Does the documentation state the author, project title, etc.?)
  * Does the documentation lead to a successful and operational conclusion?
  * Is the documentation complete? (No inferred steps with respect to the project needed to be taken)
  * Is the documentation organized, easy to read any follow?
  * Is the documentation nicely formatted, utilizing wiki formatting features? (ie it is not just some huge paragraph or endless stream of bullets on a list).
  * On a scale of 0 to 11 (yes, it goes to 11) rate the documentation on the above points.
  * Provide some suggestions for improvement that would have enhanced your experience following this documentation.

======0x1: Presentation======
Take two (2) of your project documents and make them more "class ready" - ensure the document is broken up into at least the following sections (more are welcome):

  * Main heading (Title, Author-- no actual section delineation here is needed, just that it comes before everything else)
  * Objective(s) - what is the point of this project. What do we hope to accomplish by undertaking it?
  * Materials/Reading/Prerequisites - What items/ducks do you need to get in order before starting on the project?
  * Background - general overview of what is going to be accomplished (for example, if your project is about installing a web server, do a little write-up on web servers. What is it, why do we need one, how does it work, etc.)
  * Procedure - the actual steps taken to accomplish the project.
  * References - where you got informative and useful information to help you accomplish this project when you originally worked on it (from Google, other wiki documents on the Lab46 wiki, etc.)

The aim here is to make the document more presentable, and therefore more accessible to a wider audience than just you or even other members of the class (if you were looking for a HOWTO document enabling you to accomplish some task, and have it be complete and informative, that's what we're after).

======0x2: Preparation======
Choose a project you'd like to undertake, but have yet to start on, and create the beginnings of project documentation- state desired objectives, collect potential resources, discuss the concepts or theory behind what you're looking to accomplish (The background), and describe some of the first steps you think you'd take- almost as a note to yourself in the future.

The resulting documentation should be a well-organized document that contains the following sections:

  * Main heading (Title, Author-- no actual section delineation here is needed, just that it comes before everything else)
  * Objective(s) - what is the point of this project. What do we hope to accomplish by undertaking it?
  * Materials/Reading/Prerequisites - What items/ducks do you think you need to get in order before starting on the project?
  * Background - general overview of what is going to be accomplished (for example, if your project is about installing a web server, do a little write-up on web servers. What is it, why do we need one, how does it work, etc.)
  * Procedure - some initial steps you think you'll take when starting on the project (the direction you think you need to go)
  * References - any potential information you think will help you accomplish this project should you pick it up again in the future (good idea to put down stuff that you used to create the background section as well).

The end result should be a polished (but obviously not procedure/process complete) document that you or someone else could utilize to kick off the intended project.

======0x3: Your Perspective======
After an exciting and intellectually challenging run, we're arriving at the end of this semester's journey. The course as we all experienced it, unfolds in a manner pertaining in part to how you respond to concepts and topics (do we need more time, can I crank it up a couple notches, etc.) so each semester and each class is entirely different from any other- because of each of you, and all of us, working together and learning together.

So, searching deep down within your soul- balancing reason with emotion, and considering attendance and timeliness; answer me the following:

  * What grade do you feel you deserve for this course?
  * Why do you feel you deserve this mark? (Justify your answer based on your own perceived performance, not on need.)
  * How did you feel about the course?
  * Was it useful/interesting to you?
  * What was your least favorite aspect, and why?
  * What was something meaningful to you with respect to the course? Why does this stick out in your mind?
  * Any other comments or suggestions?

======Submission=====
When done, compose an e-mail to me with your responses/URLs to the various parts.

Be sure your e-mail is organized and easy to read!
Lab46 Wiki

User Tools

Site Tools

Page Tools
