1 / 2

Addressing Non-Functional Requirements

In order to minimize the technical gap between DevTest teams and business expectations, software development teams need to understand the importance of Non-Functional Requirements for ensuring quality. Learn what Agile teams must do to close the gap to ensure continuous quality at speed. Visit: http://bit.ly/28NGOzP to learn more. <br>

Parasoft
Télécharger la présentation

Addressing Non-Functional Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Gap Between Business Risks and Software: How Teams Measure Non-Functional Requirements There is undeniably a trend today towards optimizing software application development and delivery processes. Whether the adopted initiative is termed Agile, DevOps, Continuous Delivery, Bimodal, or something else, the underlying impetus for change is the same: the business wants to differentiate itself with innovative software that bonds customers with the company, its products, and its services. For years, software development organizations struggling to negotiate the classic time-scope-quality triangle have made tradeoffs that shortchanged quality. However, now that software has increasingly become the interface to the business, delivering innovative, top-quality software at speed (quality@speed) is imperative. To explore how the evolution of the SDLC is impacting software quality, Parasoft recently conducted a survey asking software development professionals a series of questions about their team's development process and how they define and measure both functional and non-functional requirements (NFRs). Whereas functional requirements define what the system should do, NFRs describe how the overall system should behave. NFRs can include application resiliency, accessibility, availability, reliability, and testability — to name just a few. Copyright © 2016 Parasoft www.parasoft.com

  2. Survey Demographics IT Ops 4% Developer/Engineer 32% Business Analyst 6% 780 IT professionals responded to the survey. Respondents were recruited from relevant LinkedIn groups, Parasoft's customer database, Parasoft's social media outreach, and Parasoft partners' social media outreach. Architect 15% Tester 26% Senior Management 17% The most notable findings from this survey were: • There is an inverse correlation between more iterative development methodologies like Agile and the likelihood that teams will measure compliance to non-functional requirements. • Developers and testers are less likely than the business team (managers and business analysts) to believe that their organization measures NFRs. Does your team monitor compliance to NFRs? Agile-ish Agile* • In theory, Agile promotes shared ownership of software quality; however, our data indicates that in practice, Agile methodologies actually transfer an increased responsibility for quality to testers. Iterative Hybrid Waterfall 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 38% 58% of Agile-ish and Agile teams are monitoring NFRs VS • In organizations that measure compliance to NFRs, the business team is typically more influential in defining quality objectives. of Waterfall teams *Types of software development methodologies employed • DevOps is graduating from buzzword status and making its way onto the corporate agenda. To learn more, DOWNLOAD REPORT Copyright © 2016 Parasoft www.parasoft.com

More Related