Academia.eduAcademia.edu

Outline

Title
Abstract
Figures
Introduction
Capturing Knowledge: Post-Mortem Analysis
Post-Mortem Analysis for Maintenance
Discussion of Experimentation
Some Results
Related Work
Conclusion
References
All Topics
Computer Science
Software Engineering

Software maintenance seen as a knowledge management issue

Profile image of Nicolas AnquetilNicolas Anquetil

2007, Information and Software Technology

https://doi.org/10.1016/J.INFSOF.2006.07.007
visibility

…

description

15 pages

link

1 file

Abstract

Creating and maintaining software systems is a knowledge intensive task. One needs to have a good understanding of the application domain, the problem to solve and all its requirements, the software process used, technical details of the programming language(s), the system's architecture and how the diVerent parts Wt together, how the system interacts with its environment, etc. All this knowledge is diYcult and costly to gather. It is also diYcult to store and usually lives only in the mind of the software engineers who worked on a particular project.

Figures (11)
Fig. 2. Ontology overview.
Fig. 2. Ontology overview.
and SOFTWARE COMPONENTS. Briand [7] considers three kinds of documentation: (1) PRODUCT RELATED, describing the sys- tem itself; (11) PROCESS RELATED, used to conduct software projects; and (iii) SUPPORT RELATED, helping to operate the system.
and SOFTWARE COMPONENTS. Briand [7] considers three kinds of documentation: (1) PRODUCT RELATED, describing the sys- tem itself; (11) PROCESS RELATED, used to conduct software projects; and (iii) SUPPORT RELATED, helping to operate the system.
4.3. Modification process subontology
4.3. Modification process subontology
Fig. 4. Computer Science skills subontology.
Fig. 4. Computer Science skills subontology.
Fig. 5. Modification Process subontology.
Fig. 5. Modification Process subontology.
Fig. 6. Organizational Structure subontology (left) and Application Domain subontology (right). In the literature, PMA is mainly viewed as a process improvement tool. For example, Stalhane et al. start their paper [38] with the affirmation: “An obvious way to improve a software development process is to learn from past mistakes”. Other authors [5,15,23,30,43] assume the same point of view, either explicitly or implicitly. Finally, different types of person (HUMAN RESOURCES) may participate in these activities (from [7,18,24,29]): sort- WARE ENGINEERS, MANAGERS, and CLIENT’S HUMAN RESOURCES (CLIENT and USER).
Fig. 6. Organizational Structure subontology (left) and Application Domain subontology (right). In the literature, PMA is mainly viewed as a process improvement tool. For example, Stalhane et al. start their paper [38] with the affirmation: “An obvious way to improve a software development process is to learn from past mistakes”. Other authors [5,15,23,30,43] assume the same point of view, either explicitly or implicitly. Finally, different types of person (HUMAN RESOURCES) may participate in these activities (from [7,18,24,29]): sort- WARE ENGINEERS, MANAGERS, and CLIENT’S HUMAN RESOURCES (CLIENT and USER).
Fig. 7. Overview of the ISO 14764 Maintenance process [20] with the inter- mediary and final PMAs and their respective scope.
Fig. 7. Overview of the ISO 14764 Maintenance process [20] with the inter- mediary and final PMAs and their respective scope.
Duration of the Interview PMAs
Duration of the Interview PMAs
Concepts from the ontology instantiated during the four PMAs
Concepts from the ontology instantiated during the four PMAs
Duration of the KJ sessions (the duration is that of the whole “session” which included two actual meetings) for both projects
Duration of the KJ sessions (the duration is that of the whole “session” which included two actual meetings) for both projects

Related papers

Practical Software Maintenance
Carolyn Seaman

Journal of Software Maintenance: Research and Practice, 2000

Tom Pigoski's Practical Software Maintenance serves as documentation of the author's years of experience as a software maintenance practitioner. I recently had the opportunity to use portions of this book in a special topics course on late life cycle issues in the Information Systems Department at the University of Maryland Baltimore County. Pigoski's book is not meant as a textbook; its intended audience is software maintenance practitioners in industry. However, as Pigoski notes, no other book exists currently that is geared towards teaching maintenance. So I chose this one to support my course and that is the perspective from which I review it here. My overall experience with the book is that, while it offers unique and valuable insights, it often couches them in ways that are not well comprehended by students with little practical experience, and it lacks some features that would be useful in a classroom setting. First, some facts and figures. The full title of the book is Practical Software Maintenance: Best Practices for Managing Your Software Investment. The main text of the book is nearly 350 pages, divided into 21 chapters, as summarized and detailed in Table I. The book also includes a table of contents (6 pages), a glossary containing 63 definitions (7 pages), an unannotated bibliography with 184 entries (12 pages), a subject index (14 pages), and one page each of preface, acknowledgments, and author biography. Tables, figures, and icons (such as 'Tom's Tips') are used liberally throughout the text. In addition, 28 sidebars called 'Practical Experiences,' ranging from a short paragraph to several pages in length, are sprinkled throughout most of the chapters and give detailed examples from the author's own experience in real software maintenance organizations. Each chapter ends with a few review questions. The introductory chapter is very brief. It presents the author's background, upon which the material in the book is based. Also, a strong statement is made about how maintenance should fit into the overall life cycle. The author proposes, correctly I believe, that maintenance activities must start before delivery, during development, '.. . coincident with the decision to develop a system.. . '. This turns out to be a recurring theme throughout the book. Finally, some terminology is presented. The 'Overview of Software Maintenance' chapter introduces a rather eclectic collection of concepts in software maintenance. Various definitions of maintenance are presented, as well as the basic life cycle models (waterfall, incremental, etc.). There is a discussion of why maintenance is and always will

View PDFchevron_right
Conceptual model for a software maintenance environment
Miriam Capretz

Proceedings of the Thirtieth Hawaii International Conference on System Sciences, 1997

A conceptual model for a software maintenance method named COMFORM (Configuration Management Formalization for Maintenance) is presented. COMFORM provides guidelines and procedures for carrying out the maintenance process, while establishing a systematic approach for the support of existing software systems. Incremental documentation, the process of building up the software documentation while the system is maintained, has a key role in this maintenance method. The documentation required by the method consists of keeping the maintenance history and information related to the software modules being maintained. Forms have been created in order to guide the maintainers during the maintenance process. Thus, their task will be of filling in forms for generating the required documentation instead of defining their own document structures. The system information obtained by filling in forms has been formalized according to a data model which provides a common basis for the representation of the method. This paper presents the conceptual model for COMFORM which was obtained using the data model termed Object Representation Model (ORM). ORM has been used because of its enhanced semantic capabilities and it provides the necessary generality and standardization for software representation.

View PDFchevron_right
The study of software maintenance organizations and processes
Carolyn Seaman

Empirical Software Engineering, 1997

View PDFchevron_right
Advances in Software Maintenance Management: Technologies and Solutions
Francisco Ruiz

Journal of Software Maintenance and Evolution: Research and Practice, 2003

Here is a new offering, now available both as a hardcover and as an e-book, in the much-neglected category of comprehensive texts on software maintenance. It is especially welcome for those of us struggling to provide our students with a text for learning the basics of software maintenance, in preparation for their inevitable first maintenance assignments as junior software engineers. This new book, Advances in Software Maintenance Management: Technologies and Solutions, edited by Macario Polo, Mario Piattini, and Francisco Ruiz at the University of Castilla-La Mancha in Spain, is not intended to be an academic textbook and so is lacking in some areas for that purpose. However, it has some important advantages over the few other choices in this area. It also is a useful volume for managers and others interested in getting an up-to-date understanding of some of the major issues in software maintenance.

View PDFchevron_right
The Impact of Software Quality on Maintenance Process
SHERZOD TURAEV

2010

The software is always required to be developed and maintained a quality to the rapid progresses in industry, technology, economy, and other fields. Software maintenance is considered as one of the main issues in software development life cycle that is required efforts and resources more than other phase. Studies estimated that the cost of software maintenance rapidly increased that reached the 90% of the total cost of software development life cycle. Therefore, it is considered as an economic impact in information system community. Several researches are intended to estimate and reduce the cost of this task.

View PDFchevron_right
Software Maintenance: Challenges and Issues and Models for Reducing the Maintenance Cost
Shray Khanna

International Journal of Advanced Research in Computer Science, 2017

Software maintenance is a very tedious and vital job in software development life cycle (SDLC). In today’s ever growing technological market outsourcing is done for best product delivery as well high efficiency. The outsourcing companies usually deliver a completed model to the company or user and further evolution or changes are done according to the requests made, these evolution or changes comes under Software Maintenance. Software maintenance is basically the modification done to assure a quality product after it is sent to the company or user who ordered it. This paper discovers the current models and strategies taken up by most of the leading companies for software maintenance and handling. It also explores the common challenges faced and its mitigation strategies. The preventive strategies are then discussed to help reduce for the issues faced by companies so as to overcome the overhead cost after delivering the product. The model/framework and strategies will explain the wor...

View PDFchevron_right
Towards the Quality Factor of Software Maintenance Process: A Review
Jamaiah Yahaya

Journal of Telecommunication, Electronic and Computer Engineering, 2017

Software maintenance (SM) is classified as the common process of modifying a system or software product once it has been delivered to user. Different type of process applied to different type of applications and in certain stages of the processes involve adding new components to the existing system. Software maintenance process is a series of actions taken to overcome changes during the maintenance phase. To ensure the sustainable quality of software product throughout the software life cycle, a good mechanism in software maintenance process should be implemented. Most organization nowadays depend on software products to run their business operations. Thus, it is crucial to ensure the software applications operating in the organization are sustainable while preserving its quality in a long run. The kick-off study starts with identifying the quality factors related to maintainability dimension that affected software maintenance process. A comprehensive literature study is conducted t...

View PDFchevron_right
Best Practices in Software Maintenance Projects
Dr. Sanjay Mohapatra

ABSTRACT Maintenance of software projects is an important phase in software engineering. However, there are many challenges associated during this maintenance phase, including technical and managerial. In order to reduce the cost of maintaining software project, many such projects are being outsourced to low cost development countries like India, Philippines, Russia or China. This paper talks about decision parameters for outsourcing maintenance projects. However, outsourced maintenance projects have their own issues and challenges such as poor domain knowledge, lack of understanding of application & technological knowledge and managerial issues such as lack of motivation, attrition. To find solution to these issues, the research conducted study in CMM level 5 organizations and based on case studies, developed an approach for addressing these issues and challenges successfully. The best practices so identified such as training the trainer, process oriented systematic approach, developing a test strategy and involving end users during execution can be adopted in other organizations as well. It was observed that the best practices improved productivity while reducing defects in the deliverables.

View PDFchevron_right
Software Maintenance Like Maintenance in Other Engineering Disciplines
Gustavo Villavicencio

Proceedings of the 22Nd ACM SIGSOFT International Symposium on Foundations of Software Engineering, 2014

Software maintenance exhibits many differences regarding how other engineering disciplines carry out maintenance on their artifacts. Such dissimilarity is caused due to the fact that it is easy to get a copy from the original artifact to be used in maintenance, and also because the flat dimension of the software text facilitates access to the components by simply using a text editor. Other engineering disciplines resort to different artifact 'versions' (obtained by dissassembling) where the introduction of modifications (previous comprehension) is easier. After which the artifact is reassembled. In software engineering this approach can be simulated by combining program transformation techniques, search-based software engineering technology and design attributes.

View PDFchevron_right
A disturbing result on the knowledge used during software maintenance
Nicolas Anquetil

Ninth Working Conference on Reverse Engineering, 2002. Proceedings., 2002

As part of a long term project aiming at empowering software maintainers with knowledge based tools we conducted an empirical study on the knowledge they use when doing maintenance. For example, it is commonly assumed that Application Domain knowledge is fundamental when doing maintenance. The goal of this study is to validate this assumption by monitoring software engineers and analyzing the knowledge they used in their maintenance activity. We studied six software engineers in two different organizations.

View PDFchevron_right

References (44)

  1. Victor Basili, Patricia Costa, Mikael Lindval, Manoel Mendona, Car- olyn Seaman, Tesoriero Roseanne, Marvin Zelkowitz. An experience management system for a software engineering research organization, in: Proceedings of the 26th Annual NASA Goddard Software Engi- neering Workshop. NASA Goddard Space Flight Center, 2001.
  2. Victor R. Basili, Gianluigi Caldiera, H. Dieter Rombach. Encyclope- dia of Software Engineering, volume 1, chapter The Experience Fac- tory, pages 469-76. John Wiley & Sons, 1994.
  3. Victor R. Basili, Mikael Lindvall, Patricia Costa. Implementing the experience factory concepts as a set of experience bases, in: Proceed- ings of 13th International Conference on Software Engineering and Knowledge Engineering, SEKE'01, pp. 102-109. Knowledge Systems Institute, 2001.
  4. T.J. BiggerstaV, B.G. Mitbander, D. Webster, Program understanding and the concept assignment problem, Commun. ACM 37 (5) (1994) 72-83.
  5. A. Birk, T. Dingsøyr, T. Stålhane, Postmortem: never leave a project without it, IEEE Softw. 19 (3) (2002) 43-45.
  6. G. Booch, J. Rumbaugh, I. Jacobson, The UniWed Modeling Lan- guage User Guide, Addison-Wesley, 1998.
  7. Lionel C. Briand, Victor R. Basili, Yong-Mi Kim, Donald R. Squier, A change analysis process to characterize software maintenance pro- jects, in: International Conference on Software Maintenance/ ICSM'94, pp. 1-12, 1994.
  8. B. Collier, T. DeMarco, P. Fearey, A deWned process for postmortem review, IEEE Softw. 13 (4) (1996) 65-72.
  9. T.H. Davenport, P. Laurence, Working Knowledge: How Organiza- tions Manage What They Know, Harvard Business School Press, Boston, 1998.
  10. K.M. de Oliveira, F. Zlot, A.R. Rocha, G.H. Travassos, C. Gallota, C. Menezes, Domain-oriented software development environment, J. Syst. Softw. 172 (2) (2004) 145-161.
  11. Kleiber D. de Sousa, Nicolas Anquetil, Káthia M. de Oliveira, Learning software maintenance organizations, in: Grigori Melnik, Harald Holz (Eds.), Advances in Learning Software Organizations - 6th International Workshop, LSO 2004, No. 3096 in Lecture Notes in Computer Science, pp. 67-77. Verlag, June 2004. ISBN 3-540- 22192-1.
  12. Dirk Deridder, Facilitating software maintenance and reuse activities with a concept-oriented approach, Technical report, Programming Technology Lab -Vrije Universiteit Brussel, May 2002.
  13. M.G. Batista Dias, N. Anquetil, K.M. de Oliveira, Organizing the knowledge used in software maintenance, J. Universal Comput. Sci. 9 (7) (2003) 641-658.
  14. T. Dingsøyr, R. Conradi, A survey of case studies of the use of knowl- edge management in software engineering, Int. J. Softw. Eng. Knowl. Eng. 12 (4) (2002) 391-414.
  15. Torgeir Dingsøyr, Nils Brede Moe, Nytrø Øystein, Augmenting experi- ence reports with lightweight postmortem reviews, Lecture Notes in Computer Science, 2188(2001) 167-181, PROFES 2001, Berlin, Germany.
  16. Michael Gruninger, Mark S. Fox, Methodology for the design and evaluation of ontologies, in: Workshop on Basic Ontological Issues in Knowledge Sharing/IJCAI'95, August 1995, Also available as a Tech- nical Report from the Department of Industrial Engineering, Univer- sity of Toronto.
  17. Nicolas Guarino (Ed.), Formal Ontology in Information Systems. Frontiers in ArtiWcial Intelligence and Applications. IOS Press, Amsterdam, 1998.
  18. Standard for software maintenance. Technical report, IEEE -Insti- tute of Electrical and Electronics Engineers, May 1998. ISBN: 0738103365.
  19. ISO/IEC 12207 Information technology -Software life cycle pro- cesses. Technical Report 12207, ISO/IEC, 1995.
  20. ISO/IEC 14764: Information technology -Software Maintenance. Technical Report 14764, Joint Technical Commitee International Standards Organization/International Electrotechnique Commis- sion, 1999.
  21. I. Jacobson, G. Booch, J. Rumbaugh, The UniWed Software Develop- ment Process, Addison-Wesley, 1999.
  22. M. Jørgensen, D.I.K. Sjøberg, Impact of experience on maintenance skills, J. Softw. Maint.: Res. Pract. 14 (2) (2002) 123-146.
  23. Norman L. Kerth, An approach to postmorta, postparta and post project review, On Lione: http://c2.com/doc/ppm.pdf. Last accessed on: 06/01/2003.
  24. B.A. Kitchenham, G.H. Travassos, A. von Mayrhauser, F. Niessink, N.F. Schneidewind, J. Singer, S. Takada, R. Vehvilainen, H. Yang, Towards an ontology of software maintenance, J. Softw. Maint.: Res. Pract. 11 (1999) 365-389.
  25. M.M. Lehman, Programs, life cycles and the laws of software evolu- tion, Proc. IEEE 68 (9) (1980) 1060-1076.
  26. Ikujiro Nonaka, Hirotaka Takeuchi, The Knowledge-Creating Com- pany. Oxford University Press, 1995. ISBN 0195092694.
  27. S.L. PXeeger, What software engineering can learn from soccer, IEEE Softw. 19 (6) (2002) 64-65.
  28. S.L. PXeeger, Software Engineering: Theory and Practice, second ed., Prentice Hall, 2001.
  29. T.M. Pigoski, Practical Software Maintenance: Best Practices for Software Investment, John Wiley & Sons, Inc., 1996.
  30. Linda Rising, Patterns in postmortems, in: Proceedings of the 23rd Annual International Computer Software and Applications Confer- ence, pp. 314-15. IEEE, IEEE Comp. Soc. Press, October 25-26, 1999.
  31. Oscar M. Rodriguez, Aurora Vizcaíno, Ana I. Martínez, Mario Piat- tini, Jesús Favela, How to manage knowledge in the software mainte- nance process, in: Grigori Melnik, Harald Holz (Eds), Advances in Learning Software Organizations -6th International Workshop, LSO 2004, Lecture Notes in Computer Science 3096, pp. 78-87.
  32. Springer Verlag, June 2004. ISBN: 3-540-22192-1.
  33. Oscar M. Rodriguez, Aurora Vizcaíno, Ana I. Martínez, Mario Piat- tini, Jesús Favela, Using a multi-agen architecture to manage knowl- edge in the software maintenance process, in: Mircea Gh. Negoita, Robert J. Howlett, Lakhmi C. Jain (Eds.), Proceedings of the 8th International Conference on Knowledge-Based Intelligent Informa- tion and Engineering Systems, KES 2004, Lecture Notes in Computer Science 3213, pp. 1181-1188, Springer Verlag, 2004. ISSN 0302-9743.
  34. F. Ruiz, A. Vizcaíno, M. Piattini, F. García, An ontology for the man- agement of software maintenance projects, Int. J. Softw. Eng. Knowl. Eng. -SEKE 14 (3) (2004) 323-349.
  35. I. Rus, M. Lindvall, Knowledge management in software engineering, IEEE Softw. 19 (3) (2002) 26-38.
  36. K. Schneider, J.-P. von Hunnius, V.R. Basili, Experience in imple- menting a learning software organization, IEEE Softw. 19 (3) (2002) 46-49.
  37. Carolyn B. Seaman, Unexpected beneWts of an experience repository for maintenance researchers, in: International Workshop on Empiri- cal Studies of Software Maintenance, WESS'00, http://hometown.aol. com/geshome/wess2000/metricsandmodels.htm, October 2000. accessed on: 02/01/2005.
  38. Mark S. Fox, Mihai Barbuceanu, Michael Gruninger, An organiza- tion ontology for enterprise modeling: preliminary concepts for link- ing structure and behaviour, Comput. Ind. 29 (1996) 123-134.
  39. Tor Stålhane, Torgeir Dingsøyr, Geir K. Hanssen, Nils Brede Moe. Post-mortem -an assessment of two approaches, in: Proceedings of the European Software Process Improvement 2001 (EuroSPI 2001), October 10-12, 2001.
  40. Amrit Tiwana. The Knowledge Management Toolkit. Prentice Hall PTR, 2000.
  41. T.R. Gruber, Toward principles for the design of ontologies used for knowledge sharing, Int. J. Hum. Comput. Stud. 43 (5-6) (1995) 907-928.
  42. J. Valett, S. Condon, L. Briand, Y.-M. Kim, V. Basili. Building an experience factory for maintenance, in: Proceedings 19th Annual Software Engineering Workshop. NASA Goddard Space Flight Cen- ter, November 1994.
  43. Anneliese von Mayrhauser, A. Marie Vans. Dynamic code cognition behaviors for large scale code, in: Proceedings of 3rd Workshop on Program Comprehension, WPC'94, pp. 74-81. IEEE, IEEE Comp. Soc. Press, November 1994.
  44. Yourdon (Ed.), Minipostmortems. COMPUTERWORLD, March 19, 2001.

Related papers

Software maintenance
Gerardo Canfora

2002

This article is an overview of software maintance, its relevance, the problems, and the available solutions. The focus is on the structure of the maintenance activity, including general models of the maintenance process, existing standards, and management practices and tools. The article also includes a discussion of related areas that support software maintenance, and particularly reverse engineering, reengineering, and legacy systems.

View PDFchevron_right
Knowledge for software maintenance
Nicolas Anquetil

Journal of Information Technology, 1997

Knowledge management is emerging as a promising area to support software engineering activities. The general idea is to use knowledge gained in previous projects to help future ones. We believe this approach is even more relevant when considering software maintenance where maintainers often have to modify a system that they did not develop, that has no documentation, and that nobody knows intimately. Contrasting with this lack of information on the system, maintainers need a lot of knowledge: about the application domain, the organization software maintenance procedures, the system itself, the language used, past development methods, etc. Although one can readily agree with this fact, there is no clear, exhaustive definition of what knowledge would be useful to perform software maintenance. In this paper we describe our research to identify these needs. This research is part of a long term project that aims at building a knowledge management system for software maintenance.

View PDFchevron_right
A framework for software maintenance and support phase
Zafar Nasir

2010

Software maintenance is one of the major concerns of software development and maintenance organizations. Over the years, the cost of maintenance has become the critical factor in decision making pertaining to long term viability of business and information systems. Software maintenance has strong bearing with overall software development life cycle. Depending upon the abilities of project team in the overall software development environment, a good software maintenance process would reduce the cost involved in terms of money, manpower, resources and time. In this paper we have discussed a simple but comprehensive framework for software maintenance and support phase. Based upon the guidelines of the proposed framework for software maintenance could be easily manageable and also become cost-effective.

View PDFchevron_right
A Review on Software Maintenance Issues and How to Reduce Maintenance Efforts
Mauricio José Ribeiro Rotta

Software Maintenance and evolution are identifying by their huge cost and slow speed of implementation. Survey showed that around 60% of the maintenance effort was on the total cost of software. But after delivering the software to the client, the maintenance work begins. This paper suggests some issues and problems faced by software maintenance process. There are some issues of software maintenance i.e.: database size, system age, maintenance budget, system size, staff size or restructuring for change. This paper presents several ways to reduce cost and efforts involved in software maintenance. Software maintenance costs can be reduced significantly if the software architecture is well defined, clearly documented, and creates an environment that promotes design consistency through the use of guidelines and testing quality. Keywords Software maintenance, issues and problems in software maintenance, cost and challenges in maintenance, maintenance cost reduction.

View PDFchevron_right
Software Maintenance: Concepts and Practice
Penny Grubb

2003

The purpose of this book is to explore the key issues underpinning software change and to discuss how these issues impact on the implementation of changes to software systems. The motivation for the book came from the need for texts dealing directly with challenges that software engineers face when modifying complex software systems. The extent of this challenge can be seen in the cost of modifying software. This cost can reach 70% of the total life-cycle cost [4, 36, 176]. Software maintenance is recognised as a key area in software engineering [9, 163]. Despite this, many mainstream software engineering courses are biased towards the development of new software systems at the expense of issues surrounding changes to these systems after they become operational [70].

View PDFchevron_right

Related topics

  • Information Systems
  • Software Engineering
  • Knowledge Management
  • Software Maintenance
  • Software Evolution
  • Knowledge Extraction
  • Software Process
  • Legacy software

    • Cited by

    Uncovering the failure of Agile framework implementation using SSM-based action research
    Kevin Suryaatmaja

    Palgrave Communications

    It is undeniable that the Agile software development (SD) framework has been commonly used in information technology projects. However, many of the early adopters failed to implement it properly. Some researchers had proposed a solution by using the adaptation framework as a support, but they cannot clearly explain its development. Furthermore, the correlation between adaptation framework and problem solving is dubious. This study reviews and discusses the literature and empirical studies on the failure of Agile SD implementation by revisiting the supporting framework that used to comprehend the issues in Agile SD implementation. A comparative approach is used to review the literature available in academic databases, such as ProQuest, EBSCO, IEEE, and Scopus, to ensure research originality and novelty. By filtering 87 papers that met the initial criteria, only 4 researchers focused on the area of knowledge management and used the learning process as a supporting framework in Agile SD implementation. However, they did not clearly explain the development of the framework for Agile SD. The author's initial research on a corporation reveals the failure of Agile SD implementation. Soft systems methodology (SSM)-based action research (AR) proposed to identify the real issues in Agile SD implementation. SSMbased AR provides a solution by clarifying the development of a framework using tacit and explicit knowledge to validate the development process. This study can help practitioners and academics understand the process of Agile SD implementation by early adopters who still need assistance with its application. This study is the first to explore Agile SD implementation in a corporation using the experience-based approach, contributing to knowledge improvement. It contributes to the scholarly literature by presenting concepts that combine humancentric aspects and knowledge management to improve the learning in the organization.

    View PDFchevron_right
    Organizational Learning Applied to Software Engineering: A Systematic Review
    André Menolli

    International Journal of Software Engineering and Knowledge Engineering, 2013

    Organizational learning assists the companies to improve significantly their processes by means of experiences reuse, making knowledge accessible to the whole organization. In software engineering it is important that the acquired knowledge is stored and systematically reused. This paper aims to present a systematic review, by identifying in which software engineering areas are the organizational learning studies concentrated, and how the organizational learning concepts are being applied in software engineering. This systematic review identified 2496 papers. After eliminating the duplicate titles and those not related to the review, 1184 papers remained. Applying the exclusion criteria, the number of papers was reduced to 68. These papers were analyzed and classified according to the software engineering areas defined in the SWEBOK, and the main organizational learning theories and techniques. It was observed that many software engineering researches apply organizational learning c...

    View PDFchevron_right
    Decomposing God Classes at Siemens
    Anne Etien

    2019 IEEE International Conference on Software Maintenance and Evolution (ICSME)

    A group of developers at Siemens Digital Industry Division approached our team to help them restructure a large legacy system. Several problems were identified, including the presence of God classes (big classes with thousands of lines of code and hundred of methods). They had tried different approaches considering the dependencies between the classes, but none were satisfactory. Through interaction during the last three years with a lead software architect of the project, we designed a software visualization tool and an accompanying process that allows her to propose a decomposition of a God Class in a matter of one or two hours even without prior knowledge of the class (although actually implementing the decomposition in the source code could take a week of work). In this paper, we present the process that was formalized to decompose God Classes and the tool that was designed. We give details on the system itself and some of the classes that were decomposed. The presented process and visualisations have been successfully used for the last three years on a real industrial system at Siemens.

    View PDFchevron_right
    580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved