Is Douglas Reynolds Consulting – providing Web application development services using Adobe technologies. Participates in development teams to provide ColdFusion, Flex/ActionScript, and AIR solutions. Was member of development team providing ColdFusion, Flex/Actionscript, AIR, and RoR solutions to financial organizations. Founded onFocus, a small business-centric design/development house. Has contributed to documentation development for the cfEclipse open source ColdFusion plugin for Eclipse. Is a member of the PDXRIA user group. Thinks that Twitter is a way of life.
Proposals for this user
One of the best ways in which to coerce the needs out of a user is to use an iterative prototype development methodology which is flexible enough to allow us developers to quickly build functional prototypes that can be changed to meet users newly defined or changing needs in an agile manner. When working with data this can be a complex process as data may not exist, we may not know what the back-end technologies will be, and we might not want to get locked into any particular schema. Still we would like to interpret a user’s needs and develop a prototype which gives the user the ability to ‘play’ with the application and manipulate some data, getting some feedback from the application along the way. In return, most users seem to be able to better define their needs using functional prototypes and can provide better needs information to developers. So the question arises, ‘How can I develop a functional data-driven application prototype in Flex without needing to know, well, anything about the back-end?’ The answer may be found within the Cairngorm Microarchitecture.
|Cooking||2009-04-03 19:20:39 +0000|