This paper defines the best software metrics that can be used to define the size of the software in the current industry of information technology (IT)
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
A software system continues to grow in size and complexity, it becomes increasing difficult to
understand and manage. Software metrics are units of software measurement. As improvement in coding tools
allow software developer to produce larger amount of software to meet ever expanding requirements. A method
to measure software product, process and project must be used. In this article, we first introduce the software
metrics including the definition of metrics and the history of this field. We aim at a comprehensive survey of the
metrics available for measuring attributes related to software entities. Some classical metrics such as Lines of
codes LOC, Halstead complexity metric (HCM), Function Point analysis and others are discussed and
analyzed. Then we bring up the complexity metrics methods, such as McCabe complexity metrics and object
oriented metrics(C&K method), with real world examples. The comparison and relationship of these metrics are
also presented.
FUNDAMENTALS OF software developement and a detail outcome of the software based on the project management and the various metrics and measurements development in software engineering
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
A software system continues to grow in size and complexity, it becomes increasing difficult to
understand and manage. Software metrics are units of software measurement. As improvement in coding tools
allow software developer to produce larger amount of software to meet ever expanding requirements. A method
to measure software product, process and project must be used. In this article, we first introduce the software
metrics including the definition of metrics and the history of this field. We aim at a comprehensive survey of the
metrics available for measuring attributes related to software entities. Some classical metrics such as Lines of
codes LOC, Halstead complexity metric (HCM), Function Point analysis and others are discussed and
analyzed. Then we bring up the complexity metrics methods, such as McCabe complexity metrics and object
oriented metrics(C&K method), with real world examples. The comparison and relationship of these metrics are
also presented.
FUNDAMENTALS OF software developement and a detail outcome of the software based on the project management and the various metrics and measurements development in software engineering
A study of various viewpoints and aspects software quality perspectiveeSAT Journals
Abstract The software quality is very important research of software engineering grown from the last two decades. The software engineering paradigm adopted by many organizations to develop the high quality software at affordable cost. The high quality software is considered as one of the key factor in the rapid growth of Global Software Development. The software metrics computes and evaluates the quality characteristics and used to take quantitative and qualitative decisions for risk assessment and reduction. The multiple stakeholders can view the software quality in multiple angles with various aspects. In this paper we present multiple views of the software quality with respect to various quality aspects. Key Words : Stakeholders, Functional aspect, Structural aspect, Process aspect, Metrics etc.
7.significance of software layered technology on size of projects (2)EditorJST
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process (AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a software project.
Identification, Analysis & Empirical Validation (IAV) of Object Oriented Desi...rahulmonikasharma
Metrics and Measure are closely inter-related to each other. Measure is defined as way of defining amount, dimension, capacity or size of some attribute of a product in quantitative manner while Metric is unit used for measuring attribute. Software quality is one of the major concerns that need to be addressed and measured. Object oriented (OO) systems require effective metrics to assess quality of software. The paper is designed to identify attributes and measures that can help in determining and affecting quality attributes. The paper conducts empirical study by taking public dataset KC1 from NASA project database. It is validated by applying statistical techniques like correlation analysis and regression analysis. After analysis of data, it is found that metrics SLOC, RFC, WMC and CBO are significant and treated as quality indicators while metrics DIT and NOC are not significant. The results produced from them throws significant impact on improving software quality.
A study of various viewpoints and aspects software quality perspectiveeSAT Journals
Abstract The software quality is very important research of software engineering grown from the last two decades. The software engineering paradigm adopted by many organizations to develop the high quality software at affordable cost. The high quality software is considered as one of the key factor in the rapid growth of Global Software Development. The software metrics computes and evaluates the quality characteristics and used to take quantitative and qualitative decisions for risk assessment and reduction. The multiple stakeholders can view the software quality in multiple angles with various aspects. In this paper we present multiple views of the software quality with respect to various quality aspects. Key Words : Stakeholders, Functional aspect, Structural aspect, Process aspect, Metrics etc.
7.significance of software layered technology on size of projects (2)EditorJST
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process (AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a software project.
Identification, Analysis & Empirical Validation (IAV) of Object Oriented Desi...rahulmonikasharma
Metrics and Measure are closely inter-related to each other. Measure is defined as way of defining amount, dimension, capacity or size of some attribute of a product in quantitative manner while Metric is unit used for measuring attribute. Software quality is one of the major concerns that need to be addressed and measured. Object oriented (OO) systems require effective metrics to assess quality of software. The paper is designed to identify attributes and measures that can help in determining and affecting quality attributes. The paper conducts empirical study by taking public dataset KC1 from NASA project database. It is validated by applying statistical techniques like correlation analysis and regression analysis. After analysis of data, it is found that metrics SLOC, RFC, WMC and CBO are significant and treated as quality indicators while metrics DIT and NOC are not significant. The results produced from them throws significant impact on improving software quality.
POLITICA DE CALIDAD: “Trabajar con objetividad y transparencia para seguir construyendo el Municipio deseado, mediante el alto desempeño de los procesos y buscando la excelencia en la prestación del servicio, contribuyendo así a elevar la calidad de vida de sus habitantes, por medio del mejoramiento continuo y el compromiso del talento humano;
ANALYSIS OF SOFTWARE QUALITY USING SOFTWARE METRICSijcsa
Software metrics have a direct link with measurement in software engineering. Correct measurement is the prior condition in any engineering fields, and software engineering is not an exception, as the size and complexity of software increases, manual inspection of software becomes a harder task. Most Software Engineers worry about the quality of software, how to measure and enhance its quality. The overall objective of this study was to asses and analysis’s software metrics used to measure the software product and process.
In this Study, the researcher used a collection of literatures from various electronic databases, available since 2008 to understand and know the software metrics. Finally, in this study, the researcher has been identified software quality is a means of measuring how software is designed and how well the software conforms to that design. Some of the variables that we are looking for software quality are Correctness, Product quality, Scalability, Completeness and Absence of bugs, However the quality standard that was used from one organization is different from others for this reason it is better to apply the software metrics to measure the quality of software and the current most common software metrics tools to reduce the subjectivity of faults during the assessment of software quality. The central contribution of this study is an overview about software metrics that can illustrate us the development in this area, and a critical analysis about the main metrics founded on the various literatures.
Modern gadgets and machines such as medical equipments, mobile phones, cars and even military hardware run on software. The operational efficiency and accuracy of these machines are critical to life and the well being of modern civilization. When the software powering these machines fail it exposes life to danger and can cause the failure of businesses. In this paper, software quality measure is presented with the emphasis on improving standard and controlling damages that may result from badly developed application. The research shows various software quality standards and quality metrics and how they can be applied. The application of the metrics in measuring software quality in the research produced results which shows that the code metrics performance is better than the design metrics performance and points to a new way of improving quality by refactoring application code instead of developing new designs. This is believed to ensure reusability and reduced failure rate when software is developed
The most important aim of software engineering is to improve software productivity and quality of software product and further reduce the cost of software and time using engineering and management techniques.Broadly speaking, software engineering initiative has been introduced during software crisis period to describe the collection of techniques that apply engineering and management skills to the construction and
support of software process and products. There is no universally agreed theory for software measurement and the software metrics are useful for obtaining the information on evaluation of process and product in software engineering. It helps to plan and carry out improvement in software organizations and to provide objective information about project performance, process capability and product quality. The process capability is extremely important for software industry because the quality of products is largely determined by the quality of the processes. The make use of of existing metrics and development of innovative software metrics will be important factors in future software engineering process and product development. In future, research work will be based on using software metrics in software development for the development of the time schedule, cost estimates and software quality and can be improved through software metrics. The permanent application of measurement based methodologies is used to the software process and its products to provide important and timely management information, together with the use of those techniques to improve that software process and its products. This research paper mainly concentrates on the overview of unique basics of software measurement and exclusive fundamentals of software metrics in software engineering.
Abstract The management of software cost, development effort and project planning are the key aspects of software development. Throughout the sixty-odd years of software development, the industry has gone at least four generations of programming languages and three major development paradigms. Still the total ability to move consistently from idea to product is yet to be achieved. In fact, recent studies document that the failure rate for software development has risen almost to 50 percent. There is no magic in managing software development successfully, but a number of issues related to software development make it unique. The basic problem of software development is risky. Some example of risk is error in estimation, schedule slips, project cancelled after numerous slips, high defect rate, system goes sour, business misunderstanding, false feature rich, staff turnover. XSoft Estimation addresses the risks by accurate measurement. A new methodology to estimate using software COSMIC-Full Function Point and named as EXtreme Software Estimation (XSoft Estimation). Based on the experience gained on the original XSoft project develpment, this paper describes what makes XSoft Estimation work from sizing to estimation. Keywords: -COSMIC function size unit, XSoft Estimation, XSoft Measurement, Cost Estimation.
IJRET : International Journal of Research in Engineering and Technology is an international peer reviewed, online journal published by eSAT Publishing House for the enhancement of research in various disciplines of Engineering and Technology. The aim and scope of the journal is to provide an academic medium and an important reference for the advancement and dissemination of research results that support high-level learning, teaching and research in the fields of Engineering and Technology. We bring together Scientists, Academician, Field Engineers, Scholars and Students of related fields of Engineering and Technology
Metrics serve as important indicator of the efficiency and effectiveness of software process. Analysis of defined metrics helps identify area of improvement and devise subsequent actions.......Read more
STATISTICAL ANALYSIS OF METRICS FOR SOFTWARE QUALITY IMPROVEMENT ijseajournal
Software product quality can be defined as the features and characteristics of the product that meet the user needs. The quality of any software can be achieved by following a well defined software process. These software process results into various metrics like Project metrics, Product metrics and Process metrics. Software quality depends on the process which is carried out to design and develop software. Even though the process can be carried out with utmost care, still it can introduce some error and defects. Process metrics are very useful from management point of view. Process metrics can be used for improving the software development and maintenance process for defect removal and also for reducing the response
time.
This paper describes the importance of capturing the Process metrics during the quality audit process and also attempts to categorize them based on the nature of error captured. To reduce such errors and defects found, steps for corrective actions are recommended.
In the ever-evolving landscape of technology, enterprise software development is undergoing a significant transformation. Traditional coding methods are being challenged by innovative no-code solutions, which promise to streamline and democratize the software development process.
This shift is particularly impactful for enterprises, which require robust, scalable, and efficient software to manage their operations. In this article, we will explore the various facets of enterprise software development with no-code solutions, examining their benefits, challenges, and the future potential they hold.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Top 7 Unique WhatsApp API Benefits | Saudi ArabiaYara Milbes
Discover the transformative power of the WhatsApp API in our latest SlideShare presentation, "Top 7 Unique WhatsApp API Benefits." In today's fast-paced digital era, effective communication is crucial for both personal and professional success. Whether you're a small business looking to enhance customer interactions or an individual seeking seamless communication with loved ones, the WhatsApp API offers robust capabilities that can significantly elevate your experience.
In this presentation, we delve into the top 7 distinctive benefits of the WhatsApp API, provided by the leading WhatsApp API service provider in Saudi Arabia. Learn how to streamline customer support, automate notifications, leverage rich media messaging, run scalable marketing campaigns, integrate secure payments, synchronize with CRM systems, and ensure enhanced security and privacy.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Software Metrics for Identifying Software Size in Software Development Projects
1. COMPUSOFT, An international journal of advanced computer technology, 4 (8), August-2015 (Volume-IV, Issue-VIII)
1960
Software Metrics for Identifying Software
Size in Software Development Projects
V.S.P Vidanapathirana1
and K.H.M.R Peiris2
1,2
Faculty of Information Technology, Sri Lanka Institute of Information Technology, Colombo, Sri Lanka
Abstract: Measurements are fundamental any engineering discipline. They indicate the amount, extent,
dimension or capacity of an attribute or a product, in a quantitative manner. The analyzed results of the
measured data can be given as the basic idea of metrics. It is a quantitative representation of the measurements
of the degree to which a system, component, or process possesses a given attribute. When it comes to software,
the metrics are a wide scope of measurements of computer programming. The size oriented metrics takes a main
role in it since they can be used as the key for better estimations, to improve trust and confidence, and to have a
better control over the software products. Software professionals traditionally have been measuring the size of
software applications by using several methods. In this paper the researchers discuss about the software size
metrics for identifying software size and it is mainly focused on the software development projects in today’s
Information Technology (IT) industry.
Keywords: Engineering discipline, Software, Software Metrics, Software Size, Programming, Software
Development Projects
I. INTRODUCTION
Frequently the world has been experiencing a
software crisis as a result of the inability in
producing high quality and reliable software due to
the lack of software management capabilities.
These software management capabilities include
the accuracy or the improvements of the software
metrics and the utilization of such metrics.
Software metrics are tools for anyone involved in
software engineering to understand varying aspects
of the code base, and the project progress [1]. Using
software metrics is different from testing errors,
since they can provide a wider variety of
information about the aspects like quality, schedule,
cost, complexity or the size of a software system.
When looking at the current state of software
metrics, there are many metrics invented for all the
categories in software metrics field such as product
metrics, process metrics, resource metrics and
project metrics. Each of these metric types have
unique purposes, set of specifications and
methodologies attached to them, therefore
identifying the best and the most accurate resulting
software metric has become sort of confusing.
Faced with this situation, the authors has chosen to
indicate a great diversity of product software
metrics, more specifically the software size metrics
used in software development projects in the
current IT industry.
Product metrics describes the characteristics of the
software product at any stage of its development,
from requirements to installed system [2], and
software size is one of the most important and
common characteristic that comes under product
metrics type. It uses the either source or the object
code of the particular program in order to measure
the software size. It helps to determine and predict
the quality of the current software product and
identify the adjustments or techniques that can be
used to level up or improve the quality of the
product as well. Since the results gained from the
product metrics are not personal biased, it gives the
opportunity of comparing.
The rest of this paper is organized as follows.
Section 2 has provided the existing related work.
Section 3 describes the objectives of conducting
this research and the methodology of this paper is
discussed in Section 4. Result and discussion is
Given in Section 5 and finally Conclusion is
presented in Section 6.
II. LITERATURE REVIEW
T.Manoharan et.al. have discussed that the
source code metrics measure the size of a software
ISSN:2320-0790
2. COMPUSOFT, An international journal of advanced computer technology, 4 (8), August-2015 (Volume-IV, Issue-VIII)
1961
program by counting the number of lines in the text
of the program's source code and is also used to
predict the amount of effort that will be required to
develop a program, as well as to estimate
programming productivity or effort once the
software is produced. [3]
D.Beyer et. al. have discussed that two
widespread-used size metrics for object oriented
source code are the number of methods as indicator
for functional size and the number of attributes as
indicator for size of encapsulated data. [4]
A. Abran et al. have mentioned measuring the
functional size of software was originally proposed
in 1979 by Albrecht in a communication describing
the result of an effort started in the mid-seventies in
one IBM business unit. The overall goal of the
work described in Albrecht’s original paper was to
measure the productivity of software development,
as viewed from an economic perspective. The
functional size of software was proposed as a
generic measure of the “output” of the development
process which allows a comparison of projects in
which software was developed using different
programming languages. [5]
E. E. Mills et.al. Have described a number of
metrics attempt to quantify software “size.” The
metric that is most widely used, LOC, suffers from
the obvious deficiency that its value cannot be
measured until after the coding process had been
completed. Function points and system Bang have
the advantage of being measurable earlier in the
development process—at least as early as the
design phase, and possibly earlier. Some of stead’s
metrics are also used to measure software size. [6]
V. Tiwary et.al. Have discussed the complexity
has a direct impact on overall quality, so
complexity of the modules should be less. Size of
the software reflects the complexity, development
effort and reliability of the software. LOC (Lines of
Code) or KLOC (Lines of Code in thousands) is an
intuitive initial approach to measuring software size.
LOC or KLOC is depends upon the factors such as
blank lines, comments, executable statements etc.
The reliability will decrease if modules have a
combination of high complexity and large size.
High complexity and small size will sometimes also
decrease the reliability because; the smaller size
results in a short code which is difficult to alter. For
the object oriented code additional metrics are
required to evaluate the quality of the software.
Weighted method per class (WMC) is one of them
such metrics which is used to predict how much
time and effort is required to develop and maintain
the class. [2]
N. E. Fenton et.al have mention that the Size
Metrics are represented by a number of metrics
attempt to quantify software “size”. For a software
application is easy to measure the number of lines
of codes for quantify software size. We discuss here
a little bit about some aspects of software size.
Each product of software development is a physical
entity. In this acceptation, it can be described in
terms of its size. The most commonly used measure
for the length of a code source of a program is the
number of lines of code. [7]
M.H. Sherif et.al have discussed that code size
and code complexity are two essential metrics to
predict the development effort, fault-proneness
analysis, and other risk management activities
during coding phase. However, it is found that size
and complexity metrics only become inadequate to
describe the attributes of modern software. [8]
Software quality metrics are a subset of software
metrics that focus on the quality aspects of the
product, process, and project. In general, software
quality metrics are more closely associated with
process and product metrics than with project
metrics. Nonetheless, the project parameters such
as the number of developers and their skill levels,
the schedule, the size, and the organization
structure certainly affect the quality of the product.
[9]
A. J. Albrecht et. al. proposed a function-
oriented metric which has subsequently gained
wide currency: the function point. Function points
are computed using the experimental relationship
between the direct measures of the software’s
information domain and estimation of its
complexity on a weighted scale. The information
domain values are based on the following criteria:
number of user inputs, number of user outputs,
number of user inquiries, number of files, and
number of external interfaces. Once they are
computed, function points are used in a manner
similar to lines-of-code to normalize measures for
software productivity, quality, and other attributes
such as, errors per function point, defects per
function point etc. [10]
Software size estimation is a critical issue in the
project management area. Good early estimations
are essential for a reliable prediction of project
effort and cost as well as for an efficient planning
and scheduling. Software size represents one of the
most interesting internal attributes of a software
product. Internal attributes can be measured in
terms of the product itself, separate from its
behaviour while external product attributes can be
measured only with respect to how the product
relates to its environment. The first ones, such as
software size, are easier to measure than external
3. COMPUSOFT, An international journal of advanced computer technology, 4 (8), August-2015 (Volume-IV, Issue-VIII)
1962
ones. Software measurement presents the problem
that it can only be carried out when the product is
finished and then it is not very useful. For that
reason, many metrics provide functional measures
of the software size such as metrics of functions
points, functions blocks, object points or Bang
metrics Those variables obtained from software
specifications should have a correspondence with
the final product size expressed, for example, in
lines of code. The recent class point approach based
on design documentation is an alternative for object
oriented products. [11]
III. OBJECTIVES
In order to identify and understand the specific
objectives based on the topic "Software Metrics for
identifying Software Size in Software Development
projects", the authors have several objectives as
follows.
- Identify the current usage of software size
metrics for software development projects.
- Identify the current methodologies of
software size metrics used in software
development projects in IT industry.
- Analyse the advantages and disadvantages
of software size metrics in software
development projects.
- Identify the knowledge about software size
metrics among the industrial individuals.
- Find the best and the most accurate software
size metrics in software development
projects.
IV. METHODOLOGY
Since questionnaire is one of the best methods that
can be used to gather large amounts of information
from a large crowd in a short period of time and in
a relatively cost effective, practical manner the
team decided to conduct an online questionnaire
which includes questions to lead the way of finding
the best software size metrics which are available in
current IT industry. The questionnaire was consist
of simple, clear and objective set of questions
where the responsive parties can give their personal
ideas about the software size metrics that they use
and identify as the best metrics that estimate the
software size in software development projects.
In order to become participants in the survey, the
team contacted 50 selected individuals, who has
experience in the roles of Project Managers,
Quality Assurance Engineers, Software Engineers,
Developers, Business Analysts, Interns, and as well
as undergraduates in the IT related field. The online
questionnaire that includes 11 questions were
emailed to them to gather the response.
Figure 1: Flow chart of the initial study
Out of the 50 participants, 40 of them responded.
Therefore the survey makes a success rate of 80%.
After gathering the responses, the team analyzed
and discussed those information to come up with a
meaningful result, as well as a clear conclusion.
V. RESULTS AND DISCUSSIONS
The audience of the survey was purely IT
industry oriented, because it was conducted among
participants who are currently working on and
worked with software development projects. Most
of them were having experiences in the industry
between 2 to 5 years, which makes a percentage of
42.5%. A percentage of 40% can be identified as
4. COMPUSOFT, An international journal of advanced computer technology, 4 (8), August-2015 (Volume-IV, Issue-VIII)
1963
the next highest, the participants who has industry
experiences less than one year. The rest of the 7%
have experiences in the industry for more than 5
years.
Figure 2: Years of experience
92.5% of industry participants responded that they
think that software metrics are important in
software development projects. The idea of “maybe”
was given by 7.5% of them. No one responded that
the software metrics are not important in software
development projects.
Figure 3: Importance of software metrics
Among the participants, 57.5 % of them responded
that the idea about software metrics that measures
the software size is important in software projects.
30% of them mentioned that it depends, and 12.5%
of them responded that it does not important in
software development projects.
Figure 4: Importance of software size metrics
The usage of the software size metrics among the
participants was 90%. 10% of them do not use
software metrics that measures the software size in
their software development projects.
Figure 5: Usage of software size metrics
Among the participants who use the software
metrics to measure the software size, the highest
percentage of 72.5% goes with the software metric,
Function point analysis. The next highest goes with
a percentage of 67.5%, towards the Lines of code
metric. A few of them, a percentage of 15% use
Number of classes in a design diagram, and 12.5%
of them use Object points. Feature points metric is
used by 10% of the participants. None of them use
number of boxes in a data flow diagram as a
software metric, in the development of software
products.
Figure 6: Types of software size metrics in use
As the most accurate software size metric, the
participants have selected Function point analysis,
which can be represented in a percentage of 62.5%.
Lines of code were selected by 30% which makes it
the next highest. Feature points made a percentage
of 17.5% and for number of classes in a design
diagram it was a percentage of 5%. A very few
participants has selected number of boxes in a data
flow diagram as the most accurate software size
metric, and that percentage was 2.5%.
Figure 7: The most accurate software size
metrics
From the participants, 55% think the number of
boxes in a data flow diagram as the least accurate
software size metric. 30% of them think it is lines
of code, and for 17.5% it is object points. Feature
points were selected as the next less accurate
software size metric by making a percentage of
15%. A percentage of 12.5% think that the less
accurate software metric is the number of classes in
a design diagram. A very few of the participants
think it is function point analysis, which can be
represented in a percentage of 5%.
Figure 8: Least accurate software size metrics
Among the participants, 85% of them think that
there is a difference in software products there are
with software size metrics and 15% think there is
5. COMPUSOFT, An international journal of advanced computer technology, 4 (8), August-2015 (Volume-IV, Issue-VIII)
1964
no any difference in software products when they
are without software size metrics.
Figure 9: Difference between software products
with metrics and without metrics
According to the responses of the industry
participants for the questionnaire, software metrics
play a huge role in software development projects
and among them; there are metrics that can be used
to measure the software size, to ensure the quality
of the software products. At the end of the project
they can be used to deploy a project with less bugs
and errors so it makes them easy to maintain as
well.
Based on the answers provided by the industry
participants, the software size metrics the scope of
the project can be calculated, and they are
important to have a baseline measure about the
code’s efficiency. It makes easier when it comes to
comparison between projects, and also is useful to
estimate project resource estimations. When it
comes to calculating the costs and financial
purposes, the size of the software is important since
it allows for better time and cost estimates for
repetitive projects.
Software metrics which measure the software size
make it easier to manage the risks in software
developing projects, since they provide a good idea
about cost estimations and financial states. In
complex projects, they ensures the efficiency of the
code. Therefore the quality of the software product
is well assured.
Some of the industrial workers consider that the
software size is not an important fact in software
development projects. They consider it as a time
consuming process which needs additional effort
and time other than the developing time. And as the
team realized, it requires more knowledge since
some of the industrial workers are not much
familiar with the metrics that can be used to
measure the software size. On the other hand, since
the software size is just a small factor in a software
product, they think it does not make any difference
even if they use software metrics to estimate the
software size.
Some of the well experienced industrial workers do
not believe that the software size metrics are
important for the process of implementing quality
software products. It is mostly because of the
confidence they have by being in the IT industry for
a long time. Based on their experience on
development projects they believe software size
estimation is not a considerable and important
factor in achieving the success in those projects.
VI. CONCLUSION
The results gained from the conducted online
survey revealed the usage of software metrics that
are currently in industrial use, which organizations
use to measure the software size in software
development projects. It also showed the most
accurate and least accurate software size metrics
among them.
Clearly Function point analysis and Lines of code
plays a massive role in software size metrics but
when considering the accuracy, function point
analysis method can be considered as the most
accurate metric that can be used to measure the
software size. Function point analysis does not
consider about the programming language is being
used or the platform in the software development
project runs, therefore the assessing the
productivity of them can be done in an easy and
accurate manner. Lines of code metric is mostly
suitable for the projects with very tightly
constrained environments, but not for complex
projects that involves many resources and efforts.
According to the results gathered, number of boxes
in the data flow diagram can be considered as the
least accurate software metric when measuring the
software size in software development projects. The
main drawback in that method is that it takes a long
time to create a data flow diagram, and difficult to
construct as well. On the other hand, since the
physical considerations are left out in the data flow
diagram, the programmers may get confused
towards the system. Therefore a software product
cannot be assured its quality by a metric with such
issues.
ACKNOWLEDGMENT
Our sincere gratitude goes all the people who
contributed to make this research a success. Finally
we would like to thank all the anonymous
reviewers for their comments and suggestions.
REFERENCES
[1] R. Kumar and R. Verma, “Software Quality Metrics:
Concept and Significance”, 2nd ed. Jhunjhunu, 2014.
[2] V. Tiwari and R. Pandey, “Open Source Software and
Reliability Metrics”, vol. 1, Dec. 2012.
[3] T.Manoharan, “Metrics Tool for Software Development
Life Cycle”, vol. 2, pp. 1-16, Jan. 2014.
6. COMPUSOFT, An international journal of advanced computer technology, 4 (8), August-2015 (Volume-IV, Issue-VIII)
1965
[4] D. Beyer, C. Lewerentz, and F. Simon, “Impact of
Inheritance on Metrics for Size, Coupling, and Cohesion in
Object-Oriented Systems”, vol. 2006, pp.1-17, Mar.2001.
[5] A. Abran, S. Oligny, C. Symons, D. St-Pierre and J.M.
Desharnais, “Functional Size Measurement Methods –
COSMIC- FFP: Sesign and Field Trials”, 2000.
[6] E. E. Mills, “Software Metrics, SEI Curriculum Module
SEI-CM-12-1.1”, resources.sei.cmu.edu, 1988. [Online].
Available:
http://resources.sei.cmu.edu/asset_files/CurriculumModule/
1988_007_001_15608.pdf.[Accessed: March 20, 2015].
[7] N. E. Fenton and S. L. Pfleeger, “Software Metrics: A
Rigorous & Practical Approach”, 2nd Edition, London:
International Thomson Computer Press, 1997, pp. 638.
[8] M. H. Sherif, "Handbook of Enterprise Integration",CRC
Press, 2009. [Online]. Available: http://goo.gl/JUh9Gz.
[Accessed: March 20, 2015].
[9] S. H. Khan, "Metrics and Models in Software Quality
Engineering", Addison-Wesley Professional, 2003.
[Online]. Available: http://goo.gl/TxXUSx. [Accessed:
March 20, 2015].
[10] A. J. Albrecht,"Measuring Application Development
Productivity",vol. SE-9 ,pp. 648-652, Nov. 1983.
[11] M. N. M. García and F. J. G. Peñalvo, "Improving
Estimations in Software Projects with Data Mining
Techniques", vol. 18, pp. 265-278, April 1992.