Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


[xml-dev] A brief history of how we develop information systems

From: "Costello, Roger L." <costello@-----.--->
To: "'xml-dev@-----.---.---'" <-------@-----.---.--->
Date: 4/13/2009 12:14:00 PM
Hi Folks,

I've compiled, from the references listed at the bottom, a brief history of the way that information systems are developed. Of interest to me is that it shows the gradual liberating of data, user interface, workflow, and most recently, enabling data to move about freely.

I welcome your thoughts.  /Roger


1. 1965-1975: Divide-and-Conquer

Information systems were decomposed into applications, each with their own databases.  There were few interactive programs, and those that did exist had interfaces tightly coupled to the application program. Workflow was managed individually and in non-standard ways.


2. 1975-1985: Standardize the Management of Data

Data became a first class citizen. Managing the data was extracted from application programs. Data was managed by a database management system. Applications were able to focus on data processing, not data management.


3. 1985-1995: Standardize the Management of User Interface

As more and more interactive software was developed, user interfaces were extracted from the applications. User interfaces were developed in a standard way.


4. 1995-2005: Standardize the Management of Workflow

The business processes and their handling were isolated and extracted from applications, and specified in a standard way. A workflow management system managed the workflows and organized the processing of tasks and the management of resources. 


5. 2005-2009: Data-on-the-Move (Portable Data)

Rather than data sitting around in a database waiting to be queried by applications, data became portable, enabling applications to exchange, merge, and transform data in mobile documents.  Standardized data formats (i.e. standardized XML vocabularies) became important. Artifact-, document-centric architectures became common.


References:

1. Workflow Management by Wil van der Aalst and Kees van Hee
http://www.amazon.com/Workflow-Management-Methods-Cooperative-Information/dp/0262720469/ref=sr_1_1?ie=UTF8&s=books&qid=1239573871&sr=8-1

2. Building Workflow Applications by Michael Kay
www.---.com

3. Business artifacts: An approach to operational specification by A. Nigam and N.S. Caswell
http://findarticles.com/p/articles/mi_m0ISJ/is_3_42/ai_108049865/

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent