Iteration6 big activity diagram

I haven't written all the unit tests for the Big Activity Diagram yet, but wanted to get this branch in a state that it could be merged to master. 

Ran into some issues with the call operation action unit tests because I had removed the comment lines that get printed for an activity for the various control flows and activity nodes that are in the diagram. So put the genClassMethod call in the genMethodsFromActions(), which required me to then add require_relatives logic to support the operation being called on a Class, but then found out that it couldn't actually call the method probably because it ended up just being a line of Ruby in the middle of the file, outside of any method definition. So I put a hash in front of it to make it a Ruby comment for now. 

1) Need to decide how the CallOperationAction should be printed out or where the best place for it is in the final output files. 
2) Need to add more unit tests for the overall Big Activity Diagram. 
3) Need to revisit how the logic is getting printed in the deliver_Order method defined in Process_Order.rb because it has two return statements, even though I think it should only have one.. or is this valid ruby code for now if the if/else control guards are getting printed as comments?


Currently all unit tests passing: https://76.230.136.103:8085/job/hollytest/31/testReport/