Ok, thank you. Now I understand what FLiP is, I didn't realize it was the entire development process. I was thinking it was a different way to design, other than, what I call, the standard development cycle of a fusebox application.
Thanks again, Don -----Original Message----- From: Anthony Cooper [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 4:29 AM To: [EMAIL PROTECTED] Subject: Re: Process Timeline Planning I haven't seen a definitive guide but a couple of things I have read are at: Lee's Page - http://www.bjork.net/index.cfm/fuseaction/content.display/page/flip.htm FuseWiki - http://64.225.94.183/cgi-bin/fusewiki?FLiP Hope they give you a brief outline. Ant ----- Original Message ----- From: "Donald Pavlik" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 08, 2002 11:43 PM Subject: RE: Process Timeline Planning > Can someone point me to some information about FLiP? I am not sure if > I am currently using it or not, but I want to make sure I am or am not. > > Don > > -----Original Message----- > From: Paul Schmidt [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 08, 2002 2:53 PM > To: [EMAIL PROTECTED] > Subject: RE: Process Timeline Planning > > > Jeff, > > since I?m working on projects using FLiP I found out that the > prototyping phase actually needs the most time effort. For some > customers prototyping means not only to work on a front-end, like > Steve would say, but to communicate with the provide in a very > critical phase. Having that in my mind I realized, that this IS the > most important project phase. > > Within our last FB3 project in which we were using Hal?s MVC adoption > very efficiently, we spent 2 weeks on prototyping and 1 week in > development including testing. Before getting the lead I made a > wireframe, describing the flow of about 60% of the whole application. > That took 20 minutes. > > With that wireframe and the business specifications of the customer I > created a MM (using Visual Mind). After that we began with > prototyping. I have to say that the customer did a real good job > within that phase, because he really USED the prototype/devnotes very > efficiently. > > After that 2 weeks in prototyping (gotta get HTML programmers, huh...) > we began with 2 men developing the app. In that phase we actually did > not finish up the fusedocs first. One wrote the fusedocs and the other > one did the coding and testing right after that. We saved allot of > time doing it that way and it did not affect quality. Not at all. > > Hope this helps a little - for more details you can contact me off > list and ask more specific questions... > > > Paul Schmidt, > Infusion Networks > > -----Original Message----- > From: Jeff Chastain [mailto:[EMAIL PROTECTED]] > Sent: Montag, 8. April 2002 18:20 > To: [EMAIL PROTECTED] > Subject: Process Timeline Planning > > How does anybody do process planning or scheduling for FB apps? Hal > mentioned in a recent class that the vast majority of time was spend > in the prototyping phase, but I was wonding if anybody had anything > more specific. > > I may be asking an impossible question (since the prototype depends on > the client and the back-end number of fuses etc. depend on the > prototype) but managers tend to ask the impossible, so I thought I > would ask. > > Thanks for any input. > -- Jeff > > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
