This past week at ebizQ was a busy one SOA-wise, with experts dissecting the issues leading to SOA worst practices, the new mode of application development that is arising, the role of a newly emerging professional, the business architect, and why data kills SOA.
In too many SOA and BPM projects, companies will either buy the software without first consulting the business. "IT will purchase what they consider to be the best software and then will shoe-horn the business processes into that technology," Peter Woodhull of Modus 21 observes in his latest article published here at ebizQ, which discusses the best and the worst of SOA and business process management.
James Taylor, decisioning systems guru, discussed the new application development paradigm that is evolving. Notably, the "Application Development 2.0" stack would better support automated decisioning, by "modeling processes, events and decisions as first class objects, supporting declarative (rules-based) approaches to developing business logic, using visual metaphors to manage rules, processes, events, and integrating analytics and dashboards directly." Expect a greater role for business analysts in the new app dev scenario, he adds.
Michael Poulin reports he has been engaged in an online debate about the role of the business architect. Interestingly, one of the questions that came up was "how would you describe business architecture in less than 140 characters?" Michael discusses the different viewpoints on this emerging role, and hints that it may track closely to that of business process design. "There is nobody else for this job," he says. There are few supporting roles in the organization, such as that enjoyed by technology architects.
Dave Linthicum elaborated more on why and how the lack of attention to data is stymieing SOA efforts. He notes that there are three core issues that SOA architects typically don't deal with, including "the ability to move large amounts of data from point A to point B; the ability to abstract data away from poorly designed databases that you may or may not own;" and "the ability to manage data, and deal with MDM and data quality issues."
Also, an important announcement from ebizQ: It's official -- ebizQ's next SOA in Action virtual conference will be a two-day event that takes place on October 28 and 29. Hear and share information with more experts and practitioners than you can find at most on-site conferences. And there's no cost to view it from your desktop! The line-up includes Randy Heffner of Forrester, Yefim Natis of Gartner, Roy Schulte of Gartner, well-known speaker and thought leader David Linthicum, and more!
In too many SOA and BPM projects, companies will either buy the software without first consulting the business. "IT will purchase what they consider to be the best software and then will shoe-horn the business processes into that technology," Peter Woodhull of Modus 21 observes in his latest article published here at ebizQ, which discusses the best and the worst of SOA and business process management.
James Taylor, decisioning systems guru, discussed the new application development paradigm that is evolving. Notably, the "Application Development 2.0" stack would better support automated decisioning, by "modeling processes, events and decisions as first class objects, supporting declarative (rules-based) approaches to developing business logic, using visual metaphors to manage rules, processes, events, and integrating analytics and dashboards directly." Expect a greater role for business analysts in the new app dev scenario, he adds.
Michael Poulin reports he has been engaged in an online debate about the role of the business architect. Interestingly, one of the questions that came up was "how would you describe business architecture in less than 140 characters?" Michael discusses the different viewpoints on this emerging role, and hints that it may track closely to that of business process design. "There is nobody else for this job," he says. There are few supporting roles in the organization, such as that enjoyed by technology architects.
Dave Linthicum elaborated more on why and how the lack of attention to data is stymieing SOA efforts. He notes that there are three core issues that SOA architects typically don't deal with, including "the ability to move large amounts of data from point A to point B; the ability to abstract data away from poorly designed databases that you may or may not own;" and "the ability to manage data, and deal with MDM and data quality issues."
Also, an important announcement from ebizQ: It's official -- ebizQ's next SOA in Action virtual conference will be a two-day event that takes place on October 28 and 29. Hear and share information with more experts and practitioners than you can find at most on-site conferences. And there's no cost to view it from your desktop! The line-up includes Randy Heffner of Forrester, Yefim Natis of Gartner, Roy Schulte of Gartner, well-known speaker and thought leader David Linthicum, and more!
Leave a comment