Sequence Diagram

     Sequence Diagrams are typically used in software engineering
to visualize a work flow of the steps that take place when one
or multiple types of users interact with the system. Well, that
is just what we have here. I outlined a general interaction between
a VJ and Performer user and the system.
     It was not too many years ago that I failed a software engineering
test horribly by drawing the wrong type of diagram altogether as
my response to an open ended (dreaded blue book) question.
Apparently, it was not worth "partial credit". (unless 0% is counted
as a part)
      Anyway, I guess I was not completely soured to their usefulness
for this stage in designing a software. This is a necessary step in
in defining the classes for my UML Class diagram. I picture here a
broad view of the larger Manager and Controller classes that will house
instances of the various types of nodes. I did not want to have this diagram
looking at the finer granularity of the Manager classes sending updates
and configuring individual instances of AudioNodes, TrackingNodes, etc.
This would have made the diagram even more exeedingly difficult to
understand. This way of understanding the system as a set of Input
Conroller and Node Manager Classes that talk to one another is a
bit more straightforward. The place to model the nitty gritty aspects
of the system down to specific parameters and data types would be
the Class Diagram (to be created soon).


Sequence Diagram

Publish at Scribd or explore others: uml diagram

Paper Prototype (Part 1Revised)

This is a more completed Paper Prototype example.
It goes through the steps you would need to set up the
system to begin using it. The use-case does not by any means
explore every feature described in the Feature Document. This
would probably take 15 to 30 minutes worth of Stop motion video
(like this one) to properly explain each possible usage.
It does, however, visualize the steps for using a combination
of high priority capabilities of the system. This, in a sense,
demonstrates a more realistic picture of what may be accomplished
within the scope of this thesis project. IE. I may not be able to
implement every feature described in the Feature Document, but
I should aim to, at least, complete what is shown in this Paper
Prototype demo completed in some working sense.

[----------------------------------------------------------]
[ ----- Removed from web to reclaim space------ ]
[ -------- Please see the latest version ------------ ]
[----------------------------------------------------------]

Paper Prototype (Part 1 Draft)

The first section of the Paper Prototype has been posted (with some mistakes).
This needs to be refined and have the rest of it completed.

If nothing else, at least the general idea is coming together.

[----------------------------------------------------------]
[ ----- Removed from web to reclaim space------ ]
[ -------- Please see the latest version ------------ ]
[----------------------------------------------------------]

PaperPrototype (hardware)

The Hardware portion of the Paper Prototype is complete
(for the most part - missing the MIDI Keyboard yet). Next
I will need to make the sample visuals to clip into the
3 Ring binder "stage" area. Also, I will need to create poster
board cut outs of how the user interface will look. This
step should be pretty straight forward as I can follow the
diagrams that I created for the feature document.
I will then be able to film a stop motion of interacting
with the system. I can cut back and forth between the
reacTable interface, how this is being changed, and then
show how the stage visual has changed. I will have all of the
visuals in the correct order in the binder to follow along
with the interface usages that I am demonstrating.
A visual script of this whole process will have to come
as a natural result of creating the Paper Prototype video.
I can create the video simply based on loose notes, but the
more official script can be finalized as I complete the final
demo video.
PaperPrototype(hardware)

Publish at Scribd or explore others: Academic Work online software

Feature Description (Revised)

Ok, I have a complete and revised version of the feature doc up as promise.
To do a "story board" equivalent for this type of project, I think it would be
best to create a Paper Prototype (here is an example of what that looks like).
Basically, I will create the physical and user interface components of the
system out of foam core, poster board, etc drawn on with colored pencil.
I will also haveprint outs of what some of the visuals might look like to
represent the final projection. I can then write a script to follow to show a
use-case of a user interacting with the proposed system. While I act this out,
I can also take still pictures to later assemble it into a stop motion
demonstration. This is the plan (that and write the research paper).

1.3 Feature Revised)

Publish at Scribd or explore others: 2008 history