老虎机模拟器手机版

書名： IBM Rational Team Concert 2 Essentials
作者名： Suresh Krishna TC Fenstermaker
本章字數： 539字
更新時間： 2021-04-09 22:07:49

Chapter 4. Team and Source Control

Change in all things is sweet.

--Aristotle

Source control is a fundamental aspect of modern software development. The source control system helps us to store, version, and control the requirement documents, design documents, architecture blueprints, test documents, and of course, our source code.

The following is a quote about SCM from Roger Pressman's book Software Engineering: A Practitioner's Approach:

Source Control Management (SCM) is a set of activities designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting on the changes made

With the increasing complexity of software development, we must consider the following:

Integration of source control with team processes
Seamless integration of source control system into coding environment
Traceability of the issues/bugs/enhancements to the source code and vice versa
Ability to suspend the current work in favor of another task
Creating branches that allow for parallel development and merge there after
Ability to resolve conflicts from other team members changes on the same source code

Introduction

In this chapter, we will see:

How Rational Team Concert enhances the source control management experience giving greater control to the development team
Different concepts in the source control
How to work with the Rational Team Source Control

The source control component of Rational Team Concert manages the change flow of the source code, documents, and other artifacts generated by each team member. Rational Team Concert's source control organizes files and folders into components and streams, and provides workspaces where we can view and modify file and folder contents. The repository objects represent the configuration of the system being developed and allow any configuration to be retrieved, shared, or built.

Rational Team Concert's source control is integrated into the other parts of the life cycle as follows; this enables the developer to focus on the real domain problems and worry less about the tools that they use:

The Ration Team Concert's Build Engine is integrated in such a way that it can pull the snapshot of the files from source control and reproduce the exact source build.
Work items and Change sets can be linked together providing traceability of changes to the reasons for a change.
Process management uses source control as an integrated mechanism. For example, we can set up the process in such a way that new hires in our team must get their change sets reviewed by the project leader before submitting.

Rational Team Concert lets us benefit from SCM's ability to track and version our changes, whether or not we are ready to share those changes with our team. As a user we have our own private repository workspace that stores the changes we've made, independent of everyone else's changes. When we load our repository workspace, the files and folders in it are transferred from the repository on the server to our Eclipse workspace on our computer. To push a change from our Eclipse workspace to the repository workspace we check in the change.

In the next sections, we will look at some examples using the team invitation and team source control system.

官术网_书友最值得收藏!

IBM Rational Team Concert 2 Essentials