Engenharia de Software - Aula 16 - Gerenciamento de configurações (Parte 1)

Summary

Professor Marcelo Fantinato's lecture on software engineering discusses configuration management, a critical aspect of software development. He explains that it involves combining different parts of software to create final products, managing versions, and releases. The lecture highlights the importance of tracking changes, integrating components, and ensuring that the final software configuration functions correctly. It also touches on change management processes, emphasizing the need for systematic handling of modifications to maintain control and deliver a quality product to the client.

Takeaways

• 📚 The lecture is part of a software engineering course at UNIVESP, focusing on 'Configuration Management'.
• 🔧 Configuration Management is not as intuitive as it seems and is related to the software development process rather than the end-user configuration of software.
• 🔩 It involves combining different parts of the software to create a final product, which can be done in various configurations based on different versions of components.
• 🛠️ The purpose of Configuration Management is to ensure that the integrated system works as intended and to maintain control over which version changes are incorporated into each system version.
• 🔄 Integration and configuration testing are crucial to guarantee that the system functions properly after combining different parts.
• 📈 Configuration Management includes activities such as version control, change management, and release management.
• 🔄 Version control is a key aspect of Configuration Management, where each part of the system (code, components, databases, etc.) can have different versions that are combined to form a release.
• 📝 A 'Release' is a version of the software that is delivered to the client, similar to the concept of 'version' but at the system level.
• 🔧 Change Management involves a systematic process to handle changes in the software, triggered either by the discovery of defects or by client requests for modifications.
• 🏢 The Change Control Board (CCB) plays a crucial role in evaluating, prioritizing, and approving or rejecting change requests based on cost-benefit analysis and impact on the system.
• 📋 Tools are used to support the opening of change requests and the entire lifecycle of the change, from initiation to closure.

Q & A

What is the main topic of the 16th class of the software engineering discipline taught by Professor Marcelo Fantinato?

The main topic of the 16th class is 'Configuration Management' within the software engineering discipline of the computer engineering course at UNIVESP.

How does the speaker describe the initial perception of 'configuration management'?

The speaker describes the initial perception of 'configuration management' as something that is not very intuitive. It is often misunderstood as simply configuring software, but in the context of software engineering, it refers to the management of different parts of the software to form the final product.

What are 'configurations' in the context of software engineering?

In the context of software engineering, 'configurations' refer to different combinations of the various parts of the software. These configurations are used to assemble the final software product that is delivered to the client.

Why is configuration management important in software development?

Configuration management is important in software development to ensure that the final integrated system works as intended. It helps to control which versions of components are incorporated into each version of the system and prevents the loss of control over changes.

What are the three main activities involved in configuration management?

The three main activities involved in configuration management are version control, change management, and release management.

What is an 'item of configuration' according to the speaker?

An 'item of configuration' is any part of the system that can have different versions and that is worked on during development. These items are combined to form a release for the client.

What is the process when a change is needed in the software?

When a change is needed in the software, a Change Request (CR) is submitted. This request is then analyzed by the development team to determine its validity and impact. A Change Control Board (CCB) evaluates the change, considering factors like cost-benefit analysis, and makes a decision to approve or reject the change.

What role does the Change Control Board (CCB) play in configuration management?

The Change Control Board (CCB) is responsible for reviewing and evaluating the proposed changes to decide what will be included in the system. They consider the consequences, impact, benefits, and costs of making or not making the change.

How are changes in software development managed systematically?

Changes in software development are managed systematically through a process that includes registering change requests, analyzing their impact, evaluating them, and making decisions based on cost-benefit analysis. Tools are used to support the opening of change requests and the entire lifecycle of the change.

What is a 'release' in the context of software delivery to clients?

A 'release' is a version of the software that is made available to clients. It is similar to the concept of a version but refers to the entire system rather than individual components.

What are the two main reasons for changes in software development?

The two main reasons for changes in software development are the correction of defects, identified either by developers or testers, and requests from the client for the system to be different, not due to a defect but due to a change in requirements or ideas.