User Tools

Site Tools


Sidebar

projects

spi0 (due 20180117)
wcp1 (due 20180117)
wcp2 (due 20180124)
psd0 (due 20180131)
wut0 (due 20180131)
wcp3 (due 20180131)
wut1 (due 20180207)
wcp4 (due 20180207)
wut2 (due 20180214)
wcp5 (due 20180214)
psd1 (due 20180228)
wut3 (BONUS, due 20180228)
wcp6 (due 20180228)
psd2 (due 20180314)
fml0 (due 20180418)
haas:spring2018:sysprog:projects:spi0

Corning Community College

CSCS2730 Systems Programming

Project: SPI0

Errata

This section will document any updates applied to the project since original release:

  • revision #: <description> (DATESTAMP)

Objective

In this project, we get started with some course initialization activities.

Project Overview

Course Homepage

You're reading this, so you've likely already found your way to the course homepage. It consists of the syllabus plus additional course resources.

Please familiarize yourself with it, bookmarking important resources as appropriate, so that you can refer back when needed.

I'd recommend knowing how to get to the projects page (where you found the link for this project), as new content will be posted there.

Syllabus

Be sure to read through and over the syllabus, ensuring there are no questions on the material and organization of the course.

Journal Intro

Familiarize yourself with your Journal, and once there:

  • customize it (title/subtitle)
  • add an introduction
  • create your first week content

NOTE: Week 1 journal entry will be due before Thursday of week 1, the same as the remainder of the intro Journal content.

Mailing List

There is a class mailing list set up for use with this class (sysprog@lab46.corning-cc.edu).

We will use this for class discussions (along with irc, the notes wiki page, your Journal, etc.) and to disseminate announcements and other information.

As the mailing list web pages are currently inaccessible (my end, somewhat intentional), you will need to submit to me a preferred e-mail address with which I will subscribe to the class mailing list.

You will do so via submitted a text file (name info.text) when you submit this project.

Your e-mail address should be identified in info.text as follows:

e-mail: yourname@domain.tld

I will specifically look for the lead-in “e-mail: ” to identify your submitted e-mail address.

You can use any valid e-mail address (gmail, campus, lab46, other).. I merely emphasize that it be something you check fairly regularly.

Class Chat (IRC)

Using the tutorial, set up a screen session and join the #csci channel on irc. This has proven useful for more interactive (debugging!) conversations.

Lab46 Shell

Hopefully for none of you, this will not be your first experience in the LAIR and/or logging onto Lab46.

As such, please ensure you can still log into the pods and lab46, from both the LAIR and from outside (especially home, or wherever you may find yourself regularly doing classwork outside of class).

If you have any issues (such as forgetting your password), please contact me to get it resolved.

Personal/Per-User Lab46 Mercurial Repository

NOTE: If you have already done this in a prior semester, you do NOT need to do it again.

To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your Lab46 mercurial repository.

This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong.

Like the Journal, I will be looking for a minimal amount of repository-related activity PER WEEK.

Book/Reading

For those who have had me in past courses, you know I've never been a fan of the textbook approach to undertaking a topic. For one, it tends to narrow the dynamic nature of the class.

But generally: I find most textbooks suck.

That is not the case for this class! There is an absolutely WONDERFUL book, that even has programming questions in it that I find most worthy of undertaking. And THAT is the book listed for this course.

I am intending for us all to read through and utilize the programming exercises in this book, to complement our larger class projects.

Submission Criteria

To be successful in this project, the following criteria must be met:

  • Project must be submit on time, by the posted deadline to be eligible for full credit.
    • Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline.
    • Early submissions can earn 1 bonus point per day in advance of the posted due date.
  • Track/version appropriate files in your repository
  • Create and submit a text file called info.text that contains the following information:
    • preferred name/nickname (prefixed with “name: ”)
    • preferred e-mail address (prefixed with “e-mail: ”)
    • irc nick used in class chat (your username if unchanged, and prefixed with “irc: ”)
    • other information I should know (if any).

Submission

To submit this project to me, use the submit tool, run the following command at your lab46 prompt:

$ submit sysprog spi0 info.text
Submitting sysprog project "spi0":
    -> info.text(OK)

SUCCESSFULLY SUBMITTED

You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.

I'll be evaluating the project based on the following criteria:

13:spi0:final tally of results (13/13)
*:spi0:submitted project successfully [1/1]
*:spi0:customized journal title [1/1]
*:spi0:customized journal intro [1/1]
*:spi0:provided e-mail address for class mailing list [2/2]
*:spi0:joined class irc chat [2/2]
*:spi0:submitted info.text file [2/2]
*:spi0:provided requested information in info.text [1/1]
*:spi0:cloned lab46 mercurial repository into ~/src [1/1]
*:spi0:committed and pushed populated .hgignore file [1/1]
*:spi0:configured hgrc file [1/1]

NOTE: Depending on the point values of other projects, I may choose to scale the value of this project as appropriate.

haas/spring2018/sysprog/projects/spi0.txt · Last modified: 2018/01/15 20:27 by wedge