The privately owned US company Coverity claims that its newly released and browser-based software tool Coverity Integrity Control supports development organizations to set standard policies for code quality and security, and then manage, monitor and report on these policies as code is tested.
The Open Group Conference was held in San Diego from Feb 7-11,2011. In this news item we cover highlights of the conference especially around the topics of EA, Cloud and SOA.
Clive Gee, an experienced IBM SOA Practitioner, describes how IT securing the networks has evolved into what he refers to as Information risk management. As the collaboration space increases with application integration and service oriented systems, he examines the risk management of the increased the surface area of threats and vulnerability.
Two weeks back the US CIO's office released a 90 page proposal entitled, Proposed Security Assessment and Authorization for US Government Cloud Computing. The document is the result of 18 months of work among the NIST, GSA, ISIMC and the CIO Council to evaluate security controls and multiple Assessment and Authorization models for US Government Cloud Computing.
CBDI talks about the history and evolution of the CBDI-SAE reference framework in the September 2010 Journal Report. CBDI-SAE reference framework has evolved in the in the past few years by embracing Event Driven Architecture (EDA), Real time Business Intelligence (BI) and Cloud architectural patterns and process principles based on continuous improvement.
The latest version of software architecture analysis and quality governance tool SonarJ supports structural debt index and architecture quality model. The company behind the product, hello2morrow, last month announced the release of version 6.0 of the tool. The new release also includes sand-box testing and an updated version of Sonar plugin.
In his new post, eBIZQ’s Joe McKendrick discusses some of the mysteries surrounding SOA: the difference between SOA and cloud computing, how can SOA fail when nobody really has fully implemented it, how to measure SOA success, and others.
A new Steve Jones’ post “Why contracts are more important than designs” discusses an important issue, service contracts, explaining why more time should be spent designing the services contracts.
The importance of SOA governance still remains the question of heated debate. The new spin on this is introduced by merging SOA with cloud computing. Several recent posts discuss this issue stressing the importance of governance, but shifting its focus from design-time to run-time
Everyone agrees that SOA governance is required for a successful SOA implementation. At the same time the question of whether Registry and/or Repository is required for a successful governance implementation is still subject to debate.
In his new post, Ganesh Prasad tries to describe the most complex issues of an SOA implementation and provides recommendations on how to solve them.
Mike Kavis, wrote an article for the SOA institute in which he characterizes the success of any SOA implementation into four factors people, process, technology, and business. He believes that a good management strategy is to create and communicate a roadmap that plots out key deliverables in each of these areas.
Once all your teams use Agile and are busy implementing local improvements, what happens to the larger organization formerly called "IT" or "Systems Development"? A coach with a large Agile program shared the strategy they designed to let the larger community spot trends and benefit from all this learning. Paulo Caroli calls it "Retrospective of Retrospectives".
The Open Group released last week two new industry standards: The Open Group Service Integration Maturity Model (OSIMM) and SOA Governance Framework.
Last month the Open Group made available their SOA Source Book. They describe it as “a collection of source material produced by the SOA Working Group for use by enterprise architects working with Service-Oriented Architecture”