Differences

This shows you the differences between two versions of the page.

--- haas:spring2021:sysprog:projects:sppx [2021/01/28 13:08] – [Task] wedge
+++ haas:spring2021:sysprog:projects:sppx [2021/01/28 13:24] (current) – external edit 127.0.0.1
@@ Line 15: / Line 15: @@
   * discussing the chapter (in the class discord)
   * experimenting/playing with the content in your own code
+  * identifying a UNIX tool or program you'd like to implement, making use of pertinent concepts (announce this in discord; where possible, I'd like each person to do a DIFFERENT thing)
   * implementing some UNIX tool or program that incorporates content covered in the given chapter (and where applicable, builds upon previous chapters). While not exclusively limited to programming problems at the end of each chapter, they are a good starting point (clear with me any deviations from that pattern).
+  * code should include statement of limitations (what functionality does your code implement, what, especially compared to standard system tools, does it not implement)
+  * no compiler notes, warnings, syntax errors, logical errors, or runtime errors (if there are compiler flags to issue, they should be clearly documented in the code/utilized in Makefile)
+  * if you are implementing a UNIX tool (even if with only a subset of functionality), if it outputs in a certain way, or takes input in a certain way (as the core value of the tool), your implementation should, as best as possible, seek to conform with that structure of content.
+The overall aim is to enable you to challenge yourself, explore areas and concepts you are not familiar with, and grow as a programmer and problem solver. I don't want to see you just doing things the way you are familiar with (simply because you've always done them that way).
 The outline of semester progress:
@@ Line 35: / Line 41: @@
 <code>
 TOTAL:sppX:final tally of results (TOTAL/TOTAL)
-*:sppX:LATE penalty (3 days) [-ALL]
+*:sppX:read indicated chapter in book [PTS/PTS]
-*:sppX:post picture of prototype to #desig discord channel [6/6]
+*:sppX:asked, responded, worked through any questions [PTS/PTS]
-*:sppX:post picture to #desig by Sunday before deadline [1/1]
+*:sppX:reveal of interesting insight, knowledge gained [PTS/PTS]
-*:sppX:grabit the code on lab46 by Sunday before deadline [1/1]
+*:sppX:discussion regarding chapter content, library, system [PTS/PTS]
-*:sppX:code is pushed to lab46 repository [6/6]
+*:sppX:experimentation, playing reporting insights gained [PTS/PTS]
-*:sppX:no negative compiler messages for program [6/6]
+*:sppX:selection of UNIX tool or program to implement [PTS/PTS]
-*:sppX:proper output formatting per specifications [6/6]
+*:sppX:implementation of pertinent UNIX tool or program [PTS/PTS]
+*:sppX:statement of limitations in code [PTS/PTS]
+*:sppX:no warnings, compiler notes in code [PTS/PTS]
+*:sppX:no syntax errors in code [PTS/PTS]
+*:sppX:no logical errors in code [PTS/PTS]
+*:sppX:no runtime errors in code [PTS/PTS]
+*:sppX:duplicating similarly structured content in code [PTS/PTS]
 </code>
+Additionally:
+  * Solutions not abiding by spirit of project will be subject to a 25% overall deduction
+  * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
+  * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction
+  * Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools