The IRM2 Guiding Principles, Part I
In the process of redesigning IRM 2, I’ve been developing a list of principles of what IRM 2 is about, and what the interface should present to the user.
- Normal users should not feel intimidated: The problem reporting section of IRM should be as fluid and easy to use as possible. This is not bugzilla.
- IRM 2 should be extendable: The old single function computers with its fixed fields is a thing of the past.
- IRM 2 should be clean: A lot of functionality in IRM 1 could be boiled down to a kludgy hack. While this improved under subsequent releases, it wasn’t clean.
- And more…. I’ll be adding more, but also feel free to suggest more principles.
