|
Outsourcing SLAs
The greatest challenge of outsourced or distributed development is how to ensure that high-quality, flexible code is delivered promptly and predictably–regardless of obstacles such as communication barriers, different development environments, and team turnover. Developers might implement code based on a misunderstanding of your requirements and quality policies. The outsourcer's status estimations might be inaccurate or untruthful. Or, the code might be completed on time, but require tremendous rework. These and other headaches can be prevented by establishing a process that ensures code is developed according to your expectations, using an automated infrastructure to drive this process, then actively monitoring the developers' adherence to the process.
Parasoft delivers the visibility and consistency needed to reduce the risks of outsourcing and geographically-distributed development. An automated framework manages software verification methods to ensure that all software development activities meet your expectations, which are defined as SLA requirements. This enables a consistent workflow that reduces downstream rework. Moreover, reports provide objective, real-time information about code quality, requirement implementation status, and the process being used to build and test the code. The system alerts you to issues as they emerge so you can address them before they impact deadlines or budgets.
SAMATE
Parasoft provides automated identification of SAMATE Annex A source code weaknesses in high-complexity C, C++, and Java code–as well as
additional programming languages (.NET languages, JavaScript, XML, etc.).
Context-sensitive suppressions allow teams to prevent rules from firing under specific circumstances where they do not apply. This
reduces the level of noise, ensuring that every violation reported is a real problem that should be fixed. Suppressions can be defined
in the code to ensure they are always visible when code is reviewed and modified.
To promote fast remediation, each source code weakness detected is prioritized, assigned to the developer who wrote the related
code, and distributed to his or her IDE. These results provide a textual description of the precise weakness location, as well
as direct links to the problematic code and a rule description. Every rule description includes an explanation of the rule
rationale and benefits, a sample violation, an explanation of how to correct the violation, and a demonstration of how to
correct the sample violation. In addition, results are available in XML, PDF, HTML and custom format reports.
Custom
Many organizations attempt to implement quality initiatives by introducing software verification methods such as unit testing, peer code review, or static analysis, but find that their efforts eventually decay as schedule/budget pressures emerge, policies and projects evolve, and employees come and go. The few organizations that enjoy long-term success are the ones that make quality an integral part of their day to day workflow.
To help organizations ensure adoption and establish a sustainable, repeatable, and predictable process, Parasoft ingrains compliance tasks into the team's application development process. As developers write code, our automated infrastructure monitors the team's compliance to the organization's policies for ensuring that quality is built into the code and maintained in response to changing business needs. This can include static analysis, peer code review, unit and component testing, and regression testing. To ensure that the compliance process remains on track and does not disrupt project progress, Parasoft automates and optimizes the workflow so team members can focus on tasks that truly require human intelligence.
|
