
Episode 518: Karl Wiegers on Software Engineering Lessons
Software Engineering Radio - the podcast for professional software developers
00:00
Non Functional Requirements
There must be a point where you get so far along that you can't change the design. Well, that becomes very expensive, right? And a good example of when that can happen as if people have not done a thoughtful job about exploring some non functional requirements along the functionality. If we don't make that an important part of our requirements exploration, then we can have a problem just like your you're getting at, gavin.
Transcript
Play full episode