ACM Home Page
Please provide us with feedback. Feedback
Few useful considerations for maintaining software components and component-based systems
Full text PdfPdf (273 KB)
Source ACM SIGSOFT Software Engineering Notes archive
Volume 32 ,  Issue 5  (September 2007) table of contents
SECTION: Article abstracts with full text online table of contents
Pages: 1 - 5  
Year of Publication: 2007
ISSN:0163-5948
Authors
P. S. Grover  Guru Gobind Singh Indraprastha University, Delhi. India
Rajesh Kumar  Thapar University, Patiala. India
Arun Sharma  Amity University, Noida. India
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 101,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

Component-Based Systems (CBS) maintenance may require several activities different than normal applications, such as upgrading the functionality of black-box components (for which code may not be available), replacement of older version components with the new ones for better and improved functionality, tracing the problem of compatibility between the new components with system, and so on. The focus of this paper is on investigating several issues and concerns about maintainability of component-based systems. It also explores the acceptance of maintainability characteristics and sub-characteristics as defined in ISO9126 quality model for CBS. The paper proposes two new sub-characteristics, namely trackability and portability, to be included under the maintenance activity.


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
Paul Allen (2002): CBD Survey: The State of the Practice, a white paper by Cutter Consortium. Web: http://www.cutter.com/research/2002/edge020305.html
 
2
 
3
International Standard, ISO/IEC 9126 -1 (2001), Institute of Electrical and Electronics Engineering, Part 1, 2, 3: Quality Model 2001, http://www.iso.ch.
 
4
Rawashdeh A, Matalkah B (2006): A New Software Quality Model for Evaluating COTS Components, Journal of Computer Science 2(4): 373--381, 2006.
 
5
IEEE Standard for Software Maintenance, IEEE Std 1219--1998. The Institute of Electrical and Electronics Engineers, Inc. 1998.
 
6
ISO 9126 (2001): Information Technology - Product Quality - Part1: Quality Model, International Standard ISO/IEC 9126, International Standard Organization.
 
7
Mark R Vigder, J. Dean (2000): Maintaining a COTS-Based Systems" Proceedings of the NATO Information Systems Technology Panel Symposium on Commercial Off-the-Shelf Products in Defense Applications, Brussels, Belgium, April 3--5, 2000.
 
8
 
9
Judith A. Clapp, Audrey E. Taub (1998): A Management Guide to Software Maintenance in COTS-Based Systems", at http://www.mitre.org/work/tech_papers_98/mgt_guide_sftwrmaint.pdf
 
10
Sharma Arun, Kumar Rajesh, Grover P S (2007): Complexity Measures for Software Components, WSEAS Transactions on Computers, Issue 7, Volume 6, and pp: 1005--1012
 
11
 
12
 
13
A Alvero, E Santana de Almeida, S Romero de Meira (2005): Quality Attributes for a Component Quality Model in the proceeding of 10th International Workshop on Component-Oriented Programming, Glasgow, Scotland, - at ECOOP 2005, Glasgow, Scotland (July 25--29, 2005)
 
14
 
15
 
16


Collaborative Colleagues:
P. S. Grover: colleagues
Rajesh Kumar: colleagues
Arun Sharma: colleagues