Specifying Software Requirements

Custom software development is a high risk business. Even with sixty years of experience under our belts we sill manage to waste millions of dollars on failed projects.
It doesn't have to be that way on your project. Software developers have known for many years that broad user engagement in writing software requirements substantially increases the probability of success.
In this talk Les Chambers looks at one of the barriers to user engagement: language.
As a user, how do you tell your story to a technical person? How do you shed light on your real world in a way that will support the development of a complete, correct, unambiguous and verifiable statement of requirement.
Citing the "use case" as an example, Les looks at the thought processes, frameworks, models and modes of expression that nontechnical people can employ to improve the accuracy and efficiency of their dialog with software developers.

Category:

Science & Technology

Tags:

• yt:quality=high
• capture
• business
• user
• system
• software
• requirements
• specification
• SRS
• URS
• SyRS
• ConOps
• functional
• story
• use
• case
• nonbehavioural
• nonfunctional
• safety
• requirement
• rationale
• concept
• of
• operations
• document
• workshop
• seminar
• training

[Jayz457]

Good video I have been asked to write some software requirements and needed a good over view and this helped out.