How to Address the Problem of Poorly-Defined Requirements in Software System Design
• Webcast
Publisher
Software Engineering Institute
Topic or Tag
Watch
Abstract
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
About the Speaker
Lyndsi A. Hughes
Lyndsi Hughes is a member of the technical staff in the CERT division of the Software Engineering Institute (SEI) at Carnegie Mellon University (CMU).
Lyndsi joined the SEI in 2010. During her tenure at the SEI, Lyndsi has operated and maintained numerous specialized computing environments in support of research projects, …
Read more
Lori Flynn
Dr. Lori Flynn is a senior software security researcher in the CERT Division at Carnegie Mellon University's Software Engineering Institute. Flynn's research focuses on automated software security analyses using static analysis. Sometimes her work extends to cybersecurity, AI/ML, automated program repair, malware analysis, SBOM/SCA tools, DevSecOps, and mobile computing. She …
Read more