To set this view - I work in one of the industries which assesses everything too much and One of the main metrics we love tracking is the SLOC (code source - declarative and executable statements). We use it for project size and cost estimates, project planning, and many other things. We try to use it to compare apples to apples (i.e., we do not compare SLOC in one language / domain to any other language / domain). Note : We do not evaluate different developers on this metric, nor do we call some wrong or bad things because the SOACAC is different from the hope we do , However, the possibility of having more bugs to consider a project is more SOLOC.
To a large extent, I have started working in projects that use libraries instead of components, otherwise hands will be coded - for example JSF instead of JSF, rather than JDBC, in Hibernation Be it Therefore ... instead of writing lines of code, our team is developing XML files XML Mapping still tries, and still there is a vague connection to complexity - that in a given project in these XML configuration files More than 100X can suggest that more attempts have been made to make it and it can be more complex to debug than just one project, 1/100 of XML files.
So ... Is there any suggestion for measuring the size of these XML configuration files? # Element # element of elements? anything else?
Interesting questions are the only metric I know (except for counting nodes and properties, as you suggest Some structured documents are called complexity metrics.
Is currently its best link (it's been a while) I will also get this small device which, apparently It will count for you (other can be):
Besides, I'm afraid that my only sol It seems just right to track just one matrix, and to re-evaluate them to determine whether they actually tend to be striving with the effort applied to each document ...
Comments
Post a Comment