Welcome to the Software Process and Measurement Cast 70!The interview on the SPaMCAST 70 is with Suzanne Robertson.  We talked about requirements . . . a lot and that was good therefore this part one of the interview.Suzanne is co-author of (Addison-Wesley Second Edition 2006) a book that provides guidance on finding requirements and writing them so that they can be understood by all the stakeholders. She has more than 30 years experience in systems specification and building. Her courses on requirements, systems analysis, design and problem solving are well known for their innovative workshops and business games.Suzanne has varied experience as a manager, programmer, analyst, and designer. She has consulted, done research and taught in Europe, Australia, the Far East and the United States. Current work includes research and consulting on stakeholder rights and responsibilities, the specification and reuse of requirements and techniques for assessing requirements specifications. The product of this research is Volere, a complete requirements process and template for assessing requirements quality, and for specifying business requirements.Contact Data:Atlantic Systems Guild:  Volere Requirements Resouces:  Email:  [email protected]  The essay is a continuation of my essay titled "Traceability: A Radical Approach Based on User Involvement".   Part Five discusses the final leg of the model criticality.   We will now have the heart of the model defined and be ready to start putting it all together.Join the SPaMCAST’s community by joining the SPaMCAST Facebook page and get involved!!!!  There are a number of ways to share your thoughts with SPaMCAST: •    Email SPaMCAST at [email protected]•    Voice messages can be left at 1-206-888-6111•    Twitter – •    BLOG – •    FACEBOOK!!!! Software Process and Measurement               Next Software Process and Measurement Cast: The interview in show 71 is Part 2 of my interview with Suzanne Robertson, author, teacher, consultant and a member of The Atlantic Systems Guild.  We finished our discussion of requirements and mastering the requirements process.