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 Tuesday, May 17th from 8:00am-11:00am 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!

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

Choose a two projects 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 notes 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 polished (but obviously not procedure/process complete) documents that you or someone else could utilize to kick off the intended projects.

Making the transition from a casual user to the role of developer and/or systems administrator/engineer/architect is an important one which opens the mind to many new possibilities. Imagine yourself a year, or even a semester, ago, and reflect on your current awareness in the realms of computing.

Answer me the following:

• You're now more an expert than you were back then. What are you an expert at?
• What is amazing to you that you would never have thought you'd realize?
• The better you get at something, the more you realize there is to learn. What are some things you realize you need to learn more?
• Self-proclaimed experts that preach they know it all never do. Admitting our weaknesses enables us to grow. What are some of your knowledge “holes”, why do you think you have them, and what steps might you undertake to fill them in?

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?

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!