Deployment of Software Metrics Measurements Techniques within Software Development Process

Published on November 2016 | Categories: Documents | Downloads: 80 | Comments: 0 | Views: 553
of 5
Download PDF   Embed   Report

Journal of Computing, eISSN 2151-9617, http://www.JournalofComputing.org

Comments

Content

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 11, NOVEMBER 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING WWW.JOURNALOFCOMPUTING.ORG

19

Deployment of Software Metrics Measurements Techniques within Software Development Process
Zahra Gholami, Nasser Modiri, and Sam Jabbehdari
Abstract— Software quality is an important criterion in producing softwares which increases productivity and results in powerful and invincible softwares. We can say that quality assurance is the main principle and plan in software production. Solution which is suggested for quality assurance and improvement of software is measurement. The result of measurement process is to acquire a set of metrics. Software metrics are continuous usage of techniques based on measurement in software development process and products in order to provide timely and significant management information, with using these techniques in improvement of process and its products. Therefore we need derivation of respective metrics in order to achieve our goal. Considering the importance of software metrics, utilization of international standard software life cycle process model (ISO/IEC 12207) and measurement process of Plan/Do/Check/Act in order to monitor software production cycle is presented in this paper. Index Terms — Software Metrics, Measurement, Software Development Process, ISO/IEC 12207

——————————  ——————————

1 INTRODUCTION
owadays development and quality improvement of software development process and increasing performance and throughput of people involved is an important matter for every corporation which deals with information technology and software industry. Requests for efficient software have increased since computers became more powerful and because of vital role of technology in promotion of business, software problem are effective on most companies and governments. These days many companies realized that most of software problems are technical and software engineering is different from other engineering fields because software products are intellectual but the other engineering products are physical. There is measurement in centre of every engineering which is a method based on known standards and agreements. Software metrics include wild range of measurements for computer softwares; also measurement could be used throughout the software project in order to help estimation, quality control, throughput evaluation, project control. The main aim of this essay is to review and propose parameters as software metrics which are applied in standard ISO/IEC 12207 in order to remove weakness points of this standard and also helping us in quality measure of mentioned standard and to provide the possibility of
————————————————

N

quality effective factors development process [2, 3].

investigation

in

software

2 SOFTWARE DEVELOPMENT PROCESS
Software development process is a structure and also a framework for introducing organization in order to design and generate a new software product consist of key solutions, issues and problems of a software product from early stages of marketing to mass production and finally release that[6].

Fig1.PLC and SLC of Softwarte Development Process

 Zahra Gholami is with Department of Software Engineering, Islamic Azad University, North Tehran Branch - Tehran, Iran.  Nasser Modiri is with Department of Software Engineering, Islamic Azad University, Zanjan Branch - Zanjan, Iran.  Sam Jabbedari is with Department of Software Engineering, Islamic Azad University, North Tehran Branch - Tehran, Iran.

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 11, NOVEMBER 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING WWW.JOURNALOFCOMPUTING.ORG

20

3 SOFTWARE METRICS
Software metrics are parameters for measuring softwares which measurement won’t have any meaning without them. It doesn’t mean that software metrics can solve every problem but they can conduct managers to improve processes, throughput and quality of softwares [9].Metrics are continuous and executable activities on whole project and are collected in long period of time; they show the rate of progress in periodic performances. Metrics have ring-incremental mechanism because the most valuable information is obtained when we have a sequence of data. Then the data obtained from metrics as feedback should have been given to the manager in order to find existing mistakes, provide solution for them and prevent further rising of faults. This makes defects detection be done before presentation to the customer [4, 5].

Product Metrics
These are metrics that analyze final product for example the time needed for presentation of product, rate of execution, maintenance costs, and product user friendliness.

Resource Metrics
Metrics which describe feature of available resources. For example number of programmers, analysts, designers and required systems.

Risk Metrics
Metrics that are used for identification, giving priority to the probable risks of projects and reducing the probability of them.

3.1 Metrics Types
Other metrics can be defined with considering different viewpoints such as:

Management Metrics
Metrics that are used for progress and development of project management [7, 13].

Subjective Metrics
These metrics can’t be evaluated and are express with a set of qualitative attributes. The main objective of these metrics is to identify and evaluate of metrics which are less ponderable quantitatively.

Methodology Metrics
They are metrics which we can consider the most suitable construction model for a product with using of them (Table 1).
   

Objective Metrics
Metrics that can be evaluated and are measurable such as number of human resources, number of resources, size of memory, number of documentation and number of modules.

Global Metrics
These metrics are used by software managers and are comprehensive metrics which we can evaluate project status with using of them, such as the budget, project time schedule, cost of implementation.
Fig 2. Sample Form for Perposed of Software Metrics [2, 8, 9]

4 METHODOLOGY
Phase Metrics
These kinds of metrics are specific to each phase and they measure the rate of progress or regression in specific phase. For example number of people in each phase, specific documentation of phase, improvement percent, and delay percent. Software product process model that can be different according to the type of the product. Four decades passed from the first primary activities for organizing software product process. At the first times because of the lack of regular procedure (Methodology) for following software product process producers were confronted with several problems that results low quality of produced softwares, overhead costs and failure to fulfill scheduled plans. Need to compile methodology, construction model and following of them in software product process became more tangible and in this four decades many of methodologies have risen which with utilization of them software with more quality developed.

Calculated Metrics
These metrics can be calculated. For example cost, error, complexity, rate of execution, execution time.

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 11, NOVEMBER 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING WWW.JOURNALOFCOMPUTING.ORG

21

TABLE 1 METHODOLOGY METRICS [15, 16]

5.1 Proposed of Software Metric Cycle According to Plan/Do/Check/Act

5 PLAN/DO/CHECK/ACT CYCLE
Plan/Do/Check/Act Cycle was established by Japanese in 1951 based on doming cycle. This cycle consist of 4 following stages: Plan: determining of objectives and required process for presentation of results according to customer’s requests and or organization policies. Do: implementation Check: monitoring and measurement of process and product according to policies, objectives and requirements or request related to product and reporting of results. Act: doing activities in order to improve process performance. This cycle is based on scientific methods and feedback plays a basic role in that so the main principle of this scientific method is iteration. When a hypothesis is being denied the next execution of cycle can expand knowledge and these iteration makes become closer to the aim [12].A Process is partitioned into PDCA Activities show in Figure3.  

Fig 4. Software Metrics Cycle according to Plan/Do/Check/Act [1]

6 PROPOSED PATTERN
Considering the point that plan/Do/Check/Act is a simple and effective process for measurement of software metrics following of that is a high assurance for success in control and monitoring of software production cycle metrics and with considering the weaknesses of standard ISO/IEC 12207 we can apply our desired metrics during this cycle to the different phases of the mentioned standard so that defects would be eliminated to some extent (Figure 5).

6.1 Features of pattern
 
Fig 3. Partitioning a Process into PCDA Activities [11]

In this pattern we apply different metrics considering the importance via Plan/Do/check/Act cycle and features which we can express for this pattern consist of followings:

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 11, NOVEMBER 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING WWW.JOURNALOFCOMPUTING.ORG

22

Further Reliability
With using resource, risk and management metrics which are the most important metrics at the start of project and utilization of Plan/Do/Check/Act cycle for each metrics we can provide further monitoring and control on production processes and so further reliability for establishing a project will be realized.

REFERENCES
[1] [2] Z. Gholami, et al. “Monitoring Software Product Process Metrics”, IJCSIS Journal, vol.9, No.10, October 2011. Rafa E.Al-Qutaish, “Measuring the Software Product Quality during the Software Development Life-Cycle: An International Organization for Standardization Standards Perspective, Journal of Computer Science, 2009. Habra Naji, et al. “A Framework for the Design and Verification of Software Measurement Methods”, Elsevier, the Journal of Systems and Software 81 633–648, 2008. Raffo, David M., “Software Project Management using PROMPT: A Hybrid Metrics, Modeling and Utility Framework “, Elsevier, Information and Software Technology 47 1009–1017, 2005. Osmudson John S., et al. “Quality Management Metrics for Software Development”, Elsevier Science, Information & Management 40 799–812, 2003. Day, G. “The Product Life cycle: Analysis and applications issues,” Journal of Marketing, Vol 45, autumn 1981. N. Fenton, and S. Pfleeger, “Software Metrics - A Rigorous and Practical Approach,” Brooks Cole Publishing Company, ISBN: 0534954291, 1998. Somerville, “Software Engineering,” Pearson Education, ISBN: o321210263, 1999. R. Pressman, “Software Engineering: A Practitioner’s Approach Edition,” McGraw-Hill Science/Engineering/Math, 5th ISBN: 0072853182, 2001. P. Goodman “Software Metrics: Best Practices for Successful IT Management,” Rothstein Associates Inc., 2004. Raghu Singh, “An Introduction to International Standard ISO/IEC 12207 Software Life Cycle,” FAA, Washington DC, April 26, 1999. G. Gorenflo, J. W. Moran, “The ABCs of PDCA for Public Health Foundation‘s website, 2010. A Guide to the Project Management Body of Knowledge (PMBOK), an American National Standard, ANSI/PMI 99-0012008, 2008. ISO/IEC 12207:2008, International Standard, System and software engineering-Software life cycle processes. Kruchten,  Philippe,  The  Rational  Unified   Process–  An  Introduction,  3rd  edition,  Addison‐Wesley,  2004   ISBN:0‐321‐19770‐4  Agile Alliance , (2006) Available from agilealliance.com 

[3]

Cost Reduction
With using metrics which are applied to the standard ISO/IEC 12207 we can prevent next duplication because of observation at the start of project.

[4]

[5]

Risk Reduction
We can also minimize the risk with using risk and management metrics.
   

[6] [7]

[8] [9]

[10] [11]

[12] [13]

[14] [15]   Fig 5. Proposed Pattern based of ISO/IEC12207 standard [14]

[16]  

7 CONCLUSION
Result of this essay is proposal of a pattern that is based on standard ISO/IEC 12207 and uses proposed metrics for monitoring of processes. One of the methods for controlling and monitoring of software production process is software metrics that can be applied to every phase so that transition to the next phase would be more assured. It should be noted that this reliability isn’t completely definite but it can prevent increasing cost because of negligence to some parameters so metrics are necessary and essential.

Zahra Gholami received her B.Sc Degree in Computer Engineering from Islamic Azad University (Lahijan branch), Lahijan, Iran in the year 2008. Currently she is pursuing M.Sc in Computer Engineering from Islamic Azad University (Tehran North Branch), Tehran, Iran under the guidance of Dr Modiri. She is presently working on Metrics of Software Development Process. Dr.Nasser Modiri received his M.S. Degree from the University Of Southampton, U.K, and Ph. D. degree from the University of Sussex, U.K. in 1986 and 1989, respectively. In 1988 he joined The Networking Centre of Hemel Hempstead, and in 1989 he worked as a Principal Engineer at System Telephone Company (STC) Telecommunications Systems, U.K. Currently, Dr. Modiri is the president of Ayandehgan Rayaneh Co. developing web-based software and designer and implementer of information technologies services for Intranet networks while teaching actively MSc courses in network designing, software engineering and undertaking many MSc projects. He is currently developing applications for Virtual Universities, Virtual Parliaments, Virtual Organizations, ERP, GPS+GSM, GPRS, RFID, ISO/IEC 27000, ISO/IEC 15408 technologies.

JOURNAL OF COMPUTING, VOLUME 3, ISSUE 11, NOVEMBER 2011, ISSN 2151-9617 HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING WWW.JOURNALOFCOMPUTING.ORG

23

Dr Sam Jabbehdari currently working as an assistant professor at the department of Computer Engineering in IAU (Islamic Azad University), North Tehran Branch, in Tehran, since 1993. He received his both B.Sc. and M.S. degrees in Electrical Engineering Telecommunication from K.N.T (Khajeh Nasir Toosi) University of Technology, and IAU, South Tehran branch in Tehran, Iran, in 1988, through 1991 respectively. He was honored Ph.D. Degree in Computer Engineering from IAU, Science and Research Branch, Tehran, Iran in 2005. He was Head of Postgraduate Computer Engineering Department IAUNorth Tehran Branch during 2008-2010. He also has written “Advanced Topics in Computer Networks” book in Persian Language (Tehran, Classic, 2009). His current research interests are Scheduling, QoS, MANETs, Wireless Sensor Networks and Grid Computing Systems.

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close