Displaying items by tag: requirements management
Join us for our upcoming webinar, featuring Adrian Pitonak and Jan Jancar from Softacus, as they delve into the topic of "IBM DNG Export/Import.
Event Details:
Date: 25th of March 2024
Time: 3:30 pm CET
Location: Zoom
Link for registration: https://zoom.us/j/93121909731?pwd=dXRWb3gxUXhMUFFJdnpLYlNHSTFLdz09
Agenda Highlights:
The primary objective of the presentation is to highlight the diverse array of methods and techniques utilized with our clientele concerning Excel export and import processes.
- How to create an excel export - different ways and options
- Excel RoundTrip - how to do it
- Excel exchange with suppliers and customers
- Export of data from Publishing Engine to Excel
- Export to Excel via JRS
- Tips and tricks for Excel exporting
This event is tailored for professionals and users of Doors Classic and DOORS Next Generation (DNG), whether you hold the title of or have a keen interest in Excel export and import processes.
Die MedConf 2024 findet vom 16. April bis 18. April 2024 in München Unterhaching als Präsenzveranstaltung statt. Die Konferenz mit begleitender Ausstellung ist die etablierteste und wichtigste Networking Plattform der Medizintechnik.
Die MedConf adressiert Mitarbeiter und Führungskräfte von Medizintechnik Unternehmen, die insbesondere aus den Bereichen Research & Development, Qualitätsmanagement, Produktentwicklung, Regulatory Affairs usw. kommen. Jährlich besuchen rund 250 Teilnehmer die Konferenz. Mehr Information zu der Veranstaltung finden Sie auf https://www.medconf.de/
Unser Solution Director, Jan Jancar, wird am drittem Tag der Konferenz, 18. April, um 13:30 Uhr CET eine Präsentation zum Thema „Traceability zwischen Requirements und Normen in Configuration Management-Umgebung“ halten.
Wir freuen uns auf unsere Teilnahme an der MedConf 2024 und auf die Gelegenheit, spannende Kontakte aus der Medizintechnik-Industrie zu knüpfen.
We are excited to invite you to our upcoming webinar on the topic of "Commenting Options in IBM DOORS NG."
Date: January 29, 2024
Time: 3:30 - 4:30 pm CEST
Sing up now under this link
During the webinar, we will explore essential aspects of commenting in IBM DOORS NG, including:
- Effectively using comments
- Reviewing comments
- Collaborating with internal and external stakeholders
- Techniques for exchanging comments with end customers who do not have direct access
Our Solution Director, Jan Jancar, will introduce valuable techniques, such as:
- Reviewing comments efficiently
- Commenting on base and module artifacts
- Finding comments using both out-of-the-box and attribute-based techniques
This webinar is designed to enhance your understanding of the commenting functionalities within IBM DOORS NG, providing valuable insights that can optimize your workflow.
Save your spot by registering here. After registration, you will receive a confirmation email with the webinar access details.
Feel free to invite your colleagues who might find this topic relevant.
We are looking forward to seeing you at the event!
We're thrilled to announce our upcoming webinar Requirements Reuse in DOORS Next Generation / ELM.
Softacus has been selected as one of the Top 10 IBM Solution providers for 2022 by the CIOApplications Europe - a popular European magazine on innovations and technology.
In this article, featured in the magazine in December 2022, our Solution Director, Jan Jancar, talks about the challenges engineering teams are facing nowadays and how Softacus and the IBM Engineering Lifecycle Management solution help organizations improve collaboration among software and system developers, increasing efficiency and product quality.
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 history maintenance.
The Challenges to Managing History in DOORS Next Generation
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. 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 ‘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 and time and author of it. Revisions can be restored to the current state (except revisions which were created with linking operations).
Another source of history of an artifact are system attributes which preserve information on date and time of creation and modification of an artifact and a user who created and modified an artifact. These attributes are updated by the application on creation of an artifact (Created On for date and time of creation and Created By for username) and Modified On and Modified by for the latest modification. Additionally, if you use ReqIF import to add artifacts, attributes with prefix ‘Foreign’ will show you related information from the source.
Of course, a revision list and attributes of a single artifact is not enough to manage requirements history, so versions of artifacts are aggregated to baselines. The first kind of baselines is a DOORS Next baseline, in other words it can be explained as a snapshot which includes certain revisions of artifacts. Baselines are created to preserve some agreed state of requirements.
When we are talking about artifacts revisions It is meaningful to mention that module artifacts revisions are specific - they are created when module structure is changed (set and / or order of included artifacts) or attributes of module itself. So when you edit an artifact in module context without changing position of this artifact in module - you do not create new revision of module automatically. To capture the state of a module you need to create a DOORS Next baseline.
DOORS Next with configuration management capabilities has more options to manage history of requirements. First of all - streams, which allow you to have parallel timelines for different variants of requirements. All requirements in DOORS Next have their initial stream, which is the default timeline for requirements changes. DOORS Next has an option to create a parallel timeline using additional streams, which is mostly used to manage variants of requirements.In this case usually some existing version of requirements is used as an initial state for a new stream. And changes of artifacts in a new stream will not affect the initial stream - revisions of artifacts created in a new stream are visible only in this stream unless the user initiates synchronization. During synchronization the user has options with merging approaches, and one of them is using changesets, which is explained below.
Changesets are another kind of data set in DOORS Next which can be observed in the audit history. There are two types of changesets - user created changeset (name of changeset in this case is specified by user) and internal changeset, which is a reference for changes in the audit history. Internal changesets can be found in the audit history and can be also used as an option to deliver changes across streams. Created by user changesets aggregate small changesets automatically created by DOORS Next, which can be found in audit history and in the merging menu when you deliver changes from one stream to another. Both types of changesets can be found on stream’s page, and if a stream is allowed to be edited only via changesets - it means, users are forced to create a changeset to edit requirements in a stream - a list of changesets of a stream gives you a good representation of history for a stream.
Another functionality to manage history is Global Configuration baseline. When you enable DOORS Next project area for configuration management, links between requirements in different components are created via Global Configuration stream - you need to switch to Global Configuration context to create a link across DOORS Next components and also to see such links. As each component is baselined independently in DOORS Next, in order to preserve cross-component linkage state you need to create a Global Configuration baseline. When you perform this action, baselines are created on each component level automatically and included to a Global Configuration baseline. Switching to this baseline in the future will show you the exact state of linking at the moment of global baseline creation - proper links between proper revisions of artifacts.
Specialized solutions, Approaches, Tips
- As mentioned above, baselines are created on component level (or project area level if project area is not enabled for configuration management). When number of baselines grows, some maintenance of baselines is required - to shorten the list of baselines, some of them need to be archived
- To help users with navigation in list of baselines we provide special widget, which filters from the flat baseline list those baselines which were created in a certain module context
Over the last few months, we’ve seen the role of AI grow from an important technology tool to truly a force for good. From automating answers to symptom and other citizens questions to finding insights in public data, AI has helped people deal with an unprecedented challenge at a scale never before seen.
But as organizations and individuals emerge from this pandemic, we see the role of AI continuing to be critical – not only to respond to what’s happening today, but to plan for an uncertain future.
Join our panel of AI experts and business leaders as they share key learnings from the past few months and what organizations can do to prepare for and manage future changes with AI.
More information here
This is session 7 of 7 that covers the IBM ELM tool suite.
IBM Engineering Lifecycle Management (ELM) is the leading platform for today’s complex product and software development. ELM extends the functionality of standard ALM tools, providing an integrated, end-to-end solution that offers full transparency and traceability across all engineering data. From requirements through testing and deployment, ELM optimizes collaboration and communication across all stakeholders, improving decision- making, productivity and overall product quality.
Presented by: Jim Herron of Island Training.
Webinar - IBM ELM SERIES #1: Managing Requirements with IBM® Engineering Requirements Management DOO
This is session 1 of 7 that covers the IBM ELM tool suite.
IBM Engineering Lifecycle Management (ELM) is the leading platform for today’s complex product and software development. ELM extends the functionality of standard ALM tools, providing an integrated, end-to-end solution that offers full transparency and traceability across all engineering data. From requirements through testing and deployment, ELM optimizes collaboration and communication across all stakeholders, improving decision- making, productivity and overall product quality.
Presented by: Jim Herron of Island Training
You’re invited to join IBM thought leaders and experts to learn how today’s most innovative companies are adopting holistic development processes to stay competitive, become more agile, improve productivity and quality, and increase development efficiency.
Date: Thursday, May 5 th at 3pm CET
Agenda:
- Drive engineering excellence for sustainable public infrastructure
- Streamline engineering complexity in regulated industries
- Remove data silos across the engineering lifecycle using digital threads
