scholarly journals Visually Exploring Software Maintenance Activities

Author(s):  
Stanislav Levin ◽  
Amiram Yehudai
2010 ◽  
Vol 13 (2) ◽  
Author(s):  
Cláudia Werner ◽  
Chessman Corrêa ◽  
Rodrigo Santos ◽  
Marcelo Schots ◽  
Leonardo Murta ◽  
...  

Maintenance represents an important activity in software industry as it is the one that takes the biggest effort among Software Engineering activities apart from its high cost. In this sense, software configuration management helps to overcome some difficulties related to software maintenance such as the lack of product knowledge and negligence in maintenance activities. This paper presents a configuration management deployment process based on standardization of practices and tools, taking into account the software development organizational culture. The results of its application in an industrial case are discussed.


Author(s):  
Evan W. Duggan

The correlation between the quality of information systems (IS) development practices, the products they shape, and systems maintainability has been well established. Several organizations have expended large amounts of money on ineffective software that have attracted high maintenance activities, which consume a disproportionate share of IS development resources. The IS quandary is how to reverse this trend, and free up resources for more productive organizational endeavors. This chapter presents a review of a variety of IS quality-oriented approaches (based on research findings and dispassionate practitioner accounts) and an indication of their advantages and weaknesses, and the development environments and contexts for which they are most suited. These techniques are available to software developers to be used individually or in synergistic combinations to confront the prevalent problem of poor software quality and reduce its unfavorable impact on software maintenance.


Author(s):  
Lerina Aversano ◽  
Fiammetta Marulli ◽  
Maria Tortorella

The relationship existing between a business process and the supporting software system is a critical concern for organizations, as it directly affects their performance. The knowledge regarding this relationship plays an important role in the software evolution process, as it helps to identify the software components involved by a software change request. The research described in this chapter concerns the use of information retrieval techniques in the software maintenance activities. In particular, the chapter addresses the problem of recovering traceability links between the entities of the business process model and components of the supporting software system. Therefore, an information retrieval approach is proposed based on two processing phases including syntactic and semantic analysis. The usefulness of the approach is discussed through a case study.


Author(s):  
S. CHEN ◽  
W. T. TSAI ◽  
X. P. CHEN

This paper presents a software maintenance environment for assembly programs, SAMEA. It presents an object-oriented database support for displaying, understanding, modifying and configuring assembly programs for software maintenance. Understanding of assembly programs is based on the theory of explicit representation of various structural and functionality elements of code and multiple relationships among them. Modification of program is based on an object-oriented incremental editor and a set of rules to check the correctness of instruction format. The characteristics of SAMEA are: integration of multiple tools, on-line information, ease of adoption of new tools, and finally, support of software maintenance activities such as program understanding, ripple effect analysis, and program redocumentation. The ripple effect of a contemplated change is the parts of the code that need to be reexamined for possible modification. Assembly code elements and relations among code elements are represented as objects in SAMEA which is built on top of an object-oriented database GemStone. SAMEA consists of 26K lines of C code and 4K lines of GemStone code. We have successfully populated 18K lines of BAL code in SAMEA.


2014 ◽  
Vol 3 (3) ◽  
pp. 26
Author(s):  
Michael O'Brien

Effective communication of knowledge is paramount in every software organisation. Essentially, the role of documentation in a software engineering context is to communicate information and knowledge of the system it describes. Unfortunately, the current perception of documentation is that it is outdated, irrelevant and incomplete. Several studies to date have revealed that documentation is unfortunately often far from ideal. Problems tend to be diverse, ranging from incompleteness, to lack of clarity, to inaccuracy, obsolescence, difficulty of access, and lack of availability in local languages. This paper begins with a discussion of information seeking as an appropriate perspective for studying software maintenance activities. To this end, it examines the importance and centrality of documentation in this process. It finally concludes with a discussion on how software documentation practices can be improved to ensure software engineers communicate more effectively via the wide variety of documents that their projects require.


Sign in / Sign up

Export Citation Format

Share Document