Sidebar
Table of Contents
Corning Community College
CSCS2650 Computer Organization
PROJECT: Building The Thing (BTT0)
OBJECTIVE
Obtain the latest stable release of Vircon32, in source code form, and build it and the associated DevTools in your development system. Collaboratively document the build process.
EDIT
You will want to go here to edit and fill in the various sections of the document:
BTT0 documentation
Resources
URLs
API
Vircon32
Obtain source of latest stable release of Vircon32 DevTools
environment configuration
Obtain source of latest stable release of Vircon32 emulator
URL
environment configuration
Hello World
Bootstrap a fairly simple “Hello, World” example, modified sufficiently from any provided tutorial or demo code.
This is a link to the provided tutorials on the Vircon Github page: https://github.com/vircon32/ConsoleSoftware/tree/main/Tutorials/RobotGame
Indicate some potential changes/functions used here.
Some potential changes/functions could be:
- Changing the position of the text( making it appear in the bottom right of the screen )
- Changing the color of the text
- Changing what the text says ( and / or make it a different language )
- Changing the background color to one of the provided colors( make it green )
- Implementing your own background( make it Jesse from Breaking Bad )
- Making your own font( Turn a tree into the alphabet )
- Adding sounds( like it saying “Mr.Worldwide” ) when booting up the demo
Cartridge Build Scripts
In the tutorials and demos there are corresponding build scripts that will take all the code and related resources, and run the appropriate development tools to create a Vircon32 cartridge file.
Part of your task is to author your own custom build script. Do not just use an existing script, and do not just lightly modify the provided scripts: craft your own, with descriptive comments, that suit your individual effort.
SUBMISSION
To be successful in this project, the following criteria (or their equivalent) must be met:
- Project must be submit on time, by the deadline.
- Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline.
- Executed programs must display in a manner similar to provided output
- output formatted, where applicable, must match that of project requirements
- Processing must be correct based on input given and output requested
- Output, if applicable, must be correct based on values input
- Code must be nicely and consistently indented
- Code must be consistently written, to strive for readability from having a consistent style throughout
- Code must be commented
- Any “to be implemented” comments MUST be removed
- these “to be implemented” comments, if still present at evaluation time, will result in points being deducted.
- Sufficient comments explaining the point of provided logic MUST be present
- No global variables (without instructor approval), no goto statements, no calling of main()!
- Track/version the source code in your lab46 semester repository
- Submit a copy of your source code to me using the submit tool by the deadline.
Submit Tool Usage
Let's say you have completed work on the project, and are ready to submit, you would do the following:
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
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.
RUBRIC
I'll be evaluating the project based on the following criteria:
52:btt0:final tally of results (52/52) *:btt0:submitted modified demo code for project by duedate [13/13] *:btt0:submitted original build scripts and cartridge [13/13] *:btt0:contributed to project documentation [13/13] *:btt0:committed project related changes to semester repo [13/13]
Pertaining to the collaborative authoring of project documentation
- each class member is to participate in the contribution of relevant information and formatting of the documentation
- minimal member contributions consist of:
- near the class average edits (a value of at least four productive edits)
- near the average class content change average (a value of at least 1024 bytes (absolute value of data content change))
- no zero-sum commits (adding in one commit then later removing in its entirety for the sake of satisfying edit requirements)
- adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
- content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
- no contributions, co-efficient is 0.50
- less than minimum contributions is 0.75
- met minimum contribution threshold is 1.00
Additionally
- Solutions not abiding by spirit of project will be subject to a 50% 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 or otherwise maintaining consistency in code style and presentation 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
