Sidebar
Corning Community College
Systems Programming
Syllabus / Course Home Page
Announcements
Welcome to CSCS2730 Systems Programming!
- (Aug 23rd) Wiki Login Problems? Check the Class Notes Wiki Page for some information.
Course Information
| Instructor: | Matthew Haas | Course Number: | CSCS2730 |
|---|---|---|---|
| Faculty E-mail: | haas@corning-cc.edu | Course Load: | 3 credit hours |
| Mailing List: | sys@lab46.corning-cc.edu | Semester: | Fall 2010 |
| Class IRC: | #sys | Public Directory: | /var/public/sysprog |
| Class Meeting: | MF 1:28pm - 2:56pm / B003 | CRN: | 75898 |
<html>
<!– ^Finals Week Meeting Day:|Monday, May 17th, 2010^Finals Week Meeting Time:|11:15am - 2:15pm| –>
</html>
Projects: Systems Programming Projects
Course Notes (Wiki): http://lab46.corning-cc.edu/notes/sysprog
Mailing List URL: http://lab46.corning-cc.edu/mailman/listinfo/sys
Resources: Systems Programming Resources
Course Description
Systems programming for portable operating system implementations. File and Device I/O, timers, process management, sockets, threads, file systems, terminals, signals, pipes, semaphores. Focus on concurrency and effective resource utilization.
(3 cr. hr.) (Fall). Prerequisites: CSCS1320, CSCS1730, or Instructor consent.
Course Objectives
Upon completion of this course, students will be able to:
- better understand file I/O for efficient data processing
- utilize capabilities built into the operating system
- write programs that interact with and spawn processes
- use pipes and sockets to communicate and share data
- demonstrate knowledge of concurrency
- design programs that handle signals
- explore efficient solutions to data- and processing- intensive problems
Referenced Books
Understanding Unix/Linux Programming: A Guide to Theory and Practice
By: Bruce Molay
Publisher: Prentice Hall
ISBN: 0-13-008396-8
Book URL: http://www.pearsonhighered.com/academic/product/0,3110,0130083968,00.html
Grading Policy
The grading policy is broken down into 3 areas: Journal, Projects, and Participation.
Journal
36%
For the duration of the course I would like for you to keep a journal which details your experiences and revelations of your journey through the course. Each week (excluding break weeks) I would like for you to contribute to your journal, so that a written account can exist to tell your individual story of the course. (Great for looking back on things, and also useful if you are meeting with me).
In some cases, I may present some more structured activities to be done in the journal. But in general, you are to use the journal to record insights from your epic journey you've embarked upon this semester. While I welcome off-topic banter, that should not be the exclusive subject matter of your entries. Please reference the Journal Initialization Tutorial for further information.
To get credit on your journal entries each week, you need to accomplish the following:
- journal entry is ready by the collection deadline (2AM on the Tuesday the following class week)
- minimum word count (300 words each week)
- entry is contained in the appropriately named wiki page (week1 for Week 1, week2 for Week 2, etc.)
- identifies and includes extrapolation of provided keywords for the week (if given)
Relate to what is going on in class- the topics, what you're doing with them, something you've realized, etc. Excessive irrelevant content (in the absence of any substantial class-related content) risks invalidating the entry.
Note that I am not interested in “English teacher approved” essays- in some courses and settings that is more important. For this course, I want you to be able to effectively convey your thoughts in words- a crucial ability that can later be applied to “proper English essays”.
You can never write too much in my class.
There will be no make-ups for missed journal entries. Have entries ready by the deadline or lose credit.
NOTE for those taking multiple courses with me: Journal content each week MUST reflect consideration from ALL courses you have with me.
Additionally, there are some journal achievements that can be unlocked:
- INTRO: You've filled out an intro section, minimum 192 words, so that it details who you are (x1)
- ALTER: You've customized the journal from the defaults; says your name, changed colors, etc. (x1)
- EXIST: The journal and all entries exist with at least minimum word count in each entry (x1)
- CREATE: You successfully created your journal in the prescribed way before given deadline (x1)
- WRITE: 3 journal entries exceed the minimum word count (x4)
In your journal I would like for you to detail your experiences in the course. Summary of experience/class notes; or statements/musings on questions like: Do you understand the material? Is it interesting? Anything not making sense? Any parallels to the real world? and general comments and thoughts.
Use the journal to allow me to see the course through your eyes.
Projects
36%
Projects constitute the portion of your grade involving activities you perform in the name of experiencing and demonstrating knowledge in this class- the means by which I will be assessing your understanding of the material through directed explorations of various topics. Such projects may be comprehensive to one another.
Two key products of performing a project are demonstration and documentation. Demonstration is presenting your finished project, that meets project specifications, to the instructor and being able to respond to any questions on any particular facet therein.
Perhaps more important than demonstration of a working project is the documentation. Documentation includes the instructions for recreation of the end product from the ground up, allowing not only the original author(s), but individuals of sufficient skill to recreate and understand important concepts through reading the prepared documentation.
I reserve the right to request, for any project as terms of acceptance of project demonstration, the recreation of an equivalently functional end result through following of accumulated project documentation. If documentation fails to produce the desired outcome, it will reflect negatively upon the project evaluation.
A list of provided projects may be given, but there might also exist opportunities for additional project ideas- such projects are subject to approval by the instructor prior to starting, and are held to the same demonstration and documentation standards as standard projects.
In some cases, depending on the situations involved, a project may be conducive for group-based collaboration. This is not the default case, but is specified on a case-by-case basis. In such scenarios, all involved group members should be identified prior to starting on the project. Additionally, ALL group members in a collaborative situation must perform fairly equivalent work output into the completion of the project. Deficient members may experience reduced success.
Participation
28%
Maintaining an ever present effort in your journey with respect to being present for class gatherings and making your presence known (both in and outside of class) is an important aspect to academic interactions.
Participation is like the “I care” component of your grade. If you care enough to learn and help enhance the experience, you will have no trouble here. If you are disruptive or are not putting forth effort, however, then it will be duly reflected.
This isn't a “kiss up to the teacher” grade. I don't want people bending over backwards to please me. I want to see people learning and asking questions and growing, not agreeing with everything I say. Sometimes I will specifically ask questions or say things for the sole purpose of getting individual perspectives.
Participation is the contribution of YOU to the overall class, in a positive and harmonious manner to the overall group :)
Submission Guidelines
The following are some guidelines to keep in mind when preparing your work for submission. Not all may always be applicable, to each class, or even each submission.
Digital is best
Technology is a wonderful thing. It facilitates many of the tasks we'd otherwise have to do manually by hand.
The intent here is to make things easy on both you and me.
So use the technology, and don't just it for the sake of using it– use it to make the task at hand easier (ie use the technology available for the course).
With that said, some additional aspects to keep in mind:
- e-mails were designed to be plain text; don't make them into web pages
- e-mails should always have an informative subject line
- if you've got non-text files to include in an e-mail, attach them to the message
- if you've got many attachments, archive & compress them, and just attach the archive
- I can not easily open Microsoft Works documents; don't give me any in that format
- Plain text is preferable over any enriched text format (RTF, WORD, WordPerfect, etc.)
If appropriate, I also will accept submissions via singing telegram, airplane banner, crop circles, creative dance, three part rock aria, etc. so long that I get to witness such creativity, and receive something which lets me look back on it later (photos, video, transcription on paper, etc.). Chances are such unique submissions will gain you favorable considerations.
Identification
Where applicable, be sure to include the following information on any submission:
- Name,
- Course and Section,
- Due Date,
- Assignment # and description,
- Short abstract describing the purpose of your program / assignment.
Presentation of this information in a clear and organized fashion will make your assignment all the easier to read. You may come up with your own format for the display of this information.
Any e-mail submissions should have an appropriate subject line. Please use subjects on all e-mails. This is also very important.
Leaving off the subject line is like sending a letter without putting a stamp on it– it causes someone extra work. And that someone would be me. So don't do it. Please please please use informative subject lines!
Paraphrasing
For any provided questions, keywords, etc.: identify each question or selection you are answering by listing or paraphrasing the original question.
Do not just give me an answer.
This is important. I mean it. You don't know how frustrating it is to get an assignment that just has the answers on it. It takes so much longer to grade.
I reserve the right to deduct points if you don't do this.
Organization
Keep your programs and assignments organized and easy to read.
Use a uniform writing style. Messy or unorganized submissions will have points deducted. Think to yourself: does it look good? Would I want to read this? Take pride in your work.
These assignments are not just for me to read and grade- you may wish to incorporate them into a portfolio for use in the future. Making an investment now could pay off later!
Timeliness
Turn in submissions on time.
Late submissions will be subject to an appropriate penalty. Circumstances vary, see the Late Policy for details.
In many cases, where possible, I do accept resubmissions.
Errors
If you encounter an error while performing some task (and the directions do not indicate you should be receiving an error), chances are you made a typo. Consult the class mailing list, class chat, ask someone, or contact me.
WARNING
Submissions containing answers based on user error will be considered incorrect.
Backups
Be sure to keep a backup copy of all assignments submitted in the event something is lost in transmission.
Important
It is your responsibility to be able to send another copy of your submission should the original be lost.
Common Sense
Use your own judgment. The world today is increasingly filled with rules and policies dictating what you can and cannot do. I am not about to go and list all the specifics and restrictions regarding assignment submission.
You are here to learn and to grow, and I want to allow you a certain amount of flexibility in that process. Spending all your time formatting an assignment to my specifications isn't my idea of learning. Incorporate these guidelines into your general style, if you miss the mark I'll let you know. But focus more on learning and understanding than worrying about dotting every 'i' or crossing every 't'. There's enough of that elsewhere in the world.
Late Policy
Sometimes, even though we try our hardest to get everything in on time, the spurious Murphy's Law will make an appearance. Your dog ate your network cable, a burst of cosmic rays damaged your RAM precisely where your work was located… the list goes on.
If something is not submitted by its respective due date, and no advance attempt has been made to communicate with me, the assignment will be invalidated of any value.
Bottom line.. if something is going to be late: let me know. It happens, just don't make a habit of it. Communication is key.
Attendance
Attendance plays an important part in one's educational journey each semester. Missing class deprives you of essential knowledge and hinders understanding towards your eventual mastering of a topic.
Because we are all here to learn (and if learning isn't a priority, I highly suggest you think about making it such), and believe it or not- learning isn't just about one person, but the entire group. So it is important to be present in order to positively contribute to the learning experience.
I also reserve the right to drop students from the course due to excessive absences.
Network Outages
In the event that a significant network or computer outage occurs on a network under CCC jurisdiction, an appropriate adjustment will be made to any applicable due dates.
If, however, an outage occurs on your end, that shouldn't necessarily be used as an excuse for missing deadlines on work submission. Everyone has a CCC student account, so work can be done while on campus. A certain amount of leniency will typically be granted, if you are usually on-time with your assignments and maintain regular communication with me.
If you experience any sort of problem connecting that does prevent the successful submittal of an assignment or assessment, I expect some notification on your part. Any error messages or diagnostic results will be useful in determining the scope of the problem and consideration regarding due dates.
Collaboration
Because this course is open resource (ie book, computer, note, etc.) I would like it generally to remain closed person. The reason for this is that the amount of resources available to you are vast, and the goal here is to discover and learn the material through individual initiative.
It IS possible to help others without giving away answers.
Respond to questions with a question, give pointers to where information might be located in legitimate sources, remind them of the usefulness of manuals, and the availability of search engines.
Individuals are allowed and expected, to assist others through the mailing list and class chat WITHOUT GIVING EXPLICIT ANSWERS, so long as it does not interfere with any other existing circumstance. If groupwork is required on anything, that attribute will be specifically stated.
Explicit copying on any class work is forbidden. If any evidence or suggestion of non-authentic work is discovered in your particular direction, you risk both my wrath as well as the possibility of disciplinary action by the school. So just play it safe and make sure your work is your own.
Topics
Although not set in stone, the following will be a rough sketch of the anticipated topics to be covered in the class this semester:
- UNIX Systems Programming
- Users, Files, and the Manual
- Directories and File Properties
- Focus on File Systems
- Connection Control
- Terminal Control and Signals
- Event-Driven Programming
- Processes and Programs
- Shell Variables and the Environment
- I/O Redirection and Pipes
- Servers and Sockets
- Connections and Protocols
- Programming with Datagrams
- Threads
- Inter Process Communication
Semester Calendar
Note that we may have some days during the semester where the regular class gatherings will not occur. These are listed in the calendar.
