Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
Monitoring Software Product Process Metrics

Monitoring Software Product Process Metrics

Ratings: (0)|Views: 160 |Likes:
Published by ijcsis
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. One of the most important challenges in Software Engineering is lack of software metrics for monitoring and measurement of software life cycle phases which causes low quality and usefulness of software products. 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.
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. One of the most important challenges in Software Engineering is lack of software metrics for monitoring and measurement of software life cycle phases which causes low quality and usefulness of software products. 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.

More info:

Published by: ijcsis on Nov 25, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

11/23/2012

pdf

text

original

 
(IJCSIS) International Journal of Computer Science and Information Security,Vol. 9, No. 10, October 2011
Monitoring Software Product Process Metrics
 
Zahra Gholami Nasser Modiri Sam Jabbedari
Department of Software Engineering Department of Software Engineering Department of Software EngineeringNorth Tehran Branch - Islamic Azad Zanjan Branch - Islamic Azad North Tehran Branch - Islamic AzadTehran, Iran Zanjan, Iran Tehran, IranGholamizahra64@yahoo.com NasserModiri@yahoo.com S_jabbehdari@iau-tnb.ac.ir
Abstract
 — 
Software quality is an important criterion inproducing softwares which increases productivity and results inpowerful and invincible softwares. We can say that qualityassurance is the main principle and plan in software production.One of the most important challenges in Software Engineering islack of software metrics for monitoring and measurement of software life cycle phases which causes low quality and usefulnessof software products. Considering the importance of softwaremetrics, utilization of international standard software life cycleprocess model (ISO/IEC 12207) and measurement process of Plan/Do/Check/Act in order to monitor software production cycleis presented in this paper.
 Keywords-Software Metrics, Measurement, Software Product Process,
 
 ISO/IEC 12207 
I.
 
I
NTRODUCTION
 Nowadays development and quality improvement of software production process and increasing performance andthroughput of people involved is an important matter for everycorporation which deals with information technology andsoftware industry. Requests for efficient software haveincreased since computers became more powerful and becauseof 
 
vital role of technology in promotion of business, softwareproblem are effective on most companies and governments.These days many companies realized that most of softwareproblems are technical and software engineering is differentfrom other engineering fields because software products areintellectual but the other engineering products are physical.There is measurement in centre of every engineering which is amethod based on known standards and agreements. Softwaremetrics
 
include wild range of measurements for computersoftwares, also measurement could be used throughout thesoftware project in order to help estimation, quality control,throughput evaluation, project control. The main aim of thisessay is to review and propose parameters as software
 
metricswhich 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 thepossibility of quality effective factors investigation in softwareproduct process [9].II.
 
S
OFTWARE
P
RODUCT
P
ROCESS
 Software product process is a structure and alsoa framework for introducing organization in order to designand 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].
Figure1. Software Product Process
III.
 
S
OFTWARE
M
ETRICS
 Software metrics are parameters for measuring softwares
which measurement won‟t have any meaning without them. Itdoesn‟t mean that software metrics can solve every problem
but they can conduct managers to improve processes,throughput and quality of softwares [4]. Metrics are continuousand executable activities on whole project and are collected inlong period of time; they show the rate of progress in periodicperformances. Metrics have ring-incremental mechanismbecause the most valuable information is obtained when wehave a sequence of data. Then the data obtained from metricsas feedback should have been given to the manager in order tofind existing mistakes, provide solution for them and preventfurther rising of faults. This makes defects detection be donebefore presentation to the customer.
 A.
 
 Metrics Types
Other metrics can be defined with considering differentviewpoints such as:
47http://sites.google.com/site/ijcsis/ISSN 1947-5500
 
(IJCSIS) International Journal of Computer Science and Information Security,Vol. 9, No. 10, October 2011
1)
 
Subjective Metrics
These metrics can‟t be evaluated and are express with a
 set of qualitative attributes. The main objective of thesemetrics is to identify and evaluate of metrics which are lessponderable quantitatively.
2)
 
Objective Metrics
Metrics that can be evaluated and are measurable such asnumber of human resources, number of resources, size of memory, number of documentation and number of modules.
3)
 
Global Metrics
These metrics are used by software managers and arecomprehensive metrics which we can evaluate project statuswith using of them, such as the budget, project timeschedule, cost of implementation.
4)
 
Phase Metrics
These kinds of metrics are specific to each phase and theymeasure the rate of progress or regression in specific phase.For example number of people in each phase, specificdocumentation of phase, improvement percent, and delaypercent.
5)
 
Calculated Metrics
These metrics can be calculated. For example cost, error,complexity, rate of execution, execution time.
6)
 
Product Metrics
These are metrics that analyze final product for examplethe time needed for presentation of product, rate of execution, maintenance costs, and product user friendliness.
7)
 
 Resource Metrics
Metrics which describe feature of available resources. Forexample number
 
of 
 
programmers, analysts, designers andrequired systems.
8)
 
 Risk Metrics
Metrics that are used for identification, giving priority tothe probable risks of projects and reducing the probability of them.
9)
 
 Management Metrics
Metrics that are used for progress and development of project management [1, 2, 3, 8].IV.
 
P
LAN
 /D
O
 /C
HECK
 /A
CT
 Plan/Do/Check/Act Cycle was established by Japanesein 1951 based on doming cycle. This cycle consist of fourfollowing stages:
 
Plan: determining of objectives and required process forpresentat
ion of results according to customer‟s requests and or 
organization policies.Do: implementationCheck: monitoring and measurement of process andproduct according to policies, objectives and requirements orrequest related to product and reporting of results.Act: doing activities in order to improve processperformance.
 
This cycle is based on scientific methods and feedback plays a basic role in that so the main principle of this scientificmethod is iteration. When a hypothesis is being denied the nextexecution of cycle can expand knowledge and these iterationmakes become closer to the aim. A Process is partitioned intoPDCA Activities show in Figure2 [5].
Figure 2. Partitioning a Process into PCDA Activities [7]
48http://sites.google.com/site/ijcsis/ISSN 1947-5500
 
(IJCSIS) International Journal of Computer Science and Information Security,Vol. 9, No. 10, October 2011
 A.
 
Proposed of Software Metrics Cycle according toPlan/Do/Check/Act 
Figure3. Software metrics cycle according to plan/Do/Check/Act
V.
 
P
ROPOSED
P
ATTERN
Considering the point that plan/Do/Check/Act is a simpleand effective process for measurement of software metricsfollowing of that is a high assurance for success in control andmonitoring of software production cycle metrics and withconsidering the weaknesses of standard ISO/IEC 12207 we canapply our desired metrics during this cycle to the differentphases of the mentioned standard so that defects would beeliminated to some extent (Figure 4).
 A.
 
Features of Pattern
In this pattern we apply different metrics consideringthe importance via plan/Do/check/Act cycle and featureswhich we can express for this pattern consist of followings:
1)
 
Further Reliability
With using resource, risk and management metrics whichare the most important metrics at the start of project andutilization of Plan/Do/Check/Act cycle for each metrics we canprovide further monitoring and control on production processesand so further reliability for establishing a project will berealized.
2)
 
Cost Reduction
With using metrics which are applied to the standardISO/IEC 12207 we can prevent next duplication because of observation at the start of project.
3)
 
 Risk Reduction
We can also minimize the risk with using risk and management metrics.
 
VI.
 
C
ONCLUSION
Result of this essay is proposal of a pattern that is basedon standard ISO/IEC 12207 and uses proposed metrics formonitoring of processes. One of the methods for controllingand monitoring of software production process is softwaremetrics that can be applied to every phase so that transition tothe 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 sometrics are necessary and essential.R
EFERENCES
 
[1] N. Fenton, and S. Pfleeger, “Software Metrics
- A Rigorous and
Practical Approach,” Brooks Cole Publishing Company,
ISBN: 0534954291, 1998.
[2] Somerville, “Software Engineering,” Pearson Education,
ISBN: o321210263, 1999.[3]
R. Pressman, “Software Engineering: A Practitioner‟s Approach 5
th
 
Edition,” McGraw
-Hill Science/Engineering/Math, ISBN: 0072853182,2001.[4
] P. Goodman “Software Metrics: Best Practices for Successful ITManagement,” Rothstein Associates Inc., 2004.
 [5
] G. Gorenflo, J. W. Moran, “The ABCs of PDCA for Public HealthFoundation„s website,
2010.
[6]Day, G. “The Product Life cycle: Analysis and applications issues,”
 Journal of Marketing,
Vol 45, autumn 1981.
[7] Raghu Singh, “An Introduction to International Standard ISO/IEC12207 Software Life Cycle,” FAA, Washington DC, April 26, 1999.
 [8] A Guide to the Project Management Body of Knowledge (PMBOK),an American National Standard, ANSI/PMI 99-001-2008, 2008.[9] ISO/IEC 12207:2008, International Standard, System and softwareengineering-Software life cycle processes.
49http://sites.google.com/site/ijcsis/ISSN 1947-5500

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->