5724-W87 IBM Engineering Requirements Management - DOORS Next 7.0

IBM Asia Pacific Sales Manual
Revised: May 25, 2021


Table of contents
Product life cycle datesProduct life cycle datesDescriptionDescription
Program numberProgram numberOperating environmentOperating environment
AbstractAbstractPlanning informationPlanning information
HighlightsHighlightsPublicationsPublications


Product life cycle dates

Top rule

Program Number VRM Announced Available Marketing Withdrawn Service Discontinued
5724-W87 07.00.02 2020-12-08 2020-12-11 - -
5724-W87 07.00.01 2020-07-07 2020-07-07 - -
5724-W87 07.00.00 2020-03-17 2020-03-20 - -
5724-W87 06.00.06 2018-06-12 2018-06-15 2021-04-16 2022-04-30
5724-W87 06.00.05 2017-11-28 2017-12-04 2021-04-16 2021-04-30
5724-W87 06.00.04 2017-06-06 2017-06-06 2021-04-16 2021-04-30
5724-W87 06.00.03 2016-11-29 2016-12-05 2020-12-18 2020-12-31
5724-W87 06.00.01 2015-12-08 2015-12-14 2020-12-18 2020-12-31
5724-W87 06.00.00 2015-06-09 2015-06-26 2020-12-18 2020-12-31
5724-W87 05.00.02 2014-12-02 2014-12-05 - 2018-04-10
5724-W87 05.00.01 2014-09-09 2014-09-09 - 2018-04-10
5724-W87 05.00.00 2014-06-02 2014-06-02 - 2018-04-10
5724-W87 04.00.06 2014-02-24 2014-02-28 2017-09-15 2017-09-30
5724-W87 04.00.05 2013-12-03 2013-12-06 2017-09-15 2017-09-30
5724-W87 04.00.04 2013-08-27 2013-08-30 2017-09-15 2017-09-30
5724-W87 04.00.03 2013-06-03 2013-06-07 2017-09-15 2017-09-30
5724-W87 04.00.01 2012-11-27 2012-11-27 2017-09-15 2017-09-30
5724-W87 04.00.00 2012-06-04 2012-06-12 2017-09-15 2017-09-30
5724-W87 03.00.01 2011-06-06 2011-06-14 2018-07-13 -
5724-W87 02.00.00 2009-11-17 2009-11-24 2015-04-30 2015-04-30
5724-W87 01.00.00 2008-11-18 2008-11-18 2018-07-13 2012-04-30


Back to topBack to top

Program number

Top rule

  • IBM Engineering Requirements Management DOORS Next 7.0.2 (5724-W87)


Back to topBack to top

Abstract

Top rule

Rational DOORS Next Generation 6.0.5

Responding to popular demand, IBM Rational DOORS Next Generation 6.0.5 brings usability improvements to distinguish the different ways of managing requirements (module versus base artifacts). The release responds to FDA demands by providing FDA-compliant electronic signature support for both baselines of requirements data and associated work items in Rational Team Concert. Continuing with the theme of usability, improvements have been made for module scrolling responsiveness while working with larger module specifications. From an administrative perspective, it is now simpler to manage larger numbers of projects with the ability for a project to inherit its base properties from a central definition.

IBM Rational DOORS Next Generation 6.0.3

Teams that create and evolve complex IT systems and mechanical- electrical-software products need modern tools and developments practices to overcome the challenges of increasing solution complexity, compliance, and cross-organization coordination and collaboration. Version 6.0.3 furthers this with the following enhancements:

  • Extend agile development to agile program and portfolio planning with built-in Scaled Agile Framework (SAFe) 4.0 templates.
  • Gain efficiencies from easier parallel development and reuse of requirements and tests with Global Configuration Management of many component streams and baselines within project areas in IBM Rational DOORS Next Generation and Rational Quality Manager.
  • Find insight into project dependencies and status using:
    • Jazz Reporting Service with more development data
    • More ready-to-copy reports
    • More graph formatting options
  • Collaborate more easily on requirements with expanded use case support for requirements interchange across supply chains and new user interface wireframe diagrams.
  • Improve productivity of manual testing with new customizations and automated testing across multiple servers.
  • Improve productivity in complex software development with improved change and merge use cases in Rational Team Concert source control management and enhancements when updating Rational Team Concert work items while using Git.

IBM Rational DOORS Next Generation 5.0.0

Rational Requirements Composer is renamed to IBM Rational DOORS Next Generation. Although previously sold as separate offerings, Rational Requirements Composer and Rational DOORS Next Generation have, in fact, been identical products for some time and will now be taken forward with a single product name. A single Jazz-based requirements tool will result in a higher quality product for clients with less confusion as to which requirements management tool to use. All customer entitlements for Rational Requirements Composer will be renamed to Rational DOORS Next Generation, but features and functions will stay the same.

Rational DOORS Next Generation 5.0 includes the following features:

Performance and scale: Reducing the functional load on the central Jazz Team Server while also offering support for additional scale by deploying multiple Requirements Servers to share a single common Jazz Team Server.

Usability: Improving both the speed in which end users are able to perform their tasks and enhancing the look of the overall environment in which they work.

Integrations and extensions with OSLC and JavaScript: Continuing to improve JavaScript support with additional APIs with additional APIs for manipulating group requirements.

Nonfunctional requirements: This release updates most supporting environments including support for Microsoft Windows 8.1, Internet Explorer 11, and Chrome 30.

Rational Requirements Composer 4.0.6

Rational Requirements Composer provides the essential business capability to define business needs and manage all project requirements across the development life cycle. It fosters better business and development collaboration in an online requirements community involving a wide set of stakeholders (customers, analysts, developers, testers, and operations or production).

Rational Requirements Composer 4.0.6 (part of the Rational Collaborative Lifecycle Management solution) expands support for enterprise deployment, delivers higher value for some systems customers, and provides enhanced capability for customer consumability (time-to-value) in the software and IT market.

Rational Requirements Composer 4.0.5

Rational Requirements Composer 4.0.5 features:

  • Copy-and-link as a way of creating requirements and links inside a project
  • Ability to create links between artifacts using drag and drop with two different Browser windows
  • Ability to rearrange artifacts in a module using drag and drop in the web client
  • Fast loading and scrolling on large modules
  • Requirements management reporting metrics to report on new data measurements
  • Exciting preview of the first steps to support client side customization with Java Script

Rational Requirements Composer advances the way that teams work together to develop products and solutions. For more information about the CLM vision, architecture, products, and community, see

http://jazz.net


Back to topBack to top

Highlights

Top rule

Engineering Requirements Management DOORS Next 7.0.1 (5724-W87)

Enhancements in version 7.0.1:

  • A key focus of Engineering Requirements Management DOORS Next 7.x is to extend the overall scale of data that can be managed by using a DOORS Next Requirements Management server. Performance testing information for Engineering Requirements Management DOORS Next 7.0 can be found on the Jazz website, including how the solution was tested and the types of loads that were supported. Testing continued in version 7.0.1 and can now support up to 1,000 concurrent users working on a single Engineering Requirements Management server using an Oracle database.
  • When using change sets to modify requirements, it is common for dependencies between change sets to be created when multiple people change the same requirements or are making changes in the same module when there are changes to the structure of the module. Whereas DOORS Next 7.0 mandated delivering dependent change sets, Engineering Requirements Management DOORS Next 7.0.1 enables dependencies to be overruled when selecting change sets for delivery.
  • Requirements Interchange Format (ReqIF) is improved in the way attachments and graphical elements are used as part of requirements information. Where possible, DOORS Next 7.0.1 can import OLE elements from applications such as DOORS directly into attachments in DOORS Next. DOORS Next can export graphical elements such as diagrams in a format that can be seen but not edited in other requirement tools, including DOORS.
  • Trace column information can be tailored to be more succinct in the information that is displayed, including the use of traversable link indicators rather than displaying more verbose URLs.

IBM Rational DOORS Next Generation 5.0.0

Investment in the DOORS Family entitles you to use either DOORS, DOORS Next Generation, or both.

  • Rational Requirements Composer: Is renamed to IBM Rational DOORS Next Generation. Customer entitlements will remain unchanged and simply be renamed at renewal time.
  • DOORS Next Generation: Delivers a major release of the product, making groundbreaking changes to the product architecture to support more flexible deployment configurations able to support higher volumes of data and concurrent users. This release also continues the focus on the end user's ability to develop and manage requirements quickly and efficiently.

IBM Rational Requirements Composer 4.0.6

IBM Rational Requirements Composer 4.0.6 (part of the Rational Collaborative Lifecycle Management (CLM) solution) delivers the following capability:

  • Expands a project team's support for requirements definition and management support for enterprise deployment.
  • Delivers higher value for some systems development customers.
  • Provides enhanced capability for customer consumability (time-to-value) in the software and IT market.

The focus for this release is:

  • Module usability improvements for artifact creation:
    • Preferred types in a module and in-line type selection
    • Improved module responsiveness: initial display, and artifact creation
  • Introduction of general-availability client-side, API customization with JavaScript


Back to topBack to top

Description

Top rule

Engineering Requirements Management DOORS Next 7.0

Engineering Requirements Management DOORS Next 7.0 improvements are focused on product scale, resilience, and throughput. This release simplifies requirements exchange across your value chain that typically involves customers and suppliers.

  • Performance and scale: a new data architecture consistent with the rest of ELM.
  • 9x improvement over data scale for each RM application server based on release testing. Support for 20 million artifacts per-server (Oracle) and 10 million artifacts per-server (DB2) for 500 concurrent users with a smaller server footprint. Where more scale is required, we continue to support and recommend multiple RM server environments.
  • Performance at scale offers more graceful degradation with many instances of functions running faster.
  • Dependency on Apache Jena technology is significantly reduced and this greatly increases the robustness of the server architecture.
  • The new data architecture enables organizations to perform more efficient systems monitoring using MBean technology in line with the rest of ELM.
  • Changes to functions resulting from improvements in scale and performance include link suspicion and validity being consolidated to the single capability of link validity:
    • A key requirement for any requirements tool is to understand change. It is essential to monitor, understand, and take action for engineering changes.
    • Consolidating suspect links and link validity reduces the user cost for transitioning from a single version of requirements to requirements under configuration management and brings consistency for decision-making regarding impact analysis of related engineering changes.
  • Functions that have been removed in this release include:
    • The built-in capability for ReqPro migration.
    • The component used to view old style diagrams. All previously created RRCx-based drawings should be converted to the new diagram format prior to migrating to Engineering Requirements Management 7.0.
    • TRS (tracked resource sets) 1.0 feeds. All integrations have used TRS 2.0 for some releases.
    • Specific features to resolve data spills are not available in this release, but are expected to return in a future release.
  • Value chain enhancements for working with customers and suppliers:
    • Automatic data type mapping. Working with customers and suppliers often involves receiving data over which you have little control and bringing it into your own project areas. Where possible, it is always advised to bring data into a component or project area that is specific to that supplier. This release introduces a way to automatically map Engineering Requirements Management DOORS data into Engineering Requirements Management DOORS Next data types in such a way that round tripping becomes more reliable, requires less manual effort, and can be managed among different suppliers.
    • Tagging missing data. IBM typically recommends that requirements are never deleted in a specification because they improve visibility for an audit trail. When working with suppliers, data might be missing in a returned data exchange and one must decide whether to interpret that as requirements have been deleted by the supplier or were not included in an exchange. Engineering Requirements Management DOORS Next 7.0 introduces tagging to imported data so filters can be used to manage this situation.

IBM Rational DOORS Next Generation 6.0.6:

Requirements repurposing

As users decompose requirements from one level to the next it is very typical to copy a high level requirement to draft a lower level need.

This release introduces decomposition support that:

  • Allows for type repurposing to reshape requirements from high level to low level types
  • Transforms your requirement type on a copy operation
  • Links back to the originator of the repurpose operation
  • Copies and links between requirements in different components

Enterprise and scale

Adopt a deployment topology that has multiple RM servers:

  • Provides another layer of control
  • Extends the scale of data that DOORS Next Generation can support

This release removes some of the constraints of cross-server working:

  • Drag-and-drop linking
  • Support for custom RM link types
  • Support for multiple JTS servers

Constraints:

  • All data must be in the same global configuration.
  • Link types must be defined in both RM servers and have the same URI values.
  • Related RM servers must be registered with the same LDX.

Focus on module data

To facilitate reuse, requirements within modules are also placed into a root "base" folder. This can be distracting to users if they want to see only modules. This release:

  • Enables a project to define the root location for base artifact folders, allowing for the user to focus solely on the module data
  • Removes some of the risk of linking to incorrect requirements
  • Refocuses the user on only the requirements in which he or she is interested
  • Enables a project manager to continue to apply access controls from a central place

Support for the supply chain with a mix of DOORS and DOORS Next Generation

This release removes the ReqIF restriction of data, crossing a mixed supply chain of IBM Rational DOORS and DOORS Next Generation where DOORS Next Generation is the original host.

  • DOORS enforces attribute level locking in order to remove the need for merging conflicting changes.
  • DOORS Next Generation has no attribute level locking as it has functionality to support merging of conflicting changes.
  • This release introduces attribute level locking control in the ReqIF package created from DOORS Next Generation. This enables round tripping of requirements updates with ReqIF with a supply chain that uses a mixture of DOORS and DOORS Next Generation.

Usability

This release includes many smaller enhancements designed to improve the daily processes of a requirements engineer.

Rational DOORS Next Generation 6.0.5

FDA compliance -- Supporting electronic signatures for baselines

Like many other industries, FDA-related organizations rely on governance and compliance around requirements data. FDA also has requirements to ensure accountability and a documented consensus of decision making. This release provides support for electronically signing baselines in conformance to FDA regulations.

Usability -- Differentiating free-standing requirements and modules of data

DOORS Next Generation allows for requirements to exist in their own right (base artifacts) and in the context of specifications (modules). This release makes it easier to distinguish requirements in their different forms, ensuring fewer errors are made in finding relevant information and in the creation of traceability.

Administration -- Managing projects at a higher scale

As the scale of organizations grow, so does the administrative overhead for managing multiple project environments to keep them all adhering to company standards. This release introduces Project base property inheritance that allows an organization to manage many of the generic properties of a project in a single place. Projects can now inherit Roles, Permissions, and Workflows between similar project areas.

Linking -- A focus on link ownership, specifically when using configurations

Traceability is one of the most important aspects of requirements data. When combined with Configuration Management linking can get very complex and difficult to maintain. Care is needed to govern which versions of information are related to each other. This release introduces the concept of "link direction" ensuring consistency with linking with a focus on "link ownership." Knowing that a link is always owned from the place it starts from allows users and organizations to know more clearly what will happen as versions are created and Global Configurations are defined.

Other enhancements and work in progress

This release continues to work on Configuration Management functionality with improvements to the merge and conflict resolution dialogs and also the ability to support import of multiple versions of ReqIF package into different streams and for those requirements to be seen and treated as different versions of the same information.

Performance and scale continues to be a focus for DOORS Next Generation. Several improvements have been made around performance including support for more responsive scrolling around larger modules.

IBM Rational DOORS Next Generation 6.0.3

Rational DOORS Next Generation 6.0.3

In addition to the major addition of component based development of requirements, this release has had three themes.

In this release, it is simpler to filter, search, and generally navigate requirements information. Filters have now moved in to a more interactive control above the requirements to allow for simpler interaction and analysis of information without struggling to get to grips with a query. Views are placed in their own area to allow your organizations to more easily pre-define how team members should view requirements. Finally, the overall layout of the display is easier to control in hiding controls if all you require to do is read or write your requirements.

Migration from DOORS to DOORS NG has a new mechanism to improve the value of your data by instilling an artifact type to your previous DOORS data. Rather than relying on data validation techniques to make sure that accurate requirements are being added to DOORS, DOORS NG can now be more fully utilized to ensure that information can only be provided with relevant attribute values. For example, a requirement could have a priority whereas a heading might never need this attribute value.

IBM is a full contributor to the ReqIF implementers forum, in accordance with the OMG. DOORS NG 6.0.3 makes a number of improvements for working with requirements across a supply chain where organizations use different implementations or even different requirements tools. This release introduces improvements with reporting around ReqIF import while making it far simpler to configure ReqIF files based on predefined module "views".

Deprecation ofRRCx

As previously announced, the older diagramming capability within DOORS NG, called RRCx, is now deprecated. DOORS Next Generation 6.0 introduced new Diagram Editors to support informal diagramming within requirements sets without the need to install an additional browser. The original graphical editors (RRCx) remained to provide consistency and time to move over to the new technology. The third-party components that were used within RRCx are now deprecated in two of the three major browsers (Firefox and Chrome). So in this release the Java plugin (RRCx) that provides the old diagram editors is no longer available.

  • Version 6.0.3 extends the new Diagram Editor to support a full UI Wireframe palette and associated functionality.
  • RRCx artifact types will be read only. The diagrams will look identical, will all be clickable, printable and reportable.
  • The DOORS NG product team intends to provide a utility to convert an RRCx diagram into the Diagram Editor format. All of the RRCx format types will be supported. While this conversion will not be pixel perfect, it is expected to preserve every shape, connection, artifact link, and comment in the original RRCx diagram. While plans are subject to change, this conversion utility is expected in the first half of 2017.

IBM Rational DOORS Next Generation 5.0.2

Rational solution for Collaborative Lifecycle Management 5.0.2 delivers the combined capabilities of Version 5.0.2 of Rational Team Concert, Rational DOORS Next Generation, and Rational Quality Manager in one easy-to-install and easy-to-use product that enables continuous delivery with:

  • Stronger support and improved ease of use for Requirements manipulations
  • Easy, intuitive tracking and planning for Agile projects
  • Ability to visually manage and optimize multiple workflows with Kanban boards and taskboards
  • Easy-to-use Report Builder with graphical and multi-artifact traceability reports
  • Several usability and performance improvements
  • Better support for Audits and Compliance
  • Better integrations

The functionality that is offered with Collaborative Lifecycle Management 5.0.2 includes:

Stronger support for requirements manipulation while extending support for lifecycle integrations over disciplines and requirements projects

Rational DOORS Next Generation 5.0.2

Drag and drop document embedding

With the support to attach files directly in the web browser, you can extend the richness of your requirements data.

Requirements often need supporting information in the format of diagrams, documents or spreadsheets. In this release, you can drag file attachments from your local file system directly to the requirements in your web browser. A preview of the attachments is displayed with the requirements information. Where attachments contain several pages, you can preview the information without the need for the original application to be installed. The file types that are supported for preview in the web browser include

Word           .doc  .docx  .dot
Excel          .xls  .xlsx  .xlsm
PowerPoint     .ppt  .pptx
Visio          .vsd  .vdx   .vsdx
Adobe          .pdf  .psd
Open Office    .odt  .ods   .odp
Text           .txt  .rtf

Module views

Views show different visualizations of the same requirements data, for example, selecting attributes to be displayed alongside requirements or defining a filter to limit the display to a subset of requirements. Views are often carefully defined by project managers to share between many people, but it is also quite typical for an average team member to make ad hoc changes to views as a day-to-day operation. This release makes a day in the life of the typical team member easier. You can make temporary changes to views without saving them, and you can reuse modified views in different browser windows or tabs.

IBM Rational DOORS Next Generation 5.0.0

Performance and scale

In order to reduce the functional load on the Jazz Team Server (JTS) and to support more flexible deployment options, this release enhances the overall architecture by moving the requirements management-specific data on to the requirements management server. In previous releases the architecture for Rational DOORS Next Generation has differed from other CLM applications in that all data was stored within the central JTS; this is now made consistent.

Support for multiple requirements management application servers sharing a single JTS is now possible using the new data architecture. A single JTS ensures that users, licenses, and other central configurations can be shared over multiple requirements management deployments. This enables higher data scale by segregating different programs into their own requirements management servers.

A data migration is therefore required for this release to move the requirements management data to the requirements management server and to rerun the indexes for the data in this new location.

For detailed instructions, see the Installation Guide. For extended configuration guidelines detailing hardware and configuration information, see

http://jazz.net

Usability

End user productivity improvements: Improving both the speed in which end users can perform their tasks and enhancing the look of the overall environment in which they work.

Major improvements to module editing focus on end user productivity. Recent improvements include the following:

  • Seamless and quick keyboard shortcuts avoid the need to switch from keyboard to mouse on a frequent basis.
  • Individual requirements are easier to edit.
  • You can view and modify artifact properties from within the module user interface.
  • Preferred requirement types accelerating accurate module production.
  • Performance improvements in editing and scrolling modules or larger sizes (more than 10,000).
  • You can display and manipulate folder hierarchy while browsing module data.
  • Drag and drop is enabled throughout the user interface, allowing move and copy of artifacts, restructure within modules, and linking between different modules in different web browser tabs or windows.
  • Metric reporting is built into the tool, and support for custom reports complies with organization process guidelines.
  • Delivered through a web only user interface, DOORS Next Generation delivers all capabilities deployable in a cost-effective way.

Updated rich text edit control:

Rational DOORS Next Generation makes use of a third-party control that supports the edit of rich text. This affects the quality of service for pasting rich text from applications such as Microsoft Word and offers an enhanced user experience for manipulating inline tables.

Integrations and extensions with OSLC and JavaScript

JavaScript extensions:

Rational DOORS Next Generation 4.0.6 introduced the use of JavaScript to enable extensions to the product. This release adds function for interacting with requirements data to offer stronger utilities:

  • Creation, deletion, and move of requirements within a module
  • Requirement (artifact) type manipulation
  • Access to user details to enable script extensions to self- moderate themselves
  • An example script that demonstrates how to use the new facilities to convert a flat module into a module containing hierarchy; using JavaScript to help manipulate imported data from CSV files

OSLC and web services:

The OSLC API is extended to enable the creation of RM-specific link types through API calls.

Nonfunctional requirements

The following platforms are now supported by Rational DOORS Next Generation:

  • Microsoft SQL Server 2012
  • Windows 8.1
  • Internet Explorer 11
  • Google Chrome 30
  1. Windows XP and Microsoft Windows Vista are no longer supported platforms
  2. Internet Explorer 8 is no longer a supported platform

The Rational solution for systems and software engineering

The IBM Rational solution for systems and software engineering (SSE) helps teams to specify, design, implement, and validate complex products and systems. In addition to DOORS and DOORS Next Generation, SSE offers an integrated set of capabilities to enable your teams to deliver competitive, high-quality products predictably while meeting regulatory and compliance requirements.

  • Accelerate your systems and software development and delivery processes.
  • Design systems of systems that are safe, secure, and able to respond to changing requirements and operational situations.
  • Offer lifecycle traceability within the development process and across engineering domains.
  • Improve product quality and demonstrate compliance to regulations.

For more information, see

http://jazz.net/products/systems-engineering-and-embe dded-software/

Rational DOORS Next Generation is part of a broader IBM Rational solution called the Collaborative Lifecycle Management solution. It advances the way teams work together to develop products and solutions. For more information on the Collaborative Lifecycle Management vision, architecture, products, and community, see

http://jazz.net

Support in Version 5.0

  • Windows 8.1
  • Internet Explorer 11 (in addition to IE 9 and IE 10)
  • DB2 10.5: DB2 Workground Server Edition is now bundled with Collaboration Lifecycle Management, Team Concert, Quality Manager, and DOORS NG
  • WebSphere Application Server 8.5.5 is now bundled with Collaboration Lifecycle Management, Team Concert, Quality Manager, and DOORS NG
  • SQL Server 2012
  • z/OS 2.1
  • DB2 V11, for z/OS 2.1 (Client only)
  • MAC OSX and Safari latest versions

Some notable changes include the removal of support for:

  • Windows XP
  • IE8
  • DB2 9.7
  • WAS 7.0
  • RedHat 5
  • Oracle 10
  • SUSE 10
  • Windows Server 2008 (Note: 2008 R2 support is retained.)
  • Visual Studio 2005 and 2008

Bundling IBM DB2 Enterprise Server Edition 10.1 significantly offers increased data protection, scalability, and performance for all its database-intensive operations which, based on DB2 technology, is designed to manage data more effectively and efficiently. Greater availability is delivered through enhancements such as online, automated database reorganization. In addition, the increased scalability and the ability to leverage the latest in server technology helps deliver increased performance of backup and recovery processes.

Translation information for IBM software can be found online at

http://publib.boulder.ibm.com/infocenter/prodguid/v1r 0/clarity/index.jsp

Rational Requirements Composer 4.0.6

Productivity improvements for the end user

Module usability improvements for artifact creation:

Preferred types in a module and in-line type selection. When you create an artifact type that is based on the Module format, you can specify the types of artifacts to use in that module in the Preferred Module Content field. Then, when other team members add artifacts to modules, the preferred artifact types are presented by default.

Improved module responsiveness: initial display, and better artifact creation. The initial load time of a module is improved. Most module load times are now reduced to within a few seconds. This improvement affects modules of all sizes on repositories that contain a large number of artifacts.

Client-side API scripting with JavaScript

Rational Requirements Composer 4.0.6 introduces client-side customization using JavaScript. JavaScript was selected as the client customization language as it is both a commercial-off-the-shelf language because it is easy to recruit experience or learn. It provides a high volume of Internet based help, including samples.

Rational Requirements Composer 4.0.6 non-functional improvements

Requirements Composer 4.0.6 provides updates for Java 6 SR15.

Translation information for IBM software can be found online

http://publib.boulder.ibm.com/infocenter/prodguid/v1r 0/clarity/index.jsp

Rational Requirements Composer 4.0.5

Productivity improvements for the end user

Flawless accelerator key support: When using a tool for an extended period of time, keyboard accelerator keys increase user productivity. This release reviews and extends all accelerator keys to streamline the productivity of the analyst.

Drag and drop: It is now possible to use drag and drop operations for many different activities including:

  • Move information around in a module
  • Link between different requirements within a module
  • Display two modules side by side in different windows and drag and drop linking between them. Essential for high volume link creation
  • Copy and link operations to aid the analyst drawing high-level requirements into lower level specifications to decompose into further detail

Fast loading and scrolling of large modules reduce the wait time to see further pages of information while scrolling within modules.

Expose module views to the Rational Quality Manager integration: Allowing an Rational Quality Manager tester to test against subsets of requirements within a module.

Includes printing improvements that allow an organization to use custom templates for both Document Generation and now quick printing from within a module.

Technology preview for client scripting with JavaScript

Rational Requirements Composer 4.0.5 gives an exciting insight of how client customization will look using JavaScript. JavaScript was selected as the client customization language as it is both a commercial, off the shelf language (easy to recruit experience or learn). It provides a high volume of Internet-based help that includes samples and the leading web browsers all come with built in development environments.

This latest release offers a technology preview for scripting so that organizations can plan for their needs and provide feedback.

Support for a technology preview is not offered through the normal email support services. Instead support will only be provided through the jazz.net forum.

Further information can be found on Jazz.net

http://jazz.net/wiki/bin/view/Main/RMExtensions_4_0_5

Platform Support for Rational Requirements Composer 4.0.5:

Rational solution for Collaborative Lifecycle Management 4.0.5 including Rational Requirements Composer 4.0.5 provides support for:

  • Internet Explorer 10
  • FireFox 24ESR
  • Windows Server 2012
  • Traditional WebSphere Application Server 8.5.5

Rational Requirements Composer 4.0.4

Rational Requirements Composer 4.0.4 focuses on better usability with improved artifact locking for project teams that work together on the same set or requirements, on individual module usage with better performance for artifact creation, on Rational Publishing Engine (RPE) improvements resolving some known report issues, and on the overall performance for enterprise deployments.

Bundling DB2 Enterprise Server Edition 10.1 significantly offers increased data protection, scalability, and performance for all its database-intensive operations which, based on IBM DB2 technology, is designed to manage data more effectively and efficiently. Greater availability is delivered through enhancements such as online, automated database reorganization. In addition, the increased scalability and the ability to deliver the latest in server technology helps deliver increased performance of backup and recovery processes.

Rational Requirements Composer 4.0.3

Rational Requirements Composer 4.0.3 focuses on better usability with improved artifact locking for project teams that work together on the same set or requirements, on individual module usage with better performance for artifact creation, on Rational Publishing Engine (RPE) improvements resolving some known report issues, and on the overall performance for enterprise deployments.

Bundling DB2 Enterprise Server Edition 10.1 significantly offers increased data protection, scalability, and performance for all its database-intensive operations which, based on IBM DB2 technology, is designed to manage data more effectively and efficiently. Greater availability is delivered through enhancements such as online, automated database reorganization. In addition, the increased scalability and the ability to deliver the latest in server technology helps deliver increased performance of backup and recovery processes.

In many organizations, teams struggle to develop good sets of requirements for projects to deliver, then struggle further to manage those requirements through the project lifecycle and through the inevitable requirements changes.

Whole team - whole requirements lifecycle

Requirements have their own information lifecycle. They often start as informal notes from meetings, a document from your customer, or a set of regulations or policies from a third party. From this information a group of people, typically led by an analyst, develop an increasing understanding of and consensus about what a project or program needs to deliver to meet particular business objectives.

To varying degrees, the team expresses ideas in text, pictures on white boards, discussions in conference calls, presentations, process diagrams, mind maps, and a host of other notations. These notations clarify thinking, share understanding, and build consensus and commitment. Eventually actionable requirements are distilled from this information and used to guide the activities of design, development, and test activities.

Rational Requirements Composer exists to help teams accelerate this process and get better outcomes from it. Traditional requirements management tools tend to be used mainly by business, systems, or requirements analysts to develop formal requirements, decompose them into detailed requirements, capture them in requirement specifications, analyze these requirements, and manage changes to them.

There is significant value in doing this, especially in complex projects, (mediated by contractual or compliance obligations), and those in which the cost of failing to meet requirements is high (for example, where systems are safety-critical). Many software development projects could benefit from more tool support for the full requirements information lifecycle and more iterative approaches that can provide better value with less overhead.

Next-generation requirements solution

Requirements Composer is a next-generation, requirements solution designed to help whole teams through the whole requirements lifecycle, especially teams following iterative and agile methodologies:

  • Provides a wiki-like environment for expressing requirements and requirements context in many notations (textual and visual).
  • Helps teams through the transition of requirements from document- based information to database-oriented records with individual attributes and states.

Once requirements are in database record form, a team can express various types of trace relationships among them, and manage both these relationships and changes to specific requirements themselves. In this form, the requirements are most useful to delivery teams (design, development, test, and so on) through traceability of their work back to the requirements. This traceability lets teams answer important questions about the quality and completeness of requirements and the true earned value of the project to date. As an example, the degree to which the team's deliverables have met the requirements. Requirements, after all, are the backbone of the project, and their fulfillment is the purpose of the project in the first place.

Rational Requirements Composer is the "next-generation RequisitePro." Teams using Rational RequisitePro have the opportunity to migrate to Rational Requirements Composer to implement Collaborative Lifecycle Management.

Process + tool automation = value

It is important to note that a requirements tool becomes valuable when it automates and supports a set of requirements practices for an extended project team (extended to include customers and numerous stakeholders). Team members use the tool and become advocates for it when it adds value for them personally (for example, when there is personal as well as organizational return on investment).

There is no one perfect requirements methodology for everyone. Teams face differing constraints and opportunities to optimize. For example, the requirements process for a small team updating an existing web application can be a lot simpler than the one for a project involving hundreds of people delivering a major new IT application.

In general, teams do best when they define a process that provides "just enough" requirements management. This is a lean approach, to only do the things that provide significant value or address significant constraints, and minimize the activities that do not add value.

Requirements Composer does not force a team into a particular project methodology or way of expressing requirements. It is for teams who aspire to improve the effectiveness of their requirement management processes and recognize that this will be a journey of many small (and some big) changes to the way that they do things.

Requirements Composer can help teams to:

  • Improve the quality and customer satisfaction of delivered solutions. Better requirements and traceability across requirements, development, and test activities can lead to projects that are more likely to meet customer needs and have fewer latent defects.
  • Lower project costs and get to market faster. There is less rework when fewer requirements are discovered late in the cycle, change is managed more effectively, and teams do less rework.
  • Reuse requirements artifacts across an enterprise or program.
  • Make more professional the outsourcing contractual relationship. With the information needed to assess project status and completeness of deliverables, enable both customer and outsourcing partner to focus on defining, delivering, and managing against the business value of the projects under development.

Requirements Composer supports and automates many of the activities related to requirements management:

  • Engagement of customers and stakeholders in the requirements process
  • Requirements elicitation and validation
  • Requirements specification development
  • Requirements analysis, prioritization, and estimation
  • Scope management
  • Change management
  • Contract management
  • Reporting

Rational Requirements Composer 4.0 includes bundled IBM DB2 9.7 (for details, see the Hardware requirements and Software requirements sections), which offers increased data protection, scalability, and performance. Greater availability is delivered through enhancements such as online, automated database reorganization. In addition, the increased scalability and the ability to utilize the latest in server technology, helps deliver increased performance of backup and recovery.

Multicultural support and translation information for IBM software can be found online at

http://www.ibm.com/software/globalization/scorecard/i ndex.html

IBM Rational Requirements Composer 4.0.1 supports the following improved capabilities to support the business analyst in the development process:

  • Modules: Now the business analyst can organize and group requirement artifacts together in a consistent and chronological structure typically seen in many common requirements specifications. This now allows teams using document-driven templates an easier way to know where their requirements are in their repository and a consistent way for working in distributed teams. Team members who have been used to working in documents or spreadsheets will find modules an easier way to begin working in a requirements management environment.
  • Enhanced Requirements Interchange Format (ReqIF) support for Rational Requirements Composer 4.0 (June 2012) began to support some of the ReqIF scenarios for data exchange from one project repository to another. Requirements Composer 4.0.1 now expands on the ReqIF capability to let project teams take project requirements from one repository to another, allow editing and modification, and then return it (round trip) back to the original database to merge the new updates. This also allows analysts the ability to take data offline to another computer and sync it back to the team's project repository when their offline work is complete.
  • Traceability view improvements: Rational Requirements Composer has supported real-time traceability views since Rational Requirements Composer 3.0.1, but each release continues to focus on additional and improved ways for utilizing traceability information. In this Rational Requirements Composer release, attribute-level details can be displayed in a single view showing the analyst what is happening to data on the other end of links. Traceability views can be sorted, filtered, and saved to represent the data in crucial displays for business and process decisions.
  • Artifact Locking: Project team members working in the same repository will now have the ability to lock requirement artifacts while editing to prevent others from making changes to their information during the definition, capture, or review and editing phases. Lock icons will indicate to other team members what information is currently being used and let team members better collaborate on cross-project information.
  • Collection Comparison: Team members will discover the deltas from milestone to milestone through the collection comparison to see difference markup from change to change. Each collection can once again be applied to a comparison against another version of the collection or the current version to help team members know what has changed from milestone to milestone.
  • HP Quality Center (HPQC) Integration: An OSLC-based integration to allow testers and analysts to connect HPQC tests and test plans to project requirements being managed by the business team in Rational Requirements Composer. The integration gives a similar experience to other OSLC integrations, letting team members work in their respective project locations.
  • Design Management (DM) integration: Use the Design Management capabilities to architect, design, and develop software and systems in an iterative and collaborative way together with Rational Requirements Composer. Share designs, stay current with others, and understand downstream impacts of design changes connected to project requirements. Two options are available: Rational Software Architect Design Manager for most software designer or Rational Rhapsody Design Manager for systems and embedded software engineers.
  • A 20-25% improvement in performance give the user a better working experience.


Back to topBack to top

Operating environment

Top rule

Hardware requirements

Disk space:

  • Client machines: 1 GB
  • Server machines: 5 GB minimum, 10 GB or greater, recommended, depending on the size of database

Display:

  • Client machines: 1024 x 768 resolution, or greater
  • Server machines: 1024 x 768 resolution, or greater

Memory:

  • Client machines: 1 GB; 2 GB recommended
  • Server machines: 4 GB, or greater

Network bandwidth use:

  • Client machines: 100 Mbps
  • Server machines: 100 Mbps

Processor:

  • Client machines: Intel Pentium 4, Intel Dual Core Hyperthreading Processor (recommended)
  • Server machines: Pentium Xeon 32-bit or 64-bit (recommended), dual-core or quad-core

Software requirements

Application servers:

  • Apache Tomcat 7.0.32 and future fix packs
  • WebSphere Application Server OEM Edition for z/OS, 7.0 fix pack 23and future fix packs
  • WebSphere Application Server for z/OS, 7.0 and future fix packs
  • WebSphere eXtreme Scale 7.1.1.1 and future fix packs
  • WebSphere Application Server - Base 7.0.0.23 and future fix packs
  • WebSphere Application Server - Express 7.0.0.23 and future fix packs
  • WebSphere Application Server Network Deployment 7.0.0.23 and future fix packs
  • WebSphere Application Server for z/OS, 7.0.0.23 and future fix packs
  • WebSphere Application Server - Base 8.0.0.3 and future fix packs
  • WebSphere Application Server - Express 8.0.0.3 and future fix packs
  • WebSphere Application Server Network Deployment 8.0.0.3 and future fix packs
  • WebSphere Application Server for z/OS, 8.0.0.3 and future fix packs
  • WebSphere Application Server - Base 8.5 and future fix packs
  • WebSphere Application Server Network Deployment 8.5 and future fix packs
  • WebSphere Application Server for z/OS, 8.5 and future fix packs

Databases:

  • IBM Derby SDK 10.8.1.2 and future fix packs
  • DB2 Enterprise Server Edition 9.7 and future fix packs
  • DB2 Workgroup Server Edition 9.7 and future fix packs
  • DB2 Express Edition 9.7 and future fix packs
  • DB2 Enterprise Server Edition 10.1 and future fix packs
  • DB2 Workgroup Server Edition 10.1 and future fix packs
  • DB2 Express Edition 10.1 and future fix packs
  • DB2 for i 7.1 and future fix packs
  • DB2 for i 6.1 and future fix packs
  • DB2 9 for z/OS, 9.1 and future fix packs
  • DB2 10 for z/OS, 10.1 and future fix packs
  • Microsoft SQL Server Enterprise Edition 2008 SP1 and future fix packs
  • Microsoft SQL Server Standard Edition 2008 SP1 and future fix packs
  • Microsoft SQL Server Enterprise Edition 2008 R2 and future fix packs
  • Microsoft SQL Server Standard Edition 2008 R2 and future fix packs
  • Oracle Database 10g Enterprise Edition Release 2 10.2.0.1 and future fix packs
  • Oracle Database 10g Standard Edition Release 2 10.2.0.1 and future fix packs
  • Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs
  • Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs
  • Oracle Database 10g Enterprise Edition Release 2 10.2.0.1 and future fix packs
  • Oracle Database 10g Standard Edition Release 2 10.2.0.1 and future fix packs
  • Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs
  • Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs
  • Oracle Real Application Clustering (Oracle 11g Release 2)

Eclipse:

  • IBM Eclipse SDK 3.6.2 and future fix packs
  • IBM Eclipse SDK 4.2.2 and future fix packs (RTC Client Only)

Web servers:

  • Apache Server 2.2.19 and future fix packs
  • IBM HTTP Server 7.0 Fix Pack 23and future fix packs
  • IBM HTTP Server 8.0 and future fix packs
  • WebSphere Application Server Network Deployment 8.5
  • WebSphere Application Server Network Deployment 8.0.0.3
  • WebSphere Application Server Network Deployment 7.0 fix pack 23
  • Squid 3.0 for caching

Identity management:

  • Apache Directory Server 1.5.5 and future fix packs
  • IBM RACF for z/OS V1R11 and future fix packs
  • IBM Tivoli Directory Server 6.3 and future fix packs
  • Microsoft Active Directory 2008
  • Microsoft Active Directory 2008 R2

Installer -- Capilano Components (IBM Installation Manager and IBM Packaging Utility) 1.6.3 and future fix packs

Java SDK:

  • IBM Java SDK 6.0.1.1 (J9 2.6) and future fix packs (for z/OS)
  • IBM Java SDK 6.0.13 and future fix packs
  • Sun Java SDK/JRE/JDK 6.0 Update 23 and future fix packs
  • IBM Java SDK/JRE 7.0 and future fix packs (client only)
  • Oracle Java SDK/JRE/JDK 7.0 and future fix packs (client only)

License Use Management -- Rational License Key Server 8.1.3.3 and future fix packs:

Runtime environment:

  • Microsoft Visual Studio 2005 SP1 and future fix packs
  • Microsoft Visual Studio 2008 SP1 and future fix packs
  • Microsoft Visual Studio 2010 and future fix packs
  • Microsoft Visual Studio 2012 and future fix packs
  • Rational Developer for Power Systems Software 8.0.3.2 and future fix packs

Web browsers:

  • Apple Safari 5.1 and future fix packs
  • Google Chrome 21 and future releases, mods and their fix packs
  • Microsoft Internet Explorer 8.0 and future fix packs
  • Microsoft Internet Explorer 9.0 and future fix packs
  • Mozilla Firefox ESR 17

Operating systems:

AIX:

  • AIX 7.1 Power System - Big Endian
  • AIX 6.1 Power System - Big Endian

IBM i:

  • IBM i 7.1 Power System - Big Endian
  • IBM i 6.1 Power System - Big Endian

Linux:

  • Red Hat Enterprise Linux (RHEL) Server 6 x86-64
  • Red Hat Enterprise Linux (RHEL) Workstation 6 x86-32
  • Red Hat Enterprise Linux (RHEL) Client 6 x86-32
  • Red Hat Enterprise Linux (RHEL) Client 6 x86-64
  • SUSE Linux Enterprise Server (SLES) 11 x86-64
  • Ubuntu 12.04 LTS x86-64
  • SUSE Linux Enterprise Desktop (SLED) 11.0 x86-32
  • SUSE Linux Enterprise Server (SLES) 11 System z
  • SUSE Linux Enterprise Server (SLES) 11 Power System - Big Endian
  • Red Hat Enterprise Linux (RHEL) Workstation 6 x86-64
  • Red Hat Enterprise Linux (RHEL) Server 6 Power System - Big Endian
  • Red Hat Enterprise Linux (RHEL) Server 6 System z
  • SUSE Linux Enterprise Desktop (SLED) 11.0 x86-64

Mac OS:

  • Mac OS X Snow Leopard 10.6 x86-64
  • OS X Lion 10.7 x86-64
  • Mac OS X Snow Leopard 10.6 x86-32

Solaris:

  • Solaris 11 SPARC
  • Solaris 10 SPARC

Windows:

  • Windows Server 2012 Standard Edition x86-64
  • Windows 7 Ultimate x86-32
  • Windows 8.1 Professional x86-64
  • Windows 8.1 Standard x86-64
  • Windows Server 2012 Datacenter Edition x86-64
  • Windows 8.1 Enterprise x86-64
  • Windows 7 Professional x86-32
  • Windows Server 2008 R2 Enterprise Edition x86-64
  • Windows 7 Professional x86-64
  • Windows 7 Enterprise x86-32
  • Windows 7 Enterprise x86-64
  • Windows Server 2008 R2 Standard Edition x86-64
  • Windows 7 Ultimate x86-64

z/OS:

  • z/OS 1.12 System z
  • z/OS 2.1 System z
  • z/OS 1.13 System z

For additional system requirements details, see

http://jazz.net/wiki/bin/view/Deployment/CLMSystemReq uirements405406


Back to topBack to top

Planning information

Top rule

Customer responsibilities

Not applicable



Back to topBack to top

Publications

Top rule

No publications are shipped with this product.

The IBM Publications Center portal is located at

http://www.ibm.com/shop/publications/order

The Publications Center is a worldwide central repository for IBM product publications and marketing material with a catalog of 70,000 items. Extensive search facilities are provided. Payment options for orders are via credit card (in the US) or customer number for 20 countries. A large number of publications are available online in various file formats, and they can all be downloaded by all countries.



Back to topBack to top

Trademarks

Top rule

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.

Windows is a trademark of Microsoft Corporation.

Terms of use

IBM products and services which are announced and available in your country can be ordered under the applicable standard agreements, terms, conditions, and prices in effect at the time. IBM reserves the right to modify or withdraw this Sales Manual at any time without notice. This Sales Manual is provided for your information only. Additional terms of use are located at

Terms of use


© IBM Corporation 2021.