CrossTalk: The Journal of Defense Software Engineering. Volume 19, Number 12, December 2006
SOFTWARE TECHNOLOGY SUPPORT CENTER HILL AFB UT
Pagination or Media Count:
The articles in this issue of CrossTalk aim to help the readers with their own requirements challenges. In our first article, Twelve Requirements Basics for Project Success, Dr. Ralph Young shares insights he has gathered from his own experience as well as reading about the experience of others. Deb Jacobs follows these basics with specific advice on understanding your requirements in Interpreting Requirements in a He SaidShe Said World. Next, Dr. Nancy Mead gets even more specific as she discusses different requirements elicitation methods in Experiences in Eliciting Security Requirements. Our final theme article, Requirements as Enablers for Software Assurance, discusses work that Dr. Seok-Won Lee and Robin A. Gandhi have done to consolidate software security requirements from several guidance documents in the Department of Defense in order to identify the applicable set of security requirements necessary for certification and accreditation. Our supporting article by Dr. Jeffrey Carver, Dr. Forrest Shull, and Dr. Ioana Rus suggests performing requirements and design inspections from varying perspectives in Finding and Fixing Problems Early A Perspective-Based Approach to Requirements and Design Inspections. While all of the practices of the CMMI, AS9100, and ISO 9000 play a role in our current success with software delivery, requirements management was one of the earliest practices that showed visible results. Good requirements engineering requires more than managing existing requirements it requires effectively eliciting the requirements, verifying requirements are accurate and useful, managing those requirements, and testing the end-product against the requirements.
- Computer Programming and Software