Notice: This repository contains an assessment for my high school Software Development class. Chances are you don't want to be here, but if you do - read on. A live continuous deployment of the project can be found at http://domo-arigato-origami.herokuapp.com.

In order to satisfy criteria outlined in the Software Requirements Specification, I have designed the following solution for Takumi Nakamura:

This solution will take the form of a web application. Using this approach will provide Tukumi with a number of advantages, the most noteworthy being accessibility and the potential to expand the scope of the system in the future. The live demo shows the latest working example as it would appear on Takumi's custom domain name (eg - www.arigato-origami.com), and can therefore be accessed from anywhere in the world with a persistent internet connection. As opposed to a traditional "local" .exe software solution, a web application will have no compatibility issues with PC, Mac or Linux operating systems and works out-of-the-box with Desktop Computers, Laptops, Tablet Devices and Smart Phones. Furthermore, since it is available online, Takumi can still interact with the system if he is out of the office or away on a holiday.

A web application will also allow Takumi to expand the scope of the system in the future. When the workload for manually inputting orders & classes becomes unmanageable - the system can be opened up to customers as a full public website so that they can do it themselves. This would not be difficult, as the foundations for the program will already be laid. Nevertheless, the private version will remain password protected for obvious reasons until Takumi chooses launch a proper website.

The core functionality of this application will be written in Ruby, a programming language that has elegant syntax, is natural to read and easy to write. More specifically it will use a tiny DSL called Sinatra, as well as a powerful text file database platform I created myself called JTask - both of which run on Ruby. Supporting languages (which are only involved in the presentation of the user interface) are HTML, CSS and JavaScript.

Sounds fun, right? Let's get the party started...

// Set the base cost price of an origami lesson. The default value
// is $25.00, however this value can be changed by an admin (on the settings page).
lesson_price = Input lesson_price

Function calculate_lesson_price(num_lessons, order_cost)
  grand_total = num_lessons * lesson_price
  IF num_lessons > 4
    // Apply a 20% discount
    grand_total = discount(grand_total, 0.2)
  ELSEIF order_cost > 50
    // Apply a 10% discount
    grand_total = discount(grand_total, 0.1)
  END IF

  return grand_total
End Function

Function discount(price, percentage)
  return price - (price * percentage)
End Function

Function gst(total)
  return total * 0.1
End Function

total = calculate_lesson_price(3)
gst = gst(total)

// Show our awesome work to the world...
PRINT "Hello, world! Your total invoice price is $" + total + " plus $" + (total * 0.1) + " GST."
// If someone orders just 3 lessons (with no additional goods),
// the above line should return as:
// "Hello, world! Your total invoice price is $75 plus $7.5 GST."

*The VCAA clearly stipulates that "databases cannot be used to support solutions". Therefore, I will be using text files to create, read, update and destroy data for the system and the size of each data item will be irrelevant. It is worth noting, however, that in a real world scenario this technique would not be scalable and a proper database would be used to prevent the obvious security and performance issues.

Unfortunately.

• User sessions work and are secure
• The user interface is not difficult to navigate
• Outputs of the system are clear and accurate
• Website feels smooth and works efficiently
• Prices can be updated
• Lesson prices can be calculated
• GST is calculated correctly
• Code is well formatted and sufficiently documented