COSC 6397/4397 Special Topics In Software Development (Ruby-Rails-AJAX)

COSC 6397/4397 Special Topics in Software Development (Ruby-Rails-AJAX)
Spring 2007 - MW 5:30 - 7:00PM
University of Houston - Department of Computer Science

Instructor: Dr. Venkat Subramaniam email:cosc155g@bayou.uh.edu
Office Hours: Visit following page for details: http://www.cs.uh.edu/~svenkat

Online Info: http://www.cs.uh.edu/~svenkat/classes Please visit to add to mailing list

Grading: Assignments: 20%, Homeworks: 20%, Final (app) 20%, Project 40%.

Syllabus (subject to change):

Programming using Ruby
Benefits, strengths, and power of Ruby
Detailed study of the Ruby language
Quick introduction to Web Development
MVC and Web Applications
What is Rails?
Benefits of Rails
Rails fundamentals
Model, control
Active Records
Generators 
Rich client and Web
AJAX support in Rails
Frameworks for AJAX

Team Project - Requirements and Grading Policy

A Team Project carries 40% of the grade. The project has to be proposed by the team and approved by the instructor. All reports should be type written double-spaced. Each student, based on performance and contribution, as indicated by peer evaluation, will receive a percentage of their final team project grade.

Students are encouraged to discuss the project details with the instructor on a regular basis, during the semester. The objective of these discussions is to explore various options and tradeoffs in design and development of the project.

Scores: Initial report 6 pts; Development report 6 pts; Project refined report 6 pts; Demo 10 pts; Project Evaluation 12pts.

1. Project Team [Due: Jan. 31]

No more than 5 registered students may belong to a team. Each student of a team will be a project developer, and one of them will serve as the team leader. If any team member(s) drops from the course, the team is still responsible for completing the project.

2. Project Proposal [Due: Feb. 7]

A proposal of the project with title and objective should be submitted. The proposal should be two to five pages. It should also contain an estimation of time required, per person, to analyze, design, implement and test the project.

3. Initial Report [Due: Mar. 7]

The Initial report report should contain details about the functionality that will be implemented. It should include details about what the application will do, more from the application behavior point of view than from how it will be implememented internally.

4. Development Report [Due: Apr. 4]

This report should include details on the system design, must include snapshots of application under development. Details about various approaches taken in developing the system must be presented. This should also present details on problems faced and how they are being resolved.

5. Project Refined Report [Due. TBD]

This report will contain refinements made to the system upon further development.

6. Project Demonstration [Due: TBD]

The project demonstration will be scheduled for the final exam time or earlier. One or more members of the team should demonstrate the project in front of a terminal. The grade for this will be based on the team’s answer to questions raised during the demo, organization and presentation of the demo. Each team member is required to be present for this event.

No late submissions allowed on any assignments. Most announcements/assignments will be through email

Please signup for the mailing list