This paper describes a precise form of use case that promotes the specification of inter-actor options and alternative course conditions. Precise cases use a description language with a Structured English grammar to specify interactions. The design goals for the notation are to maximize understandability by application experts, not familiar with formal object-oriented concepts, and to supply sufficient information and structure to support both manual and automated test design. In addition to a detailed example, a development process, and guidelines for modeling and test coverage are provided.

Choosing an analyst is so much more than just selecting the guy with the most experience in a particular technology or domain. The truth of it is you need to find someone that is fairly agnostic of the applications and technologies within your environment and find someone that first comes with the foundation skills that will make them a great analyst. The second thing you want to ensure is that the person comes with the personality to make them a great fit within your environment, and finally you want to find a person who fits the career level to meet the performance you are expecting for the assigned role. The last thing you look at is the specific technologies they have experience with (unless there is some very unique challenge coupled with an elongated learning curve).

Requirements quality is tangible. It is possible to look at the specific characteristics of requirements documentation and determine if it is sufficiently clear, accurate and complete to lead to a successful project. Since flawed requirements trigger about 70% of all project failures,1 this paper will present some hard and fast rules for looking at requirements documents, in any format, and being able to determine if they are reasonably well constructed. It will outline the key points to look for in a requirements document, and why this can save a company hundreds of thousands of dollars. Finally, it will offer five straightforward questions to address when evaluating requirements quality.