Cell Phone Software Forum
| View previous topic :: View next topic |
| Author |
Message |
Guest
|
 Posted: Sun May 06, 2007 9:09 pm Post subject: Discuss in detail why should some software metrics be kept " |
 |
|
Hi every one, am in to a serious discussion with you.. i hop you all
with me..
In software development there are lot "metrics" involved. List down
these metrics and explain the usage of these metrics. Discuss in
detail why should some software metrics be kept "private"? |
|
| Back to top |
|
 |
| |
Ads |
Advertising
Sponsor
|
|
Phlip
Guest
|
| Posted: Sun May 06, 2007 9:34 pm Post subject: Re: Discuss in detail why should some software metrics be ke |
|
|
suziperu wrote:
| Quote: |
In software development there are lot "metrics" involved. List down
these metrics and explain the usage of these metrics.
|
We are not here to do your homework or exams for you!
If we disagreed with your course sylabus, for example, you'd be screwed...
| Quote: |
Discuss in
detail why should some software metrics be kept "private"?
|
None whatsoever; here's an example why:
http://www.indicthreads.com/content/view/446/105/
"Under its Open Quality Initiative, Agitar publishes extensive unit-level
testing metrics about its own products, including formal weekly-build
results of its upcoming unannounced products and trends over time. Agitar
also publishes these testing metrics for popular open-source Java projects,
including Hibernate, JUnit, Struts, Cruise Control, Spring, and commercial
open source products such as JasperSoft's JasperServer and Oracle's
BerkeleyDB Java edition.
"Available at the new web site, www.openquality.org, are:
* Agitar's Open Quality metrics on its own commercial products;
* The metrics for popular open-source projects and the products of other
initiative participants;
* Quality-Level Agreement (QLA) templates that establish binding
acceptance-quality criteria for in-house, offshore, or outsourced software
development.
"Agitar challenges other software companies to publish testing metrics for
their own products and is making the Open Quality website available to all
Java ISVs and SIs willing to go public with their testing data. Metrics on
the quantity and quality of unit tests are a very effective and objective
way to measure the depth of testing as the code is developed. Unit tests are
evidence that quality was "built into" the code and help ensure that quality
remains high as the software is changed. The initiative's goal is to let
developers and decision-makers know how thoroughly the code they use has
been unit-tested -- the bedrock of quality."
Now suppose I sought to retain a software shop. Do I chose shop A, who
publishes all their metrics, each time their developers integrate, on their
open web site? Or shop B who keeps metrics a secret?
(Or C, who doesn't collect any metrics at all?)
--
Phlip
http://www.oreilly.com/catalog/9780596510657/
"Test Driven Ajax (on Rails)"
assert_xpath, assert_javascript, & assert_ajax |
|
| Back to top |
|
|
| |
Ads |
Advertising
Sponsor
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
223 Attacks blocked
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
