 |
|
The UI Architect's role is to construct and implement the technical design for an organization's use of web technology to accomplish the company's organizational objectives. This includes the selection of Web Applications, Hardware, and Software Platforms even Designing and Implementing the application framework. The UI Architect is also responsible for ascertaining system volume and analyzing traffic patterns for hardware optimization. Exceptional knowledge of various Web development languages, platforms and hardware is essential.
|
|
| Human Computer Interaction |
|
A pragmatic approach to interaction modeling is presented by which a designer can describe how the user gets tasks done with a newly developing system. The notation proposed allows an interaction designer to make explicit both how user actions cause visible or noticeable changes in the state of the machine and how the user is expected to use this feedback to generate the next action.
 Read More About Human Computer Interaction |
|
| Competitive Review and Gap Analysis |
|
Provides a baseline of an organization’s key competitors’ web sites related to features and functionality.
Read More About Competitive Review and Gap Analysis |
|
| User Experience Brief |
|
Defines the characteristics of online users and how they will use the Internet to make choices among brands. This document helps determine which online imagery, content, and features are the most relevant, compelling, and appealing for the outline audience in representing the client’s brand.
Read More About User Experience Briefs |
|
| Target Audience Personas |
|
Guide the design of the site architecture, as well as the creative approach and execution. A persona represents a group of target audience members who visit a site and identifies their interests and abilities.
Read More About Target Audience Personas |
|
| User Experience Concepts |
|
Used to crystallize the key messaging, positioning, essence, and user experience that will be associated with the proposed brand concepts.
Read More About User Experience Concepts |
|
| Feature Descriptions |
|
Provided in a document and are based upon client requirements and ideas, internal brain storm sessions, and any research that has been performed.
Read More About Feature Descriptions |
|
| Feature Set |
|
Provides an overview of features to be executed, including assumptions such as number of pages, source material, level of Vignette involvement, and whether images, workflows, or wireframes are required.
Read More About Feature Sets |
|
| Conceptual Map |
|
The initial visual representation of the relationships between the categories, and the content areas of the site. The conceptual map is used as a springboard for developing the site map and serves as the initial grouping of like objects and ideas.
Read More About Conceptual Maps |
|
| Content Audit & Analysis |
|
Is the result of an assessment of the client’s current content assets with a focus on each asset’s relevance and relationship to the client’s brand strategy. This document typically includes cataloging of information groupings, copy concerns, gap analysis, redundancy listing, style enhancement, and hierarchy of information. A detailed overview of static and dynamic content elements. The purpose of the matrix is to link the different content elements with the overall design and technical architecture of the site.
Read More About Content Audit and Analysis |
|
| Content Outline |
|
Provides a clear overview of what information will be on each page of a website and where that information is coming from.
Read More About Content Outlines |
|
| Site Map |
|
Provides a visual representation of each page of the web site and the logical flow of navigation between them. It also denotes functional features, and levels of navigation including primary, secondary, tertiary, utility, and footer.
Read More About Site Maps |
|
| Wireframes |
|
Provide the skeleton of navigational and content elements. Final wireframes provide a refined framework of each page level on which the User Experience team can build the site look and feel.
Read More About Wireframes |
|
| Work Flows & Process Flows |
|
Describe in detail key functions users will perform. Workflows record steps that target audience members must follow and the functions associated with each discreet task. Mapping interactions ensures the target audience experiences a logical flow during the process.
Read More About Work Flows & Process Flows |
|
| Design Concepts / Look and Feel Options |
|
Are developed in a variety of styles to provide the client with options to choose from in deciding how the website should look to the end user.
Read More About Design Concepts / Look and Feel Options |
|
| Variation Designs |
|
Illustrate the look and feel of designs that vary from the basic homepage and secondary page designs.
Read More About Variation Designs |
|
| Style Guide |
|
Provides a summary of the product or web standards that guide the User Experience team during development, including site design standards and page styles.
Read More About Style Guides |
