Post

1 follower Follow
0
Avatar

Deleting "phantom" requirements

Hi!

I have a shared project which has multiple packages and package files, which is being worked on by multiple analysts (simultaneously).

In the course of moving, rearranging and renumbering packages, we seem to have created a set of "phantom" requirements. The requirements are included in the requirements list, but they are not identified with ANY package (including the root package).

When I try to delete them, I get an "unhandled exception" (Object reference not set to an instance of an object), which is associated with the UCD file.

I have done a system directory cleanup, but that did not help.

This may need to go to "support", but I'm hoping to get an answer soon.

I think I can work around this, because the requirements are not appearing in my BRD, although they ARE appearing in my Excel requirements extract.

Thanks!

Tom

Tom Tomasovic Answered

Please sign in to leave a comment.

1 comment

0
Avatar

I'm not sure what might have happened here exactly, Tom, but I think it'd be best if you zipped up your working folder and sent it in to us (support@serlio.com). Let us know which requirements are the ghosts, and we should be able to clean up the data and put things right. (Of course your project will remain completely confidential, as always.)

Jason

Permanently deleted user 0 votes
Comment actions Permalink