Maintenance of a computer-based system accounts for a large proportion of the total system cost. However, no well-established techniques exist for assessing the maintainability of such a system. This paper presents a case study in assessing the maintainability of a large, software intensive system. The techniques we used are described, and their strengths and weaknesses discussed.

Process modelling is a key activity of software process management and it is the starting point for enacting, evaluating and improving software processes. The current competitive marketplace calls for the continuous improvement of processes and therefore, it is fundamental to have software process models with a high maintainability. In this paper we introduce a set of metrics for software proce...

Dependency injection (DI) is generally known to improve maintainability by keeping application classes separate from the library. Particularly within Java environment, there are many applications using principles of DI with aim maintainability. There exists some work that provides an inference on impact maintainability, but no conclusive evidence provided. The fact publicly available tools for ...

A major strength of open-source software is that the source code is open to scrutiny by anyone who chooses to examine it. Accordingly, it is reasonable to assume that the quality of open-source software will be higher than that of closed-source software. After all, closed-source software is examined by only a limited number of individuals, all of whom are paid to do so. It seems equally reasona...

Software maintainability has been an important external quality attribute that concerns both styles of software development, the proprietary model as well as open source. As lots of open source software are predominantly built using the OO paradigm, there exists a need for empirical validation with respect to certain quality aspects especially maintainability. There are a few studies in the pas...

Software organizations face constant pressure due to stakeholder requirements and the increasing complexity of software systems. This complexity, combined with defects in code quality failures, can pose risks To ensure is understood before maintenance, developers must spend over 60% their time modifying improving quality, which costly. study examines impact refactoring activities on maintainabi...