Core SDP role-based suites target software architects, analysts, developers, and testers
Following up on the enterprise tools strategy it announced last autumn, Borland is now shipping Core SDP (Software Delivery Platform). With this move, the company adopts the model previously embraced by Microsoft and IBM, in which product suites are based on the role the developer occupies in the software-delivery infrastructure. In this initial release Borland identifies four principal roles: architect, analyst, developer, and tester. (Others will be added later.) The tool chains for these roles are all built on a platform of services called Core::Foundation, which includes a central team repository, versioning and configuration management, requirements management, and collaboration and project-management capabilities.
The roles are all Java-based. Core::Architect bundles UML modeling, support for design patterns, code audits, and metrics. The Core::Analyst role places greater emphasis on capturing and defining requirements, analyzing impact of changes, and scheduling. Core::Developer is the principal programming toolset, using either JBuilder 2005 or Eclipse as the IDE. Core::Developer doesn’t have the modeling or requirements tools of the first two roles, but it has profilers, testing frameworks, and static code analyzers, and it includes good support for J2EE and Web services. Core::Tester bundles greater testing and profiling resources, as well as test- and defect-management tools.
Vendors adopting the role-based model are looking to capture greater sales from an existing stable of products. This plan works if buyers see extra value in the product integration; simple bundles of tools won’t work. In this regard it seems to me that Borland has added sufficient new functionality and integration to Core::Foundation to make its case to enterprise buyers.
Cost: Starts at $5,900 per developer seat
Looking for the missing free copy icon? It's been replaced. There's a new direct link that works like a...
Supreme Court's decision is bad news for developers targeting the U.S. market, who will now have to...
The transition from command line to line-of-command requires a new mind-set -- and a thick skin
If an 'independent' code review says a product is totally secure, you aren't hearing the full story
A spate of projects from IBM's DeveloperWorks Open portal covers everything from improving Spark...
Built for development teams, Git can’t meet enterprise scalability and security requirements on its own...
AWS's developer-focused approach is one lesson enterprises should glean from the cloud leader