haas:spring2018:unix:projects:pwn0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:spring2018:unix:projects:pwn0 [2018/03/11 15:50] – [Submission] wedge | haas:spring2018:unix:projects:pwn0 [2018/03/12 20:47] (current) – [Verification] wedge | ||
|---|---|---|---|
| Line 100: | Line 100: | ||
| ====Only specifying starting value==== | ====Only specifying starting value==== | ||
| - | In the event only the starting value is specified, assume a count of 16 (so display 16 values, starting at the starting value). Note that for binary and octal, all numbers should be displayed in a block, so if an additional place value comes into the picture, leading zeros must be visible on the preceding values. | + | In the event only the starting value is specified, assume a count of 16 (so display 16 values, starting at the starting value). |
| For example: | For example: | ||
| Line 465: | Line 465: | ||
| * if statements | * if statements | ||
| * loops | * loops | ||
| - | * at least 1 function | + | * at least 1 function |
| * your logic needs to: | * your logic needs to: | ||
| * flow (one thing leads into the next, as best as possible) | * flow (one thing leads into the next, as best as possible) | ||
| Line 476: | Line 476: | ||
| To be sure, I'll be checking to make sure you solution follows the spirit of what this project is about (that you implement functional, flowing logic utilizing the tools and concepts we've learned, in an application that helps demonstrate your comprehension). Don't try to weasel your way out of this or cut corners. This is an opportunity to further solidify your proficiency with everything. | To be sure, I'll be checking to make sure you solution follows the spirit of what this project is about (that you implement functional, flowing logic utilizing the tools and concepts we've learned, in an application that helps demonstrate your comprehension). Don't try to weasel your way out of this or cut corners. This is an opportunity to further solidify your proficiency with everything. | ||
| - | ====Output Formatting with printf(1)==== | + | =====Spirit of project===== |
| + | The spirit of the project embodies many aspects we've been focusing on throughout the semester: | ||
| + | |||
| + | * recognizing patterns to employ effective solutions in problem solving | ||
| + | * utilizing concepts and tools covered | ||
| + | * demonstrating comprehension of concepts, tools, and problems | ||
| + | * employing concepts in knowledgeable and thoughtful manner | ||
| + | * following instructions | ||
| + | * implementing to specifications | ||
| + | * utilizing creativity | ||
| + | * being able to control solution via consistent, clear, and organized presentation | ||
| + | |||
| + | Basically: I want your solution to be the result of an honest, genuine brainstorming process where you have (on your own) figured out a path to solving the problem, you have dabbled and experimented and figured things out, and you can command the concepts and tools with a fluency enabling you to pull off such a feat. Your solution should demonstrate the real learning that took place and experience gained. | ||
| + | |||
| + | Cutting corners, avoiding work, skimping on functionality, | ||
| + | |||
| + | =====Identifying shortcomings===== | ||
| + | I would also like it if you provided an inventory of what functionality is lacking or out of spec when you submit the project. The better you can describe your deviations from stated requirements, | ||
| + | |||
| + | The more fluent you are in describing your shortcomings on accomplishing the project (ie "I didn't know how to do this" is far from fluent), the better I will be able to gauge your understanding on a particular aspect. | ||
| + | |||
| + | This can be in the form of comments in your script, or even a separate file submitted at time of submission (if a file, be sure to make mention of it in your script so I can be sure to look for it). | ||
| + | =====Output Formatting with printf(1)===== | ||
| You might be wondering how you can full off some of these output formatting feats. The **echo** command, after all, is rather rudimentary. | You might be wondering how you can full off some of these output formatting feats. The **echo** command, after all, is rather rudimentary. | ||
| Line 627: | Line 649: | ||
| There you will find a file by the name of **outputlist**, | There you will find a file by the name of **outputlist**, | ||
| - | Using these files, you can check the functionality of your script in a number of operating conditions, to verify that it is indeed working as it should be. While this isn't likely to cover the full spectrum of possibilities, | + | Using these files, you can check the functionality of your script in a number of operating conditions, to verify that it is indeed working as it should be. While this isn't likely to cover the full spectrum of possibilities, |
| =====Submission===== | =====Submission===== | ||
| Line 647: | Line 669: | ||
| < | < | ||
| - | 78:usf0:final tally of results (78/78) | + | 78:pwn0:final tally of results (78/78) |
| - | *:usf0:usf0.sh submitted with submit tool [3/3] | + | *:pwn0:pwn0.sh on help displays informative usage and exits [4/4] |
| - | *:usf0:usf0.sh has a shabang invoking bash [3/3] | + | *:pwn0:pwn0.sh effectively utilizes variables in operations |
| - | *:usf0:usf0.sh runs without error [6/6] | + | *:pwn0:pwn0.sh effectively utilizes command expansions |
| - | *:usf0:usf0.sh with no arguments | + | *:pwn0:pwn0.sh effectively utilizes regular expressions [4/4] |
| - | *:usf0:usf0.sh is commented explaining implementation | + | *: |
| - | *:usf0:table heading and separators conform to project specifications | + | *: |
| - | *:usf0: | + | *: |
| - | *:usf0:binary column is correct | + | *: |
| - | *:usf0:octal column is correct and formatted to specifications | + | *: |
| - | *:usf0:decimal column is correct and formatted to specifications | + | *:pwn0:pwn0.sh accurately displays values in proper alignment |
| - | *:usf0:hexadecimal column is correct and formatted to specifications | + | *:pwn0:pwn0.sh accurately displays values in requested bases [4/4] |
| - | *:usf0:starting value is properly | + | *:pwn0:pwn0.sh accurately displays |
| - | *:usf0:ending value is properly checked for and verified | + | *:pwn0:pwn0.sh range logic flexibly works forward |
| - | *:usf0:signed option | + | *:pwn0:pwn0.sh iterates as appropriate in given scenarios |
| + | *:pwn0:pwn0.sh includes additional bases as requested | ||
| + | *:pwn0:pwn0.sh omits specified bases as requested | ||
| + | *:pwn0:pwn0.sh | ||
| + | *:pwn0:pwn0.sh operates according to specifications | ||
| + | *:pwn0:pwn0.sh logic is organized | ||
| </ | </ | ||
| + | |||
| + | 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 | ||
haas/spring2018/unix/projects/pwn0.1520783401.txt.gz · Last modified: 2018/03/11 15:50 by wedge
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
