I can't possibly imagine what takes 24 hours of meetings a week to redesign... I'm sure the process isn't being done as efficiently as it could be - (I blame middle management already).
(Insert cliché about broth, chefs, spoiling, etc).
There are a lot of use cases when redesigning the UI for consumer applications, particularly when struggling to meet the demands of an audience that is primarily in their teens yet still seeking to please the adult executives who arguably constitute the most important user base (because they lay off those of us who fail to please them).
Ah, yes, I know what you mean.. I was once involved with a games development platform, and they had almost 1,000 use cases - I quit the company shortly after all that nonsense started - And the project flopped because the three companies involved were trying to overdefine everything. (And one of the companies didn't understand games development).
I think use cases are okay - Although I rarely use them - on the automation systems I work with these days I have generally about 4 use cases.
The problem with use cases is that they're a bit too finite and too "boxed-in" sometimes. Someone needs to come up with use cases that are more flexible and cover more scenarios - I use currently use Cmaps to capture my requirements and use scenarios - I hear cmaps are gaining quite a lot of popularity in the education sector for knowledge managment.
Well, when a product has 53 million active users, you can't really skimp on spec'ing out the use cases with something as high-livel as cmaps. Every possible path through the user interface needs to be tracked and documented so it can be thoroughly tested. Any time your user base is in excess of a million people per day, you are guaranteed to hit fringe states that otherwise might be ignored. Besides which, as I mentioned, trying to please all fifty three million people means complicating the user interface rather than simplifying it... It is that deliberate overcomplication that requires so many hours (and people).
Comments 11
(Insert cliché about broth, chefs, spoiling, etc).
Reply
Reply
I think use cases are okay - Although I rarely use them - on the automation systems I work with these days I have generally about 4 use cases.
The problem with use cases is that they're a bit too finite and too "boxed-in" sometimes. Someone needs to come up with use cases that are more flexible and cover more scenarios - I use currently use Cmaps to capture my requirements and use scenarios - I hear cmaps are gaining quite a lot of popularity in the education sector for knowledge managment.
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Have a good day!
Reply
Use the easy button.
Reply
Leave a comment