On Thu, 3 Mar 2005 23:40:49 +1000, Barry Beattie <[EMAIL PROTECTED]> wrote: > hi all > > for Mark Jen-type reasons, I have a "hyperthetical" question.
I know you typed english then - yet i have no idea what that line said :) hehehe > Say there's a decent-sized app to make. A couple of years worth. Say > that part of it, about a third, is to be developed off shore. > Basically one big module. Probably by a J2EE dev shop that would > branch out into CF. Hmm.. big app eh.. i can take an *educated* guess as to what it is ;) > > Now, if the locally-built part is about a third finished when the > offshoring starts, and has been developed using it's own "home-grown" > MVC-type framework with heavy use of DHTML UI components (and > mark-up)... > > (here's the question) > > ...what initial steps should be done to ensure as few integration and > support heartaches as possible? What issues should be considered? Its like asking if you offshore LEFT part of a bridge and you build the RIGHT part, what planning has to be done in regards to making the two ends meet? No? You would all have to have totally clean seperation at both ends and the joiner would have to be neutral territory for both. I personally would recommend you look at preliminary source management, in that at each step of the way test to make sure each module is infact totally blackboxed because the moment each component starts having tenticals - and if no communication is present - you could wind up having a hybrid system that goes from one plane to another (ie like doing 30% of an app in ASP and the rest in CFMX). > Obviously, because this outsourced module will need in-house support > (eg minor bug fixes and changes after sign-off), the documentation > (all the way down to code comments and variable/method naming) needs > to be up to scratch. > > anything else worth worring about? Just your job if it all goes pair shape hehehehehe.. I would totally approach this with kitten gloves as it only takes one rogue developer to build something important and you could end up being a house of cards. As long as you detail what is expected in both API's and Integration rulings you should be able to get away clean. Again if you adopt MVC, each letter part has to be cleanly seperate from one another - aswell as mini-blackboxing? > thanx > b > > PS: even Oracle-type "follow the sun" development may be a possibility. -- Regards, Scott Barnes http://www.mossyblog.com --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
