Software Requirements Best Practices

Email Alerts

Register now to receive news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Secure code review process: How many review rounds are needed?

    Expert Michael Cobb details how to argue for a multistep secure code review process like the Microsoft SDL, and the pros of secure coding practices.

  • virtual patching

    Virtual patching is the quick development and short-term implementation of a security policy meant to prevent an exploit from occurring as a result of a newly discovered vulnerability. A virtual patch is sometimes called a Web application firewall (WAF).

  • The whole team approach to QA/test time

    QA/test role does not just belong to the test manager. In the whole team approach, the responsibility is spread throughout the team.

  • Protecting software: Writing security requirements

    Business analysts and product managers play an important role in protecting software. Requirements expert Scott Sehlhorst explains more.

  • Requirements management process: Security and application performance

    Organizations need to explicitly address security and application performance during the requirements management process according to expert Dan Cornell.

  • Scaling Agile requirements management to the enterprise level

    While the principles of Agile requirements management are the same regardless of project size, there are several considerations for scaling to the enterprise.

  • How traceability benefits the software development lifecycle

    Read expert Scott Sehlhorst’s explanation to learn how traceability of requirements improves visibility into building the right product as well as building the product right.

  • Application security testing: Protecting your application and data

    Application security testing is critical in ensuring your data and applications are safe from security attack. This e-book, written for IT management, including QA and development managers, explains the basics of application security and then delves deeper into common vulnerabilities and performance concerns.

  • How to define security requirements and manage risk in software development

    Defining business security requirements is a collaborative effort, involving the participation of architects, business analysts and regulatory bodies. There is no black-and-white answer about achieving the best possible security for your software applications. Costs and benefits must be weighed. Read this response from expert Sue Burk for more insight into how security requirements are defined and prioritized.

  • Debunking myths of application lifecycle management

    In this tip, we expose three myths of Application Lifecycle Management (ALM) which continue to quietly impede successful software development and delivery across industries. Understanding that best-in-class isn’t always the best option, that there is no such thing in application development as one-size-fits-all and that point-to-point integrations are not a panacea will empower DevOps and large enterprise organizations to improve the speed, quality and collaborative nature of their application delivery process.

  • VIEW MORE ON : Building security into the SDLC