Simple calculator: Difference between revisions

From Computer Science Wiki
(Created page with "right|frame|This a problem set for you to work through <ref>http://www.flaticon.com/</ref> This is a problem set. Some of these are easy, others are far m...")
 
 
(One intermediate revision by the same user not shown)
Line 21: Line 21:
== Unit Tests ==
== Unit Tests ==


* '''User Input:''' Name: Bill
* '''User Input:''' sum(12,33)
* '''Expected output:''' Hello Bill
* '''Expected output:''' 45


* '''User Input:''' Name: TJ
* '''User Input:''' diff(25,5)
* '''Expected output:''' An administrator! Hello TJ
* '''Expected output:''' 20
   
   
* '''User Input:''' Name: 123
* '''User Input:''' quot(30,2)
* '''Expected output:''' Hello 123
* '''Expected output:''' 60


== Hacker edition ==
* '''User Input:''' prod(30,2)
 
* '''Expected output:''' 15
In the hacker version:  
 
* Your program should test for valid user input. The user input should be only allow for strings
 
THIS PART ISNT DONE YET


== How you will be assessed ==
== How you will be assessed ==

Latest revision as of 14:37, 20 June 2019

This a problem set for you to work through [1]

This is a problem set. Some of these are easy, others are far more difficult. The purpose of these problems sets are:

  1. to build your skill applying computational thinking to a problem
  2. to assess your knowledge and skills of different programming practices


What is this problem set trying to do[edit]

In order to complete this problem set, you should have a good understanding of Functions.

The Problem[edit]

  1. Write a function that accepts 2 numbers and returns the sum
  2. Write a function that accepts 2 numbers and returns the quotient
  3. Write a function that accepts 2 numbers and returns the product
  4. Write a function that accepts 2 numbers and returns the difference


Unit Tests[edit]

  • User Input: sum(12,33)
  • Expected output: 45
  • User Input: diff(25,5)
  • Expected output: 20
  • User Input: quot(30,2)
  • Expected output: 60
  • User Input: prod(30,2)
  • Expected output: 15

How you will be assessed[edit]

Your solution will be graded using the following axis:


Scope

  • To what extent does your code implement the features required by our specification?
  • To what extent is there evidence of effort?

Correctness

  • To what extent did your code meet specifications?
  • To what extent did your code meet unit tests?
  • To what extent is your code free of bugs?

Design

  • To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
  • To what extent is your code eliminating repetition?
  • To what extent is your code using functions appropriately?

Style

  • To what extent is your code readable?
  • To what extent is your code commented?
  • To what extent are your variables well named?
  • To what extent do you adhere to style guide?

References[edit]

A possible solution[edit]

Click the expand link to see one possible solution, but NOT before you have tried and failed!

not yet!