DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > Can Speed and Quality Coexist in the SDLC?

Can Speed and Quality Coexist in the SDLC?

Be it via Agile, DevOps, Continuous Delivery, or some other paradigm, can speed of delivery co-exist with quality of delivery? Read on to find out more.

Erika  Barron-Delgado user avatar by
Erika Barron-Delgado
·
Jul. 30, 16 · DevOps Zone · Survey/Contest
Like (2)
Save
Tweet
3.42K Views

Join the DZone community and get the full member experience.

Join For Free

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.

for an overview of what we found, see this infographic...

can speed and quality coexist in the sdlc?

or, watch this brief video:

for a deeper dive into this study, download the complete 14-page "how teams measure non-functional requirements" report . in addition to providing detailed results and findings, the report explores:

  • why measuring nfrs is critical for devops and continuous delivery
  • the 3 major impacts that agile has on software testers
  • architects' real influence on nfrs
  • what needs to change as agile teams adopt devops
Software development Coexist (image)

Published at DZone with permission of Erika Barron-Delgado, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Types of UI Design Patterns Depending on Your Idea
  • Debugging Java Collections Framework Issues in Production
  • 6 Things Startups Can Do to Avoid Tech Debt
  • What Is HttpSession in Servlets?

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo