A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.
I am a little desperate.
I have to write a Style Guide for an existing Software. I haven't heard anything about UI-Design and so before.
Well I googled and tried to teach myself. The problem is that everthing I found was about "stick to the real world" so "everybody" will be able to use your Software.
But I work on a tool to design and build a SCADA system (e.g. for running a power plant). There will be hardly more than 1 or 2 dozen developers using the tool.
Atm we use this tool ourself (not more than 10 users, most of them developed the tool themselves), and we know how things work. But if we want to sell it there should be some kind of consistency.
So my question is: does anyone of you know good literature (online or offline) about how to design Software for "power users".
Thanks a million in advance,
Power users. Hmm. Write em a script language instead, or make it command line only.
Otherwise, use UI the standards for your target platform which are usually published and freely referenceable. Writing your own from scratch is a thankless task, expecially with no UI experience.
Two pieces of advice:
Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces (Morgan Kaufmann Series in Interactive Technologies)
by Carolyn Snyder
-->Great read on how to define and refine a UI fast.
User Interface Design for Programmers
by Joel Spolsky
-how to do UI, simple and sweet
Tuesday, June 28, 2005
First 9 chapters of the Spolsky book are right here:
Say no to kilometer-long URLs!
Alex from the Horizontal Scrollbar Police
Tuesday, June 28, 2005
I have a little experience with this (I used to develop simulations for power plants, including the control systems).
Use general good UI books. For example, I like Developing User Interfaces for Windows by McKay. Search on Amazon for others.
Think in terms of common tasks. Get very specific. Come up with a paper design and watch people work to see where the hangups are.
- Import a list of all sensors (ID, description, min, max, units, alarm settings, etc.)
- Add a turbine to the main control page.
- Add a temperature alarm to change the turbine color.
- Add a touch point to go to turbine details.
- Check which sensors are not used in the SCADA
By looking at specific tasks, you'll think of more elegant ways to perform each of these and other tasks. The books will just give you a pallette to work from.
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz