IBM Rational DOORS Next Generation Preview
Summary
TLDRDiese Vorschau präsentiert IBM Rational DOORS Next Generation (DNG) und DOORS Next Generation on Cloud (DNGC), die für die Anforderungsverwaltung entwickelt wurden. Es wird erläutert, wie DNG bei der Verringerung von Risiken, Steigerung der Projektpräzision, Zufriedenstellung von Kunden und Sicherstellung der Systemsicherheit hilft. Die Vorteile von DNGC im Zusammenhang mit der Zusammenarbeit von Stakeholdern, der Verwaltung von Anforderungen in Hierarchien, der Verfolgbarkeit und dem Umgang mit Änderungen werden dargelegt. Es wird auch auf die Verwendung von Dashboards, Filtern, Verknüpfungen und Historien für die effektive Projektverwaltung eingegangen.
Takeaways
- 😀 IBM Rational DOORS Next Generation (DNG) ist ein Werkzeug für Anforderungsmanagement, das darauf abzielt, Risiken zu reduzieren und die Vorhersagbarkeit von Projekten zu verbessern.
- 🔍 Eine gute Anforderungsmanagementpraxis ist entscheidend, um Kundenzufriedenheit zu gewährleisten und sicherzustellen, dass entwickelte Systeme sicher sind.
- 🚫 Probleme wie unzureichende, widersprüchliche oder falsche Anforderungen sowie Gold-Plating (überflüssige Funktionen) können das Projekt beeinträchtigen.
- 🔗 DNG unterstützt die Zusammenarbeit zwischen Stakeholdern durch webbasierte Clients, die leicht zu bedienen sind und einen geringen Lernaufwand erfordern.
- 📊 Dashboards im Jazz-Plattform bieten sofortigen Zugriff auf relevante Projektdaten und sind für verschiedene Rollen anpassbar.
- 📁 Die Hierarchie und Struktur in DNG ermöglichen die Verwaltung von komplexen Datenmengen und den Separationsaspekt zwischen verschiedenen Interessensgruppen.
- 🔍 DNG ermöglicht die Filterung und Anzeige von Anforderungen in Modulen, die als Dokumente organisiert sind und als atomare Elemente fungieren können.
- 🔗 Traceability ist ein Schwerpunkt in DNG, wobei Anforderungen auf verschiedene Arten von Artefakten, wie Arbeitsgegenständen oder Designelementen, zurückverfolgt werden können.
- 🔎 Der Link Explorer in DNG visualisiert und erlaubt die Navigation durch die Verbindungen zwischen Anforderungen und anderen Artefakten.
- 📈 DNG bietet Tools für die Auswirkungsanalyse von Änderungen in Anforderungen, was bei der Verwaltung von Komplexität und Schätzung von Änderungskosten hilfreich ist.
- 📝 Die Versionsgeschichte in DNG ermöglicht es, alle Änderungen an Anforderungen nachzuverfolgen, einschließlich der Identität des Änderers und der geänderten Textpassagen.
Q & A
Was ist IBM Rational DOORS Next Generation (DNG)?
-IBM Rational DOORS Next Generation (DNG) ist ein Werkzeug für Anforderungsmanagement, das zur Reduzierung von Risiken, Verbesserung der Projektpräzision, Zufriedenstellung der Kunden und Sicherstellung der Systemsicherheit beiträgt.
Wie kann DNG bei der Lösung von Problemen in der Anforderungsverwaltung helfen?
-DNG kann dabei helfen, indem es die Zusammenarbeit zwischen Stakeholdern ermöglicht, die Verwaltung von Anforderungen in Hierarchien organisiert, die Verfolgbarkeit von Anforderungen aufrechterhält und den Umgang mit Änderungen erleichtert.
Was sind die Hauptprobleme, die Entwicklungsorganisationen bei der Anforderungsverwaltung haben können?
-Hauptprobleme umfassen zu wenige oder keine Anforderungen, widersprüchliche oder falsche Anforderungen sowie Goldplating, bei dem zusätzliche Anforderungen oder Features hinzugefügt werden, die möglicherweise nicht den Aufwand wert sind.
Wie kann man sich bei DNG anmelden, wenn man noch keinen Jazz-Benutzernamen hat?
-Wenn man keinen Jazz-Benutzernamen hat, kann man auf der rechten Seite des Anmeldebildschirms auf die Schaltfläche 'Jetzt registrieren' klicken und die Registrierungsformulare ausfüllen, während das Video pausiert wird.
Was ist der Zweck des Projekt-Dashboards in DNG?
-Das Projekt-Dashboard bietet sofortigen Zugriff auf die für den aktuellen Betrachter relevanten Projektdaten, unabhängig davon, ob es sich um einen Test-Ingenieur, der die aktuelle Fehlerliste ansieht, oder einen Projektmanager, der den Projektstatus überwacht.
Wie wird die Komplexität in der Anforderungsverwaltung mit DNG bewältigt?
-Durch die Verwendung von Hierarchien und Strukturen kann DNG große Datenmengen bewältigen und den Interessengruppen verschiedener Stakeholder gerecht werden.
Was ist ein Modul in DNG und wie unterscheidet es sich von einem Word-Dokument?
-Ein Modul in DNG ist eine Art von Dokument, das die Struktur der Anforderungen bietet. Jede Anforderung im Modul ist ein atomarer Element, das in diesem Modul verwendet wird und nicht wie ein Word-Dokument bearbeitet wird.
Wie kann man die Verfolgbarkeit von Anforderungen in DNG visualisieren und durchsuchen?
-Die Verfolgbarkeit von Anforderungen kann durch die Verwendung von Views, wie z.B. dem 'Downstream Traceability View' und dem 'Link Explorer', visualisiert und durchsucht werden, wodurch eine vollständige Verfolgbarkeitskette durch die verschiedenen Ebenen der verbundenen Anforderungen angezeigt wird.
Was zeigt der 'Link Explorer' in DNG?
-Der 'Link Explorer' zeigt alle Artefakte, die mit einer bestimmten Anforderung verbunden sind, sowie den Typ der Verbindung. Dies hilft bei der Navigation durch die verbundenen Artefakte und bei der Durchführung von Auswirkungsanalysen.
Wie kann man die Änderungsgeschichte einer Anforderung in DNG einsehen?
-Die Änderungsgeschichte einer Anforderung kann durch das Öffnen des 'History'-Moduls für die Anforderung eingesehen werden, wobei jede Änderung, einschließlich des Änderers, aufgelistet wird und Änderungen im Text farbcodiert hervorgehoben werden.
Outlines
😀 Einführung in IBM Rational DOORS Next Generation
Dieser Abschnitt stellt IBM Rational DOORS Next Generation (kurz DNG) vor, ein Werkzeug für Anforderungsmanagement, das zur Reduzierung von Risiken und Verbesserung der Projektvorhersagbarkeit eingesetzt werden kann. Es wird auf die Bedeutung guter Anforderungsmanagements hingewiesen, das dazu beitragen kann, Kunden zufriedenzustellen und Systeme sicher zu gestalten. Probleme wie unzureichende oder fehlerhafte Anforderungen sowie Gold-Plating, bei dem Projekte unnötige zusätzliche Anforderungen hinzufügen, werden diskutiert. Es wird erklärt, wie DNG dabei helfen kann, und es wird ein Blick auf die Benutzeroberfläche von DNG geworfen, einschließlich des Projekt-Dashboards und der Möglichkeiten zur Zusammenarbeit zwischen Stakeholdern.
🔍 Erweitertes Anforderungsmanagement mit IBM DOORS Next Generation
In diesem Abschnitt wird auf die Funktionen von DNG eingegangen, die es ermöglichen, Anforderungen effizient zu verwalten. Es wird gezeigt, wie Anforderungen in Modulen organisiert werden, die wiederum in Dokumenten strukturiert sind. Die Atomarität von Anforderungen wird betont, was bedeutet, dass sie in verschiedenen Modulen wiederverwendet und bearbeitet werden können, ohne dass Änderungen manuell nachverfolgt werden müssen. Die Verwendung von Filtern und Ansichten wird erläutert, um Anforderungen zu durchsuchen und zu visualisieren, und es wird auf die Möglichkeit hingewiesen, Anforderungen mit anderen Artefakten wie Arbeitsgegenständen oder Designelementen zu verlinken.
🔗 Traceability und Zusammenarbeit in IBM DOORS Next Generation
Dieser Abschnitt konzentriert sich auf die Traceability-Funktionen von DNG, die es ermöglichen, die Beziehungen zwischen Anforderungen und anderen Artefakten nachzuverfolgen. Es wird gezeigt, wie man mithilfe des Link Explorers die Verbindungen zwischen Anforderungen und anderen Elementen wie Designelementen oder Testfällen visualisiert. Die Möglichkeit, die Auswirkungen von Änderungen auf Anforderungen zu analysieren und die Potenzialkosten von Änderungen zu schätzen, wird ebenfalls diskutiert. Der Abschnitt verdeutlicht die Bedeutung von Traceability für die Verwaltung von Änderungen und die Zusammenarbeit zwischen Projektbeteiligten.
📝 Historisierung und Audit Trail in IBM DOORS Next Generation
Der letzte Abschnitt betont die Funktion zur Historisierung von Anforderungen in DNG. Es wird erläutert, wie man die Änderungshistorie von Anforderungen einsehen und auditieren kann, um eine vollständige Aufzeichnung der Änderungen und der verantwortlichen Personen zu erhalten. Die Möglichkeit, Kommentare und Diskussionen in Zusammenhang mit Anforderungen zu pflegen, wird ebenfalls thematisiert, um einen Kontext für Entscheidungen zu bieten. Schließlich wird auf die Fähigkeit hingewiesen, die Verwendung von Anforderungen in verschiedenen Modulen, Sammlungen und Überprüfungen nachzuverfolgen.
Mindmap
Keywords
💡IBM Rational DOORS Next Generation
💡Anforderungsmanagement
💡Risikomanagement
💡Konflikt und Überschneidung von Anforderungen
💡Gold-Plating
💡Jazz.net
💡Dashboard
💡Hierarchie und Struktur
💡Modul
💡Zurückverfolgbarkeit
Highlights
Introduction to IBM Rational DOORS Next Generation (DNG) and its importance in requirements management.
Effective requirements management can reduce risk, improve project predictability, satisfy customers, and ensure system safety.
Challenges in development organizations include poor requirements, conflicting or incorrect requirements, and unnecessary 'gold-plating' of features.
DNG helps manage requirements by organizing them into modules, supporting collaboration among stakeholders through web clients.
Project dashboards in DNG provide instant access to relevant data for different roles, such as test engineers and project managers.
DNG supports ISO 26262 functional safety standards, offering traceability across various levels of connected requirements.
Modules in DNG allow for hierarchical organization, managing complexity and separation of concerns between stakeholders.
Filtering and viewing options in DNG enable users to customize how requirements are displayed and trace their relationships with work items.
DNG's strong typing mechanism allows for defining custom requirement types with specific attributes, improving precision in requirements management.
The Link Explorer tool in DNG provides a visual representation of traceability paths, aiding in impact analysis and navigation of connected artifacts.
DNG facilitates collaboration by maintaining conversations between team members within the context of specific requirements.
The history and audit trail features in DNG allow for tracking changes to requirements, providing a comprehensive view of modifications over time.
DNG integrates with other tools like Rational Quality Management and design management tools, enabling seamless traceability from requirements to test cases and design elements.
The Link Explorer's configurable link display in DNG helps in visualizing complex relationships between requirements, test cases, and design elements.
DNG's audit trail and history features provide transparency in decision-making, supporting compliance with standards and improving project accountability.
Transcripts
hi this is Andy and in this preview
we're going to look at IBM rational
doors next generation and IBM doors next
generation on cloud or DNG for short and
in doing so we're going to be talking
about requirements management there have
been many industry studies that
highlight the importance of good
requirements management get it right and
we can reduce risk to improve the
predictability of our projects satisfy
our customers and ensure that our
systems we're building are safe get it
wrong and well bad things happen some of
the biggest problems development
organizations face are poor requirements
they might have too few or even no
requirements they might have enough
requirements but they conflict overlap
or just plain wrong and then there is
the dreaded gold-plating where the
project adds additional requirements or
features they think the customer will
like and the effort required to meet
them simply isn't worth it let's see how
DNG can help go ahead and click the
button to open rational doors next
generation now note that it opens in a
new tab so you can switch back to this
previews tab whenever you want now you
may be asked to log into jazz.net which
is the website for products like DNG if
you don't have a jazz user ID then click
the register now button on the right and
pause this video while you fill out the
registration form if you already have a
jazz user ID then use it to log in on
the left hand side I've now logged in
and I can see the team's dashboard you
should be seeing the same thing if
you're not then it's likely that you're
a new user and the Jazz minions are
still busy setting up your new ID in
which case just try refreshing the page
until the dashboard appears in the world
of requirements management collaboration
between stakeholders is critical and
that's where IBM's jazz strategy comes
in web clients allow any stakeholder to
participate with little to no learning
curve everyone can use a web browser
journey starts here on the project
dashboard dashboards are a common
capability across the Jazz platform they
can be created for the overall project
or for teams or personal dashboards can
be created for individual users
dashboards give instant access to the
project data that's most relevant for
the current viewer whether that's a test
engineer looking at the current defect
list or a project manager looking at the
status of the project and what's more
the data presented in these dashboards
is always up to date in this sample the
widget on the left is showing a view of
the test cases in quality management
that have validated by connections to
requirements in this project the widget
in the center is showing the number of
safety goals grouped by their ACL rating
and that's their automotive safety and
integrity level part of the risk
classification scheme that's defined in
the ISO 26262 functional safety standard
lastly the widget on the right is
showing the safety goals their ACL
ratings and the requirements that
satisfy them downstream let's dive a
little deeper into the project go ahead
and click the artifacts menu there in
the title bar just underneath that bar
you should now be able to apply a filter
right now it's sent to all so let's
click on modules so that we only see
those in the sidebar on the left click
on the plus symbol next to the adaptive
cruise control requirements folder to
expand it into a tree view you can see
that the project is organized into
folders and has hierarchy one of the
basic tenets of managing complexity in
requirements management hierarchy and
structure allows us to deal with large
volumes of data and also allows us to
manage the separation of concerns
between different stakeholder
communities go ahead and click on the
item definition requirements artifacts
folder note that since we have a filter
applied the only thing we can see in
that folder is a module called item
definition requirements go
head and click that module to open it a
module is just another word for document
in fact it looks a little bit like a
Word document
it gives structure to the requirements
you can click on the little twisties to
collapse or expand headings but it isn't
a Word document each requirement in the
module is an atomic element it's just
simply being used in this module that's
another one of the basic tenets of
requirements management granularity
individual requirements can be traced to
other artifacts in the system such as
work items or design elements they can
be reused in many different modules they
can be locked for editing allowing many
team members to work on the same
document at the same time and any
changes are captured automatically by
dmg forming an audit trail we'll see all
of this and more in a few moments but
first let's see something much simpler
at the top of the module you should see
a text box with the words type to filter
by text written inside it click in that
box and type the words speed and then
hit the enter key
notice that the module is now filtered
showing you only the requirements with
that word in their text notice that in
the left-hand sidebar
there are views views are user
customizable and allow both filtering
and configuring of the display
converting the module into a kind of
spreadsheet where the attributes and
links of the requirements can be shown
in columns go ahead and click the work
item traceability view you now have the
document kind of view on the left and on
the right is an additional column
showing the work items in the Jazz work
item system that have been traced to the
requirements in this module if you hover
your mouse over one of those linked work
items you'll get a rich hover
another common capability across the
Jazz platform you can see essential
information about link
artifacts without the need to actually
navigate into the other tool it's a huge
time-saver
of course these links are also navigable
so if you did click them you would be
taken to the right artifact in the right
place in that other tool again a huge
time-saver if you click the downstream
traceability view in the sidebar then
you can see that these item definition
requirements are satisfied by
requirements in another module further
downstream
in fact this project has been created to
the ISO 26262 functional safety standard
which mandates traceability so there are
in fact modules at many different levels
and the requirements in those modules
have traceability links between them in
a few moments we'll look at another way
to visualize and explore that
traceability
but first let's follow the link go ahead
and click one of the requirements in the
satisfied by column now it doesn't
matter which one you click since they're
all pointing at the same requirement in
the next module down but that's just
because this is some simple demo data
you're now looking at the safety goals
module and the requirement you clicked
has been selected now in the list of
views on the left click the a sill view
at the top of that list the display
changes and now instead of showing the
linked artifacts we have columns that
show various attributes of the safety
goal requirements severity probability
control ability and the overall aesol
rating notice also that the top two rows
don't have any values for those
attributes DNG has a very strong typing
mechanism you can define your own
requirement types and the sets of
attributes that those types have in this
example safety goal requirements have an
ACL rating whereas headings do not and
this negates the need to have values
like not applicable in the list of views
on the left click upstream traceability
in a satisfies column click any of those
linked require
they're to return to the item definition
requirements module and let's look at
another way to explore that traceability
the link Explorer let's start with a
single requirement go ahead and type the
number 73 into the search and filter box
you used earlier and then hit the enter
key that should filter the module to
show you only requirement 73 the time
gap shall be maintained by a combination
of brake control and engine management
since the downstream traceability view
is still applied you can also see that
requirement 73 is satisfied by
requirement 147 place your mouse into
the first column so that the pencil icon
appears click that pencil icon to open
the context menu for this requirement
and way down at the bottom there you can
see an entry called open links Explorer
go ahead and click that entry now give
the tool a moment or two to populate
itself and you should see all of the
artifacts connected to requirement 73
along with the type of link now we can
expand and collapse this tree manually
but there is a faster way in the top
right hand corner of the window there
are four buttons if you hover your mouse
over those buttons a tooltip will appear
to tell you what those buttons do go
ahead and click the button furthest to
the right configure link display that
will open a pop-up menu where you can
choose the link types you want included
along with the number of levels you want
the tree to expand to click inside the
type to filter box and type s 80 then
the list will collapse and you can
select the one we want more easily
that's satisfied by go ahead and click
that satisfied by check box whilst this
dialog is open
set the number of levels to expand
option to five and then click the apply
button
now again this
we'll take a few moments as DNG sorts
through the database but once it's
finished the view will reconfigure
itself showing you a complete
traceability path down through the
various levels of connected requirements
now you can use this view for navigation
clicking one of the entries in the view
will actually open it but don't do that
just yet go ahead and click the
configure link display button again and
let's add two more link types into the
mix replace SAT with V al to locate the
validated by link and place a check in
that box that will include any test
cases in rational quality management
next replace V al with ref2 locate the
refined by architecture element link and
place a check in that box as well that
will bring in any linked model elements
from the design management tool once
you've ticked both of those options
click apply and the view should repaint
itself straight away you'll find the
link to model elements at the far left
since the model is at the systems
engineering level it's linked to the
item definition requirements if you
hover your mouse over one of those
linked diagrams and then click show more
in the rich hover pop-up you can even
view and pan around that linked diagram
without going anywhere near the modeling
tool test cases are at the far right
since they're connected to the hardware
requirements for the radar subsystem now
this view shows traceability and is a
very useful way of navigating around the
connected artifacts but it also
highlights impact analysis the ripple
effect up or downstream as the
requirements change and if there's one
thing that's certain in requirements
management it is that change is
inevitable dealing with the effects of
change can be a complex time-consuming
effort views like this help to manage
that complexity and can even allow you
to estimate the potential cost of
change before it's made okay let's take
a look at the hardware requirements
scroll over to the right and in the
next-to-last column click on requirement
one one nine the hardware shall provide
a layer to communicate with both Flex
ray and canvas systems the radar
subsystem hardware requirements module
opens up and the requirement you just
clicked is selected now note that this
module has a sketch in it this was
created directly in DNG and is a very
useful way to illustrate a concept
therefore moving to formal modeling
later in the right-hand sidebar click
the selected artifact tab there you can
see all of the attributes of the
selected requirement including the last
time it was modified and who modified it
but what were those modifications well
in a few moments we'll find out but
first let's stay in this sidebar click
the selected artifact tab again that
will collapse that section now you can
see that there are three other sections
artifact comments artifact links and
where artifact used click artifact
comments and note that that section
changes its name to simply comments then
click the only entry in that section to
expand it what you can see there is a
conversation between the project manager
the requirements engineer and the
supplier conversations like these
typically take place in external systems
like email and are very quickly lost
here they are maintained in context for
an audit trail of why key decisions have
been made click that comment section
again to collapse it and then click the
artifact links section here you can see
another way to view the requirement
traceability this time just for this
single requirement and only one level up
or down click artifact links again to
collapse that section and then click
where artifact used
because requirements are atomic they can
be used over and over again in modules
in collections and in reviews this
section shows you exactly where a
particular requirement is being used go
ahead and click the ECU requirements
review link to open it in a new browser
tab you can see that this requirement is
one of a collection of requirements that
are part of this formal review process
close this browser tab and switch back
to the radar subsystem hardware
requirements module now let's take a
look at those modifications we mentioned
earlier in the main document view in the
center in the ID column click the ID of
requirement 1 1 9 now we'll open that
requirement in its own view at the top
right-hand side of the window you'll see
an edit button and just to the left of
that is a button with three horizontal
lines the javea mouse over that button
the tooltip is more actions click that
button and select the first menu item
open history you're now looking at the
historical view of requirement 1 1 9 now
you're currently looking at revisions
that is a list of all of the baselines
and changed sense that this requirement
appears in you can open the historical
view for a specific change set or
baseline but instead go ahead and click
the audit history tab at the top left
hand side of the page for a complete
audit trail for this requirement every
change is listed here along with who
made it if you click on the expand all
link at the top of that list and scroll
down you can see that when changes a
textual the text of the requirement is
even color-coded to highlight those
changes just like track changes in a
word document click on the close history
button at the top right-hand side of the
page to switch back to the requirement
and then click the blue arrow in the
requirement heading bar at the top left
to return to the module view
well that's it for this preview we've
only just scratched the surface here so
feel free to explore rational doors next
generation on your own and I'll join you
again in the next preview
you
浏览更多相关视频
ESG-Risk: ESG-Risiken im Kreditprozess
Microsoft Teams: Kanal vs. Chat? Kollaboration in Microsoft 365 #microsoftteams #tipps #microsoft365
So rankst du Platz 1 bei Google SGE
Aerospace & AI - Airbus’ responsible and human-centric approach to AI | #aidatasummit24
6 UF Modul C Teil 1
Digitale Ethik: Warum wir sie dringend brauchen | Oliver Zöllner & Tobias Keber | TEDxStuttgart
5.0 / 5 (0 votes)