The concepts
The CodeCount toolset is a collection of tools designed to automate the collection of source code sizing information. The CodeCount toolset spans multiple programming languages and utilizes one of two possible Source Lines of Code (SLOC) definitions, physical or logical.
The CodeCount toolset is provided in source code only, and may be used as is, modified or further distributed subject to certain limitations.
The tools in the collection are supplied in C source code only. You are responsible for compiling and building executable versions.
The Product
The CodeCount toolset is copyright USC Center for Software Engineering but is made available with a Limited Public License which permits the distribution of the modifications you make provided you return a copy to us so we can further enhance the toolset for the benefit of all.
Joel on Software is a webpage of a NY sw developer, Joel Spolsky, which also has partially published in print. This page is the archive page with all the articles.
Crap4j is a Java implementation of the CRAP (Change Risk Analysis and Predictions) software metric – a mildly offensive metric name to help protect you from truly offensive code.
The CRAP metric combines cyclomatic complexity and code coverage from automated tests (e.g. JUnit tests) to help you identify code that might be particularly difficult to understand, test, or maintain – the kind of code that makes developers say: “This is crap!” or, if they are stuck maintaining it, “Oh, crap!”.
The best way to learn more about CRAP and Crap4j is to check the various articles, newsgroups and blogs about them.
"Relying on CVS and Subversion [...] with access controls limited to the select few committers makes it very difficult for those on the fringes to get more involved."
Europäische Geschichte Online (EGO) is an online European transcultural history composed of multimedia knowledge items encompassing the period from 1450 to 1950. EGO is methodologically pragmatic, international and interdisciplinary. It combines a variety of approaches and perspectives from debates in multiple languages and thus interlinks international scholars working in the various disciplines of European history.
Business process management (BPM) – while also its own independent practice / school of thought – is an application of technology that is served by many products, not the least of which is jBPM. The best definition of BPM that I've found is: "Business Process Management (BPM) is the concept of shepherding work items through a multi-step process. The items are identified and tracked as they move through each step, with either specified people or applications processing the information. The process flow is determined by process logic and the applications (or processes) play virtually no role in determining where the messages are sent.".
C. Paris, N. Colineau, and R. Wilkinson. HT '09: Proceedings of the Twentieth ACM Conference on Hypertext and Hypermedia, New York, NY, USA, ACM, (July 2009)
D. Rosca, S. Greenspan, M. Feblowitz, and C. Wild. Requirements Engineering, 1997., Proceedings of the Third IEEE International Symposium on, (January 1997)
T. Sohn, K. Li, W. Griswold, and J. Hollan. Proceeding of the twenty-sixth annual SIGCHI conference on Human factors in computing systems, page 433-442. New York, NY, USA, ACM, (2008)