BPM and SOA: Data Information and SOA
In his words, Mike Rosen has “a nit to pick” with a common Enterprise Architecture categorization of the enterprise into business, data, application and technology. That nit concerns differentiating data and information, a distinction Mike asserts is key to avoiding impediments to successful implementation and operation of SOA. In this Column he provides a way to understand and use “data in context,” i.e. information.
Mike Rosen
Mike Rosen is Chief Scientist at Wilton Consulting Group and a Founding Member of the Business Architecture Guild. Mr. Rosen is also an Adjunct Research Advisor for Business and Enterprise Architecture for IDCs CIO Advisory Practice. He has more than 30 years of technical leadership experience architecting, designing, and developing software applications and products. Currently, he provides expert consulting services in the areas of Enterprise Architecture, Business Architecture and SOA. Previously, Mr. Rosen was CTO at AZORA Technologies and M2VP, Inc., and Chief Enterprise Architect at IONA Technologies, PLC, and Genesis Development Corporation. Mr. Rosen was also a product architect, technical leader, and developer for commercial middleware products from BEA and Digital. His involvement in product development includes Web services, Java, CORBA, COM, messaging, transaction processing, DCE, networking, and operating systems.
Latest posts by Mike Rosen (see all)
- Digital Transformation: Architecture Value - January 3, 2022
- Digital Transformation: Digital Transformation and the New Normal - July 6, 2021
- Digital Transformation Processes: Achieving “Good” Outcomes - January 4, 2021
- Digital Transformation: BizOps and Business Architecture - November 2, 2020
- Digital Transformation: Turning Data Into Value - June 1, 2020
