Component Tagging

In big companies, EWM (formerly named RTC) is used in mixed domains of development. A Project Area may contain different components of different platforms, programming languages, ... Therefore, developers can easily make mistake when selecting, opening and working on the wrong components. The solution for these problems is Component Tagging that helps creating tags and filtering component in the developer's workspace. Firstly, Component Tagging displays component more accurately. In crossed-environments Project Area, component tagging defines vertically the working scope. For example, there are two component types for z/OS and for another platform in a Stream. A Cobol developer is assigned to a bug-fixing task. He may select the wrong component of type "other" component and has come back from the beginning to open the right sources to work on. That is the reason why the Component Tagging idea was born. By tagging the component in the Project Area / Stream creation phase, Cobol developer will only see the sources in his scope, and he will not waste time to filter himself the code sources. So that all the views Team Artifact, Component to add popup, Stream, Pending Changes, Project Explorer, … will display only the sources of the predefined tag. To implement this suggestion, we can bind a specific property to the component object. This tag needs to be selected by developers in the Repository Workspace's creation. So that developers will work properly in their predefined scope. Secondly, Component Tagging should be integrated in the entire developing-building-packaging-archiving cycle. By using this feature, developers will be able to create build and packaging process based on the code sources filtering automatically, no need of manual components selection. All the dialogues display the sources concerned by default and make these processes more smoothly. In conclusion, in the crossed-technologies environment, the demand of the tagging and filtering component in native level of EWM is real. This feature helps reducing manual filtering time of developer as it is applied into all views in developer's workspace. In addition, it will help reducing steps in building, packaging and archiving in developer's workload.