Product Risk Analysis Clarifies Requirements

This presentation re-emphasizes that requirements are important. The difference between functional and nonfunctional requirements will be covered. Then, Product Risk Analysis will be described, along with the elements of the analysis and steps toward performing the analysis.

This paper was originally presented at STAREAST '99 — a conference produced by Software Quality Engineering. For more information on this conference, visit the current STAREAST website.

About the author

Jim Kandler's picture Jim Kandler

James Kandler has been involved in software management and quality with several different companies, since 1989. He holds a Bachelor's degree in Biomedical Engineering, and a Masters degree in Engineering Management. Currently he is Manager of Software Quality Engineering in Corporate Research of Baxter Healthcare Corporation, providing software testing and process consulting and resources to Baxter divisions. This group has been increasingly involved with IT and product validation and has increased 250 percent in the last year. He sits on 2 corporate boards and coordinates software quality outsourcing. He is a member of IEEE and ACM and holds the ASQ STQE certification and the QAI CSTE certifications. He has also presented software quality topics at several international conferences.

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!