ACM Home Page
Please provide us with feedback. Feedback
Component-based measurement: few useful guidelines
Full text PdfPdf (257 KB)
Source ACM SIGSOFT Software Engineering Notes archive
Volume 28 ,  Issue 6  (November 2003) table of contents
SECTION: Papers table of contents
Pages: 4 - 4  
Year of Publication: 2003
ISSN:0163-5948
Authors
N. S. Gill  Maharshi Dayanand University, Rohtak, Haryana (India)
P. S. Grover  University of Delhi, Delhi, India
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 19,   Downloads (12 Months): 155,   Citation Count: 6
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/966221.966237
What is a DOI?

ABSTRACT

Software industries are striving for new techniques and approaches that could improve software developer productivity, reduce time-to-market, deliver excellent performance and produce systems that are flexible, scalable, secure, and robust. Only software components can meet these demands and following this; component-based software engineering (CBSE) has emerged, which has generated tremendous interest in software development community. The paradigm shift to software components appears inevitable, necessitating drastic changes to current software development and business practices. The scope of this paper is to suggest few necessary guidelines for deriving component-based metrics. The paper discusses issues related to component-based development (CBD) and suggests a general definition of software component based on several existing definitions. Further, the paper outlines the necessity of component measurement and also discusses the limitations of traditional software metrics for component-based development (CBD) systems. Finally, this paper also suggest few necessary guidelines for CBD measurement and proposes some relevant metrics applicable to CBD systems, which after proper quantification and validation may help guiding risk and quality management of component-based systems.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Allen Paul (2001): The State of the Practice. Component Development Strategies Journal, March 2001, Vol. XI, No. 3. pp. 1--16.
 
2
Azuma, Motoei (1996): Software Products Evaluation System: Quality Models, Metrics and Processes--International Standards and Japanese Practice. Information and Software Technology Journal. 38 (1996), pp. 145--154.
 
3
Bhatti, S. (1998): Management of Component-Based Software Engineering. In Proceedings of International Workshop on Component-Based Software Engineering, 1998.
 
4
 
5
Brown Alan (1998): From Component Infrastructure to Component-Based Development. In http://www.sei.cmu.edu/cbs/icse98/ papers/p21.html.
 
6
 
7
8
 
9
Etzkorn, L. H., Hughes Jr., W. E., Davis, C. G. (2001): Automated Reusability Quality Analysis of OO Legacy Software. Information and Software Technology Journal, 43, 2001, pp. 295--308.
 
10
 
11
Han, Jun (1998): Characterisation of Components. In proceedings of International Workshop on Component-Based Software Engineering, 1998.
 
12
Hevner, A. R. (1997): Phase Containment Metrics for Software Quality Improvement. Information and Software Technology Journal, 39, 1997, pp. 867--877.
13
 
14
Kamiya, T., Kusumoto S., Inoue K., Mohri Y. (1999): Empirical Evaluation of Reuse Sensitiveness of Complexity Metrics. Information and Software Technology Journal, 41, 1999, pp. 297--305.
 
15
 
16
 
17
 
18
 
19
20
 
21
 
22
Wesner, J. W. et al (1995): Wining with Quality. Addison-Wesley, Reading, MA, 1995.

Collaborative Colleagues:
N. S. Gill: colleagues
P. S. Grover: colleagues