How To Address The Problem Of Poorly-Defined Requirements In Software System Design Software Engineering Institute (SEI) Webcast Series podcast

İçerik Carnegie Mellon University Software Engineering Institute and SEI Members of Technical Staff tarafından sağlanmıştır. Bölümler, grafikler ve podcast açıklamaları dahil tüm podcast içeriği doğrudan Carnegie Mellon University Software Engineering Institute and SEI Members of Technical Staff veya podcast platform ortağı tarafından yüklenir ve sağlanır. Birinin telif hakkıyla korunan çalışmanızı izniniz olmadan kullandığını düşünüyorsanız burada https://tr.player.fm/legal özetlenen süreci takip edebilirsiniz.

Software Engineering Institute (SEI) Webcast Series »
How to Address the Problem of Poorly-Defined Requirements in Software System Design

25d ago 54:48

Paylaş

MP4•Bölüm sayfası

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

174 bölüm

#Tech #Cybersecurity #Securecoding #Softwarearchitecture #Softwaredevelopment #Softwareengineering #Carnegie Mellon University Software Engineering Institute #SEI Members of Technical Staff #Video #Podcasting Education