@Michael it is an honor to me reading this from you. The form of this document [1] is based on a writing structure I have learned in the University which can be found throughout business plans, scientific theses or project plans ... etc.
The structure is like this: *1) Analysis* Describe the current state from an objective point of view *2) Evaluation* Evaluate the positive and negative things you see in your subjective point of view *3) Goals* Goals can be seen as a subset of a roadmap in our project in which you can define goals you would want to achieve in future. *4) Alternatives* Set up ways how to achieve these 3) Goals. As a simple example: Assume you want to get to Rome in Italy. There are many possible ways to it. By flight, by car, by foot ... etc. *5) Checkup* Test if you have reached these 3) Goals ... for example with JIRA tickets, or make a checkup if you have reached the goals that were defined in a roadmap. *6) Vision* A vision differs from 3) Goals because you cannot define precise 3) Goals for it, but, they are needed to have them, because, future 3) Goals could emerge out of it. Hope, this helps someone structuring his or her mind for Apache Flex :) [1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex -- Sebastian (PPMC) Interaction Designer Looking for a Login Example with Apache Flex? Please check out this code: http://code.google.com/p/masuland/wiki/LoginExample On Tue, Jun 4, 2013 at 3:33 PM, Michael A. Labriola < labri...@digitalprimates.net> wrote: > > >IMO ... Apache Flex needs an MVC framework out of the box ... may it be > Parsley, Spring AS or Swiz. I'd call it then "Apache Flex MVC" framework. > >Having that would bring more stability to the our Flex market. More > information can be found here [1]. > > >[1] https://code.google.com/p/masuland/wiki/WhatsWrongWithFlex > > While I don't necessarily agree with all of the conclusions, I think this > is really well done. You do an excellent job of building your point and > organizing information. It would be an interesting format to help justify a > lot of tech decisions. > > Just my musings, > Mike > > > >
