jscientificcalculator

JSCIENTIFICCALCULATORGroup

We<3Dobbins

JSCIENTIFICCALCULATORGroup We<3Dobbins Staff

WE<3DOBBINS STAFF

Managers

Chris Buzzerd (Repository) Michael Kelleher (Process) Allison Corey (Website) Brandon Grant (Docs) Erik Dacosta (Contact)

WE<3DOBBINS STAFF

Code Developers

Joey Reaves Chris Rock Danial Afzal Rex Robinson Ross Friedberg Kiyotaka Iwataki

WE<3DOBBINS STAFF

GUI Developers/Designers

Robert Krieger Bruce Shaw Long Mai  Erik DaCosta Allison Corey Brandon Grant

JSCIENTIFICCALCULATORTesting Procedure

TEST PLAN 1.0 Testing Process

1.1 Integration Testing 1.2 Release Testing Procedures 1.3 Performance Testing

2.0 Requirements Traceability 2.1 Numbering System (X.Y)        X – Requirement number         Y – Test case number for requirement

2.2 Other Information: For all requirement test cases, it is assumed that the first case step is to successfully compile, and then run the program. “Selecting” a button or numeral simply means clicking on it.

2.3 Test Cases

3.0 Schedule

4.0 Recording Procedure 4.1 Results Reporting 4.2 Documenting Success 4.3 Analysis 

5.0 Constraints The only foreseeable constraints relating to this Java Scientific and Graphing

Calculator relate to the Graphical User Interface. Buttons for requirement functions must be added in order for requirements to be tested as part of the system.

TEST PLAN SCHEDULE

Week Tasks3 Testing documents and test schedule.

4 By Friday night, the coding team will have all requirements implemented and the testing team will have all test cases written for Increments One and Two. By Sunday night, the testing team will run all test cases and report any bugs and errors to the coding team. The coding team will fix errors for final testing.

5 Write test cases for final increment.

6 By Thursday night, the coding team will have all requirements implemented and the testing team will have all test cases written for the final increment. By Friday night, the testing team will run all test cases and report any bugs and errors to the coding team. By Sunday night, the coding team will fix errors for final testing. Final testing will conclude by Monday night.

EXAMPLE TEST CASESTest Case Case Steps Expected Result

7.1 1) Select “SHIFT”2) Select “abs”3) Select “(“4) Select “–“5) Select “5”6) Select “)”7) Select “=”

The value 5 should be displayed after the equals button has been pressed.

7.2 1) Select “SHIFT”2) Select “abs”3) Select “i“4) Select “=”

The value 1 should be displayed

 9.2 1) Enter "5.2"2) Select "GCD"3) Enter "2.6"4) Select "="

The calculator should display "2.6" 

JSCIENTIFICCALCULATORIncrement One

REQUIREMENTSWeek Requirement Written By Importance

1 Multiple Variables

Chris Rock 3

1 Absolute Value Command

Robert Krieger 14

2 Window Bounds

Brandon Grant 2

2 Cartesian Plane

Erik DaCosta 1

WORK ASSIGNMENTS WEEK 1

Code Team Research ways to code/implement graphing area. Create code to handle multiple variables. (store

to a variable) Create code to handle absolute value function.

GUI Team Research Cartesian Plane / Bounds in JAVA Create GUI for Absolute Value option Create GUI framework for Cartesian Graphing

Utility Create GUI for Multiple Variables option

WORK ASSIGNMENTS WEEK 2

Code Team Research ways to code/implement graphing area. Create code to handle multiple variables. (store

to a variable) Create code to handle absolute value function.

GUI Team Research and implement Cartesian Plane. Finish GUI framework.

INCREMENT REPORTWeek Requirement Status

1 Multiple Variables Implemented, not integrated

1 Absolute Value Command

Complete

2 Window Bounds Incomplete

2 Cartesian Plane Implemented, not integrated

SC

REEN

SH

OTS

: SH

IFT M

OD

E

1) Returns the absolute value of the expression.

1

SUMMARY

Because of the difficulty of some of the requirements and internal miscues, the increment was not completed. To remedy the problem, three requirements were removed, and the schedule was reshuffled to evenly distribute anticipated weekly workloads.

SUMMARY: REVISED SCHEDULE

Week Requirement(Graph Based

Requirement

1 Abs. Value

2 Multiple Variables

3 Cartesian Plane GCD

4 Trace LCM

4 Coordinate Finder Differentiation

5 Window Bound

6 Minimum Function

6 Maximum Function

JSCIENTIFICCALCULATORIncrement Two

REQUIREMENTS

Week Requirement(Graph Based Requirement

3 Cartesian Plane GCD

4 Trace LCM

4 Coordinate Finder Differentiation

WORK ASSIGNMENTS WEEK 3

Code Team Implement Graphing. Implement Greatest Common Denominator and

Least Common Multiple. Code inputting equations for graphing. Code ways to handle Multiple Variables

GUI Team Create GUI for GCD, LCM, x, d/dx, and Multiple

Variables. Update Documentation.

WORK ASSIGNMENTS WEEK 4

Code Team Finish LCM and GCD. Implement Coordinate Finder. Finish Multiple Variables.

GUI Team Add X: and Y: fields and a find button to the

Graph. Add Intersect, Clear, and Delete buttons to

Graph panel. Create equation scroll box on the Graph panel.

INCREMENT REPORT

Week Requirement(Graph Based Requirement

3 Cartesian Plane Complete

3 GCD Complete

4 Trace Incomplete

4 LCM Complete

4 Coordinate Finder Incomplete

4 Differentiation Complete

SC

REEN

SH

OTS

: SH

IFT M

OD

E

1) Graphs the current equation in the screen

2) Graphs the derivative of the current equation in the screen

3) Returns the Greatest Common Denominator of two numbers

4) Returns the Least Common Multiple of two numbers

5) The “x” variable button

6) The “Z” variable button

1 23 4

5 6

SC

REEN

SH

OTS

: GR

AP

H P

AN

EL

1) Graphing are

2) X coordinate search

3) Y coordinate search

4) Activate coordinate search

5) Active equations

6) Displays equation intersections

7) Deletes highlighted function

8) Deletes all functions

9) Changes window bounds

10) Refreshes the graph panel.

4

1

32

10

56

98

7

SUMMARY

The function to determine the Intersection of two equations was added back to the program. It was one of the functions removed from the project because of its complexity and time restraints. All outstanding requirements from Increment One were finished except for some implementation hold ups with Multiple Variables, and with Increment Two, with the re-addition of Intersection, Trace and Coordinate Finder were stalled to get a head start on its implementation.

JSCIENTIFICCALCULATORIncrement Three

REQUIREMENTS

Week Requirement(Graph Based

Requirement

5 Window Bounds

6 (Intersection) Minimum

6 (Intersection) Maximum

WORK ASSIGNMENTS WEEK 5

Code Team Complete Trace and Coordinate finder. Finalize Multiple Variables. Finish and Integrate Intersection. Modify Mode button to switch graphing modes.

GUI Team Implement a means to display function

intersections. Create finalized Test Cases.

WORK ASSIGNMENTS WEEK 6

Code Team

GUI Team

OUR THOUGHTS

QUESTIONS?