Business Architecture: Use Context Diagrams to Bridge from Processes to Services
Mike Rosen proposes context diagrams as a means to address the challenges business architects face. Here he demonstrates the application of the context diagram and shows how it enables the architect to put things into a broader context, demonstrate the value of his/her work, and drive analysis into design and implementation.
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)
- Business Architecture: Critical Thinking in Business Architecture - December 1, 2014
- Business Archicture: Abstraction in Business Architecture - October 6, 2014
- Understanding Why and How Well - February 3, 2014
- Business Architecture: Use Context Diagrams to Bridge from Processes to Services - October 1, 2013
- Business Architecture: Business Architecture Scenarios - May 7, 2013
