The stories behind the sites we build...

We are proud to present the designs and stories behind some of the website we've designed for our clients ...

Our Process

Our Software Development ProcessIn many respects, software development for the Web is a linear process. Many decisions are dependent on past steps. Changing something in the early stages of the project may cost almost nothing. Changing that same thing later on may double, triple, or even even increase the cost of the project 10-fold. Changes late in the game also usually introduce painful delays. Unanticipated change late in the game can even cause a project to fail.
A small, simple website can often be built by an experienced developer quickly, without a formal, documented work flow process. But in reality, the developer is usually keenly aware of what has to happen and in what order for a successful result.
As websites become larger and more complex, the need for a solid development process increases as do the risks of not using one. The subtleties are many and complex. Missing or not completing even a small step can make or break the project, jeopardizing usability, functionality, budgets, and/or deadlines. Generally, the larger the project, the more important the process.
At UNETY, we've been building websites since 1995. We have developed our process and fine-tuned it over the years. We use it on all our projects. We believe it is one of the reasons for our many successes.  It has become a standard and is used by instructors at the college level.
Below is an overview of our process. It will give you a good understanding of what is involved.
At the onset of every project of significant size, it is important to create a Project Plan. This plan should be used as a guide to keep activities on track and coordinated throughout the development of the Web site. 
The Project Plan should contain all relevant planning information and should be writing, reviewed, and approved by the client before proceeding.
Although contents and level of detail will vary with each client, a Project Plan typically contains:
  1. A list of Web site goals to ensure that a desirable result will be achieved and to measure success
  2. An explanation of how these goals will contribute to the company and a discussion of the expected return on investment
  3. A description of the target audience(s) and their needs, habits, and preferences and an explanation of how the Web site will benefit them
  4. A preliminary Online Marketing Plan, containing a discussion about how this Web site will be marketed and how this will be integrated into existing marketing efforts
  5. An analysis of the online competition with emphasis on their strengths and weaknesses compared to the client
  6. A work schedule in calendar and/or Gantt Chart format
  7. An implementation budget
  8. A list of team members' roles and responsibilities
  9. A description of an assumption or dependencies
  10. A written description of the desired look & feel of the site

The next step in creating a Web site is to decide what the pages should look like, how they should be arranged, and what they should do. This is called the User Interface Design
In order to create a competitive and professional-looking Web site, it is important to have direct access to graphic designers who specialize in designing for the Web. 
Professional user interface designers are skilled at creating an easy-to-use site as well as producing stunning graphics and state-of-the-art special effects. 
Designers work closely with clients to create the desired look and feel and to layout the organizational structure of the Web site. Their design may coordinate with existing collateral or may be a brand new image. 
The User Interface Design should contain all relevant design information and should be writing, reviewed, and approved by the client before proceeding. 
The User Interface Design step typically results in the following:
  1. A Hierarchy Diagram of the proposed Web site, showing the major sections and navigational links of the site.
  2. A Functional Description of each of the proposed sections in the site, describing what users should be able to do and see in that section. If features will be phased in, the time frame/phase needed should be clearly noted. Also, who is responsible for the work in each section should be noted.
  3. A full-color Mock up of the master page and one or two sub pages created in Photoshop and suitable for framing or use in presentations, proposals, promotional or fundraising materials etc.
  4. Electronic version of final design will be viewable online, to scale and in full color. This version will become the working prototype in the next step
  5. Graphical Design Standards to ensure consistency and increase quality. These standards will be machine-readable, to ensure consistent and uniform application across the site
  6. Hand-drawn sketches of the layout of the rest of the major screens on the site. These sketches can be used to simulate user sessions and to verify the functionality and ease-of-use of the site.

The next step in creating a Web site is to make an Online Prototype, which is a full-color, full-scale mock up of the major parts of the new site. The navigation is working, so a user visit can be simulated, but only a minimal amount of programming is done. 
Prototyping allows clients to take their site for a test run early in the process to verify the site will have the features and functions outlined in the planning step. This allows them to make changes early on, when it is much less expensive. This saves time and money, and helps ensure the desired results are achieved. 
All significant parts of the new Web site should be prototyped, verified, and approved by the client before proceeding. 
The prototyping step typically results in an online mock up of the major parts of the new site, produced from the GUI design, complete with:
  1. Preliminary graphics rendered at low-resolution suitable for use on the Web
  2. A preliminary version of the text to be used on the site including labels, headers, directions, and descriptive text.
  3. Buttons and links that work
  4. Screens scaled to fit on a typical user's screen with a minimum amount of scrolling
  5. Code that is compatible with standard Web browsers.
  6. Prototypes can be password protected at a nominal cost, if desired.

The next step in creating a Web site is to create a relational database design for the new site. The database design step typically results in the following:
  1. Data Dictionary - a list of the proposed tables and fields showing the table and field names, the characteristics of the data types, field lengths, table indexes, primary and foreign keys, possible values, if any, etc.
  2. Table / Field Naming Standards - description of the naming conventions used in designing the new tables and fields
  3. Entity Relationship Diagram - a diagram showing the relationships between fields in the tables
  4. Database Growth and Migration Plan - outlines what steps will be taken in the design process to allow the database to grow. To save costs and speed development, the database will be created with Microsoft Access and then migrated to another ODBC-compliant database suitable for use on the Web, as needed.  The database design should be prototyped, verified against the GUI, and approved by the client before proceeding.
The next step in creating a Web site is to identify the business rules to be applied to the each page of the new site.
  1. Business rules are the rules that govern the unique ways a site should work. They could range from calculating shipping costs to determining the closest store to a customer's location.
  2. This step typically results in the following:
    • A complete mapping of the fields on each screen to the fields in the database
    • A discussion and written description of how each field on each screen should work, its size, data type, and access permission

The next step in creating a Web site is to write the code for the site.
  1. This step typically consists of one or more of the following:
  2. Converting HTML files to Cold Fusion files by:
    • adding comment blocks at the top of each file and throughout the code
    • removing superfluous, slow, or erroneous auto-generated code
    • fixing tabbing and indentation, adding application variables
    • renaming the file extensions from *.html to *.cfm
    • creating dynamically included files such as headers and footers, etc.
  3. Programming session variables, client variables, and/or cookies as needed depending on logic
  4. Generating, testing, and installing database queries and output loops
  5. Writing code to generate email alerts on specific events
  6. Programming the logic to calculate values dynamically such as shipping and handling costs, sales tax, etc.
  7. Writing routines that restrict/grant access to various areas of the site
  8. Building customized reports, graphs, and charts dynamically
  9. Developing maintenance screens to enable clients to modify database contents via a Web browser
  10. Writing functions to export information to existing client systems such as accounting, inventory, procurement, etc.
  11. Testing each feature within the Web site
  12. Creating status reports, as needed.  
If you want to grab your viewers' attention immediately with a custom feature such as a multimedia presentation. This is the part of the process when our special effects experts step in. We determine the target audience of your site and come up with an audio, video, animation or Web presentation that will add style to your site.
  1. This step typically consists of creating one or more of the following:
    • Flash animations
    • Virtual reality
    • Streaming audio
    • Streaming video
    • interactive chat rooms/sessions
    • Interactive games
    • Quizzes/Exams
    • Surveys/Polls
    • Guest Books
    • Calendars
    • Registrations
    • Online Catalogs
    • Shopping Carts
    • Image Morphs
    • Image Manipulations (for example, rippling water) 

Once all the features of the site have been programmed and individually tested, the next step is integration testing. 
During integration testing, the entire Web site (end-to-end) is checked out on a test server to ensure that all components are working together correctly. All parties should participate the testing, including the developers, the client, and even some friendly users, if at all possible. 
On customer request, test site may be password protected to ensure privacy. 
At a minimum, at least one week should be allowed to ensure software and system bugs are found before publication, not after.

Once the site has been thoroughly tested, the next step is to publish it so that the intended audience can view it.This step typically consists of the following:
  1. Cleaning up of temporary, experimental, backup, and/or versions of files that are unneeded
  2. Replication of the test site on the official production site
  3. Testing of the production site to ensure that the replication was performed properly and the site is fully functional
  4. On client request, creation of CD-ROM with Web site code, *.psd files, data sources, and any other appropriate files
  5. On client request, grabbing a snapshot the final, installed look and feel of 2 or 3 significant pages from the production site, suitable for use in promotional materials, news releases, proposals, etc.

Once the site has been published, the next step is to begin marketing it, both online and in the traditional media, if this is appropriate.This step typically consists a thorough review of the Online Marketing Plan to finalization the following:
  1. A final description and analysis of the Target Audience, including any new information found during development
  2. An update of the Competitive Analysis Study
  3. An up-to-date Keyword List, sorted and prioritized by major Web site section, to be used to register the site online in search engines
  4. A Search Engine Ranking Report, showing current keyword search results for the high-priority keywords
  5. A final list of recommended Strategic Links and other online marketing strategies, such as newsgroup postings, online press releases, partnering/affiliate programs, rewards programs, direct email campaigns (opt-in only), banner ad recommendations, etc.
  6. A up-to-date plan for Integrating online marketing with traditional marketing/advertising
  7. An Initial User Feedback Analysis, to identify and implement changes needed immediately
Once the Online Marketing Plan is finalized, one or more of the following should be done at least once a month, but usually more frequently, depending on client needs:
  1. A Web Site Traffic Analysis, showing current user traffic levels, comparing current levels to past performance, and using this data to recommend marketing and Web site design changes
  2. Web Site Optimization to maximize the effectiveness of the search engine registration
  3. Search Engine Registration based on the keyword list and prioritization
  4. A Search Engine Ranking Report, showing the resulting rankings for the high-priority keywords

Once the online marketing has begun, the next step is to schedule a Project Review and Planning meeting to do the following:
  1. Recap how the project went from the customer perspective and in relation to our project methodology; identify areas for continuous process improvement
  2. Determine what level of support and maintenance is desired for the site. If appropriate, develop a Maintenance Agreement for relatively simple changes that should be done right away.
  3. Plan the scope of the next phase of the Web site. If appropriate, develop a preliminary plan for implementing more complex changes and/or additional features and functionality that will be done offline as part of the next release
This meeting should be attended by the key employees of the customer, the UNETY project manager, and the sales representative.