CS384: UNIX Process Creation and Management



->Courses
-->CS384
-->Paper
-->Lab 1
->Lab 2
-->Lab 3
-->Lab 4
-->Lab 5
->Electronic Submission
->Old Exams
->C++ Examples
->Software
->Tentative Schedule
->Support Forum
->Course Policies

[Courses]
[Rich][Home][Rich]
[Author]

Winter 2002-2003

Acknowledgement

This assignment was developed by Dr. Mark Sebern.

Assignment

The assignment may be found here.

Lab report (due 11:00pm, the day prior to week 4 lab)

Your report should include:

  • A discussion of how you approached the problem. This should contain a sufficient level of detail to convince your instructor that you were thinking as you worked on this assignment.
  • Sample program output.
  • A brief description of any problems you encountered or questions you have regarding the lab.
  • A description of how each team member contributed to the project, and an activity log indicating how much time each of you spent on the assignment (following the template provided in the lab1.xml template document). Please use the following categories:
    • Design
    • Coding
    • Debug (before you think it's working)
    • Test (after you think it's working)
    • Documentation
    • Other
  • Any suggestions you have for how the lab could be improved.
  • Documented source code
    Each section of code should be reviewed by a team member other than the author and should be clearly labeled with the names of the author(s) and reviewer(s). You may wish to use gensrc, a shell script which will produce an XML document that may be used as a starting point for your report. The file will include all of the source code files (provided you modify the script appropriately... edit gensrc for details on how to do this.)

As with any report you submit, correct spelling and grammar are required. In addition, your report should be submitted electronically following the Electronic submission guidelines. (You may wish to consult the sample report before submitting your report.) Be sure to keep copies of all your files, in case something gets lost. It may be wise to keep a diskette backup as well.

Your grade will depend on quality of design, clarity of code and documentation, as well as whether your program produces the correct results. If you have any questions, consult your instructor.

© 2002 Dr. Christopher C. Taylor Office: CC-27C Phone: 277-7339 Last Updated: Tue Dec 10 17:37:51 2002
I am responsible for all content posted on these pages; MSOE is welcome to share these opinions but may not want to.