RDI Meeting - February 8, 2008
Present: Geoffrey, Stéfan, Shawn, Lian, Susan, Peter
I (Geoffrey Rockwell) have updated this with my notes.
DEEP
- Shawn presented Scenario 2 for Story 1
- Shawn is using OverSite software to assemble wireframes. Shawn should like to note that this software is very barebones. Athough quite good on keeping one on track for process, the GUI sucks and the clickthru's generated are not very visually pleasing. This limitation prevents the user from reflecting too intensely on the finished interface and forces instead on thinking through screen content rather than fine-tuned interaction. Maybe good at this stage. I am a little frustrated by it, but ranting helps
- We need to spend some time thinking about our object model (see next meeting notes)
- Ways in which the workflow might be managed: fully graphically vs. purely code-based. (See below)
- When and how often would these workflows have to be editted
- What can we actually do?
Workflow
We discussed ways of presenting workflow:
- It is programmed by a programmer in Java or PhP.
- It is an XML file that can be used by jBPM (JBoss?)
- It is programmed, but there are some GUI Administrator functions that can be done.
- An slip approach where action slips are added through a dialog box
- A graphical programming environment.
While it is important we represent in wireframes and graphic designs the ideal, for the prototype we will probably have to hard code (1) a particular workflow.
--
ShawnDay - 11 Feb 2008
