To Do
The following list provides a list of research and/or tasks we are currently working on and/or need help with.
Important
- Get real-world case studies (e.g. try using real-world projects and share our experiences and/or models)
- Make rules more concrete (e.g. when to use circles, boxes, etc.)
- Add support for aspects?
- Experiment using Agile Draw on tablets and/or for remote collaboration (eg. using Mimio)
- Determine scope; do we include lower-level stuff like inheritance? interfaces?
Other
- Tie with other well-respected works of others - In addition to what's already been defined on the Complementary page, tie with others such as Domain Driven Design (Eric Evans), Patterns of Enterprise Architecture (Martin Fowler), Past (Yourdon, Chen, Coad, Booch, etc.), and others (e.g. High Assurance Design by Cliff Berg)
- Bounce this idea off of online groups, user groups, etc. to see response
- Conduct polls (similar to http://visualpatterns.com/polls.jsp) and surveys
- Scripting language to generate Agile Draw diagrams. Use this for import/export and copy/paste as text (and also running as automated script? not sure of value of the automated part). Use XML Metadata Interchange (XMI)?
- Research psychological meaning behind shades, shadow, 3D, ec. -- what emotions do these convey?
- Dynamic web apps need written - enable users to cast their vote by picking shapes, colors, icons, shades, etc.
Dynamic model (submitted by Dan Malks)
- Question: Noticed there were no dynamic models currently? Did I miss one? Is it out of scope? -dm
- I find simple, high-level interaction diagrams, such as sequence diagrams very useful to show interactions.
- On a secondary note, I think this could also lead to an informal use of something similar to Ambler's interaction overview diagrams (a variant on UML's Activity Diag)...these style diags may be a bit too much for Agile Draw, but at the same time, it's pretty intuitive. Here's an example of one:
Other
