|
The Challenges of SOA Security Service Oriented Architecture (SOA) has many security challenges. To address these challenges, it is not enough to set up a secure operational infrastructure. SOA security must be implemented in all key areas of software development-architecture, design, platform, governance, requirements, development, and testing. Jimmy Xu discusses today's SOA security challenges and explains why it is important to address these challenges inside software development. He presents the latest security practices: standards compliance; review of architectural blueprints and SOA platforms; secure SDLC process; threat modeling; secure coding; and security testing. This session not only prepares you to delve into the details of SOA security methodology, process, and techniques, but also gives you the background information you need to plan and scope security assurance activities in your SOA development projects
|
Jimmy Xu, CGI Inc.
|
|
SOA Testing Challenges and Proven Practices The best thing about Service Oriented Architecture (SOA) is its flexibility-a heterogeneous computing environment in which different services and service providers can use different technologies; loose coupling of components to allow any application to make use of service capabilities; and ad-hoc integration of applications within and across organizations. However, from a tester's perspective, these very advantages make the testing of Web services and SOA-based applications highly complex. Testing Web services through the front-end of applications is usually ineffective. Tracking defects to their source is difficult because of the layered application designs. Instead, you must design and execute mostly non-functional tests for compliance to standards, interoperability, security, reliability, and performance.
|
Guruprasad Gopalakrishnan, Wipro Technologies
|
|
A Toolkit for Assessing SOA Readiness Before charging "full speed ahead" into the land of service-oriented architecture (SOA), you need help to ensure success and mitigate the risks inherent in such major systems changes. Jerry Smith provides proven tools for assessing SOA readiness and outlines the essential steps to implementing SOA. Jerry presents reference SOA architectures that demonstrate solid standards and specifications to compare with your implementation plans. He introduces an SOA Maturity Model to help you understand your current organizational and technological state. The SOA Maturity Model is a communications tool that outlines how the organization’s SOA implementation will evolve along both business and technical lines. Jerry outlines the various stages the model entails and how to apply it so that technical and organizational changes are easily coordinated across the enterprise.
|
Jerry Smith, Symphony Services
|
|
The Coming SOA Revolution: What It Means To Testers Applications deployed with service oriented architectures are implemented as producers and consumers of services. Testing a Service Oriented Architecture (SOA) application is unlike anything you've done before because every service can be invoked by consumers of whom you have no knowledge. This requires you to understand the specifications of those services in order to build valid, robust tests. Before SOAs began appearing in IT organizations, testers often dealt with lack of management commitment, poor testing tools, and minimal testing environments. Now, with SOA, the risks of failure are high, and the powerful processes, protocols, and tools that software developers use to build applications can also be used by testers to verify, validate, and test SOA applications.
|
Frank Cohen, PushToTest
|