tag:blogger.com,1999:blog-8829373276206103863.post7128469435070181469..comments2018-03-19T08:38:01.911+01:00Comments on Clear Conceptual Thinking: Failure by delivering more than was specified?Rolfhttp://www.blogger.com/profile/16327210436812276291noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-8829373276206103863.post-79250383701916144052008-12-21T13:21:00.000+01:002008-12-21T13:21:00.000+01:00Thank you all for your comments. I decided to writ...Thank you all for your comments. I decided to write about the phenomenon in the future and hope I can come back to you to work on it.<BR/><BR/>Has anybody ever experienced really bad consequences from excess functionality? <BR/><BR/>You know, the scenarios presented here (including mine) seem to be hypothetical.Rolfhttps://www.blogger.com/profile/16327210436812276291noreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-34415653630409945572008-12-14T16:01:00.000+01:002008-12-14T16:01:00.000+01:00I'd add another category - capabilities that aren'...I'd add another category - capabilities that aren't aligned with the goals of the business. Often a little feature gets added because it's easy to do, but it's not aligned with the goals of the project. Leaving it in puts you at risk because customers will likely ask you to expand upon the functionality once you've exposed it to them, which diverts resources away from the your states goals.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-30726546282904426482008-12-01T12:20:00.000+01:002008-12-01T12:20:00.000+01:00Forgot to add: I would regard these as defects if ...Forgot to add: I would regard these as defects if the stakeholder who pays me does.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-83652215916808517902008-12-01T12:17:00.000+01:002008-12-01T12:17:00.000+01:00A feature which breaks a (previously unnoticed) st...A feature which breaks a (previously unnoticed) stakeholder's interest in having his IP secured; e.g. an "export database" function which would enable a competitor to extract valuable engineering information. <BR/><BR/>Or a feature which would expose the stakeholder's performance in an unwanted way; e.g. a function in a generic planning software which would enable the user to directly compare theAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-35987263534035055182008-11-28T14:14:00.000+01:002008-11-28T14:14:00.000+01:00@all so far: Thanks for your comments!3 answers fr...@all so far: Thanks for your comments!<BR/><BR/>3 answers from other sources (Roland, David and Sven, again. Thank you!):<BR/><BR/>1) if the additional features break some other requirements, like I suggested in my scenario, then the case is clear: surplus features are defects<BR/>2a) this brings up the question of the completeness of the spec as a whole. Only stated requirements lead to a failedRolfhttps://www.blogger.com/profile/16327210436812276291noreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-19611995431839816882008-11-28T10:30:00.000+01:002008-11-28T10:30:00.000+01:00The first thing I would do is requesting a test se...The first thing I would do is requesting a test set and a test protcol for that function from the provider. <BR/><BR/>If there is no test set, it is definitly a defect.<BR/><BR/>If there is test set, it depends...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-82140363480875294192008-11-27T21:07:00.000+01:002008-11-27T21:07:00.000+01:00With too many functions, one or more quality aspec...With too many functions, one or more quality aspects of a system will suffer.<BR/>Too many functions often have a negative effect on understandabilty or intuitive usability, like in this article about <A HREF="http://headrush.typepad.com/creating_passionate_users/2005/06/featuritis_vs_t.html" REL="nofollow">featuritis</A>. Or, as you mentioned already, the performance suffers.<BR/>Practically Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-55919439689853070192008-11-27T20:16:00.000+01:002008-11-27T20:16:00.000+01:00I am not very worried. BUt of course it is not goo...I am not very worried. BUt of course it is not good for performance, security, maintenance etc to have an excess.!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8829373276206103863.post-65393138076561658282008-11-27T19:51:00.000+01:002008-11-27T19:51:00.000+01:00How about a situation where the developer is provi...How about a situation where the developer is providing something to another party who intends to sell it to a third party.<BR/><BR/>Could it be that the middle man, perhaps with a monopoly position, might have some cunning plan about selling upgrades and endless support, and finds a product that exceeds the initially stated requirements an inconvenience.<BR/><BR/>Or what if the middle man's Anonymousnoreply@blogger.com