On Monday I was headed for New York a day ahead of the Eclipse New York Banking Day event. I whipped out my camera as we approached Manhattan.
I haven't been to New York in more than a decade. Welcome to the Big Apple!
I grabbed a taxi and was soon in the mid island tunnel headed for my stay at the Stay hotel.
The hotel was very reasonably priced, had nice rooms, and some funky decor in the lobby.
After dinner, I walked around to see some of the sights. New York is a very lively city and there is a great deal to see. Too bad I didn't have more time to spend here.
On Tuesday, Ian started the day with a quick overview of the agenda and expressed gratitude to the sponsors, Actuate and Sybase, as well as to Ted Epstein of Morgan Stanley for hosting the meeting with excellent facilities.
Next Mike provided a high-level overview of what's happening at Eclipse these days
and why there is value in getting involved.
He talked about the following maturity model for how organizations deal with open source.
Business agility---responding quickly to changing regulations, standards, and customer opportunities---is becoming increasingly important. Today's information technology solutions tend to result in technology silos that are poorly integrated and plagued by vendor lock-in. Eclipse offers a new approach: open collaborative development. It has established best practices for multi-organization collaboration, including development processes, intellectual property sharing, technical architecture, and sound governance. Defining a platform in open source with transparent processes that are focused on meritocracy will definitely encourage many pragmatic people to get involved to share their innovations. Businesses should focus on where they can offer competitive differentiation. There's too much effort going into building the whole enchilada in today's complex world, and that effort detracts from being able to focus on the important factors that would actually provide better value for in terms of specific business needs. Defining and implementing a common banking platform would help the industry as a whole move beyond it's current cyclic reinventing of the wheel.
Next Jochen Krause talked about e4 and where Eclipse as a platform is headed.
One of the tool challenges we all face today is how best to make developers productive with quick write-test-debug cycles while producing modular componetized applications with consistent and stable APIs. The mission of e4 is to build a next-generation platform for pervasive, component-based applications and tools. It's very important to reassure the established community that the 3.x stream will continue to be supported for the foreseeable future. Eclipse has been growing for many years, but nothing has ever disappeared, so there are often multiple ways to do the same thing, e.g., storing preferences. Some cleanup is required. He talked about the effort to model the workbench so the same type of technology folks are using to model data within their specific domains will be used directly in the platform to model the workbench. For the future, we should anticipate the browser becoming a more viable delivery vehicle for applications.
Andrew Montalenti and Ted Epstein described MODeX, Model Oriented Data eXchange, which is a graphical modeling IDE that includes a code generator, language-specific runtime components, and life cycle management tools.
Direct XML manipulation is the least common denominator in the message exchange space. Toolkits focus on SOAP envelopes, transport, and message dispatching and handling. XML Schema is something that's often ignored, or treated as only a design time thing that's not properly maintained. Developers have been left to manually translate business concepts into XML formats with issues like poor support non-containment references getting in the way. Their solution is to have developers focus at a higher level of abstraction and to generate schemas and other detailed low-level artifacts from well-defined abstract message contracts.
Andrew gave a demo of MODeX designer, which uses GEF, EMF, GMF, JFace/SWT, and Equinox, and showed how to design entities, which he compared to EClasses in Ecore, using the tool. It supports tree-based editing as well as a graphical view of the entity relationship diagram. The user can create multiple different graphical views of the same underlying model. He showed all the different things they can generate including Java, C#, and C++, as well as schemas and described how some of these generated things can be used. MODeX includes support for views that allow you to filter down the overall model to the relevant information actually needed in a particular context; the corresponding schemas for these filtered views are generated automatically. They don't yet have a good graphical representation for views, but they plan to provide that soon. MODeX is yet another extremely cool example of how powerful model driven development can be in any domain.
In his talk, Christian Meier briefly described UBS' experience with Business Capability Modeling, which involves apply modeling to abstract over existing business processes, technologies, and organizational structure.
Philipp Kutter quickly outlined the EMF model they've designed to capture all this high level information.
Tatyana Staver gave a short talk about the Eclipse Open Financial Markets Platform, which is focused on creating a middle office financial markets application.
She reiterated the earlier theme about avoiding the continuous reinvention of the wheel that we see all over our industry. Build a platform and do it right once. Then evolve it and benefit from the expertise and contributions of others.
Edwin Park shared RBC's experience with Front Office Fixed Income Application Integration.
In the past, trading applications were localized to specific product types so there were multiple applications doing much the same thing. It would be more more effective to have one integrated user interface that could be tailored to address all the specific needs. A componentized architecture is ideal for providing a common base and allowing specializations to be seamlessly integrated. The fact that Eclipse already provides a rich variety of useful of components is a big win. They're making use of p2 to help with making installation a snap. The shift from monolithic solutions to component-oriented solutions is a big organizational shift: there is more reliance on shared infrastructure and that requires better coordination across larger groups of people. Internally their development effort follows much the same process as Eclipse itself uses: they focus on addressing real immediate needs and involve others in realizing the solutions. He stressed that it's important to get management buy-in for investing in shared technology projects.
Next was my turn fo the EMF dog-and-pony show. First I took pictures of the audience.
Notice below that the monitor is showing a screen saver of my garden? I started by explaining that I was going to jump to the conclusion. I pointed out that this beautiful garden was modeled first, on grid paper, before I went out and landscaped it. The conclusion being that it's important to model first, and take action in light of that design, if you want to achieve a beautiful result.
In this picture you can see in the monitor a picture of me taking a picture. You got to like that!
I think it went well. Almost no one fell asleep, and even the one guy who did, didn't snore very loud.
After a break, Jochen Krause talked about how RAP extends Eclipse RCP to the web.
The idea of course is to have a single code base that supports both RCP and the web. Just shoehorning an RCP window into the browser didn't go over so well though, so there was an effort to map the UI in a more browser-friendly way. I totally perked up when he said that cell editors are working the latest version of RAP. Woo hoo, now it can support properties views as used by an EMF generated editor.
Finally Henrik Lindberg of Cloudsmith and Jeff McAffer of Eclipse Source described Provisioning Eclipse in the Enterprise.
Of course p2 is the focal point for this. Unzipping files just doesn't cut it and the old style update manager, which p2 replaces, had many limitations. The installable unit, or IU, is the star of this new show; everything is an IU and everything is installable. With p2, a key design point is the separation of the metadata from the artifacts for which they provide information. The overall design is based on a director for managing the metadata, a repository for managing the artifacts, touchpoints for managing the runtime targets, and an engine to produce profiles or runnable configurations. Suffice to say, p2 is an installer on steroids.
The banking day was a great success. Kudos to Ian for helping organize this, to the sponsors for helping fund it, and for to Morgan Stanley for being such excellent hosts! It was a great event and it was very nice to meet so many interesting people. For example, I ran into Jeff Ricker whose name I recognized from the EMF newsgroup.
After that, Jochen, Mitch, Jeff and I headed to JFK for our 8:15PM flight to San Francisco for the Eclipse board meeting.
I didn't arrive at my hotel until well after 1:00AM PST, so it was a very long but productive day.
Use and Misuse of Statistics
4 weeks ago