For Programmers: Free Programming Magazines  


Home > Archive > Software Testing > May 2007 > Re: Improving the quality of software/software quality - Measurement, Standards, Deve









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: Improving the quality of software/software quality - Measurement, Standards, Deve
papayamilkshake@gmail.com

2007-05-19, 8:10 am

Though I'm pretty new in terms of software testing; apologises on any
shallow comments here.

For measurement, it's worth considering Cyclomatic Complexity and
Essential Complexity originated from McCabe that measures the linearly
path taken in a program/code.

With a defined value/metric, you can assess/measure the qualtiy of the
code :)

Regards
Hs
http://loadrunnertnt.blogspot.com

On May 17, 10:47 pm, "H. S. Lahman" <h.lah...@verizon.net> wrote:
> Responding to Game...
>
>
> Define 'quality' first.
>
>
>
>
>
> The short answer is Yes, especially if one defines quality more broadly
> than reliability.
>
>
> That depends on how bad the software reliability is. For a shop at
> 3-Sigma producing serious crap, testing will have the biggest bang for
> the buck. For a shop already at 6-Sigma testing will have virtually no
> direct affect on reliability compared to other activities.
>
> *************
> There is nothing wrong with me that could
> not be cured by a capful of Drano.
>
> H. S. Lahman
> h...@pathfindermda.com
> Pathfinder Solutionshttp://www.pathfindermda.com
> blog:http://pathfinderpeople.blogs.com/hslahman
> "Model-Based Translation: The Next Step in Agile Development". Email
> i...@pathfindermda.com for your copy.
> Pathfinder is hiring:http://www.pathfindermda.com/about_us/careers_pos3.php.
> (888)OOA-PATH



Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com