Conference Paper

An Enhanced Software Maintenance Approach Based on World-Class Manufacturing Standard

Authors:
To read the full-text of this research, you can request a copy directly from the authors.

No full-text available

Request Full-text Paper PDF

To read the full-text of this research,
you can request a copy directly from the authors.

ResearchGate has not been able to resolve any citations for this publication.
Article
Full-text available
Software maintenance is one of the most debated phases in software development process for so many years. Having reputed as the most expensive phase of software development life cycle (SDLC), it utilizes the maximum share of the overall project costs as well as time. Agile software development provides opportunities to assess the direction of a project throughout the development lifecycle. However, it does not ideally map with the existing software maintenance process. One of the highlighted issues is the difficulty for searching of information as well as lack of knowledge to solve the maintenance problems within certain time frame. Thus, the main objective of this study is to improve the governance of software maintenance process in an Agile development team. In doing so, a tool named Axita is developed to assist the software maintenance team for storing of information in central data repository and managing projects in more efficient and timely manner. Based on the literature review as well as mapping between the agile software development and the existing ISO software maintenance process, we also proposed six best practices to better govern the software maintenance process in an Agile development team, to overcome the difficulty of information finding and reduce the time spent to solve the maintenance issues. We believe that our study and findings complement the efforts that have been put forth in improving the way we manage software maintenance thus enhance the efficiency of the software development process. Â
Article
Full-text available
The software that is being developed is becoming more complex and huge. The software industry has a huge problem with software maintenance. During the initial stages of software development, it becomes necessary to identify the ease with which a software system or component can be modified to correct faults, increase performance or adapt to a changing environment, i.e. software maintainability. This aids in the reduction of maintenance costs. A software is developed for some particular purpose, which may or may not change depending on the needs of the customer or the technological process. Hence, it leads to the evolution of the software to fit with the changing requirements. This non-trivial problem requires significant attention. According to some surveys, software maintenance accounts for about 80% of total software development costs. Therefore, this paper proposed a framework to integrate various World Class Manufacturing (WCM)-based technologies to create a model that can be utilized for improving maintenance, reduce time and cost of software maintenance
Conference Paper
Full-text available
Software maintenance has been recognized as the most demanding and costly phase in the software life cycle. Software maintenance tasks, although require a more complex set of skills and knowledge, are far less interesting to software engineers than software development tasks. In addition, insight into the scholarly literature revealed that the knowledge basis on software maintenance is significantly less than the knowledge base on software development. Due to the obvious constraints of small software companies, they do not have time, people, and other resources for assessing and improving their software maintenance practice. This paper presents the author’s reflections on experience in assessing and improving software maintenance practice in an indigenous micro software company.
Book
Full-text available
In the Guide to the Software Engineering Body of Knowledge (SWEBOK® Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society’s responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide’s 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK® Guide are Pierre Bourque (École de technologie supérieure (ÉTS), Université du Québec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).
Chapter
Full-text available
Software maintenance is a widely studied area of software engineering that it is particularly important in safety-critical and mission-critical applications where defects may have huge impact and code needs to be checked carefully through the analysis of data collected using a number of tools developed to investigate specific aspects. However, such tools are often not available to practitioners preventing them from applying the most recent and advanced approaches to industrial projects. This paper is an initial investigation about code analysis tools used to perform research studies on software maintenance prediction. We focus on the identification of tools that are available and can be used by practitioners to apply the same maintenance approaches described in published academic papers.
Article
Full-text available
Reporting on the SWEBOK project, the authors-who represent the project's editorial team-discuss the three-phase plan to characterize a body of knowledge, a vital step toward developing software engineering as a profession
Article
Sixty years ago, in 1956, the first explicit representation of a software development life cycle model was presented by Herbert Benington. Since then, software development life cycle models have come a long way, and the current article provides an overview of that development.
Book
During the last few years, software evolution research has explored new domains such as the study of socio-technical aspects and collaboration between different individuals contributing to a software system, theuse of search-based techniques and meta-heuristics, the mining of unstructured software repositories, the evolution of software requirements, and the dynamic adaptation of software systems at runtime. Also more and more attention is being paid to the evolution of collections of inter-related and inter-dependent software projects, be it in the form of web systems, software product families, software ecosystems or systems of systems. Withthis book, the editors present insightful contributions on these and other domains currently being intensively explored, written by renowned researchers in the respective fields of software evolution. Each chapter presents the state of the art in a particular topic, as well as the current research, available tool support and remaining challenges. The book is complemented by a glossary of important terms used in the community, a reference list of nearly 1,000 papers and books and tips on additional resources that may be useful to the reader(reference books, journals, standards and major scientific events in the domain of software evolution and datasets). This book is intended for all those interested in software engineering, and more particularly, software maintenance and evolution. Researchers and software practitioners alike will find in the contributed chapters an overview of the most recent findings, covering a broad spectrum of software evolution topics. In addition, it can also serve as the basis of graduate or postgraduate courses on e.g., software evolution, requirements engineering, model-driven software development or social informatics.
Article
Purpose Manufacturing excellence means to be the best in the field at each competitive priority and to demonstrate industry best practices. Over the years there have been many pioneering efforts in the direction of the assessment and implementation of manufacturing excellence through various frameworks, but none of the existing frameworks was found to be suitable for the Indian scenario, and the completeness of existing Indian manufacturing excellence frameworks was also found to be lacking. Hence this paper aims to focus on the development of a new framework for providing direction and guidance to an organization in achieving manufacturing excellence in Indian industry. Design/methodology/approach A literature review was carried out to provide a brief overview about the 23 frameworks of manufacturing excellence/world‐class manufacturing as proposed by various researchers, consultants, international agencies and individuals. An attempt is made to propose a new framework for manufacturing excellence using the comparative analysis of the existing frameworks along with the domain knowledge of the concept of manufacturing excellence and through discussion with experts. Findings The outcome of this research is a framework of manufacturing excellence. Research limitations/implications The proposed framework for manufacturing excellence needs to be validated through an empirical approach or by a clinical approach utilizing a case study. Originality/value Through comparative analysis, some unique elements/attributes were identified which represent the pillars of manufacturing excellence and through domain knowledge some more elements/attributes have been added. Sub‐attributes/sub‐elements for various pillars have also been identified.
Article
Numerous benefits have been claimed for firms that implement just-in-time (JIT) approaches to manufacturing. While a fair number of Western firms have been successful at such implementations, other firms that could benefit appear to be addressing only a few features rather than the overall philosophy and system. This paper considers whether each of a number of management initiatives is necessary for the implementation of just-in-time manufacturing. A case-based research methodology was used for theory testing at six plants, each which claimed to be implementing just-in-time manufacturing. Data were obtained via interviews, questionnaires, direct observation, and collection of documents. Of six management initiatives considered, four were supported as necessary conditions for both JIT flow and JIT quality, as well as for employee involvement. These four are: (1) promotion of employee responsibility, (2) provision of training, (3) promotion of teamwork, and (4) demonstration of visible commitment. The other two management initiatives were rejected as necessary conditions. These are: (1) provision of workforce security, and (2) use of group performance measures. The results also indicated that employee involvement plays a central role in JIT implementation.
Article
A major decision area for manufacturing firms is the strategy that assigns specific products, processes, customers, and markets to individual facilities within multi-facility firms. No empirical studies have been reported that identify differentiating factors in manufacturing structures or overall facility strategies. Based on responses from 305 plants, this research empirically determines the major dimensions differentiating manufacturing facility structures. Most of these support previous theories of decisions being made on differences in products, processes, materials, and customers/markets. Strategic groupings are determined and defined as “standardizers”, “customizers”, and automators”. Differences in each of these groupings are investigated for competitive priorities and performance indicators.
Article
As the information technology industry gains maturity, the number of software systems having moved into maintenance is rapidly growing. Often these systems are also potential candidates for outsourcing. However, adequate information regarding size, complexity, reliability, maintainability etc. of these systems is often missing. This makes the task of estimating maintenance efforts for any such system difficult for the organization owning the systems as well as for a software services vendor bidding to outsource maintenance of the system. This is further compounded by human and management factors related to maintenance activities such as management focus, client attitude, engineers' attitude, the need for multi-location support teams etc. These factors make the problem of objectively estimating software maintenance effort almost intractable.We submit that software maintenance is of equal if not more fundamental importance to the software industry, and has not received the attention it deserves, especially in the context of estimation models.This paper describes a holistic approach towards a study of the factors affecting the effort involved in maintenance of existing software systems. It describes how one could build a systems dynamics model to predict the effort involved to maintain a software system, based on qualitative and qualitative inputs.
Conference Paper
The traditional US approach to manufacturing is first described; then the highly competitive approach referred to as world-class manufacturing (WCM) is discussed. Next, the systems used by progressive US firms in implementation of the world-class manufacturing concept are described. The concept includes just-in-time inventory control, total quality control, and computer-integrated manufacturing. Finally, some approaches to generating more creative ideas in manufacturing that should enable the remainder of US manufacturing organizations to replicate the result of the progressive firms are described
IEEE standard glossary of software engineering terminology (IEEE Std 610.12–1990). Los Alamitos
  • I S C Committee
Design and control of logistic process in an Italian Company: Opportunities and Challenges based on Industry 4.0 principles
  • De Felice
World class manufacturing casebook: implementing JIT and TQC
  • R Schonberger
Software maintenance: Challenges and issues
  • A Gupta
  • S Sharma
Design and control of logistic process in an Italian Company: Opportunities and Challenges based on Industry 4.0 principles
  • F De Felice
  • A Petrillo
  • F Zomparelli
Development of a method for software maintenance using event logs
  • R Murdoch