As discussed in the About Us section, DevCreek started with a relatively simple concept; use a background process to capture JUnit Test data in Eclipse. The data could be collected with no real effort on the part of the developer, and by analyzing it we'd be able to better understand how we were testing, with an eye on how we could improve our testing practices.
That basic concept worked, and it did not take us long to figure out that there were many other possibilities for data collection from our software development processes, and that other aspects of our projects could be improved by paying closer attention to metrics. In general, software development has had the excuse that "there are no metrics". DevCreek is working to fix that problem, for good.
As you know, there are many potential metrics that can be collected for software development projects. In addition to many different measures, there are a myriad of different tools used to perform different tasks. To deal with this inherent complexity, DevCreek has taken the approach of defining simple protocols for public API's that make it easy for our user community to build DevCreek Agents for the tools they use on an everyday basis.
We encourage developers to share the Agents that they have created with the broader development community. For more information, please see the DevCreek Agents link under in the Community area of our site.
The current list of Metrics, API's and Agents is provided in the table below. Please follow the links for more information. For a general overview of building a DevCreek Agent for please see our DevCreek Agent and API Developer's Guide.
|Metrics Area||DevCreek API||Agents||Status|
|Testing||Unit Test||Eclipse - Maven - Ruby||Available|
|Deliverable Size||Lines of Code/Object Model||Eclipse||In Development|
|Deliverable Size||Function Points||Coming Soon!|
|Deliverable Size||Story Points||Coming Soon!|
|Effort||Team Size||Coming Soon!|
|Build||Build Activity||Coming Soon!|
|Quality||Issue Tracking||Bugzilla||In Development|