Friday, May 15, 2009

Workshop 8: Ruby on Rails Workshops Report and Evaluation

Evaluation and Report

Please answer each question in this evaluation section. In your answer, please consider content/topics presented and the technologies and teaching strategies used during the Ruby on Rails Workshops. Results will be collated and used to modify the workshop series.
This form is just a format guide to you evaluation and report. Thank you for your time to complete workshop 8.

1. List what you consider to be the three strengths of Ruby on Rails workshop series


2. List what you consider to be the three weaknesses of Ruby on Rails workshop series:


3. List what aspects of Ruby on Rails workshop series that you found to be most difficult.


4. List what improvements could be made to the Ruby on Rails workshop series:


Free response and reflective questions:

5. Reflect on your experiences with the other Web framework used in this subject: Was it effective? How can it be improved? Should other Web frameworks be used as well or instead of Ruby on Rails?

6. Did the Developer’s or IT managers Team that you joined after workshop 4 have a preference towards using other tools to facilitate collaboration? Comment on the differences between these use of the sub-forum or Interact wiki tools from your experiences in this subject.

7. Further comments to add?

Workshop 7: End of the Line: production site migration and maintenance (BLUE team)

What are the hosting solutions?
Will our Rails applications run on a cloud computing service in future?
Can we make a deployment and maintenance plan by team consensus?

Build upon the Blue team wiki inside Interact, from Workshop 6 by beginning a new page to add your ideas for policy planning and documentation about production site deployment and maintenance solutions.

Administration, scaling, reliability and integration with existing and future services are issues.

Consider all the business options of both in-house deployment and outsourcing as shown by hosting sites like http://www.engineyard.com/

Worshop 7: End of the Line: production site migration and maintenance (RED team):

Developers conclude their work with the OTBS and look at the options for deployment of the site. Examine the various platforms/software tools used for deployment such as UNIX environment suggested in the Discussion Notes, Mongrel or Mongrel cluster, Nginx, Subversion or Capistrano (during development stage), JRuby in the Java environment.

Which way?

The choice is up to you as this workshop present just one option and you may like to use another, such as deploying the OTBS in a .NET or J2EE environment

Can you get the OTBS Running in production mode as a minimal production server?

Share your success by posting progress comments and links etc to the Developers sub-forum site that has been set up for the Red team.

Wednesday, May 6, 2009

Workshop 6: Enjoying the Ride: Web framework alternatives, scalability and flexibility (BLUE team)

Are we certain that Ruby on Rails is the right platform for Web development?

Your findings should answer that question using the Blue team wiki inside Interact.

Blue team IT managers need to write a team report on the wiki about the alternative frameworks, focusing on issues of scalability, flexibility. In addition a plan for capacity planning, performance testing, site maintenance and future development of the OTBS is presented. Chapter 17 of Hartl et al (2008) is a good place to start. The structure and content and comments made in the wiki report is up to you and your team members.

[This is open to include current alternative frameworks offered by Google Apps, JQUERY, Django, Adobe as well as Java and .NET frameworks that can be included. Your research may also expand the scope to include content management systems.]

Workshop 6: Enjoying the Ride: Web framework alternatives, scalability and flexibility (RED team)

Developers may continue to build upon work with the OTBS using the topic reading to help with user registration and advanced login features from Hartl et al (2008).

o generate a controller and an action by adding a method(s) to a controller;
o create a view template for each action and to link to actions from views;
o use AJAX to improve the user experience;

Share your success by posting progress comments and links etc to the Developers sub-forum site that has been set up for the Red team.

Saturday, April 18, 2009

Workshop 5: Admiring the secenery Forms, AJAX screen layout and and mobile interfraces: To Do (BLUE team) Part C Online Taxi Business Process 3.:

END of the RIDE

a. At the end of the ride there is no delay for making a payment so the taxi driver would help the customer get out of the car and would have their luggage ready waiting for them and say goodbye.

b. The business process concludes when the company uses the taxi vehicle’s GPS location data again to send a final friendly thank you, suggests feedback via SMS and offers a goodbye message.

Workshop 5: Admiring the secenery Forms, AJAX screen layout and and mobile interfraces: To Do (BLUE team) Part C Online Taxi Business Process 2.:

DURING the RIDE

a. When the taxi arrives, the driver greets the customer by name and helps them with their luggage and then opens the car door.

b. The taxi driver would initiate a conversation and continue with it if they are interested or show interest if they started talking first.