CS274: Computer Architecture - Number System Conversions (100 Points)
Assignment Goals
The goals of this assignment are:- To programmatically convert between numbers represented in base-2, base-10, and base-16
- To develop appropriate unit tests for functions
- To write and use a Makefile
Background Reading and References
Please refer to the following readings and examples offering templates to help get you started:- Number Systems Activity
- Makefile Tutorial by Bruce A. Maxwell
- Automate your Python project with Makefile by Anton Zhiyanov
- Check: Unit Testing in C
- Introduction to Unit Testing in Java
- A Gentle Introduction to Unit Testing in Python
-
unittest: Unit Testing Framework in Python
The Assignment
What to Do
Recall the approaches we used to convert between a decimal value and a binary value, and between binary and hexadecimal values.
In this assignment, you will write a program (or a series of programs) that:
- allow the user to input which base they would like to convert from and to (base 2, 10, and 16),
- allow the user to input a value in the base they’re converting from
- convert the value to the target base
The input value should be a string that represents the numeric value; this will facilitate your looping over each digit. If desired, you may convert it to an integer data type. However, you may not use a library to convert between the bases themselves: you should do that yourself!
You may use any of several programming languages: C, C++, Java, Python, or another language if pre-approved by the instructor. You must, however, include a Makefile that compiles and runs the program. In addition, you must provide appropriate unit tests for each of your functions.
Submission
In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:- Describe what you did, how you did it, what challenges you encountered, and how you solved them.
- Please answer any questions found throughout the narrative of this assignment.
- If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
- Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
- Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
- Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
- Using the grading specifications on this page, discuss briefly the grade you would give yourself and why. Discuss each item in the grading specification.
- Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).
Assignment Rubric
| Description | Pre-Emerging (< 50%) | Beginning (50%) | Progressing (85%) | Proficient (100%) |
|---|---|---|---|---|
| Algorithm Implementation (50%) | The algorithm fails on the test inputs due to major issues, or the program fails to compile and/or run | The algorithm fails on the test inputs due to one or more minor issues | The algorithm is implemented to solve the problem correctly according to given test inputs, but would fail if executed in a general case due to a minor issue or omission in the algorithm design or implementation, including a Makefile | A reasonable algorithm is implemented to solve the problem which correctly solves the problem according to the given test inputs, and would be reasonably expected to solve the problem in the general case |
| Test Cases (20%) | Testing was performed outside of the unit test framework, or not performed at all | Trivial test cases are provided in a unit test framework | Test cases that cover some, but not all, boundary cases and branches of the program are provided | Test cases that cover all boundary cases and branches of the program are provided |
| Code Quality and Documentation (20%) | Code commenting and structure are absent, or code structure departs significantly from best practice, and/or the code departs significantly from the style guide | Code commenting and structure is limited in ways that reduce the readability of the program, and/or there are minor departures from the style guide | Code documentation is present that re-states the explicit code definitions, and/or code is written that mostly adheres to the style guide | Code is documented at non-trivial points in a manner that enhances the readability of the program, and code is written according to the style guide |
| Writeup and Submission (10%) | An incomplete submission is provided | The program is submitted, but not according to the directions in one or more ways (for example, because it is lacking a readme writeup) | The program is submitted according to the directions with a minor omission or correction needed, and with at least superficial responses to the bolded questions throughout | The program is submitted according to the directions, including a readme writeup describing the solution, and thoughtful answers to the bolded questions throughout |
Please refer to the Style Guide for code quality examples and guidelines.