Tri 2: Tech Talk 4 String Ops

String Ops: Background and Creation

String Ops was inspired by College Board FRQ2. After reviewing the LightingSequence gradShow concept and thinking about what was being asked...

• FRQ2 was determined to be mostly String methods, except for final calculation. The hypotenuse calculation seemed out of place and was omitted from String Ops.
• Java Code was created and adapted to be more generic, but contains the same basic operations. Building the LightingSequence gradShow a Tester method mimics the dialog of FRQ2.
• This Java Code contains a lot more error checking than perhaps required if you were to boiler plate the input for the FRQ2, however, you could consider checking for lengths or out of range values should be in the implementations. This error checking evolved as free form user input was excepted via the remainder of the PBL project.
• Building a Class of this quality is considered "above average" and would likely help student achieve a 4 or 5 on AP exam.

String Ops: Model View Control additions

Considering LightingSequence gradShow and thinking about a more extreme use case, the String Ops package evolved into an MVC use case. The View focused on inputs and generating messages. The Control focused on receiving requests and returning responses in a RESTful API programming style. Here are some additional details...

• Following Fibonacci MVC style, String Ops was generated using the same Package, Model, and Control pattern. Added was a local
• View Code is similarly placed in resources under MVC directory. The View Code contains a JavaScript function that is used to initiate Actions and receive Reponses.
• In Control there is an established contract on how the request and response system will work. JSON data is extracted from Model Class and is used to build the Response Body of the response. The Request Actions are directed for processing to the appropriate Model method. Observe how these two methods are brokered sequentially through Control RESTful interface.

Challenge