Tona this looks great. I wonder if there is more that we could do to clarify confusing areas like the dexterity section. It feels to me that some of the points might be related as sub-points if that makes sense. I think we probably are also at a place where we need to think about how to get this out to a pretty broad community to get a lot of feedback -- what do you think?
Best, Jess On Nov 26, 2012, at 11:20 AM, tona monjo <[email protected]> wrote: > Hi Jess, > > As we commented last week, I've been working on User States & Contexts, > specially on its visual representation, trying to transform it into what > could become a powerful tool in requirement analysis and design. > > As you will see, the goal in the last page is to have a representation able > to communicate all requirements for a given case (or an application), so it > could work as a map of needs for a design. > > Sure it can be greatly improved! Please let me know you thoughts. > > Have a nice week! > > Tona > <User States & Context_diagram.pdf> _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
