I mentioned that I classify each requirement as one of six types. Here is how I use them to elicit more comprehensive descriptions of the requirement.
Transformation (TR) - simple algorithmic transformation further description requires a list of inputs, outputs and the transformation algorithm.
Synchronization (SY) - things in different domains must be kept in synch. Description requires one master, one or more slaves, data set, quality of service info including error case, synchronization event, frequency of synchronization.
Information Display (ID) - a specific case of SY where the slave is a GUI or Log.
Required Behavior (RB) - A behavior that must occur, typically expressed by a state machine or sequence diagram without external actors.
Commanded Behavior (CB) - An actor effects the bahavior assynchronously. Description requires a list of actors who can command it, the command, a reference to the underlying RB, a reference to a ID indicating how the actor knows the command has been accepted, or the RB performed.
Work Piece (WP) - a behavior where the changes made to a "thing" are tracked. Description requires identification of the "thing", stages of progress for the thing, and the data set associated with each stage of progress.
As I classify Natural Language descriptions of requirements, if I can classify a requirement into more than one type, then I split it into multiple requirements.
The law of diminishing returns applies, so I use judgement as to what detail is required to adequately describe the capability.
I recognize that there may be many other details that could be added to these, and I welcome your input. But these are what I currently use to flush out more detail from the stakeholders.
Ideally, I would like to use these to generate analysis views. For instance, by collecting all the CBs associated with an actor, I can review the completeness of the actor's GUI interface.
Ideally, something in EA could generate the view for me. But I figure, worst case, I'll export stuff, massage it, and re-import it in a new view. I haven't tried this yet, but I hope it works in EA.
