有人使用 ABC Metric 来测量应用程序的大小吗？
它有一些好处（比如它封装了圈复杂度的概念），我想知道是否有人在“现实生活”中使用过它。 如果是这样，您的经历是什么？ 它是衡量规模的有用指标吗（相对于 KLOC 或功能点）？
对于那些想知道我抽什么烟的人： 以下是一些信息的链接： http://c2.com/cgi/wiki/Wiki ?AbcMetric
There are some nice things about it (like it encapsulates the concept of Cyclomatic complexity), and I was wondering if anyone has used it in "real life". If so, what are your experiences? Is it a useful measure of size (as opposed to KLOC or Function Points)?
For those wondering what I'm smoking:
Here's a link to some info on it: http://c2.com/cgi/wiki/Wiki?AbcMetric
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
只要您在所有应用程序中使用相同的方法，就可以通过 LOC 或您能想到的任何其他指标来安全地测量应用程序的绝对“大小”。
然而，只有当您谈论代码库的重构和维护时，大小本身才真正重要。 几乎必须将大小指标与覆盖率统计数据结合使用。
但大多数时候，功能点或类似的概念可以让您更好地了解您的应用程序到底有多大。
例如，如果它有 10 FP，那么它很小，如果它有 200，它可能很大。
但如果它有 100 个 KLOC，除了我可能会花一些时间阅读这些行之外，它本身还能告诉我什么？ 几乎什么都没有，我必须考虑大量其他因素才能理解这个指标。
显然，FP 有一个显着的缺点，即正确计算成本高昂。
The application's sheer 'size' could be safely measured in LOCs or any other metrics you could think of as long as you use the same approach across all of your application.
However the size on its own really matters only when you're talking about re-factoring and maintainance of the code base. It's almost mandatory to use the size metrics are useful in conjuction with the coverage statistics.
But most of the time Function Points or similar concepts give you much better view of how big your application really is.
I.e. as an example if it has 10 FP it's tiny, if it has 200 it's probably big.
But if it has 100 KLOCs what does it tell me on its own, aside from the fact that I'll probably spend some time reading those lines? Almost nothing, I have to take an enourmous amount of other factors into an account to be able to understand this metric.
Obviously the FPs have a significant downside of being expensive to properly calculate.