Related Content
 |
A Checklist for Managing Go-Live Decisions and Risks If you have to replace a complex existing data system in production, decisions about when and whether to go live should be treated with gravity and care. One process that can help keep you honest is developing checklists that describe very clearly what is expected to be accomplished and verified at each milestone. |
|
 |
A Definition of Done for DevSecOps In DevOps, we have a software delivery pipeline that checks, deploys, and tests every build. The goal is to produce a viable candidate for production, so we have to look at many different aspects of quality, including security. To be sure we hit all the crucial marks, we should have a definition of done for DevSecOps. |
|
 |
6 Ways to Protect Your Organization from DDoS Attacks During a DDoS attack, no one can use your application, which will result in loss of business. Brand reputation also tumbles if customers can't access your site or become casualties of the data breaches. However, there are some proven practices for preventing DDoS attacks—and for what to do if you fall victim to one. |
|
 |
What the Future Holds for Cloud Computing Thanks to the development of cloud architecture away from a server-client pattern, those in the software industry will be able to embrace heterogenous cloud services that can only run when needed. Consequently, we are due for a cloud renaissance. Here are some predictions for what the future holds for cloud computing. |
|
 |
Creating an Environment That Encourages Resilience Creating environments at work that acknowledge that failures will happen—and supporting the efforts team members make to recover—can help your organization become more effective. You cannot predict every challenge, but by embracing risk and providing opportunities for people to experiment, you can be more productive. |
|
 |
Does Testing Truly Improve Software? Without revealing problems, there is no problem-solving, since we can't solve something we aren’t aware of. Each solved problem is one fewer problem in the software—and the software is improved each time a problem is removed. But it's not testing alone that improves software. So when does that happen? |
|
 |
Why the Burden of Security Should Be Assumed by the Entire Team Quality can be improved over time, and while it’s difficult to change perception, it’s still possible. But poor security can sink your ship before it even leaves the dock. Invest in the security of your application and be sure to spread that responsibility to multiple levels of your software team. |
|
 |
Security Testers Should Think like Hackers It is a common belief that testers should think like end-users by going beyond the defined requirements, seeing if the application under test addresses end-user expectations, and evaluating how it fares against competition. But with security testing, testers have to think not only like end-users, but also like hackers. |
