Am 08.07.2014 21:43, schrieb Antoine Isaac:
>> Related to your comment during the discussion.
>> If you have a requirement in mind and you are not sure if it is
>> already contained in the requirements db, just create an new requirement.
>> I can look if there is already a requirement in the db with the same
>> semantics in order to delete duplicates.
>
>
> Great!
> I'd expect that you mail us before deleting duplicates. This would
> probably be very useful for the person who created the requirements, and
> for the others, who could also see what's happening during requirement
> elicitation.
>
I would not delete them, I would join them by linking them as duplicates.
Moreover, when a new requirement is created, existing requirements
should be autosuggested based on the description, either during entering
or after submission, where the creator could be asked to review similar
requirements, if they match. I assume that this can be done quite simply
without too much effort. For the first shot, I would simply search for
all requirements that have matching terms somewhere in the description,
let's see how far we get with that.
Cheers,
Kai
--
Dr. Kai Eckert, University of Mannheim
Research Group Data and Web Science
http://dws.informatik.uni-mannheim.de/
Phone: +49 (0) 621 - 181 2637
PGP Public Key: http://www.kaiec.org/2012/pgp/pubkey.asc
A987 3760 12A6 35A4 E6D2 577E 513A 6B84 C755 5A67
|