 |
| |
Skills used |
 |
research |
|
information
architecture |
|
prototyping |
|
problem
solving |
|
standardisation |
|
HTML / DHTML javascript |
|
Mindmap |
|
|
|
| at a glance |
Duration
13 months |
brief
design
a market-ready software development suite. |
objectives
reorder the information architecture, for logical
access to applications / functionality and increase
ease of use.
improve the visual presentation of the large amounts
of complex information stored within the system. |
main
innovations
devised
and implemented a complete prototyping process that
was so successful it later became a stand-alone
application: epiodesigner.
|
|
|
|
|
|
|
|
what is it? |
| |
a software development
suite. Epionet's powerhouse suite of ebusiness application
development and administration tools.
|
|
what does it do? |
| |
epiowave V2 is essentially
a developer tool which orchestrates the production
of web-based applications. also it can:
Design, develop and deploy enterprise business applications
faster and more cost-effectively.
Increase the capability of web development teams.
Break down communication barriers between business
users and technologists.
|
|
the brief |
| |
while the original epiowave
system EpioRADD V 1.6 boasted groundbreaking technology,
after 3 years hard-core technical development the
system was quite raw and unwieldy. the brief was
to transform this system into a user orientated
market-ready software suite. |
| |
|
|
the solution |
| |
epiowave V.2.0 the market
ready software suite for developers and enterprise
organisations the result of a vast interaction design
project lasting over 13 months that achieved the
the goal of transforming the product to a user orientated
finished suite. |
|
my involvement |
| |
as a senior member of
the epiowave V.2.0 team, I worked in conjunction
with interaction, usability and graphic designers,
developers, systems architects, management and sales
in co-ordinating and implementing the V2 project
from the set-up stage to completion and market release. |
|
How was it achieved? |
| |
The first step was to
start from first principles by analysing the information
architecture of EpioRADD V 1.6 system. looking mainly
at how the applications were structured, what functionality
was contained within each application, whether there
was a more logical place for that functionality
in another part of the system.
In order to make these decisions we first needed
to better understand the processes of developing
applications this meant a detailed developer brief
for each part of their process. also extensive user
testing and recording of this information. In some
cases complete applications were merged and stripped
down, without losing any functionality.
|
|
|
|
|
|
email 
01
02
03
04
05
06
