Open, Agile and Enterprise: Optimize your SDLC with Borland
End-users are less tolerant of poorly delivered applications than ever before. Fail to meet user expectation and you risk losing both customer loyalty – and business
Plan and manage the lifecycle
To ensure quality across the Software Development Lifecycle (SDLC), plan to succeed. Check that business requirements are met every step of the way. Open, reportable, cross-stakeholder communications are as critical to success as are tracking discussions across the SDLC from one artifact to another.
The SDLC evolves uniquely for each application, regardless of the methodology used. Borland understand the complexities of SDLC because we live it every day. Our development labs are spread across the world and we follow an Agile strategy across the SDLC, using Borland tools, to meet our customer's needs for quality solutions.
Business needs at heart
Management and Tracking is central to all SDLC activities. Everyone within the SDLC community should be able to see the measurable outcomes from where business become tasks and are aligned with people. StarTeam is a complete solution. It underpins the ever-changing knowledge flow of the SDLC, independent of whether the team uses agile, iterative, waterfall or hybrid methodology.
The SDLC starts by defining well-formed requirements that reflect the needs of the business. The SDLC ensures these are available for scrutiny by the application’s stakeholders. Caliber is the environment where requirements are authored, visualized, reviewed and managed during the complete lifecycle. It gives insight into the alignment of business need, development, testing and deployment.
Build in quality during development and deployment
Development is the engine room within SDLC. It matches people with tasks and time. Whatever the development environment, developers must use the correct documents and code – and complete their tasks to meet requirements and deadline. Borland tools (StarTeam, Caliber, DevPartner) co-exist with the developers’ environment of choice, giving the current status of tasks and access to the project's knowledge base, regardless of build or release cycle. This is particularly beneficial where development activities within the SDLC are prioritized into discrete parcels of work such as sprints, iterations or cycles.
Why keep testing until the end of the SDLC. Deploy the Borland Silk portfolio of testing tools and quality assurance is enacted early and continuously throughout an application’s journey through the SDLC. Silk covers test management, functional and performance testing. It ensures the application meets the business need regardless of the ecosystem or delivery mechanism, be that mobile, cloud or enterprise. Prioritizing testing effort to business critical capabilities means that testing and risk mitigation find a measureable and reportable quality point.
It may be the last stage in the SDLC but deployment is a critical step where a lot can go wrong. Ensuring the correct code and documents are packaged for a specific build eliminates costly last minute failures. The SDLC may contain multiple streams of development that must come together to form the final application. Borland's open approach to third party tools ensure that StarTeam's superior change management capabilities can be integrated with pre-existing, version control and deployment platforms, giving confidence that the deployment phase of the SDLC will be completed successfully.
SDLC – the Borland way
Our tools allow you to:
- Gather, refine and organize requirements – align what you develop with what your users need
- Accelerate reliable, efficient and scalable testing to deliver higher quality software
- Continuously improve the software you deliver – track code changes, defects and everything important in collaborative software delivery
Browse the tabs to learn more about SDLC the Borland way. We also have some great ideas about how SDLC applies to testing for SAP.