Engineering Insights terminology and concepts

The terms and concepts that are used in IBM Engineering Lifecycle Optimization - Engineering Insights (ENI) are defined and illustrated here. Terms and concepts that are specific to other applications are also described with links to detailed descriptions in other product documentation sections.

If you upgraded from an older version, review this list as some terms might have changed.

A detailed examination of artifacts. Analyze artifacts to explore and discover how they relate to one another.

Use the impact analysis profiles that come with ENI to customize profiles for impact analysis diagrams that show relationships between artifacts. For example, if you have a new change request, you can run impact analysis on that artifact to gauge the impact of implementing it.

The following impact analysis diagram shows all dependencies, related artifacts, and blocked artifacts that are related to the change request.

Image shows an example of an impact analysis diagram and the relationships between related artifacts.
A general term for the objects in a repository. Artifacts are created and maintained in various lifecycle management applications, such as IBM Engineering Workflow Management (EWM) work items or IBM Engineering Requirements Management DOORS® () requirements.

When administrators create or edit views, they drag artifacts from the palette onto the view canvas.

The set of UI properties that define the look and feel of links between artifact containers.
Custom artifact elements:
A custom artifact element is a set of artifacts that are gathered by a SPARQL query. The query assembles artifacts of a specific type, such as requirements or, test artifacts that are stored in the index. When administrators edit views, they can add custom artifact elements to the view by dragging them from the palette onto the view canvas.
Lifecycle Query Engine:
An index of data that can be queried. The data is retrieved from any application that implements the tracked resource set (TRS) specification: work items (from EWM), requirements, designs, and test artifacts.
A reference to another artifact. The link might be stored in another tool, such as EWM, DOORS, or another lifecycle management application.
A way of retrieving information from the index. Artifacts, such as work items, requirements, design models, and test cases are retrieved from the Lifecycle Query Engine.

Administrators can craft SPARQL queries to embed in custom views that they create. The queries pull data from the index and refresh the custom view with the appropriate artifacts. The retrieved artifacts can then be used to populate a view, run a report, perform an analysis, and more.

A saved, shareable instance of a view that shows artifacts and their relationships at the moment that instance is saved. A snapshot can be refreshed to show current artifacts and relationships.

In views you can select specific artifacts and the links among them and record your selection in a view snapshot. When you create a snapshot, all the current artifacts and relationships are saved. You can share the snapshot of a shared view with other users or set the snapshot to be a personal view. The snapshot is saved as a child of the original view. For more information, see Using Engineering Insights views.

A visual representation of artifacts and the relationships among them. ENI comes with a set of predefined views. For more information, see Engineering Insights ready-to-use views.

Go to Views > Shared Views > Sample views for new users, and open V Process. This view shows a sample systems development lifecycle. There are many systems development process methodologies, such as agile, waterfall, and V-model.

The V Process view is a common information traceability model. The information is divided between the two sides of the V. The first half of the V shows tasks that are driven by product definition, such as creation of concepts, requirements, architecture, and design. The second half of the V shows tasks that are driven by product testing and integration, such as system verification and validation, and integration, test, and verification. The verification and validation on the second half of the V can be completed simultaneously with the product definition steps on the first half of the V.

Because teams participate in early product verification and validation, they find the defects early in the development so they can avoid finding most of the problems near the end of the release. Finding defects early reduces the cost of fixing them. Early validation and improved communication among team members ensures that the quality standard is met.

The V-model doesn’t depend on any specific organization scheme, so each team can tailor the V Process view for their product.

This image shows an example V Process hardware view.

For more information about views, see Creating a Engineering Insights view.

To understand how the ready-to-use views are populated, see the term Queries.

Types of artifacts in views and diagrams

Describe what users want from a product or service. A requirement can contain links to related artifacts that enhance its definition. See IBM Engineering Requirements Management DOORS Next.
Work items:
Manage the tasks and issues that your team must address during the development cycle.
Test cases:
Help teams plan, develop, run, and report on their test plan to ensure that the quality standard is met. See Engineering Test Management.
A physical performance measurement. Reports use data from the index to produce documents that track status and progress. You can use reports to manage and mitigate development risks, improve product quality, control product costs, and more.

For information about reports, see Engineering Insights reporting.