Most web development projects include one or more of the following elements...

• Database design and creation
• Server-side computer programming
• Client-side computer programming
• Web page design

Each of these elements has to work in its own right, and in cooperation with the other elements. The more complex the project, the harder it is to bring it all together and make it work correctly.

How to keep the cost down

Here's how you can make sure your web development costs don't run over budget...

1. Insist every aspect of the development is described in an Agreement document, and make sure both you and the developer sign it
2. Don't make changes after work has started

The key to achieving the second of these two items lies with the first. You should insist that an Agreement document be created, and sit in on the process.

You need both end-users and developers in the same room, working through each aspect of the development. The end result must be a document that fully describes the development, is clear (unambiguous), and easily understood by both users and programmers.

Every minute you invest creating this document greatly increases your chance of bringing the project in on budget.

Why it's worth it

Many of the problems that usually cause headaches during a complex development could have been discovered in advance, if an Agreement document had been created. When users and programmers get together and discuss their respective needs thoroughly, the resulting development is far more likely to go smoothly.

This kind of interaction forces both users and programmers to think through what's actually required to make the system work. The ongoing interaction reduces the risk that person A assumes person B knows what they're talking about.

Users are committing to a specific set of functions for an agreed price. The developer is committing to develop those functions for an agreed price. This means both users and developers have a self-interest in being thorough.

Should a user change his/her mind about something after the Agreement document is signed, the cost of development must be renegotiated. This punishes the user for failing to think things through.

Should the developer discover he/she hasn't fully understood what's required to complete some aspect of the project, he/she can't ask for more money. This punishes the developer for failing to break down each stage of the development and understand what's involved in completing it.

Assuming you do your part, you won't need to make changes after the work has started. As a result, you'll bring the project in on budget even if the developer hasn't done his/her job properly.

Pay for a web designer or do it yourself? Can small business owners really design a website or is it a job for the pro's?

Most consumers look on the internet before going to a store. Sometimes it is their only stop: they research, compare and buy online. It goes without saying then that for a small business to reach its potential market, it should have an internet presence.

Small business operators do not often have a dedicated IT person on staff - in the past this is the person who would be given the job of building a website. It's great news then that there are now beginner-friendly website building packages on the market which are perfect for the small business person's use.

Data is entered into your web pages as one would using a word processor - with modern easy to use web builders, there is no need to know any html whatsoever.

The tutorials provided with almost all software suppliers take the novice through the process of building a website in a non-technical, easy to understand way. Having completed the tutorial, one is equipped with more than enough knowledge to launch straight into a website build.

Not all website software programs are easy to use. Small business operators do not need fully blown web design industry solutions due to the steep learning curve. One feature to look for is a WYSIWYG (What you see is what you get) editor. This simply means you type on the page as you see it.

There are expenses involved in publishing your own website - you get nothing for nothing. Apart from the cost of the software (there are free web builders however they are more difficult to use or too basic in features), a small business (or an individual or a large company) will need to register a domain name (less than $10) and find a web hosting service (around $8 per month).

Businesses should also set up a merchant's account from an organization like Paypal (free). Having a third party handle financial transactions is always reassuring for consumers and takes away an administration burden. When an item has been ordered via your website and paid for, Paypal advises you, with delivery instructions so that you can fulfill the order or if it is an electronic delivery, this part can be automated.

In any small business time is money, and the time spent learning a new skill like website building with easy to use software must be seen as a good investment. It is possible to build multiple websites so that you can have a website network feeding a central business. This is ideal for multi-brand retailers and multi-branch operators. This degree of control will reap rewards as your business grows and you build different websites to cater to changing needs.

Because you have built and are managing your website yourself, you are able to instantly react to changing trends and new opportunities. Avoid delays by not having to wait for your webmaster to make changes. Fresh content on your website is highly desirable.

Some website programs are specifically designed to assist the business person become an internet business marketer, and as your knowledge of web design grows, the more you will value search engine optimization and site map generation tools. Having a correctly designed site map helps search engines easily match your site to search requests.

If you decide to look at other ways to earn money through your website without doing a thing, you will no doubt look at including on your site some affiliate marketing and advertisements from non compete companies.

Features to look for:

Ideally you will have an instructional video, help desk support and forums. Look for testimonials from other business owners to see how they have applied the software.

Getting started is the next step once you arrive at the conclusion that a website is no longer a luxury - it is essential!

Some working knowledge of J2EE or JSF is assumed for this article.

Like some of you I've been frustrated with this technology known as JSF or Java Server Faces. There are several different flavors out there that are built on the shoulders of JSF. For instance Oracle's ADF (Application Development Framework). Oracle ADF Faces Components is a set of over a 100 JSF components that let you build a richer user interface for your Java EE applications. Oracle ADF Faces also includes many of the framework features most needed by JSF developers today.

That is great, and in many ways it will make life easier to develop in a JSF environment. Some items you will find available in these "add on" packages have a real benefit. For instance, as of the date of this article, I was very surprised that a File Upload is a feature still not implemented in JSF in respect to using natural jsf tags. There are ways to accomplish this task in JSF but they are not native JSF approaches. The process is a "no brainer" in just about every other framework available today, including asp.net.

Another simple task (I thought) was having a data table present the results of a query in an editable format. Possibly to update a user record or shopping cart. After working in other technologies it was very efficient to return a result set to a data table object and let that object take care of some of the trivial behaviors and characteristics of the table itself. When I started exploring JSF I was frequently and at every turn becoming more and more frustrated in trying to duplicate some of the most basic of processes similar to managing records through data tables.

There are not a whole lot of resources out there yet on JSF although it is growing steadily, and I found that all too often the resources that I was finding on the internet either didn't apply to the more simple tasks or the information was just completely wrong. One example of that was that it was stated in one article I read that you cannot use command buttons inside of a JSF data table. The recommendation was to use JSF hyperlinks instead when trying to perform an action from a data table due to a bug in the framework that prevented command button actions to fire if the button resided inside of a data table.

At first I thought "you've got to be kidding me"! Then I remembered that I've been finding a fair amount of "bogus" information in regards to JSF development so I decided to do further research and discovered that information to be less than accurate as well.

I simply had to find a way to populate a data table through a result set and get a command button to fire an action and pass all of the data in the data table to the backing bean to update the record. Multiple command buttons would exist as well as hidden fields pertaining to id numbers and so forth. Pretty basic stuff and we've all done it before with relative ease.

It turned out that the solution was in fact a simple one. "Binding". You've heard about it and read about it. But this approach was something a little different as far as I could find.

Many of the blogs and articles that I read dealt with passing the values as parameters and following the steps to define the parameters in faces.config files etc., then retrieving the parameters in a backing bean. Processing the passed data required another set of procedures to utilize mapping to each of the field parameters passed and then processing could begin.

That seemed like a whole heck of a lot to me just to retrieve form data. Then it occurred to me that I should be able to "bind" a text field component on a page to a backing bean. Once it is bound then all I have to do is extract the data. And that's all there is to it. My query returned results and pre-populated a data table including text fields with the values of the query pre-populated in the text fields.

Each one of those text fields was bound to a "HtmlInputText" type in my backing bean. It was not a String type like other approaches define. Doing that does require you to map parameters and populate that String variable through your set methods once the form is submitted.

What I found is that if I bind my text field to a property of text field type that it solved my problem of passing values from a data table, and I didn't have to define parameter fields anywhere in any xml file. Now that I had that figured that out I needed to figure out how to get the value of that property that I've bound my form field to, well why not getValue()?

I personally hadn't seen any examples online or in books for retrieving the value from a form binding it to the type of form element it was and simply use the getValue() to pull out the value of the object. Used like this getParameterFromForm().getValue().

Let me clarify that I am NOT saying that trying this approach isn't documented anywhere, I find it hard to believe that I've had some stroke of genius that no one has had before in the world of java, especially since I'm coming from .NET and ColdFusion.

After doing that I no longer had any problems passing form data to my backing bean. I was able to dynamically populate data tables with any number of records including any number of command buttons within that data table and I didn't have to concern myself with remembering to define parameters in any other areas of the application.

So put simply you can bind your form fields to properties of the same type in your backing bean, and then extract the value of that object using getValue() if you prefer over utilizing parameter string mapping and similar approaches for processing form data. I found it to be easier and less time consuming which has costs associated to it as well.