Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

User Interface Design

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search

Content Model Relationship

Contents

Activity: User Interface Design

Objective

The User Interface Design activity defines the front-end interface in which in user will interact with the information system. It is a separate activity from the Business Intelligence Design as it is specifically focused on the layout, information access and information presentation.

Like the Collaborative Framework Design activity, it is part of design phase, but should be kept very interactive with users and prototyping-oriented. The goal of the design is not to produce a lengthy design document, but instead a translation of business requirements and the overall architecture into a solution that can be quickly prototyped and then implemented as a working system. Although the design can take place rapidly, it should make use of the architecture framework, Information Standards and Information Governance Policies defined earlier in the project. Web Design Standards should also govern the user interface layout.

This activity is explained below in a fashion that assumes a web-based interface.

Major Deliverables

  • Interface for a user-driven collaborative system
  • Prototyped user interface

Tasks

User Interface Layout

Objective:

This task defines the overall approach for how the user will interact with the system. It is effectively the conceptual design for the user interface. At this stage decisions may also made on the appropriate technology to be used for building the interface. This builds off the baseline defined in the Technology Blueprint and existing Information Standards and Information Governance Policies. The user interface conceptual design also makes reference to existing user interface standards.

This task may be moved into the Solution Architecture Definition/Revision activity.

The Conceptual Design will often involve the creation of a mockup interface.

Input:

  • Detailed Business Requirements for Increment
  • Overall Blueprint Architecture
  • Solution Architecture Definition/Revision


Output:

  • User Interface Layout (Wireframe Design)

Website User Interface Design

The website user interface design defines how information will be presented back to the user. It includes definition of:

  • Web Site Structure and Navigation Path
  • User Interface Layout
  • Website usability design
  • Overall Blueprint Architecture
  • Solution Architecture Definition/Revision
  • Collaborative Framework Conceptual Design
  • Frontend Engineering

For information-centric system, the focus is on how users will be able to visualise information to make business decisions from large amounts of information that is returned.

Input:


Output:

  • Website User Interface Design

Web Content Design

Web content design defines the content that will be made available on the website. The includes content in web pages and digital assets such as brochureware.

Input:

  • Detailed Business Requirements for Increment
  • Overall Blueprint Architecture
  • Solution Architecture Definition/Revision
  • Collaborative Framework Conceptual Design


Output:

  • Information Delivery Design

Information Access Design

The Information Access Design task defines how users will access information through the front-end system. This includes the design of the query mechanisms and criteria used for information access as well as how any query information can be modified by the user. This task relates to "thin" information access such as Search or to the design or the initial front end of a BI system. This task also covers the Data Re-Engineering processes that happen interactively with the user and are commonly applied for Search, such as lemmatisation and spell checking are applied through a user-driven interface.


Input:


Output:

  • Information Access Design

Site Optimisation Design

Site Optimisation design involves optimising the site for performance reasons through the use of SEO techniques. It particularly focuses on how users can most effectively find the site (if applicable) through the public web through the user of keywords. It also involves overall performance improvement of the site.


Input:

  • Detailed Business Requirements for Increment
  • Collaborative Framework Conceptual Design


Output:

  • Information Delivery Design

Site Analytics Design

Site Analytics Design involves monitoring the performance of the site and how effectively users are making use of content. It may, for example, analyse clickstream data of users through the site to determine entry and exit points, most valuable content and variations in content based on user segmentation.


Input:


Output:

  • Information Delivery Design

Core Supporting Assets

Yellow Flags

Areas to look out for include:

  • Strong resistance from the organisation to follow prototype-based development techniques
  • Poorly formed information standards and policies, especially those related to security and information sharing

Key Resource Requirements

Wiki Contributors
Collapse Expand Close

View more contributors