Functional Architecture

Also known as Information Architecture, this diagrams the flow of information into and out of the application. The key deliverable with this service are use cases. A use case describes, both visually and textually, the interactions a user has with the application. Each task identified in the Business Requirements is drawn out and detailed showing the user actions from start to finish. A user can be both a physical person like a customer or a system like an email server. With this level of information, key stakeholders will have an accurate description of how the application will operate. This business document also provides development with great amount of detail ensuring that the end product meets the business need. A site map is also provided for a high level overview of page and application relationship.

Web Design

Visual design is critical for leaving a lasting impression and increasing application use and efficiency. To ensure brand consistency, all elements of the brand must be considered in the design - tone, color, typography, photography and logo usage. If a company style guide exists, we will utilize it. If one doesn't, we can create one for you - one that will accomodate different mediums, not just the web. We will understand your business, existing marketing collateral, and future plans and create a visual style that will leave your customers with a lasting impression.

A great design isn't just nice to look at, but it is also functional. Our designs are engineered with the user in mind. They are accessible, quick to learn and highly efficient. By utilizing the latest in technology, our designs never sacrifice the best of user-centered design principles (direct manipulation, affordance, consistent idioms...) to deliver a highly relevant and superb experience.

Technical Architecture

This level of design is more technical in nature (as the name implies). It consists of class diagrams, network topologies, server architecture diagrams and database schemas. It's critical that these requirements are developed by someone who understands the business and it's future plans. Without this level of understanding and "business sense", an architecture can quickly become cumbersome and rigid as the company grows. Even worse, you may find that the application simply won't scale and will need to be re-developed.