/CalculatorGUI

CalculatorGUI

2 2.1 Project 2 Queens College, CUNY, Department of Computer Science Submission details Software Engineering CSCI 370 Fall 2018 Instructor: Dr. Sateesh Mane ⃝c Sateesh R. Mane 2018 revised due date = Friday September 21, 2018 • The project 2 specification is to implement a GUI for a four function calculator. • The due date of Project 1 will be postponed, by one week, to 10/7/2018. • Project 2 has emergency priority. • All students will be required to demo their Project 2 GUI in class on 9/17/2018. • Bring a computer to class, and demo your GUI on your computer. • All students must submit individual written reports for Project 2. 1. This is because your work will be a “final submission” for the project. 2. See Sec. 2.2 for details of the report. • Tutorial:

  1. For Java code, a student has kindly written a tutorial how to make a jar in a zip file, which is safe to email.
  2. The instructions use the Eclipse IDE.
  3. The tutorial is posted online at the following link: http://venus.cs.qc.cuny.edu/~smane/cs370/projects/java_Tutorial.pdf • Teams:
  4. Students may work in teams (either existing teams or form new teams).
  5. For new teams, the names of all team members must be submitted to me before 9/17/2018. 1

2.2 Report • The project 2 report is due on Friday 9/21/2018. • There is no need to submit a report on Tuesday 9/18/2018. • The report should be submitted as a zip archive (do NOT use rar). • Please employ the following naming convention for your report (zip archive). StudentId_first_last_CS370_Project2.zip • The zip should contain an executable jar file. • The zip should contain a “cover” document (txt/pdf/docx). • Every student must submit a report.

  1. For students in teams, the jar file can be the same for all team members.
  2. However, the cover letter must be written individually (although it can be copy and paste mostly the same for team members). • The cover letter should contain the following.
  3. Names of all team members, if in a team.
  4. A “mission statement” (= implement a GUI for a four function calculator).
  5. A description/summary of what happened in the demo in class on 9/17/2018.
  6. A list of bugs that were discovered in the demo.
  7. A description of debugging procedures and tests to check the functionality.
  8. A description of additional software checks and tests to validate the functionality. • Students who did not demo a GUI in class on 9/17/2018 will receive a grade of C or D (to be decided). This does not apply to students in teams, where another team member gave the demo in class on 9/17/2018. • Red star
  9. Students who received a red star for their demo in class on 9/17/2018 will probably receive a grade of A for Project 2.
  10. However, students who do not submit an individual project report will not score A, regardless of a red star in class on 9/17/2018.
  11. All “red star students” must sumbit (in their cover document) a description of additional software checks and tests to validate the functionality. • Rigorous software testing is expected from all students. 2

2.3 GUI details • The project specification is to implement a GUI for a four function calculator. • The basic GUI layout was displayed in class. • The basic GUI functionality was displayed in class. • The four functions are the basic arithmetic operations +, −, ∗, ÷. • Buttons:

  1. Digits 0 − 9 and button “.” for decimal point.
  2. Button “+/−” to change sign of operand.
  3. Button “=” to perform calculation and display result.
  4. Buttons “C” to clear the current operand and “AC” to clear everything from memory. • You are NOT required to write a programmable calculator.
  5. You are required to support only two operands.
  6. A calculation such as 1 − 2 ∗ 3 will be performed as follows:
  7. Enter “2” then enter “∗” then enter “3” then enter = (to display “6”) then enter “+/−” to change sign (to display “−6”) then enter “+” then enter “1” then enter = (to display “−5”).
  8. You are NOT required to implement a “stack” or “binary tree” to support multiple nested operations and operator precedence, etc. • Results (for large/small magnitudes) can be displayed in fixed format or scientific notation. • Leading zeroes should not be displayed (enter “0” and “1” the display should show “1” not “01”). • Trailing zeroes should not be displayed (enter “1” and “+” and “2.0” and “=” the display should show “3” not “3.0”). • Input a fraction as “.” and “4” the display should show “0.4” (not “.4”). • Division by zero should display “err” or a suitable error message.
  9. Bad input must be trapped.
  10. The GUI must not crash.
  11. Do not worry about overflow or underflow.
  12. The GUI will not be tested with extreme numbers. • There is no memory. If the GUI is restarted all previous calculations are lost. 3

2.4 Test cases

  1. Enter “3” then “.” then “+/-” display should be “−3.” See Fig. 1.
  2. Enter “3” then “.” then “+/-” then “2” display should be “−3.2” See Fig. 2.
  3. Enter “1.00” then “+/-” display should be “−1.00” (do not erase trailing zeroes). See Fig. 3.
  4. If you enter “0” or “0.” or “0.000” then press “+/-” there should be no effect. Do not display “−0” or “−0.” or “−0.000” The sign change +/- should only do something if the displayed number is nonzero. And do not reduce the display to “0” The display should remain “as is” with all the zeroes on screen. The number is not complete. You do not know if the user wishes to appemd more digits.
  5. If you enter “9 + =” there should be no calculation. (Commercial calculator GUIs do weirdo different things. Hence there is no “correct” behavior. What I write here is just my policy.) The calculator stores “9” as operand #1 and “+” as the operation. It waits for the user to input operand #2 and it ignores the “=” entry if it does not have two operands to act on. The calculator does a math calculation (in this case +) only if it has two operands.
  6. If I enter “.” the display should show “.” or “0.” but not “0.0” or “.0” I may wish to append more digits. Hence the entry “.123′′ should display “.123” or “0.123” and not “0.0123” or “.0123” 4

Figure 1: Enter “3” then “.” then “+/-” display should be “−3.” 5

Figure 2: Enter “3” then “.” then “+/-” then “2” display should be “−3.2” 6

Figure 3: Enter “1.00” then “+/-” display should be “−1.00” (do not erase trailing zeroes). 7