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

Thinking about Quoins: Strategic Traceability of Architecturally Significant Requirements

Author Jane Cleland-Huang provides an audio recording of her Requirements column, in which she discusses how requirements engineers can keep developers informed of underlying architectural decisions and help preserve code quality during change maintenance.


Meet Elaine: A Persona-Driven Approach to Exploring Architecturally Significant Requirements

Author Jane Cleland-Huang discusses how architecturally-savvy personas provide a tangible approach for capturing performance, reliability, security, and other quality goals and for reasoning about their impact on system design.


The Inhibited Analyst

Requirements analysts need to be more inquisitive and know why people want things as well as what happens beforehand. This requires them to become less inhibited and keep asking questions until they and their stakeholders are satisfied with the answers.


What Time Is It, Eccles?

Requirements analysts need a new toolbox with both the right tools and the instructions to use them including agile development and user-centered design for techniques such as analysis of Web analytics, wire-framing, and user stories. We can also look to the creativity literature and take techniques such as constraint removal, storytelling, and other worlds.


Requirements Analysis: The Next Generation

Most requirements research and vision papers tend to focus on the near future, one research advance at a time. This podcast explores requirements practices 20 years from now, based on predicted changes to technologies, applications, and stakeholders.


Showing 6 - 10 of 16 results.
Items per Page 5
of 4