April 21, 2009 – SOA and Business Process Management (BPM)
In the past decades we have seen an evolution in programming trends. First there was the client/server, then the three tier architecture. Then we had many systems that could not talk to each other so we created EAI and other types of integrations. When these integrations became difficult to manage we created an architecture that allowed data to be generic in nature and so that this data could be used anywhere as a service. Today we call this Service Oriented Architecture (SOA). But above SOA there is a need for SOA that must be acknowledged. The entire reason for having services in the first place is because there are business processes that produce data. And in the long-term services must be governed in a way that relates to the processes that they provide services for.
There is a growing trend for organizations to be more process aware, and service oriented architecture plays a vital role in this trend. Methodologies employed in a process oriented approach are different than those of the traditional development world. Scrum, Agile, and other iterative development methodologies are widely used today but still do not address the ever-widening communication gap between the developer and the business stakeholders that create the requirements for the software the developers create. Process model driven software development is also very common these days, in which the business analyst creates a process model in BPMN (Business Process Modeling Notation) which often replaces flowcharts and hundreds of pages of requirements documents.
In this discussion we will cover:
* The process oriented methodology for software development, which yields software that is more in-line with the business objective and is more agile for the ever-changing business need.
* How to build software for business requirements that are a constant “moving target” (ever changing).
* Better communication between IT engineers and the business units through model driven software design in BPMN.
* Techniques, tips, and tricks to deliver your software to your customer sooner, and to meet more of the business objective with the product you deliver.
* BPMN is not just for business people – it’s capable of doing some very technical things as well.
* How BPEL (Business process execution language) relates to service oriented architecture, and more specifically how it relates to Java development.
* The modern architecture of process governance, which includes SOA and BPM (business process management) and how this relates to your job as a software architect/engineer.
Rick Geneva has been working with Business Process Management (BPM) and Service?Oriented Architecture (SOA) concepts since 2001, which was before these concepts were accepted as a formal mainstream practice. He has been a Java developer since 1999 and has worked in the Atlanta area as an engineer/architect for several well-known companies such as Nextel, Cox, Turner, and JBoss. In January 2007, he joined Intalio as a process expert, which is a hybrid role of both IT architect and business analyst. Rick’s current role is to help transform organizations from traditional development into more modern SOA and BPM methodologies.