'wireframe' out an app. Once the clients like it, we jamm out some
code under the premise of 'requiremnts will change' .
DK
On Wed, 13 Oct 2004 14:12:10 -0400, S. Isaac Dealey <[EMAIL PROTECTED]> wrote:
> > HI,
>
> > Does anyone on this list use the FLiP Methodology. I was
> > wondering exactly
> > what this is and what the benefits are of using it.
>
> > Thanks
>
> > Mario
>
> > <http://www.houseoffusion.com/banners/view.cfm?bannerid=3
> > 6>
>
> It's a step-by-step process for taking programming project idea from
> concept to completion which has been built primarily around Fusebox.
> Some of the middle bits (identifying circuits & fuses, etc) could be
> swapped out for any other given coding framework. The surrounding bits
> primarily involve requirements gathering and suggest that the
> application should be wire-framed and that the look and feel should be
> completed before a single line of code is written. Once that's done
> the clients sign off on the look and feel and the desired
> functionality -- they can (and will) make changes after they sign off
> on it, however, with proper documentation they pay higher fees for
> changes made after this point. The whole idea really is to streamline
> the non-coding portion of the work, to improve communication with
> clients and thereby improve client satisfaction with the finished
> product.
>
> s. isaac dealey 954.927.5117
>
> new epoch : isn't it time for a change?
>
> add features without fixtures with
> the onTap open source framework
> http://www.sys-con.com/story/?storyid=44477&DE=1
> http://www.sys-con.com/story/?storyid=45569&DE=1
> http://www.fusiontap.com________________________________
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
