Software maintenance

View this topic in
Software Maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes. (Wikipedia.org)






Conferences related to Software maintenance

Back to Top

2021 IEEE Photovoltaic Specialists Conference (PVSC)

Photovoltaic materials, devices, systems and related science and technology


2020 IEEE International Conference on Robotics and Automation (ICRA)

The International Conference on Robotics and Automation (ICRA) is the IEEE Robotics and Automation Society’s biggest conference and one of the leading international forums for robotics researchers to present their work.


2020 IEEE/ACM 42nd International Conference on Software Engineering (ICSE)

ICSE is the premier forum for researchers to present and discuss the most recent innovations,trends, outcomes, experiences, and challenges in the field of software engineering. The scopeis broad and includes all original and unpublished results of empirical, conceptual, experimental,and theoretical software engineering research.


2020 Optical Fiber Communications Conference and Exhibition (OFC)

The Optical Fiber Communication Conference and Exhibition (OFC) is the largest global conference and exhibition for optical communications and networking professionals. For over 40 years, OFC has drawn attendees from all corners of the globe to meet and greet, teach and learn, make connections and move business forward.OFC attracts the biggest names in the field, offers key networking and partnering opportunities, and provides insights and inspiration on the major trends and technology advances affecting the industry. From technical presentations to the latest market trends and predictions, OFC is a one-stop-shop.


GLOBECOM 2020 - 2020 IEEE Global Communications Conference

IEEE Global Communications Conference (GLOBECOM) is one of the IEEE Communications Society’s two flagship conferences dedicated to driving innovation in nearly every aspect of communications. Each year, more than 2,900 scientific researchers and their management submit proposals for program sessions to be held at the annual conference. After extensive peer review, the best of the proposals are selected for the conference program, which includes technical papers, tutorials, workshops and industry sessions designed specifically to advance technologies, systems and infrastructure that are continuing to reshape the world and provide all users with access to an unprecedented spectrum of high-speed, seamless and cost-effective global telecommunications services.


More Conferences

Periodicals related to Software maintenance

Back to Top

Communications Magazine, IEEE

IEEE Communications Magazine was the number three most-cited journal in telecommunications and the number eighteen cited journal in electrical and electronics engineering in 2004, according to the annual Journal Citation Report (2004 edition) published by the Institute for Scientific Information. Read more at http://www.ieee.org/products/citations.html. This magazine covers all areas of communications such as lightwave telecommunications, high-speed data communications, personal communications ...


Communications, IEEE Transactions on

Telephone, telegraphy, facsimile, and point-to-point television, by electromagnetic propagation, including radio; wire; aerial, underground, coaxial, and submarine cables; waveguides, communication satellites, and lasers; in marine, aeronautical, space and fixed station services; repeaters, radio relaying, signal storage, and regeneration; telecommunication error detection and correction; multiplexing and carrier techniques; communication switching systems; data communications; and communication theory. In addition to the above, ...


Computer

Computer, the flagship publication of the IEEE Computer Society, publishes peer-reviewed technical content that covers all aspects of computer science, computer engineering, technology, and applications. Computer is a resource that practitioners, researchers, and managers can rely on to provide timely information about current research developments, trends, best practices, and changes in the profession.


Computer-Aided Design of Integrated Circuits and Systems, IEEE Transactions on

Methods, algorithms, and human-machine interfaces for physical and logical design, including: planning, synthesis, partitioning, modeling, simulation, layout, verification, testing, and documentation of integrated-circuit and systems designs of all complexities. Practical applications of aids resulting in producible analog, digital, optical, or microwave integrated circuits are emphasized.


Computers, IEEE Transactions on

Design and analysis of algorithms, computer systems, and digital networks; methods for specifying, measuring, and modeling the performance of computers and computer systems; design of computer components, such as arithmetic units, data storage devices, and interface devices; design of reliable and testable digital devices and systems; computer networks and distributed computer systems; new computer organizations and architectures; applications of VLSI ...


More Periodicals

Most published Xplore authors for Software maintenance

Back to Top

Xplore Articles related to Software maintenance

Back to Top

Using design patterns and constraints to automate the detection and correction of inter-class design defects

Proceedings 39th International Conference and Exhibition on Technology of Object-Oriented Languages and Systems. TOOLS 39, 2001

Developing code free of defects is a major concern for the object oriented software community. The authors classify design defects as those within classes (intra-class), those among classes (inter-classes), and those of semantic nature (behavioral). Then, we introduce guidelines to automate the detection and correction of inter-class design defects. We assume that design patterns embody good architectural solutions and that ...


Methods, tools and standards (software engineering)

[1991 Proceedings] Fourth Software Engineering Standards Application Workshop, 1991

Standards provide a model that can be followed to give consistent results for some 'product'. It is not meant to stifle creativity but instead to provide a framework in which creativity can occur. In an environment that has implemented a number of standards for a defined product, methods (processes) and tools can be a benefit by automating much of the ...


Software R&D: from an art to a science

IEEE Spectrum, 1990

Changes in software development are discussed, and major trends resulting in development techniques becoming increasingly structured and disciplined and focusing more attention on building a mathematical basis of software engineering are identified. Modification of the classic waterfall model of software development (stopping at certain stages to build prototypes or changing the way the cycle progresses to better accommodate the necessary ...


An Empirical Study on Clone Evolution by Analyzing Clone Lifetime

2019 IEEE 13th International Workshop on Software Clones (IWSC), 2019

The existence of code clones has several negative impacts on software maintenance which is why vast amount of research exists in the literature to characterize clone evolution. Most of those focused on clone genealogy, and clone changeness (consistent and inconsistent changes). However, analyzing clone evolution with respect to clone location and clone lifetime requires more attention to better characterize clone ...


Developing an e-commerce application by using content component model

Proceedings 36th International Conference on Technology of Object-Oriented Languages and Systems. TOOLS-Asia 2000, 2000

Applications using the Web, such as electronic commerce applications, have become larger more complex and dynamic. Developing and maintaining such large and complex Web applications demands a systematic process and an effective engineering methodology. A suitable model of Web application that can capture its features is crucial and fundamental to the establishment of such approaches. Through a practical case, relevant ...


More Xplore Articles

Educational Resources on Software maintenance

Back to Top

IEEE-USA E-Books

  • Using design patterns and constraints to automate the detection and correction of inter-class design defects

    Developing code free of defects is a major concern for the object oriented software community. The authors classify design defects as those within classes (intra-class), those among classes (inter-classes), and those of semantic nature (behavioral). Then, we introduce guidelines to automate the detection and correction of inter-class design defects. We assume that design patterns embody good architectural solutions and that a group of entities with organization similar, but not equal, to a design pattern represents an inter- class design defect. Thus, the transformation of such a group of entities, such that its organization complies exactly with a design pattern, corresponds to the correction of an inter-class design defect. We use a meta-model to describe design patterns and we exploit the descriptions to infer sets of detection and transformation rules. A constraint solver with explanations uses the descriptions and rules to recognize groups of entities with organizations similar to the described design patterns. A transformation engine modifies the source code to comply with the recognized distorted design patterns. We apply these guidelines on the Composite pattern using PTIDEJ, our prototype tool that integrates the complete guidelines.

  • Methods, tools and standards (software engineering)

    Standards provide a model that can be followed to give consistent results for some 'product'. It is not meant to stifle creativity but instead to provide a framework in which creativity can occur. In an environment that has implemented a number of standards for a defined product, methods (processes) and tools can be a benefit by automating much of the mundane tasking required to conform to the standard's rule set. In the area of software maintenance, the draft standard, IEEE P1219, belongs to the 'Standards in the Large' category, since it encompasses many smaller standards. As such it is a good example of the coupling of methods and tools to standards. The tools and methods section of the standard lists those tools that belong to the six steps of the maintenance process as defined in the standard. Defining the standard and its processes helps identify areas in which tools can be used advantageously as well as areas that could benefit from the development of new tools. Examples of new tool opportunities and the development of these tools is described.<<ETX>>

  • Software R&amp;D: from an art to a science

    Changes in software development are discussed, and major trends resulting in development techniques becoming increasingly structured and disciplined and focusing more attention on building a mathematical basis of software engineering are identified. Modification of the classic waterfall model of software development (stopping at certain stages to build prototypes or changing the way the cycle progresses to better accommodate the necessary maintenance) is examined. The use of computer-aided software engineering (CASE) is discussed. An approach called 001, which guides the user in defining what a system should do and combines the requirements and specifications phases into one step, is described. The 001 approach eliminates errors that crop up when different parts of a system (often defined in different ways) are brought together in the design and implementation phases.<<ETX>>

  • An Empirical Study on Clone Evolution by Analyzing Clone Lifetime

    The existence of code clones has several negative impacts on software maintenance which is why vast amount of research exists in the literature to characterize clone evolution. Most of those focused on clone genealogy, and clone changeness (consistent and inconsistent changes). However, analyzing clone evolution with respect to clone location and clone lifetime requires more attention to better characterize clone evolution. In this research, an empirical study has been performed on clone evolution by considering clone location (i.e., Inter-File and Intra-File) and clone lifetime. The study has been performed on four open source software covering 12 to 66 number of versions. In the study, it has been found that, (i) Intra-File clones occurred in a repository more than Inter-File clones, which infers that developers tend to clone code in the same file than different files and (ii) Intra-File clones are more volatile than Inter-File clones, which infers that developers like to refactor or change clones of the same file more than clones spanning different files. These observations help to conclude which clones should get more attention during clone maintenance tasks like refactoring.

  • Developing an e-commerce application by using content component model

    Applications using the Web, such as electronic commerce applications, have become larger more complex and dynamic. Developing and maintaining such large and complex Web applications demands a systematic process and an effective engineering methodology. A suitable model of Web application that can capture its features is crucial and fundamental to the establishment of such approaches. Through a practical case, relevant to business to business electronic commerce, we make a study of content component Web application models, within which a content component is regarded as an independent process unit performing necessary content organizing processing and presenting functions. From the content component view, which is at the level of software analysis and design, a Web application is regarded as a collection of content components and some other service components providing certain content service. The authors emphasise more effective development and maintenance in Web application by using content component models, methods and underlying technologies.

  • On the popularity of GitHub software

    The document was not made available for publication as part of the conference proceedings.

  • Automating software: proceed with caution

    Two kinds of computer-aided software engineering (CASE) tools are distinguished: front-end tools for planning and design (upper CASE), and back- end tools for implementation and support (lower CASE). The integration of these tools to cover more of the development cycle and improve the consistency of the results is discussed. The availability of CASE software and the effect of CASE on programmer productivity are examined. The reactions of programmers and managers to the changes resulting from implementing CASE are briefly discussed.<<ETX>>

  • Maintaining COTS-based Systems: Is it Possible?

    Reliable Software Technologies

  • IEE Colloquium on 'Software in Air Traffic Control Systems - The Future' (Digest No.153)

    None

  • Improving bug reporting and testing for mobile applications

    The document was not made available for publication as part of the conference proceedings.



Standards related to Software maintenance

Back to Top

IEEE Standard Criteria for Digital Computers in Safety Systems of Nuclear Power Generating Stations

This standard serves to amplify criteria in IEEE Std 603-2009, IEEE Standard Criteria for Safety Systems for Nuclear Power Generating Stations, to address the use of computers as part of safety systems in nuclear power generating stations. The criteria contained herein, in conjunction with criteria in IEEE Std 603-2009, establish minimum functional and design requirements for computers used as components ...


IEEE Trial-Use Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Maintenance Action Information via the Extensible Markup Language (XML)

The scope of this standard is the definition of an exchange format, utilizing XML, for exchanging maintenance action information (MAI) associated with the removal, repair, and replacement of system components to maintain/support an operational system.


IEEE Trial-Use Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXtensible Markup Language(XML)

The scope of this trial-use standard is the definition of an exchange format, utilizing XML, for exchanging data resulting from executing tests of a Unit Under Test (UUT) via a test program in an automatic test environment.


Recommended Practice for the Internet - Web Site Engineering, Web Site Management and Web Site Life Cycle

Define recommended practices for World Wide Web page engineering for Intranet and Extranet environments, based on World Wide Web Consortium (W3C) and related industry guidelines. (Expanded from previous PAR which specifically mentioned HTML and XML)


Systems and software engineering -- Software life cycle processes

This International Standard establishes a common framework for software life cycle processes, with welldefined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion ...