A
business application is defined as a navigation of business
information. That means a business society, should be able restrict to
whom, information is told (please note that we don't use the word
access, a trans formative / algorithmic word, but specifically use the
word told, a communicative word) , as and when needed as deemed fit by
the business community. That means there will be times when what is
told and what is listened to (a.k.a. access) might be restricted to a
specific community of users, as per rules of navigation, as demanded by
the different stakeholders of the business. For example, credit card
information should not be told to a particular level of people or as
identified by government, a Tax exemption cannot be given before
validating whether the customer is exempt from tax (by checking his tax
certificate and a copy of tax certificate should be stored in the
premises, this might involve a different a separate communication flow
/ series of communication primitives (a.k.a workflow).
The thinking here is that the whole SDLC Process exists to create a business application and is intended to create navigation of Business information. The Business system SDLC process purpose is to identify, codify, these business data and interaction paths..
With the increasing miniaturization of technology, networking of these devices together, Web 2.0 technologies and new architectural ideas like REST can lead to enterprises that are more dynamic and cheaper. Leveraging these technology forces, allows us to architect business applications differently, leading to cost effective real time business information infrastructure.
The next few posts we will explore how this can be achieved.
