Engineering Lifecycle Management overview

IBM Engineering Lifecycle Management is a suite of applications for systems and software design and development. Teams of professionals work together across geographical and organizational boundaries to design and deliver complex products that improve competitive advantage, national security, and organizations' ability to achieve their missions in many sectors of society. 

IBM Engineering Lifecycle Management Suite is designed for people in the following roles:
  • Requirements analysts, systems engineers, and other related roles.
  • Software developers, software engineers, and related roles.
  • Quality professionals, which include test developers, test engineers, and others on quality assurance teams.
  • Project managers, program managers, product managers, and release managers.
  • Process compliance and audit teams.
Table 1. Engineering Lifecycle Management applications capabilities
Application Capabilities Run on Jazz® Team Server Sold separately
IBM Engineering Requirements Management DOORS® Next Requirements management. Yes Yes
IBM Engineering Requirements Management DOORS  (DOORS ) No Yes
IBM Engineering Systems Design Rhapsody® Systems design, which includes model-based systems engineering, model-driven simulation and development, and model-based testing. No Yes
IBM Engineering Systems Design Rhapsody - Model Manager (RMM) Yes Yes
IBM Engineering Test Management (ETM) Test management, which includes verification and validation. Yes Yes
IBM Engineering Workflow Management (EWM) Workflow management, which includes tracking, planning, and change management, source configuration management (SCM), and build or pipeline integrations. Yes Yes
Global Configuration Management (GC) Federated configuration management across tools. Yes No
Jazz Reporting Service Reporting, information visualization, and dependency analysis. Yes No
IBM Engineering Lifecycle Optimization Engineering Insights (ENI>) Yes Yes
IBM Engineering Lifecycle Optimization Publishing (PUB) Automated and formatted document generation from templates. No Yes
Jazz Team Server (JTS) User management and license management. Not applicable No

The following diagram shows the development lifecycle that the solutions support. To see overviews of the applications that are represented in the image, click the boxes. For example, click Validate and verify to see an overview of Engineering Test Management.

Functions in the development lifecycle that are supported by the solutions. DOORS Next overview RMM overview Getting started with Engineering Workflow Management Engineering Test Management overview Overview of Global Configurations Reporting overview Engineering Insights overview

You can create relationships across applications by using Engineering Lifecycle Management products to support the development lifecycle as shown in the following figure and examples:

Figure 1. Engineering Lifecycle Management connects analysts, developers, and testers
The relationships between Engineering Lifecycle Management disciplines, as described by the following examples.
Requirements
  • Requirements and designs are implemented during iteration plans and validated by test cases in test plans.
  • Requirements are elicited, documented, elaborated, and validated by analysts, engineers, customers, and other stakeholders. Implementation work is tracked in work items, and correctness is validated by test cases.
Implementation
  • Project managers and development managers use iteration plans to implement requirements in the context of a development schedule.
  • Team leads plan the iterations by using iteration plans, which divide work into tasks.
  • Developers work on defects that are submitted by testers as a result of test execution
Testing
  • The test team links requirements to test plans and test cases.
  • Testers link test cases to work items to ensure coverage of the implementation.
  • Testers run test cases and submit defects for test failures.

Engineering Lifecycle Management brings together the work of many people through the following cross-application features:

Define relationship between artifacts across applications
For example, a requirement informs a test case, and when the requirement changes, the test case must be reevaluated to make sure it is still testing the right thing.
Hover over a link to see details about the link target
For example, testers can monitor the status of a defect that they reported to the development team.
Track status by adding widgets from one or more applications to a dashboard
For example, you can add a widget that shows the defects that are blocking testers.
Create development contexts
You can create development contexts that span requirements, models, tests, implementations, and other assets managed by applications from multiple vendors by using global configuration streams and baselines.
Create reports and documents that bring together information for analysis, status, and contractual delivery
Spreadsheet-like row and column reports and graphs, network graph visualizations, dependency analysis, and generated documents based on templates.
Create a digital thread of relationships
You can create a digital thread of relationships by using Open Services for Lifecycle Collaboration (OSLC), which involves engineering assets from many tools and repositories.

Jazz Team Server

The Jazz Team Server provides foundational services, such as user management and license management, that enable the Engineering Lifecycle Management applications to work together as a single logical server. In this way, the Jazz Team Server is an integration hub for the applications. After you install the Engineering Lifecycle Management products, you install product license keys into the Jazz Team Server to permit access to the capabilities that are provided by the applications. For more information about the topologies that are supported for new or upgraded installations, see Deployment and installation planning for IBM Engineering Lifecycle Management.