Thursday, June 4, 2009

Tuesday, June 2, 2009

WORKSHOP 8 (Cristian Escobar)

Finally the last workshop is presented where we are asked to answer a group of questions as an evaluation report. This evaluation is made with the aim to improve the subject workshops, which by the feedback provided of the current students will strength the weaknesses and improve the strengths.

Evaluation and Report

1. List what you consider to be the three strengths of Ruby on Rails workshop series
· It’s well organized, step by step from beginning to the end.
· Promotes team work
· Provide different visions/roles (developer/IT Infr. Manager)

2. List what you consider to be the three weaknesses of Ruby on Rails workshop series:
· Diverging from the core of the subject
· Too spread topics, becomes less assimilation of material.
· Too basic ruby applications

3. List what aspects of Ruby on Rails workshop series that you found to be most difficult.
· New language, framework, interface, etc. to learn in a short period
· Huge workload for assignments
· Working on teams from the beginning then change and reorganize new teams.

4. List what improvements could be made to the Ruby on Rails workshop series:
· Link them with the core of the subject
· I think it is not good idea work in such big groups (teams)
· Workshops released with more anticipation.


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?
I had no experience using other Web framework. Ruby on Rails it is my first experience, so I cannot compare the use of it more than believe what I have read and study about Ruby on Rails capabilities.

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.
We really used Google group, and it works pretty good. Easy to communicate and normally prompt response by the rest of the students. It is an effective way to communicate, post with dates and time, so no excuse for the lazy ones (especially when working in groups). However I didn’t heard any comment to use any other application for communication and share the subject’s information.

7. Further comments to add?
Workshops are a fairy good idea to introduce practical and new topics. The methodology was good and clear. However I think there were too much importance to the workshops and lack of importance to the core of the subject we suppose to have. I think a better balance it will be better, resolving exercises as well like the first assignment but with less workload.

WORKSHOP 7 (BLUE TEAM)

As a continuation of the workshop 6 we were asked to add some ideas of policy planning and documentation about production site deployment and maintenance solutions.

Again, this workshop is presented as a blue team report (please follow link)

WORKSHOP 6 (BLUE TEAM)

For this workshop we had been ask to further search and answer the question: “Are we certain that Ruby on Rails is the right platform for Web development?”. A report created by the blue team should answer this question focused on the framework alternatives, mainly on the issues of scalability, flexibility. In addition a plan for capacity planning, performance testing, site maintenance and future development of the OTBS is presented.

The report was created and posted in the following the link:
http://itc594.googlegroups.com/web/BLUE_TEAM_WORKSHOP6.doc?gda=hILiy0kAAAAG0c-TWgDZ_1IVyawxAjfR2of3unBgsbsLJBC4PfSo1RQit5gZkpIhkD_Liao84qrtA-1oZDyui-um49UeGq-hhAioEG5q2hncZWbpWmJ7IQ&gsc=l4WxUQsAAACQc51nttr7qXfEnpH4J3KE

WORKSHOP 5 - PART C (BLUE TEAM)

Part C: Online Taxi Business Process Modelling Apart from the business basics of offering a clean car, safe driving, being on time, consider the business processes involved and construct a Simple Online Taxi business process model.

1. Before the ride


2. During the ride


3. End of the ride


WORKSHOP 5 - PART B (BLUE TEAM)


Part B: The enhanced customer experience through Web 2.0 technology
1. Use a table to describe how the customer experience is improved by

a. Horizontal scalability (eg ordering a taxi by mobile phone call or SMS, mobile Internet, desktop or laptop computer)
b. Service oriented features (eg SMS updates using location data, knowing the driver’s name before the ride and being greeted by your name etc)
c. Other customer services enabled by Web 2.0 (eg reputation system)




WORKSHOP 5 - PART A (BLUE TEAM)

Let put us in a situation where the client suggested to extend the user experience to include mobile devices and GPS systems for our OTBS. As an IT Inf. Managers we have to determine resources needed to extent this application. The presented workshop will lead us on the path to handle this new request to enable developers to do their job according requirements.


Part A: Survey of mobile device capability and Web 2.0 tools



1. Find out and recommend what type of mobile devices are suitable for:

a) Just the SMS message service;

Short Message Service, better known as SMS is a service which is available in todays most digital mobile phones. SMS permits sending short messages in text format between mobiles phones, some other handheld devices and also to land-lane phones.



Due SMS were originally developed as part of the GSM standard digital mobile phones, however, at this days is also available for a wide range of networks, including 3G networks.
Hence to provide a service using SMS based way of communication in both ways, almost any digital mobile is capable to do it.



b) The full user experience via SMS, GPS Taxi tracking and Google Maps

The new generation of mobile devices, specially 3G or newer generations had opened a new world of possibilities. The inclusion of GPS facilities together with the access to internet via 3G or GPRS made possible to have a full experience when services are implemented. For instance in our case, the Online Taxi Booking System, a full experience could be detecting the customer using the GPS incorporated in the mobile device, then locate the closes taxi using a GPS installed in every company’s cab, finally using SMS as the way of communication the customer can interact with the taxi service, further more this system can be optimized letting a computer do the answering to the solicitudes replying the availability and the estimated arrival time using Google maps, finally through a client confirmation, the instruction is send to the respective taxi driver.


2. Describe any new hardware, networking, software, systems, procedures and personnel that would be needed by the taxi company Website to support this stage 2 development.

The requirements of procurement needed for the taxi company website. As it was explained in last question part b, to have a full experience supporting this stage, it is necessary to have at least a minimum of :

- A server to support the whole information system
- An softwares- webpage- database available and configured to connect the different physical taxi stations using a distributed system, where is necessary to have the proper hardware to properly handled the application.

- The application itself, the interface with the user, in where he will do the requests either by internet phone or SMS.

- The human resources necessary to support the application maintain the system and any trouble that may occur.

However it is not easy to predict the required quantity of each item unless we can have a better description of the size of the real business.


Part A: Viewing the action

1. A Rails application framework named “animals” is created in the projects folder: C:\InstantRails\…\projects\>rails animals















2. We then start the ruby server for testing by access the application directory and execute the server starting command: ruby script/server















And access via Web browser at http://localhost:3000/

















3. Subsequently, a controller named “Mammal” is created to make the application do an action












4. Test the controller by browsing http:/localhost:3000/mammal and we receive no action resulted since there are no controller methods defined.

5. We create an action by editing and saving the mammal_controller.rb class in the directory projects\animals\app\controllers
class MammalController<>

6. Start the WEBrick server and browse at http://localhost:3000/mammals/breathe where we get a “missing template” message since it is missing a view for the breathe method.











7. Create and save a view named breathe.rhtml with particular content in \projects\animals\views\mammal. Then restart the WEBrick server and browse again at http://localhost:3000/mammals/breathe










































Part B: The active view: passing data from an action too a view

1. Create a new application called “scenery” in the same projects directory to demonstrate the use of an active view.









2. Create a controller called Demo in scenery\app\controllers








3. Add an action to demo_controller.rb as the method called rubycobe

4. Add a view template - scenery\app\views\demo\rubycode.rhtml
We will edit this view in later steps but you may like to add your own test HTML code to the view at this stage.











5. Save and restart the Web server and navigate to http://localhost:3000/scenery/rubycode














6. Use the Time.now example to pass data from an action to a view

7. Modify and save the rubycode action with a value for the time instance variable in the DemoController class in app\controllers\demo_controller.rb








8. Then modify and save the corresponding view template in \app\views\demo\rubycode.rhtml by adding a call by reference to the action’s instance variable















9. Restart the Web server and navigate the browser to http://localhost:3000/demo/rubycode














Part C: Screen layouts and forms processing with text fields, check boxes, radio buttons and multiple list controls


1. Create a new application called “cabs” in the same projects directory to demonstrate the use of an active view.













2. Create a controller called Vehicle in cabs\app\controllers





3. Add an action to vehicle_controller.rb as the method called cabtype






4. Add a view template – cabs\app\views\vehicle\cabtype.rhtml with some HTML code to the view








5. Save the view and restart the Web server and navigate to http://localhost:3000/cabs/cabtype











6. Create a file in the public directory – \cabs\public called input.html with



















7. Edit the vehicle_controller.rb here is a start. The data in each form element in the Rails application can be accessed via its name and a hash called params
8. Edit the view template cabtype.rhtml
9. Start the Web server and go to the opening page of this application at http://localhost:3000/input.html.