This results in variation between languages; the same task that can be done in a single line of code (or no code at all) in one language may require several lines of code in another. 7. Problems with Multiple Languages: In today s software scenario, software is often developed in more than one language.SLOC is typically used to predict the amount of effort that will be required to develop a program, as well as to estimate programming productivity or maintainability once the software is produced.there are some drawbacks in SLOC metrics that affect the quality of software because of SLOC metric output is used as a input in other Software Estimation methods Like COCOMO Model.Keywords SLOC, Metrics, Software Estimation, COCOMO, Performance Analysis I.
Advantages Using Sloc Software Metric Examples Software Is OftenINTRODUCTION There sometimes is a decidedly dark side to SLOC software metric that many of us have observed, but few have openly discussed. Whether or not our models are correct, and regardless of how well or poorly we collect and compute software metrics, people s behaviors change in predictable ways to provide the answers management asks for when metrics are applied. For this reasons we Consider Source lines of code metrics for our analysis. SLOC Metric works on Source Lines of code but when we talk about the different Programming Languages the Lines of code to perform task is vary language to language because different languages have different structures. Our in-depth analysis in this field provide a comprehensive view to understand what SLOC metric do and how much one can rely on SLOC metric. II. ADVANTAGE AND DISADVANTAGES OF LOC METRICS Advantages:- 1. Advantages Using Sloc Software Metric Examples Manual Counting EffortScope for Automation of Counting: Since Line of Code is a physical entity; manual counting effort can be easily eliminated by automating the counting process. Small utilities may be developed for counting the SLOC in a program. However, a code counting utility developed for a specific language cannot be used for other languages due to the syntactical and structural differences among languages. An Intuitive Metric: Line of Code serves as an intuitive metric for measuring the size of software because it can be seen and the effect of it can be visualized. Function points are said to be more of an objective metric which cannot be imagined as being a physical entity, it exists only in the logical space. This way, LOC comes in handy to express the size of software among programmers with low levels of experience 4. Disadvantages:- 1. Lack of Accountability: Lines of code measure suffers from some fundamental problems. Lack of Cohesion with Functionality: Though experiments have repeatedly confirmed that effort is highly correlated with SLOC, functionality is less well correlated with SLOC. That is, skilled developers may be able to develop the same functionality with far less code, so one program with less SLOC may exhibit more functionality than another similar program. In particular, SLOC is a poor productivity measure of individuals, because a developer who develops only a few lines may still be more productive than a developer creating more lines of code - even more: some good refactoring like extract method to get rid of redundant code and keep it clean will mostly reduce the lines of code2. Adverse Impact on Estimation: Because of the fact presented under point 1, estimates based on lines of code can adversely go wrong, in all possibility. Developer s Experience: Implementation of a specific logic differs based on the level of experience of the developer. Hence, number of lines of code differs from person to person. One of the applications is written in C and the other application written in a language like COBOL. The number of function points would be exactly the same, but aspects of the application would be different. The lines of code needed to develop the application would certainly not be the same. As a consequence, the amount of effort required to develop the application would be different (hours per function point). Unlike Lines of Code, the number of Function Points will remain constant. Advent of GUI Tools: With the advent of GUI-based programming languages and tools such as Visual Basic, programmers can write relatively little code and achieve high levels of functionality. For example, instead of writing a program to create a window and draw a button, a user with a GUI tool can use drag-and-drop and other mouse operations to place components on a workspace. Code that is automatically generated by a GUI tool is not usually taken into consideration when using SLOC methods of measurement. This results in variation between languages; the same task that can be done in a single line of code (or no code at all) in one language may require several lines of code in another.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |