Forgot your password?
New user?
Document Actions
UserExperience
Category: Development tools, Project management
—
Other products by this author
Current release: UserExperience 1.0.0
Released Feb 19, 2007 — tested with Plone 2.5.2, Plone 2.1.2, Archetypes 1.4, Archetypes 1.3.6, Zope 2.9, Zope 2.8
Initial public release.
Experimental releases
There are no experimental releases available at the moment.
Project Description
- Project resources
Releases
Issue trackerThis Plone product has been developed by Atopia to document User Experience of an application in terms of Actors, Use Cases (or User Stories) and Screens that hold Wireframes. Navigation between Screens is stored and offered per Use Case so that it is possible to simulate use of the application in the conceptual or early design phase and later as a reference test phase.
Per User Experience object, one can add Actors and Use Cases and connect the two with each other. A User Experience can also hold a collection of Screens which are simple wireframes (by default a Plone Wireframe) or an image which contains a wireframe or a screen mock-up. The power of this product is that one can choose an initial Screen for each Use Case and also for that particular Use Case can model all the allowed navigation of that screen and possible next screens. In this way one can re-use Screens in different Use Cases which saves a lot of work.
When a User Experience has been set op, one can, of course, navigate to all the added objects, but it is also possible to navigate to the Use Cases for a particular Actor and to to all the relevant Screens for that particular Use Case. As an extra also the entire Navigation of the Screens is provided in a graph.
This product is powerful and easy to use for documenting concepts and designs and especially reusing Screens in different Use Cases which is more valuable that just a stack of mock-ups. The design or User Experience can be verified with the client and they can even simulate (with or without help) the entire use of the application which is going to be build. When all requirements have been discussed with a client and kept in this product, this documentation can be used for developers to start working with and, more important, it can be used while testing because this is the documented experience which the client as a user has been able to test over and over again and eventually initiated the actual development of the application.
So let there be more clarity in the expected User Experience for client, sales person, project manager, developer, tester and all others involved in application development.
This product has been developed with ArgoUML, ArchGenXML, custom Plone Archetype and Page Template development.
Todo
- Make integration with graphviz.
- Have attribute Wireframe of class Screen use DefaultWireframe of parent class UserExperience.
- Do not rename objects of class Actor, Usecase, Screen or Navigation because of known Plone bug http://dev.plone.org/plone/ticket/5775
