home

Existing functionality as requirements?

I'm wondering what other's think about a dilemma we are having amongst BA's in my organization.  When documenting requirements for maintenance to our Legacy system, some BA's feel it is quite acceptable to include current functionality as a requirement if they feel that the enhancement requirements may cause that current functionality to be affected or removed. 

 An example would be something like "Retain current functionality that allows users to update termination date."

I don't necessarily agree with this, though at times it may be valid to express to the development team that the enhancement requirements should not affect current functionality.

Anyone have any comments how to communicate things like this?

 MPS

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Then log the defect by ScottWAmbler
What about in COTS SRS? by ameliagarbo

    Sponsored Announcements & Special Offers

© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group