I think we are in agreement. As I'm working for the leading OO company in Japan, so we promote OO in application software development.
The argument I'm trying to make is that I could consult users who do not have deep knowledge of OO to yet produce usable OO classes by using tools and guidelines. I just think of it just as another technique in a toolbox and do not recommend using it in every circumstances. As was pointed out, it is preferrable if every developer learn OO. Moving on with the discussion, I was wondering how much business people have to learn about the technical aspects of SOA to do BPM. For example, I think asking them to learn to write XPath, XSLT, and WSDL is too much even if it's with using a graphical interface with drag&drop features. H.Ozawa Keith Harrison-Broninski wrote: > Hitoshi Ozawa wrote: > >> It's on selecting the right tools AND developing guidelines on using >> these tools that's important. As you've stated, giving developers just a >> tool wouldn't improve the situation. >> >> Instead of giving developers just Java to work with, give them also >> a set of patterns and a guideline on creating classes using these >> patterns. >> Make sure they are using the patterns and following the guideline. > > > +1. My experience is that without this sort of guidance, a > development project will fail - if not on release 1, then at some time > in the not too distant future. > > And OO techniques certainly give you a lot more scope for pattern > application than procedural code, so I would always recommend an > OO-based approach. > > In fact, I cannot see any justification for not using OO in a software > development project, SOA or otherwise. You can always write > procedural code inside an object if you wish (in fact, you can > simulate object-orientation using a procedural language too - anyone > else here remember Objective-C? - but that's by the by). So why not > use design techniques that offer more to the power user? You are in > no way obliged to take full advantage of them, if for some reason you > happen to prefer pre-1967 coding styles. > >-- > >All the best >Keith > >http://keith.harrison-broninski.info > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
