Jazz Platform (92)
Children categories
Learn about basic concepts and multiple ways to create links between the artifacts.
In this article, you will learn about agile enterprise requirements management and how it can help you lower development costs, improve quality control, minimize risk and avoid project delays.
This Article provides an overview of basic terms and definitions related to artifacts, modules, and collections. It highlights the relationships and differences between base and model artifacts and emphasizes the importance of understanding these concepts when working with artifacts in a project.
Introduction At Softacus, we constantly strive to improve products and services. A very important part of the services offered for your infrastructure is monitoring. In addition to monitoring the basic system parameters of servers/VMs/ESXi, we offer the possibility of monitoring the IBM Jazz platform and its individual applications. This page aims to provide you with information about monitoring options for your IBM ELM applications and infrastructure. By being our customer, you have a unique opportunity to start monitoring your infrastructure at a high level. We can monitor the infrastructure that we manage - Softacus (local), or we can even set up the monitoring in the infrastructure that is deployed in your internal environments.
DOORS Next provides great functionalities for managing requirements within your team, but as your project grows sooner or later you need to export and import the data using external formats. For DOORS Next data the first format to think of is project template (or component template, in case if configuration management feature is enabled in RM). Content of template can be set up to include different types of data but all items of included types will be included to a template (e.g. you can include artifacts to a template - and it means that all folders will be added to a template). Another option is the ReqIF package - it allows interchange requirements between requirements management platforms which are compatible with ReqIF, with more data selection options (e.g. you can include only certain artifacts or modules). CSV/spreadsheet format is also an option to export and import data to DOORS Next,…
Introduction The history is an important part of the requirements management tool and the purpose of this article is to explain functions and capabilities of DOORS Next for working with history of requirements. Artifact revisions On the very basic level history of requirements management items in DOORS Next is organized on artifacts level and is presented as revisions and audit history. This information is accessible for artifacts via ‘Open history’ action in the menu (Figure 1). Figure 1 The first tab you see when you open history is ‘Revisions’, it is splitted on ‘Today’, ‘Yesterday’, ‘Past week’, ‘Past month’ and ‘Earlier’ sections which include different versions of an artifact and baselines of project area or component. When you switch to the ‘Audit history’ tab you see only versions of a current artifact with explanation of actions performed on it and changes which were created with information on date…
