To simplify and ease the integration process I suggest these guidelines for the graphics designer:

Collaborate with the Developer at Project Start

Lack of discussion with the developer about the graphic designs leads to significant problems during integration.

To make the integration process smooth discuss your design ideas with the developer at the beginning of the project.

Keep Table Nesting Levels Shallow

As nesting levels increase so does the difficulty of understanding where you are in the table structure.

Conversely, shallow nesting means it's easier to know where one is at in the table structure.

Name Tables

Select names that clearly identify the purpose of tables. The name 'A' does not convey any meaning. Whereas, the name 'CollaborationGoals' provides a better indication of the purpose of the table.

Use Naming Conventions

Locating objects can be difficult in medium to large projects. Where is the CSS style? Where is the graphic image? Searching for project objects can waste significant amounts of time over the course of a project.

Using naming conventions to identify project objects eases the task of locating these items.

• Use a prefix.
• Use a hierarchical naming order.

Examples:

• NAMIC_ButtonBack.gif
• NAMIC_ButtonGo.gif
• NAMIC_MenuHome.gif
• NAMIC_MenuLeft.gif

Use CSS

Suppose FONT tags are used across 30 application pages. Now imagine you, as the designer, desires to change the font face. How much time is required to modify the FONT tag in all 30 pages?

Suppose a CSS style is defined and then used across the 30 application pages instead of the FONT tag. To change the font face requires changing one CSS style in the applications CSS style sheet.

Using CSS is a time saver.

Organize in Alphabetical Order

Suppose you have 26 cards each stamped with the letters of the alphabet on the front the cards. Shuffle the cards. Now attempt to locate 'G'.

Place all the cards in alphabetical order. Now attempt to locate 'G'. Could you find 'G' quicker in the randomly shuffled deck or the sorted deck?

Yes, the idea makes common sense and you might ask "Why bother mentioning this guideline?". Because I've worked on projects where the objects were not organized in alphabetical order.

Design Master Pages

ASP.NET developers can create master pages which contain common graphical elements for a set of pages. All pages using the same master page have a common look and feel. Make a change in the master page and the look and feel is changed on all pages using the master page.

At project start determine which pages in the application must have a common look and feel. Then design a master page for each common set of pages and hand the master page designs to the developer. The developer will create the ASP.NET master pages and apply them to all associated pages.

Design Reusable SubForms

A better approach is to design a single reusable subform for each function in the application. Using this approach reduces design time, software development time, debugging and testing time and ultimately reduces project costs.

For example, the NAMIC Mentor Program application collects company information from the user during the account and application creation processes. I designed a single Company subform and used that subform on the account and application pages.

Minimize Precise Graphics Positioning

Debugging and fixing precise graphics positioning requires enormous amounts of time by you and\or the developer. The development time increases as one needs to debug increasing numbers of positioning problems. The problem is compounded by the differences in browser and browser versions.

A better approach is to rely less on precise graphics positioning.

Minimize Graphical Elements

For one project I worked on the designer created about 80 tiny graphical elements that had to be precisely positioned in order to create his desired design for a set of pages. I spent many hours debugging browser problems related to the 80 elements.

Was 80 elements needed for this project? Probably not. Unless the client has a large budget for the project the best option is to keep the number of graphical elements to a minimum.

I develop web applications in C#, VB, ASP.NET, and SQL Server as a contractor. I have noticed that clients run into problems hiring web developers to  create web applications. Also, clients have mentioned problems they've had with developers in Craigslist job posts.

Clients had problems with web developers who: 

• create poorly designed databases;
• create web applications with many bugs;
• create botched software designs;
• develop what they want not what the client wants;
• don't respond to client inquires; and
• leave in the middle of the project.

The impact on clients is:

• thousands of dollars are wasted; and
• revenue is lost.

One Craigslist job poster noted that he wasted $3,500 in design and development costs.

In this article I offer suggestions for finding a good software developer who will design and develop a high quality web application that meets your objectives and functions well.

Does the Developer Follow a Process?

No process = project failure.

A development process must be well-defined and followed in all endeavors in order to reach an objective. Ask the prospective developer to explain their development process. Avoid developers who don’t have a well-defined process.

Read Keys to Successful Projects  for more about our software development process.

Does the Developer Write Project Specifications?

Robert Glass states in Software Runaways, Lessons Learned from Massive Software Project Failures, that 51% of projects fail due to poor or insufficient projects specifications. Thus project specifications are crucial to the success of your projects.

Ask the prospective developer whether they write project specifications and to send you copies of specifications they have written for past projects.

If requrested, I can send examples of past project specifications that I have worked on.

Seek Senior Contractors for Large Complex Projects

Robert Glass states in Software Runaways, Lessons Learned from Massive Software Project Failures, that 42% of projects fail due to lack of senior staff.

Interns and college graduates do not have sufficient project experience to design and develop software for large complex projects.

Match the seniority of the contractor to the size and complexity of the project.

I have over 10 years experience designing and developing complex software.

Hire Developers Based on Track Record

Many Craigslist posters request the developer be local to their office. Proximity of the developer to your office does not guarantee project success. Increase the probability of project success by selecting a developer based on these criteria:

• Developer has a track record of successful projects.
• Developer has a well-defined software development process which they follow.
• Developer’s references confirm project successes.

Pay Market Rates

Pay market rates and you’ll attract experienced developers to work on your project and you’ll increase the likelihood of project success.

Current market rates (17-Jan-2006) are $50/hour to $75/hour for experienced developers. Students generally charge $20+. Developers who specialize may charge fees above the range stated. Rates vary based upon geographic location.

Check References

While I can’t be certain it seems apparent to me that many job posters do not check the developer’s references.

A few questions to ask the developers previous clients:

• Did the developer understand your objectives before starting the project?
• Did the developer write project specifications?
• Did the developer stay on the project until completion?
• Did the web application function as outlined in the specifications?
• How many bugs are in the web application?
• Did the developer respond promptly to inquires, phone calls, emails?

Know the Role of Designers vs. Developers

I’ve noticed some posters are confused about the role of a web designer versus a web developer. For example, the job title is “Web Designer” and the body of the post requests the contractor to perform software development.

A web designer designs the graphical appearance of the web site. This includes: colors, fonts, logos & images, placement of text and images on the page. Tools typically include HTML, JavaScript, Dreamweaver, Photoshop, and ImageReady.

A web developer designs the database and the actions of the web site. This includes: designing database tables, designing software to validate form inputs, storing data in the database, getting data from the database and displaying the data on pages. Tools typically include: C#, ASP.NET, and SQL Server. You may need both a web designer and a web developer for your project. Therefore, you may want to state that in your job post.

Summary

Doing your homework upfront can greatly increase the success of your project.

SourceLogic Solutions develops web applications in C#, ASP.NET, and SQL Server. We:

• Understand your objectives at the beginning of the project.
• Follow a well-defined software development process.
• Have 10 years experience developing software.
• Have a track record of successful projects.
• Have good references.

You can read more about software development process and project specifications by reading Keys to Successful projects.