[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
research-article

Design issues in client-server software maintenance

Published: 31 August 2008 Publication History

Abstract

Software requires maintenance because there are often some errors remaining in the system that must be removed as they are discovered. Even without errors, software frequently undergoes change. The main reason is that software must be enhanced to include more features. Client-server software maintenance is not as simple as centralized software maintenance because client-server software systems are more complex than software for centralized systems.
Cost associated with software maintenance is top most cost in software development, so there is a need to develop software which has maintainability i.e. the ease with which a system can be maintained. Therefore, the design and development of client-server software systems should be done keeping in mind the maintainability of the resultant software systems. There are various design issues related with the maintainability of the software. If we take care of these issues at the time of design, then the resultant system will have better maintainability and thus maintenance efforts of such system will be reduced.

References

[1]
Banker R.D., Datar S.M., Kemerer C.F. and Zweig D. (1993): "software complexity and maintenance costs", Communications of the ACM, 36(11), 81--94.
[2]
IEEE (1993): "IEEE Standard for Software Maintenance", IEEE Std 1219-1993, Institute of Electrical and Electronics Engineers, inc., New York, NY.
[3]
IEEE STD (1990): "IEEE Standard Glossary of Software Engineering Terminology", 1990.
[4]
Halstead M.H. (1977): "Elements of Software Science (Operating and Programming Systems Series)", Elsevier Science Inc., New York, NY, USA.
[5]
Jalote Pankaj (1997): "An Integrated Approach to Software Engineering", Narosa Publishing House, NEW DELHI, INDIA.
[6]
Kafura D. and Reddy G.R. (1987): "The use of software complexity metrics in software maintenance", IEEE Transaction on Software Engineering, SE-13 (3), 335--43.
[7]
Lientz B.P. and Swanson E.B. (1980): "Software Maintenance Management", Reading, MA: Addison-Wesley.
[8]
Mathew Sajan (2003): "Software Engineering", S. Chand & Company Ltd., New Delhi, INDIA.
[9]
McCabe T.J. (1976): "A Complexity Measure", IEEE Transaction on Software Engineering, SE-2 (4), 308--20.
[10]
Mosley Daniel J. (2000): "Client/Server Software Testing on the Desktop and the Web", Prentice Hall PTR, Upper Saddle River, NJ.
[11]
Nosek J.T. and Palvia P. (1990): "Software Maintenance Management: Changes in the last decade", Software Maintenance: Research and Practice, 2(3), 157--74.
[12]
Pigoski T.M. (2001): "Software Maintenance", In: Guide to the Software Engineering Body of Knowledge, Los Alamitos, CA: IEEE Computer Society Press, Trial Version 1.00, available at http://www.swebok.org/stoneman/version_0.95/C6-Software_Maintenance_Version_0_95.pdf
[13]
Pressman Roger S. (1997): "Software Engineering: A Practitioner Approach", IV edition, McGraw-Hill International Edition.
[14]
Schneberger Scott L. (1997): "Client/Server Software Maintenance", McGraw-Hill.
[15]
Sommerville Ian (2002): "Software Engineering", VI edition, Pearson Education, Asia.
[16]
Stevens W.P., Myers G.J. and Constantine L. (1974): "Structured Design", IBM Systems Journal, 13(2).
[17]
Takang A.A., and Grubb, P.A. (1996): "Software Maintenance Concepts and Practice", Thompson Computer Press, London, UK.
[18]
Yin B.H. and Winchester (1978): "The establishment and use of measures to evaluate the quality of designs", Software Engineering Notes, 3, 45--52.
[19]
Zage W.M. and Zage D.M. (1993): "Evaluating design metrics on large-scale software", IEEE Software, 75--81.

Cited By

View all
  • (2019)Analysis of the intermediate layer work in the three-tier architecture “client-server” of automation engineering problemsIOP Conference Series: Materials Science and Engineering10.1088/1757-899X/537/3/032011537(032011)Online publication date: 17-Jun-2019

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes  Volume 33, Issue 5
September 2008
68 pages
ISSN:0163-5948
DOI:10.1145/1402521
Issue’s Table of Contents

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 31 August 2008
Published in SIGSOFT Volume 33, Issue 5

Check for updates

Author Tags

  1. client-server systems
  2. maintainability
  3. software design
  4. software engineering

Qualifiers

  • Research-article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)2
  • Downloads (Last 6 weeks)1
Reflects downloads up to 22 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2019)Analysis of the intermediate layer work in the three-tier architecture “client-server” of automation engineering problemsIOP Conference Series: Materials Science and Engineering10.1088/1757-899X/537/3/032011537(032011)Online publication date: 17-Jun-2019

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media