Tool-unterstütztes Anforderungsmanagement im Produktlebenszyklus

Transkript

1 IBM Software Tool-unterstütztes Anforderungsmanagement im Produktlebenszyklus Berliner Requirements Engineering Symposium 21. November 2013 Hubert Biskup IBM

2 Agenda Toolunterstützung im Anforderungsmanagement im Wandel der Zeit Definition Jazz und OSLC Grundlagen und Konzepte von DOORS Next

3 Agenda Toolunterstützung im Anforderungsmanagement im Wandel der Zeit Definition Jazz und OSLC Grundlagen und Konzepte von DOORS Next

4 Toolunterstützung im Anforderungsmanagement im Wandel der Zeit

5 Was ist heute wichtig im Requirements Management? Bewältigen der Komplexität Erweiterte Traceability zwischen Projektteams Verwalten der Anforderungsänderungen Anforderungsbezogene Aufgaben Prozessreife Zusammenarbeit verbesserte Benutzerführung Dashboard & Projektmetriken Kommerzielle Datenbank, Sicherheit & Benutzerverwaltung Kontrollierte Wiederverwendung von Anforderungen Webbasiertes Arbeiten und vieles mehr

6 Erfassung, Strukturierung und Verknüpfung verschiedenster Anforderungsartefakte Dokumente zur Erfassung von strukturierter und unstrukturierter Information Grafische Beschreibung von Abläufen wie z.b. Geschäftsprozessen Verwendung von Glossaren, um Mehrdeutigkeiten zu vermeiden Einfügen beliebiger Dateien (z.b. Bilder, Präsentationen, Audio, Video) Visualisierung von Benutzeroberflächen mit UI Sketches und Storyboards Beschreibung von Use Cases in Diagrammen und Rich Text

7 Unterstützung grafischer Artefakte Grafische Formate können erzeugt und editiert werden wie Business Process Diagramme, Use Case Diagramme und User Interface Entwürfe.

8 Requirements Extraction (from Word Documents) Requirements Parsing Capability Automatically identify imported requirements using keywords and document hierarchy Benefits Quickly identify requirement with syntax standards using structure and key words

9 Filtering and finding requirements Filters can be saved into named Views and clicked on later to apply the same filters Linked artifacts can also be used to filter results. Use the side bar to filter results. Multiple filters are ANDed together Use clear buttons to remove all filters from a section Filter by link type or artifact type on the target end of the link 9

10 Agenda Toolunterstützung im Anforderungsmanagement im Wandel der Zeit Definition Jazz und OSLC Grundlagen und Konzepte von DOORS Next

11 Die Plattform DOORS Next Team Concert Quality Manager Business Expert Collaboration Elicit, capture, elaborate, discuss, review and organize requirements Collaborative software delivery Unify by thinking & working in unison Lifecycle quality management Coordinate quality assurance plans, processes and resources Future IBM Capabilities Your existing capabilities Business Planning & Alignment Product Collaborative & Project Lifecycle Management Management Best Practice Processes Compliance & Security Engineering & Software Tools 3rd-Party Jazz Capabilities Collaboration Presentation: Mashups Discovery Query Storage Administration: Users, projects, process

12 Insight Publishing Engine Team Concert Change ClearQuest Design Manager Software Architect Rhapsody Requirements Composer DOORS Quality Manager Open Services for Lifecycle Collaboration 3 rd Party tools Interoperation HP Quality Center DOORS DOORS Next Generation Team Foundation Server Insight Focal Point RequisitePro Publishing Engine Rose Rhapsody System Architect

13 Open Services for Lifecycle Collaboration (OSLC) Die OSLC-Initiative wird seit Juni 2008 unter Führung von IBM als offener Industriestandard vorangetrieben Mehr als 39 verschiedene Firmen arbeiten aktiv in dieser Industrie-Initiative OSLC Arbeitsgruppen: Architecture Management, PLM, Automation, Asset Management, CM, QM, RM, SCM, Software Estimation and Measurement Ziele: Vereinfachung der Zusammenarbeit über den Software-Entwicklungs-Lebenszyklus Schaffen einfacherer Werkzeugintegrationen von unterschiedlichen Tool-Herstellern Die OSLC Community spezifiziert Formate und RESTful APIs Eine offene, öffentliche/freie und nicht-properitäre Schnittstelle Webadresse:

14 Beispiel: OSLC-Links zwischen DOORS 9 und DOORS Next Direktes Verlinken mit OSLC OSLC (Open Services for Lifecycle Collaboration wird für die direkte Verlinkung zwischen DOORS 9 und DOORS Next Generation verwendet Traceability-Spalten in beiden System

15 Agenda Toolunterstützung im Anforderungsmanagement im Wandel der Zeit Definition Jazz und OSLC Grundlagen und Konzepte von DOORS Next Generation

16 DOORS Next technology base Requirements visibility and traceability across the lifecycle Open integration architecture built on the Jazz Team Server Integrations using Open Services for Lifecycle Collaboration (OSLC) Web DOORS Next Generation Requirements Management Services Change Management Services Publish Consume Consume RM Services Team Server OSLC Quality Management Services Architecture Management Services Publishing Services Consume Consume Publish COTS database Additional Services Publish Consume

17 DOORS NG module view (web client) Modern web look and feel minimizes adoption cost for new and casual users Module Properties Filter Pane Glossary Terms

18 Traceability Multi-level graphical analysis Traceability views similar to DOORS Linked Stakeholder Requirements System Requirements Linked Subsystem Requirements

19 Collaboration Collaboration through information discussions or by formal review notification available for review updates Dashboard widgets to show review participation and status Notification to personal dashboard Comments can be used inside or outside of a review

20 Built in task planning and management Supplied as part of core Jazz services Task planning and assignment to team members No additional license included with a normal DOORS NG license Support for flexible dashboards Show me all the work items assigned to me Show me progress my team are making towards project plans Show related lifecycle information How have requirements been realized by development? Has a requirement been sufficiently tested?

21 Centrally integrated repository Share a Jazz foundation server between multiple products Simplify administration Single point of configuration for users Single place for backups and disaster recovery Support for COTS databases Oracle, SQL Server, DB2 etc Integrated systems work closer together Example scenarios for DOORS NG & RQM users DOORS NG user: Specifies requirements needing to be tested Monitors traceability to tests Follows test reviews down into RQM 21 RQM User: Automatically creates draft tests based on new requirements Reviews requirements information from within RQM Follows requirements audit trail back to DOORS

22 Requirements reuse Central project based store of requirements information Referenced by specifications Reuse on an individual basis Or as part of a module template Reusing the same requirements in multiple places

23 Requirements Configuration Management Versioning and configuration management of requirements Requirement configurations and baselines Branching and merging Change sets and personal workspaces Support for configurations across requirements, designs, code, tests, etc. Create baselines across all these artifacts Customer Beta for DOORS NG currently running, planned delivery in 2014 Shared Configurations and Baselines time Product definitions DOORS Rhapsody DM

24