What if the application has functionality that wasn't in the requirements?


Q: What if the application has functionality that wasn't in the requirements?

A: It can take a serious effort to determine if an application has significant unexpected or hidden functionality, which can indicate deeper problems in the software development process.

If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer.

If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the unexpected functionality only affects areas, e.g. minor improvements in user interface, then it may not be a significant risk.


__________________________________________

Copyright 2000 - 2010 Rob Davis PE. All rights are reserved. No part of

this document may be reproduced in any form whatsoever

without written permission from Rob Davis, PE.

http://www.softwaretestengineer.com

http://www.robdavispe.com


software qa testing test tester software qa testing test tester software qa testing test tester software qa testing test tester software qa testing test tester software qa testing test tester