Share via

What is a LOB application?

  • Article

I wanted to blog about this topic for a while so I might as well make it the first post. Line of Business (LOB) applications come up quite frequently in conversations around me. However I'm not sure whether everybody has a common understanding of what that means. They're business rather than consumer applications, but what else? There's one definition here but is it sufficient? I've brainstormed LOB applications with p&p's Web Client team, weaved the results with my consulting experience with Global 1000 companies, and came up with a few traits (I'm sure there are more).

LOB applications are (in no particular order):

  • Interactive--self explanatory
  • Have multiple screens--the interaction happens on screens, and typically several of them are involved
  • Domain specific--examples include finance, insurance, health care, telecom, and e-commerce applications
  • OLTP--transaction processing rather than analytical processing
  • Have relatively simple user interface/presentation--text fields, checkboxes, buttons
  • Integrate with other systems that manage the data and execute the transactions--databases, systems of record, etc.

Do the above chracteristics represent a tall order? It depends. Here's just one data point to consider. A while back I followed the flow of a claim to understand the claim processing workflow. That particular claim processor (like pretty much all the other insurance companies I worked with) ran claims through a legacy application running on a mainframe. The folks working with the application used green screens to enter the claim information and process the claim. If you've never seen a mainframe before, this translates into very fast response times (when navigating, validating, pulling reference data, and moving from one screen to another) and keyboard-intensive navigation and input (typically with all those function keys performing some action). This may be a tall order if you're building a browser-based application.

[Update] The point about relatively simple UI warrants an explanation. Don't read it as "LOB applications ought to have boring UIs." Far from it. But if you find yourself implementing the functionality of a windowing system or that of a portal site, it's likely that you're over engineering.

Comments

  • Anonymous
    July 19, 2007
    Recently two fellow teammates got their blogs up and ruinning. Grigori Melnik is new to the team as Tom

  • Anonymous
    July 19, 2007
    Recently two fellow teammates got their blogs up and ruinning. Grigori Melnik is new to the team as Tom

  • Anonymous
    July 19, 2007
    "Have relatively simple user interface/presentation" - I question whether this item adds value to the discussion.  If you look at what WPF supports in v1, many would argue that despite being an advanced UI framework, it doesn't support LOB apps very well.  And others would argue that LOB apps don't need to have "boring" UIs.  Adding "relatively simple UI" to the definition of LOB seems to be primarily useful for justifying auto-generated, DB-oriented UI rather than task-oriented UI.

  • Anonymous
    August 03, 2007
    I never liked the term "LOB Applications" (even/especially when I was the Product Manager for the now defunct "LOB Program" at p&p), and I'm not sure the term even needs a standard definition. My advice is that whenever anyone uses the term, just ask them what they are actually talking about. Tom

  • Anonymous
    January 19, 2012
    Doesnt really make a lot of sense to be honest