USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering USC Affiliates Code Counter News USC Annual Research Review 16 March 2006 Winsor Brown - USC Lori Vaughan - Northrop Grumman Mathy Pandian - Aerospace Corporation

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Objective and Agenda  Provide status on USC CodeCount™ Tools Define Logical Source Line of Code Why Code Count Tools are important Status of Code Count Tools  Issues and Actions Solicit industry support to maintain and improve CodeCount™ Tools Future Plans

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering What can we do to Help Dilbert?

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Are we Logical or Physical?  Two major types of SLOC (Source Line of Code) Physical SLOC A count of "blank lines, comment lines" in the text of the program's source code Logical SLOC Measures the number of "statements" Language specific  Easier to create tools that measure physical SLOC  Logical SLOC measures are not sensitive to irrelevant formatting and style conventions  Physical SLOC is sensitive to formatting and style conventions  Logical SLOC can often be significantly different from physical SLOC

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Industry Requires a Set of Logical Counter Standards  Why General Estimation and Acquisition insight Historical - representative quantification of systems Size Input for parametric models Foundation for COCOMO Tool Suite  Investment in USC CodeCount™ output format USC is neutral provider of service Normalized for comparison and evaluation Systems are integration intensive Teammates and subcontractors Some industries automate CodeCount ™ output for Historical Data collection (ex: Northrop Grumman, Tecolote) USC Center for Systems and Software Engineering (CSSE) CodeCount ™ suite supports many languages

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering CodeCount Structure Most of the COCOMO suite models require some sort of sizing of computer code as an input. Ensuring consistency across independent organizations in the rules used to count lines of code is often difficult to achieve. To that end, USC-CSE highly encourages the use of CodeCount for the purposes of sizing your software for historical data collection and reporting purposes. This toolset is a collection of tools designed to automate the collection of source code sizing information. It spans multiple programming languages and utilizes one of two possible Source Lines of Code (SLOC) definitions, physical or logical Limited public license – copy left agreement George Kalb (Northrop Grumman Electronic Systems: 1994 original author) Without Industry support, CodeCount ™ team is unable to support and further enhance the toolset for the benefit of all.

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering USC CSE Affiliates' Private Area – Today & Tomorrow Today Ada Assembly C/C++ COBOL FORTRAN Java JOVIAL Pascal PL1 CodeCount ™ Tools were replaced with Rev-7 in year 2003 Tomorrow Today plus SQL Perl Markup Languages JavaScript C# C/C++ (’06) Java (’06)

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering NRO Cost Group (NCG) Request for Product Line Enhancement  Objectives: Make available logical counters for unsupported Languages and Industry Normalization  New counters SQL Perl Markup Languages JavaScript C# Diff  Requested Aerospace Corporation for assistance with Industry usage and testing Aerospace Corporation contributed concept of utilizing USC CSSE, IV&V and Software Engineering expertise Northrop Grumman Mission Systems involvement as Product Line usage experts and project management assistance

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Planned Affiliates Page – June 2006  CodeCount™ Packages to include Language Specific Labeling (e.g. Java CodeCount) Source code for counter Self documented with fixes and dates Logical code definition in table format Sample Input file (with multiple files referenced) Source files referenced Output file Each Language will include syntax specific definitions for Logical count in table format

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Available CodeCount Languages LanguageLast revision DateVersion number SQL2/2006Rev 2 Perl2/2006Rev 2 MUL2/2006Rev 2 C# 1/2005Rev 5 Java 7/2003Rev 8 C/C++ 7/2003Rev 8 Javascript 3/1999Rev 2 Ada 7/2003Rev 7 Assembly 7/2003Rev 7 Fortran 7/2003Rev 7 Cobol 7/2003Rev 7 Jovial 7/2003Rev 7 Pascal 7/2003Rev 7 PL/1 7/2003Rev 7

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Accomplishments From Fall 2005 (CS 590)  Scope definition Updating existing Languages and Adding New CodeCount™ Languages Diff tools are currently outside of scope, in the future requirement set  Focus on testing  Students broken into Language teams C/C++, Java, Javascript, SQL, Perl, Markup Language (MUL), and C# Documented bugs found  Professional Assistants Compiled bugs found and forwarded to NCG for SQL, Perl and MUL NCG / Tecolote updated counters

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Current Winter/Spring 2006 (CS 590)  Teams C/C++, Java, Perl, SQL, MUL, JavaScript, C#, CS577 Intelligent Super Structure (CS577ab project), Object Lines of Code (OLOC; for PSP) for C/C++ and Java  Schedule June 2006 all new and updated counters to be posted  Focus on Regression testing Scheduling and Deadlines Packaging Posting on the Affiliates Page

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Related Activities and Needs  CS 577 Course – Complete MBASE documentation XML counter Intelligence Superstructure (calls regular CodeCount™ tools) Differencing between versions with re-factoring and reuse-types Counting embedded and/or specialized code (e.g. security kernel)  Additional Industry donations of existing counters  Continued Sustained Mechanism for CodeCount™ configuration management New languages New features to improve usability  CodeCount™ team needs help to be a true product line Affiliate support needed to maintain consistency Industry Grant CodeCount ™ (CoCo) Suite is at the center of all COCOMO products

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Dr. Boehm and the CSSE… Barry Industry Affiliates - Let’s show our support for the new USC Center for Systems and Software Engineering (CSSE) Convocation.