Enterprise Instant Messaging

Posted by Mike Haller on Tuesday, October 28. 2008 at 21:56 in Work
Yippey! Today is the time for celebration: we officially got Instant Messaging at work. Forgotten are the days of using Outlook or network shares to send logfiles, screenshots and snippets back and forth. Also it's really nice to be able to react to messages while hanging on the phone.

We're using Jabber (OpenFire server) and i'd like to integrate the build server.
Thanks, IT Infrastructure team! I owe you :-)

The Platform: Java Business Integration

Posted by Mike Haller on Tuesday, October 14. 2008 at 10:00 in Work
We're going to bring one of our frameworks - The Dynamic Business Application Framework - to the Java Business Integration (JBI, JSR-208) world.

Today, The Platform provides components, services and core functionality vital to any business application. Based on top of that, The Platform shall become more open for reusability, flexibility and modularity. One of the many topics is to hop onto the Web 2.0 and SOA wagon. Our developers/users will be able to quickly get their dynamic applications created by The Platform connected to any services-oriented architecture and integrate it with existing corporate IT landscapes.

So, while peeking a quick look on the whole JBI topic in general, i found some worrying statements by James Lorenzen:

"I believe the biggest failure of JBI has been communicating clearly what JBI is and how to use it. It took me many months until I felt like I actually "understood" JBI."


"many months" is not exactly what I've planned to invest, just to find out what JBI is and how it works. Actually understanding a technology must occur very quickly. Else, the time lost with investigation may harm the whole project. Being able to quickly adapt and understand new technology is vital to technology-oriented projects/frameworks/people. A business-oriented project may chose whatever technology is already settled. That's plannable and fine for the project. A technology-oriented project needs to be much quicker, as there's no "meat" in the project itself. It only consists of infrastructure.

"With XML being so verbose I believe SM or OESB would probably dislike a 3 MB XML file getting pumped through it."


Someone who "actually understands" JBI and used it for months (and probably years by now) thinks that a 3MB XML will be too large for ServiceMix or OpenESB? I wonder what the implementors of those JBI containers were thinking of what we (the users) are going to put through JBI. I mean, come on, i'm going to send data and lot's of it. I'm sure that "Hello World" works well, but did you guys ever thought about that HelloWorld is only the start and if they wanted us to really do business with it that we would stick with small data sets? Business is about data. Payload - and really lot's of it.

"I remember the first video I watched when the light bulb finally went off. It was a video on how to use the Sun SMTP BC and creating a Service Assembly with Netbeans. After I watched that video everything just came together for me and my co-workers."


That sounds like a good hint. I'll try to find that video about Sun Simple Mail Transfer Protocol Binding Component (i expanded the abbreviations on purpose).

The Platform: First Contact

Posted by Mike Haller on Monday, October 13. 2008 at 10:00 in Work
At the very same time as the financial crisis 2008 is happening, I've been working on software development projects in the credit risk rating area. As one of the developers of the Credit Risk Rating Platform, my goal is to give our customers (the banks) the ability to manage credit risks and the ability to quickly adapt to changes in the rating calculation. Our customers want to be able to change the logic how ratings are calculated. And they want to be able to do that on their own and very quickly.

Formerly they all used a bunch of proprietary pieces, put together into ugly Excel sheets and Visual Basic spaghetti code. This looks fine in the books and every business guy can do it or at least change some formulas in there. However, lots of different Excel documents with lots of sheets and lots of colors and lots of different mathematical and statistical functions and lots of macro code and lots of cycling dependencies between cells ... well, you get the point. It just becomes plain unmanageable and chaotic. ("Which LGD excel sheet was used for customer X? I cannot find the latest version on the network drive...")

"The Platform" let's customers change the way the software behaves after it has been rolled out. "The Platform" is the core of our Credit Risk Rating Platform. With The Dynamic Business Application Platform, any new logic can be brought into the application by the customer without the need for a software developer to change a single line of code. (Of course, this only applies to the core application. The systems usually are solutions with additional features which are not based on the DBAF.)

Experts like financial analysts can now model how the program should calculate. They do it visually, transparently and well-documented with tool support. What has once been deeply hidden somewhere in a formula cell near the end of some Excel sheet is now visually describable, versioned, documented and tested. And it looks much better. Compare for yourself, how the two concepts look like:

Before: (with Excel)



After: (with Visual Rules)



The graphics do not show the exact same, i just wanted show how they're conceptually different. For example the Excel formula G10:=NORMSINV(B10); will probably be very similar in Visual Rules, something along the lines of DefaultThresold[10] := normsInverse(ProbabilityOfDefault[10]);.

One of the advantages is that the formula can now be expressed with more meaningful names, it can be described (the name of the blue assignment note is "Calculate PD" instead of "C10" in Excel) and documented. And you can see loops and decisions directly in the visual model. This is really good and helps to navigate quickly in complex rating models, even after months and years. Just think of the times where you have looked at some Excel formulas after years and wondered: "Did I write this garbage?! I don't remember what $G$I is and how the heck this all works. It'll take weeks to understand it again."

New project

Posted by Mike Haller on Friday, May 2. 2008 at 22:45 in Work
Started to work on a new project and in a new team today.

After having an interesting and nice time at the last project in Switzerland, i'm looking forward to new challenges. Having spent a couple of years in an enterprise service oriented architecture landscape, with plenty of integration tasks, interaction with (business) people and support tasks, the new project is self-contained and seems to be pretty straightforward. It's going to be a plain JEE Web Application and incorporates the latest cutting-edge technology of business rules modeling.

About

My name is Mike Haller and I'm a software developer and architect at Bosch Software Innovations in Germany. I love programming, playing games and reading books. I like good food, making photos and learning and mentoring about the craftsmanship of commercial software development. Stack Overflow profile for mhaller

Quicksearch

Archives