How to Address the Problem of Poorly-Defined Requirements in Software System Design

This webcast offers a solution to the problem of poorly defined requirements in system design that can lead to software flaws, cost and time overruns, and stakeholder dissatisfaction. We will tell you how to use a structured process called the ATAM (architectural tradeoffs analysis method) to develop a system design by eliciting requirements, scenarios, and priorities from stakeholders. Then, we will explain how to measure compliance with those requirements during testing using DevSecOps principles and tools, such as the SEI's Silent Sentinel.

What Will Attendees Learn?

• What software quality attributes are and why they are important
• How to prioritize competing requirements
• How to ensure architectural requirements are satisfied during development in a DevSecOps toolchain