[Sigia-l] iRise

[CD Evans]

I like the idea of this application, and I really like the wireframe 
rocks for a brand. I'm having a hard time seeing the demo on my 
design computer or finding a working beta on the site though. Anyone 
seen a copy working?

I think I can speak for quite a few of us when I recommend to to the 
company that they get a beta or demo copy up quick, or there is going 
to be a lag filled with unanswered questions where we could have 
discussed these things in this group.

All in all, the software looks like a plus for the market it's 
designed for. As an aside, a dynamic interface taxonomy might be a 
strong selling point for future release compatibility. I've 
recommended dynamic language to a few clients thus far.

CD Evans


>Simplicity leads to abundance.
>
>--__--__--
>
>Message: 6
>From: "Samantha Bailey" <a2slb at bellsouth.net>
>To: "sigia l" <sigia-l at mail.asis.org>
>Date: Mon, 8 Dec 2003 23:44:02 -0500
>Subject: [Sigia-l] iRise
>
>I meant to cc the list with this reply, in case it's of interest....
>
>>  What problems were you having that you think iRise will solve?
>>
>>  ----
>>  Ziya
>
>
>Several things. First, we will be able to import business requirements from
>Requisite Pro and we will be able to map requirements to interface elements.
>We work in a distributed environment with multiple stakeholders and we've
>had a lot of difficulty with business requirements changing mid-stream and
>while there isn't any software that can stop *that*, we do think that having
>the ability to share info. between the software our project managers use and
>the software we'll be using will lead to more consistent documentation.
>
>On the subject of documentation, we also think that this software is going
>to help us cut down on the time it will take us to develop functional specs;
>right now we tend to do functional specs haphazardly and often after the
>fact and it should be easier to work on the functional specs as we go along
>with iRise.
>
>iRise generates "functioning" prototypes from wireframes and that's going to
>cut down on our time between developing our wireframes and running our
>usability tests since we won't have to develop the prototypes separately
>(although I think our wireframing is going to be slowed down, due to both
>programming logic into the wireframes and to doing more spec documentation
>along the way).
>
>Those are the biggies.
>
>sb
>
>Samantha Bailey
>samantha at baileysorts.com | http://baileysorts.com