Web Design Goals
Working with legacy software systems provides its own considerations, but there are some general goals that can be stated for web-based software applications. To the degree that the nature of system upgrades substantially touches these areas of system design, it is important to consider the following goals within the system design.
Well designed applications should meet the following goals in order to provide lasting value:
Cozumel January 2006
Pictures from dive trip to Cozumel in January 2006: Cozumel 2006-02.
Gregg Kellogg
Utila April 2004
Pictures from dive trip to Utila, Honduras (one of the Bay Islands) in April of 2004: Utila 2004.
Gregg Kellogg
Palau January 2001
Pictures from dive trip to Palau in January 2001: Palau 2005-01.
Gregg Kellogg
Channel Islands July 2006
Pictures from Dive trip aboard the Truth Aquatics Vision in July 2006: Channel Islands 2006-07-15
Gregg Kellogg
Costa Rica/Cocos Island
Here’s a link to pictures I took while diving in Cocos Island in Costa Rica from August 25th through September 5th 2006: Costa Rica 2006-08.
Gregg Kellogg
Managing large projects
Of paramount concern in managing large development efforts is the need to ensure that the application remains relevant and maintainable and can be kept up-to-date with the requirements of the rest of the organization.
The danger of a long running project managed by a limited pool of developers is that the original requirements and goals of the system can be lost in the face of multiple enhancements. This can lead to a system that is arcane, does not reflect the actual needs of the department, and (most importantly) is over-reliant on the internal knowledge of the development team. This poses a substantial risk to the business that relies on the system for day-to-day operation.
Fortunately there is a long standing body of Industry Best Practices that have been used to successfully manage the lifecycle of large-scoped projects.
Button Labels 10
I checked in the button-labels plugin. I was frustrated when trying to create a form with multiple radio-buttons and no way to tell them apart. Basically, if the :label option is passed to radio_button, it calls content_tag() instead of tag() and uses the label as the content.
radio_button("post", "title", "Goodbye World", :label => "Goodbye World")
Goodby World
The plugin is managed on ruby_forge.
Rdoc is available.
Entered some time ago as a bug #4627.
Gregg Kellogg