Eclipse SW360 - Screenshots

A picture is worth a thousand words

The SW360 application is divided into several sections around managing a catalogue of software components and the software bill-of-material of your software projects, products or services. The menu bar as shown on home screen cover the following main sections.


A dashboard listing the components and projects created by the user logged in. With this overview, the own projects and components can be directly accessed.


The main area of work in the projects section. SW360 uses the term project as synonym for products, services, or internal projects. The projects area starts with a listing of all projects which are visible to the user, according to the visibility setting of the project.

As for individual projects, a number of subsections is provided, allowing for managing different aspects of a project: license compliance, export control (ECC), vulnerabilities, locking of attachments for project use, and vulnerabilities.

For each project, a number of attributes can be maintained, most notably external ids, which allow for a mapping to the dataset in SW360 with external systems.

For the license compliance, SW360 allows for maintaining a global clearing status for each release of a component. In addition, a clearing status can be set for use at each individual project.

Not only the clearing status for each use of a release can be captured by SW360. Also, the type of usage (contained, side-by-side installation, etc.) can be saved as attribute.


Components in SW360 can have multiple types, such as OSS, commercial component or a service (and more types), since license compliance matters for type of software, not only OSS. Components are in fact a container for releases, because license compliance information and other attributes change between different releases of a component.

At each release, basic attributes can be stored, some of them are informal, but can give relevant input to usage statistics of software in an organisation.

Of course, when if comes to license clearing, more relevant attributes can be found.

Special: Export Control and Customs

Once the software bill-of-material has been setup, not only license compliance per component can be checked. But also the export control and customs (ECC) relevant information can be assessed for each project.

ECC classifications can be set for each release of a component - SW360 supports a specific role for ECC experts who are the only users which can modify ECC data. Other users can enter ECC data which requires approval by ECC experts with the particular role.

SW360 provides an index for all data, thus searching for keywords will yield results for all different datasets, such as projects, components, licenses, etc. Search for terms can be filtered by data set types.


The preferences section of SW360 shows the basic user information. In addition, this is the area where users can generate access tokens for the REST API. Access tokens can be configured to have a limited validity or set for only allowing for read access. Once issued access tokens cannot be shown anymore because SW360 stores only a hash. Thus deletion of access tokens requires a designating name for each token.

Moreover, in the preferences section, each user can define own notification settings - depending on the user’s needs.