Support for Project Hierarchies

FlexNet Code Insight now supports the creation and management of project hierarchies as a means to keep track of projects related each other. A project hierarchy is created by simply identifying one or more projects as child projects of another project (called the parent project). Once the hierarchy is created, links are established in the Code Insight Web UI between the parent project and the associated child projects so that users can easily move between projects to assess scan results and review inventory.

A project hierarchy is useful when a product application contains one or more modules, each with a codebase for which a user wants to set up a separate project to track and assess the module’s open-source or third-party software. By setting up a project hierarchy, one can easily switch between the top-level project for the application (the parent project) and the projects for the modules (the child projects) to complete the work needed to build a composite Bill of Materials.

A project hierarchy is established for a given project from the Project Hierarchy tab on the Manage Project | Project Settings dialog accessed from the project’s Summary tab.

Note that a child project, in turn, can be a parent project to other projects. Likewise, a given parent project can be identified as a child project to other projects. Since hierarchies are created as needed, some projects might have no association with a hierarchy.

Once the hierarchy for a given project is established either as a parent or a child, users can do the following:

•

From the Summary page for the project, view and link to any of the its child and parent projects.

•

From the new Inventory view, examine the inventory of the project’s child projects as well as link to any these child projects (see All-Project Inventory View).