Analysis models add value to the requirements development process by making it possible for you to represent information at multiple levels of abstraction.
By Karl E. Wiegers
Karl E. Wiegers is a leading authority in the requirements engineering arena. He is a frequent speaker and author of the best-selling Software Requirements, Second Edition.

Even though software development organizations are producing systems and applications that are more complex and sophisticated than ever before, progress in terms of overall project success is not as impressive. Are we attacking the right problems?
By Joe Marasco
Joe Marasco, PhD, is the author of The Software Development Edge. Joe led Rational Software’s product strategy for lifecycle tools for 17 years until its acquisition by IBM. He is the CEO of Ravenflow.

Developing precise and accurate requirements is a crucial step in the success of a development project or a new business process, and today’s emerging class of tools automate this critical process.
By Adam Frankl and Tom King
Tom King and Adam Frankl lead the product development and marketing groups at Ravenflow. Tom has 30 years experience in managing software development teams and led the team that won the ITAA Total Quality Award for Software. Adam is the founder and former publisher of The Rational Edge.

All too often, software requirements are poorly written and difficult to follow. Clarifying your specifications benefits everyone involved.
By Karl E. Wiegers
Karl E. Wiegers is Principal Consultant with Process Impact and author of More About Software Requirements: Thorny Issues and Practical Advice and Software Requirements, Second Edition, both published by Microsoft Press..

Use cases capture the functional requirements of your system and drive the software development lifecycle. That's why it is important to get use cases right.
By Terry Quatrani
Terry Quatrani is UML Evangelist for IBM Rational Software and author of Visual Modeling with Rational Rose (Addison-Wesley, 2002).

Errors of conception are the most significant kind of requirements errors, and they are the hardest to detect. In this first installment of a two-part article, Kurt examines "errors of conception," which relate to requirements errors that arise from problems with the basic conception of the solution.
By Kurt Bittner
Kurt Bittner works for IBM on software development product strategy. He is a coauthor, with Ian Spence, of Use Case Modeling (Addison-Wesley, 2002).