SWEBOK V3 Chapter 5: Software Maintenance

The core concepts and principles of maintaining existing software.

Actions taken to modify, adapt, or improve existing software.

Understanding and interpreting existing code to perform maintenance tasks.

Improving the software's design and structure while keeping the functionality the same.

Understanding an existing system by analyzing its code or structure.

The steps involved in carrying out software maintenance tasks.

Tools used to assist in software maintenance tasks like debugging or code analysis.

Approximating the financial resources needed for different maintenance actions.

The initial phase of a software project, encompassing requirement definition, feasibility analysis, and process planning.

The process of establishing and agreeing upon the specific needs and functionalities of the software project.

Evaluates the practicality, cost-effectiveness, and technical possibilities of a proposed software project.

The process of defining activities, allocating resources, and estimating timelines and costs for the software development process.

Identifying, analyzing and mitigating potential risks which can impact a project

The active implementation phase of the software development project, encompassing activities such as plan execution, resource allocation, and quality management.

Final steps in a project, including evaluating if goals were met, and finalizing resources.

The process of quantifying and evaluating progress, quality, and efficiency of software development, often to monitor and adjust the project.

Guidelines and rules for software development ensuring quality, consistency, and safety. These standards can be created by organizations like the IEEE and ISO.

How software affects a company's profitability. It involves measuring costs, benefits, and finding ways to make software development more efficient.

Legal agreements outlining the terms of employment for software engineers, including duties, compensation, and rights.

Laws and regulations related to software development, including copyright, intellectual property, and data privacy.

Explanations and materials related to software, like user manuals, design documents, and code comments. It helps users understand and maintain the software.

Evaluating the cost and benefits of different design choices to find the best solution for a software project, considering factors like time, resources, and quality.

Understanding the interactions and relationships within a software development team, including communication, collaboration, and conflict resolution.

How individual developers think about challenges and solve problems in software development, including their problem-solving styles and cognitive biases.

A system of logic that uses propositions (statements that are either true or false) and logical connectives (like AND, OR, NOT) to express complex relationships.

A logic system that uses predicates (properties or relations) and quantifiers (like 'for all' and 'there exists') to reason about objects and their attributes.

Techniques used to demonstrate the truth of mathematical statements using logical arguments and existing knowledge.

A visual representation of relationships between objects (vertices) using lines or edges.

A specific type of graph with a hierarchical structure, where every vertex has a unique path from the root.

The study of probability in situations where events are countable and finite, often used in computer science and decision-making.

A model of computation that consists of a finite number of states and transitions between them, commonly used in computer science.

The ability of one integer to be divided by another integer without leaving a remainder.

A comprehensive guide to the body of knowledge for software engineering, providing a framework for understanding and applying software engineering principles and practices.

The discipline for controlling changes to a software system and ensuring that the right versions of components are used.

The processes and techniques for organizing, planning, and leading a software development team.

A structured set of activities for developing, maintaining, and improving software systems.

Software, techniques, and procedures used for software development, including coding, testing, and documentation.

Characteristics of software that meet user needs, including correctness, reliability, efficiency, and usability.

A systematic and open process for gathering feedback from experts on software engineering standards and guidelines.

To make a formal decision on a matter, especially after careful review.

SWEBOK V3 is a comprehensive guide to the Software Engineering Body of Knowledge, updated and revised from the original SWEBOK 2004. It provides a standard framework for understanding and applying software engineering principles.

The IEEE Computer Society is responsible for maintaining and updating SWEBOK V3, ensuring it reflects the latest advancements and best practices in software engineering.

SWEBOK V3 was built upon the foundation of ISO/IEC 12207:2008 and IEEE 12207-2008, an international standard focusing on software life cycle processes.

The IEEE Computer Society started creating software engineering standards in 1976, recognizing the growing importance of the field. This eventually led to the development of SWEBOK V3.

Software engineering is defined by its own professional society, standards, a code of ethics, conferences, textbooks, curriculum guidelines, accreditation criteria, certification, and licensing.

A body of knowledge is a set of principles and practices that are recognized as important in a field. It can be used for academic and training programs, certification of specialists, professional licensing, or even developing standards.

The guide provides crucial knowledge for software engineering professionals, aiding their lifelong career development. It helps them stay up-to-date with advancements and maintain a high standard of practice.

The IEEE Computer Society plays a crucial role in ensuring the quality and reliability of software. Their standards help establish best practices, improve communication among professionals, and build trust in software solutions.