3 min read

Telelogic Upgrades Tools To Tie Software Services To Business Processes

Upgraded tools are designed to be more useful in producing and deploying services-oriented architectures on top of business processes.
Telelogic, a supplier of tools for developing software based on models, has been upgrading its tools to make them more useful in producing and deploying services-oriented architectures on top of business processes.

It recently launched Telelogic System Architect for SOA and Telelogic Tau 3.1, a modeling and software development tool upgraded to support Web services.

On the business-management side of the upgrades, Telelogic also introduced Focal Point Focus on Product Management, a Web-based system aimed at helping a company capture how it plans to develop a product and bring it to market.

In effect, business managers and business analysts use Focal Point to map out what they're trying to accomplish in a new or evolving product line. The development tools, Telelogic System Architect and Tau, then weigh in. Their role is to answer the question, "Now that we know what we need to do, what technology are we going to use to do it?" said John Carrillo, senior director of strategic solutions for Telelogic, in an interview.

System Architect for SOA maps the existing application infrastructure, showing existing application services and their interdependencies with databases and other systems. In effect, System Architect maps out a workflow that models both the new business processes needed and the underlying systems and services that will be tapped to bring them about.

"Then you can start planning -- is this a one-year project, a two-year project?" said Carrillo. Telelogic also has a method of capturing the business value of different services and assigning them "a heat value," so that architects and engineers know where to concentrate effort that will be highly visible to business management.

System Architect's new SOA capabilities then address one of the emerging bugaboos of SOA design: They help select the candidate services that should be built for reuse as a part of the services-oriented architecture.

"SOA development imposes more complexity. There are a lot more dependencies between services" that must be designed into an SOA component, said Carrillo.

Once the System Architect model is complete, developers build their own software model in Tau 3.1, using diagrams, symbols, and syntax of Unified Modeling Language, which translates directly into the skeleton of an executable system.

Tau 3.1 has been upgraded to support Web Services Description Language, which makes software describable as a callable service over the Internet. It supports XML Schema Definition, a language that's understood by different computers on the Internet for its description and layout of a service presentation to users. Tau applications are produced in Java, and Tau 3.1 provides round-trip code support. That means Java code, compiled in a deployed service, can be sent back to Tau and used to build a model of what it represents. Developers can then change the model, test it with new additions, and send the code back into production.

System Architect for SOA and Tau 3.1 are immediately available.