tag:blogger.com,1999:blog-2065900066225575678.post3873752811248057646..comments2023-08-29T12:36:46.982+00:00Comments on The Nexus - Stakeholders, Requirements and Value: Requirements RevisitedAlanAJhttp://www.blogger.com/profile/02109956243066058539noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2065900066225575678.post-22050720955915404452008-01-29T23:47:00.000+00:002008-01-29T23:47:00.000+00:00Thanks, Roger. We discussed scalar requirements o...Thanks, Roger. We discussed scalar requirements on a <A HREF="https://www.blogger.com/comment.g?blogID=2065900066225575678&postID=6489669728239697769" REL="nofollow">previous post</A>AlanAJ01https://www.blogger.com/profile/02622385662655064132noreply@blogger.comtag:blogger.com,1999:blog-2065900066225575678.post-54257003702450466792008-01-29T23:12:00.000+00:002008-01-29T23:12:00.000+00:00Good point regarding risks and claimed levels of s...Good point regarding risks and claimed levels of satisfaction.<BR/><BR/>Requirements generally have a metric embedded in the condition. Sometimes this metric is scalar. For example, a reliability requirement might specify a minimum uptime (the percentage of time the service successfully delivers functionality). In that case, uptime is a scalar metric.<BR/><BR/>When testing, it can be useful not to just verify that the product meets its minimum uptime, but to gauge what the actual uptime is. Then the sales and marcom departments can use the figure, and the organization has a baseline for improvement.Roger L. Cauvinhttps://www.blogger.com/profile/08969779835314260680noreply@blogger.com