Software Requirements Talk Podcast LogoSoftware Requirements Talk

Software Requirements Talk is the podcast version of IEEE Software magazine's Requirements department, helmed by Jane Cleland-Huang. Each issue, Jane will read what appeared in print for your listening pleasure.

About Jane Cleland-Huang

Jane Cleland-Huang is an associate professor at DePaul University in Chicago as well as North American director for the Center of Excellence in Software Traceability. Her research work includes a focus on collaborative requirements engineering processes and software traceability. She has an impressive track record of research publications, and her work has earned her five distinguished-paper awards at highly ranked conferences. She coauthored a paper that was selected as a "top pick" for IEEE Software's 25th anniversary.

As editor of the Requirements column, Jane aims to make requirements and their importance more widely understood by developers, business people, and management. Understanding comes from knowing what requirements means to you and why you should care about it. Jane and her guest columnists will write about their different perspectives on requirements, and explore new areas of software engineering where requirements matter. The focus is on practical and accessible ideas.

Subscribe iTunes | Google | RSS

GORE, SORE, or What?

by Ian Alexander

Competing schools of thought in both research and industry advocate different approaches to requirements. Each favors one particular kind of artifact, such as scenarios, goals, priorities, and context models. But focusing on any one of these risks failing to discover critical project information that could readily be unearthed by other means. Perhaps a mix-and-match approach that combines requirement methods would be more effective.


Storyboarding Requirements

This installment of Software Requirements Talk describes a way to use storyboards to capture the interplay between human interaction and service design and so improve the quality of service design delivery.


Oi! Analysts

Certification for requirements analysts requires focusing on a small, possibly unrepresentative, set of tasks that might not reflect domain knowledge and could lead to good analysts not getting certified because they don't do well on the exam.


Service Design, It's All in the Brand

This installment argues that requirements analysts will soon need to deal with service design, and describes one service design method to demonstrate the challenges that analysts will face.


Agile Requirements

This column looks at agile techniques in requirements processes, summarizes their successes and failures so far, and proposes that we re-consider our use of electronic documentation in requirements projects.


Showing 6 - 10 of 10 results.
Items per Page 5
of 2