Improving software maintenance attitudes

Pengembangan perangkat lunak adalah tugas kompleks dan membutuhkan adaptasi untuk mengakomodasi kebutuhan pengguna. Untuk membuat konsep dan perubahan perangkat lunak, dalam pemeliharaan, sekarang telah dikembangkan lebih mudah dalam pengembangan perangkat lunak, pola model-view-controller, yang merupakan arsitektur yang dapat membantu memfasilitasi dalam pengembangan dan pemeliharaan perangkat luna. Hal ini, karena dalam arsitektur model tiga-lapis, yaitu: tampilan dan pengontrolan dalam pembangunan dilakukan secara independen, sehingga dapat memberikan dahan dalam pengembangan dan pemeliharaan. Selain itu, arsitektur ini juga dapat melihat hal-hal yang sederhana dan menarik bagi pengguna. Software sistem on-line test adalah perangkat lunak yang memerlukan interaksi dengan pengguna, dan pemeliharaan perangkat adaptif. Karena sistem ujian on-line memerlukan pengembangan perangkat lunak untuk mengakomodasi kebutuhan ini berkembang dengan cepat. Makalah ini untuk menganalisis Model-View-Controller dan mencoba pembangunan, untuk menerapkannya dalam pengembangan perangkat lunak sistem pengujian on-line.

Computer software is an important part of computer, whose running security has a direct impact on the computer. In addition, the maintenance and management technology of computer software plays a key role in software running. Therefore, in order to ensure the smooth running of computer software, in this paper, it studies the maintenance and management technology of computer software, and puts forward strategies to improve the maintenance and management technology of computer software, so that to ensure the software runs more reliably.

It is a belief that it is harder to maintain a code than writing a new code. The software maintenance comes into picture after the code has been delivered. The purpose of maintenance is to remove bugs, improve performance and design and adding new features to the existing system. The process of Refactoring helps in improving software’s internal structure without altering its external behaviour. It is also a part of Maintenance activity. Another belief is that Refactoring improves software design by making it more extensible and flexible. This paper presents a study of the case studies already performed in order to show the compliance of Refactoring activity with the Maintenance Phase. Keywords: Software Maintenance, Refactoring, Quantification.

As we know all software products require maintenance and support. After observing time requirements for maintenance and all needed innovations and changes I realize that cost for those activities is somewhere around half of all bugged for software product. The more years is software used and alive the more time and costs are required. Linear dependency between realized changes and costs is changing into exponential dependency as the years go. Bad and unwanted structural changes at the very beginning of software design could overcharge software maintenance. It is nothing uncommon that maintenance of poorly or wrong designed software products (for example LMS) can achieve point when cost of new development is lover than actual cost of maintenance. In this contribution is presented a proposal of effective software maintenance adverted for web 2.0 based LMS system. Our proposal exploits what should be the proper way of software design, what are the common mistakes, what are our personal experiences and finally how to gain the low cost software maintenance.

This article proposes that software maintainers would benefit from specialized education and training with regard to software maintenance. A clear distinction is drawn between the tasks involved in software development and those involved in software maintenance. It is shown that neither the average computer science undergraduate degree program, nor experience in software development fully prepare a programmer for the particular challenges faced in software maintenance. The traditional and evolving coverage of software maintenance in U.S. graduate and undergraduate computer science and software engineering degree programs is discussed. A set of proposals is given for introducing undergraduate computer science students to the field of software maintenance. An alternate approach is recommended for introducing experienced development programmers to software maintenance.

A Taxonomical Approach To ManagingQuality In Software Maintenance

In the past 70 years, science research methods have expanded from test tubes and beakers to include simulations in software. Scientific software is produced in a larger environment of collaboration that includes not only software developers, but also scientists who both use and extend the software for their research endeavors. The objective of this research is to understand the factors that promote and inhibit ecosystem formation and sustainment specific to scientific research software development. We have identified a set of relevant problems inhibiting sustainability in the scientific software context, including development, evolution and maintenance, as well as funding and leadership. We have collected data and used existing business, software, and innovation analysis techniques to examine the artifacts from several scientific research projects. We interviewed significant actors in select scientific ecosystems. We describe the differences between scientific software ecosystems and commercial software ecosystems, our initial results from interviews and data analysis, and we provide a set of recommendations and approaches towards handling software sustainability. Data suggests an ecosystem strategy can contribute to the survivability and sustainability of research software; however, such a strategy, which may distract from sustainability, requires thought and effort be given to establishing and nurturing the ecosystem, which in turn distract from the research mission. At this stage these initial results point us to future potentially fruitful investigations.

Effective software maintenance is essential to achieving global software competitiveness. Organizations' increasing dependency on software and the shortage of software skills combine to require an increase in the span of responsibility within the software maintenance function. The span of responsibility determines the cost of software ownership since it is the amount of software depended on by the enterprise divided by the number of people who maintain the software. Managers of software maintenance can improve the span of responsibility by •establishing and using organizational resources in five manners to sustain operational support for existing information systems, •applying resources to strengthen four views of software maintenance, from individual to national, •creating and applying action to eliminate the 26 main shortfalls in doing software maintenance, and •reducing the seven main risks to information system quality. This paper provides a call for action to improve software maintenance in order to strengthen enterprise and national global competitiveness. © 1997 John Wiley & Sons, Ltd.

Software design issues can severely impede software development and maintenance. Thus, it is important for the success of software projects that developers are aware of bad smells in code artifacts and improve their skills to reduce these issues via refactoring. However, software refactoring is a complex activity and involves multiple tasks and aspects. Therefore, imparting competences for identifying bad smells and refactoring code efficiently is challenging for software engineering education and training. The approaches proposed for teaching software refactoring in recent years mostly concentrate on small and artificial tasks and fall short in terms of higher level competences, such as analysis and evaluation. In this paper, we investigate the possibilities and challenges of designing serious games for software refactoring on real-world code artifacts. In particular, we propose a game design, where students can compete either against a predefined benchmark (technical debt) or against each other. In addition, we describe a lightweight architecture as the technical foundation for the game design that integrates pre-existing analysis tools such as test frameworks and software-quality analyzers. Finally, we provide an exemplary game scenario to illustrate the application of serious games in a learning setting.

Software plays a crucial role in modern societies. Not only do people rely on it for their daily operations or business, but also for their lives as well. For this reason, correct and consistent behavior of software systems is a fundamental and critical part of end-user expectations. Additionally, businesses require cost-effective production, maintenance, and operation of their systems. Thus, the demand for high-quality and maintainable software is increasing, setting it as a differentiator for the success or failure of a software product, as well as a dominating factor for the commercial success of companies. The main questions that arise concern how quality is measured and communicated to stakeholders. What, where, and when we assess and assure quality are also open issues. Many views have been expressed about software quality attributes including maintainability, security, evolvability, portability, robustness, reliability, usability, and efficiency. Some of these have been formulated in standards such as ISO/IEC 25010 (SQuaRE) and CMMI. However, the debate about quality and maintainability between software producers, vendors, and users continues, while organizations need the ability to evaluate the software systems they use or develop from multiple viewpoints. So, is ‘‘software quality in the eye of the beholder’’? This special section on Software Quality and Maintainability presents original work and relates experiences on issues pertaining to software quality and maintainability. Moreover, the theme of this special section opens discussion of how to investigate quality issues in the maintenance of software systems. Out of 15 full-paper submissions for this issue, four papers were selected. The accepted papers address a range of topics related to software quality, including code refactoring, API

An accurate maintenance effort model is essential for a successful software maintenance process. Maintenance effort is usually measured in person-hours used to perform a maintenance task. However, ...

When an organization considers the evolution of a software-intensive system, the selection of the software maintenance process to be adopted must include consideration of the particular technical c...

Synchronised visualisation of software process and product artefacts: Concept, design and prototype implementation

The paper presents a summary of the PhD thesis 'Perspectives on Improving Software Maintenance' by F. Niessink (2000). The research described in this thesis investigates process improvement of software maintenance from two perspectives: measurement-based improvement and maturity-based improvement.

A quantitative model for the support of software management