{"id":572,"date":"2008-05-05T07:00:46","date_gmt":"2008-05-05T15:00:46","guid":{"rendered":"http:\/\/www.formtek.com\/blog\/?p=572"},"modified":"2008-05-05T07:00:46","modified_gmt":"2008-05-05T15:00:46","slug":"soa-business-process-blueprints","status":"publish","type":"post","link":"https:\/\/formtek.com\/blog\/soa-business-process-blueprints\/","title":{"rendered":"SOA: Business Process Blueprints"},"content":{"rendered":"

To add emphasis to the idea that SOA is an architectural approach and not a technical specification, the OASIS <\/a>group has started a Technical Committee towards creating SOA solution blueprints. An SOA blueprint is a sort of recipe that lays out best-practices for how to implement SOA infrastructure. SOA blueprints are, in theory, vendor-neutral and in concept have been agreed to and supported by vendors like BEA, Borland, HP, Microsoft, Oracle, Sun Microsystems, and Veritas.<\/p>\n

Miko Matsumura is the chair of the OASIS SOA Blueprint Technical Committee, and blueprints are an idea that he’s promoted for several years now. “Users often cannot envision how the technologies can combine to solve their problems,” he said. “We want to show how a particular business problem can be solved completely using open standards, and not just OASIS standards… The idea is that a user can turn to a vendor and say, ‘You need to implement this blueprint in order to demonstrate your capabilities.'”<\/p>\n

Each blueprint describes how to design, test and implement a specific business problem. An SOA blueprint consists of the following components:<\/p>\n