OSLC in Aktion

Thorsten Gau, Distinguished Engineer
OOP, München, 24. Januar 2012

OSLC in Aktion:
Agilität trifft auf Unternehmensrealität
Di 7.4

© 2012 IBM Corporation

Thorsten Gau

 Seit 1994 bei IBM
– Distinguished Engineer / IBM Executive Architect
– Chefarchitekt bei IBM Global Business Services, Deutschland
– Viele erfolgreiche globale Systemintegrations- und
Anwendungsentwicklungsprojekte.
– Experte für Software Engineering Methoden,
Enterprise 2.0 Technologien and Integrations-Architekturen
– Führungsmitglied des Technical Expert Council central.
Im Verbund der IBM Academy of Technology

 Open Group

 CTO für Methoden & Werkzeuge sowie Architektur-Ausbildung

https://www.xing.com/profile/Thorsten_Gau
https://apps.lotuslive.com/contacts/profiles/view/981

@tgau


Agenda

 Das Problem
- die eierlegende Wollmichsau gibt es nicht
- Punkt-to-punkt Werkzeugintegration hat die Komplexität N²
- Proprietäre Schnittstellen  Abhängigkeit vom Hersteller und Versionen
 Open Services for Lifecycle Collaboration (OSLC)
- Referenzieren ist besser als Synchronisieren
- Das WWW als Vorbild: alles ist eine Ressource und per URL addressierbar
 OSLC in Aktion :: ein Projekt und reale, verfügbare Werkzeuge
- Projekt-Zeiterfassung: My internal accounting base (Miab)
- Anforderungsdefinition, Projektmanagement, Testmanagement
- UML Modellierung, Build-Automatisierung / Kontinuierliche Integration
 Noch mehr Action, Zusammenfassung und weiterführende Information

3 © 2011 IBM Corporation 3

Himmlisch Agil: Ein kleines bevollmächtigtes Team an einem Ort
und ein simples Werkzeug, das gerade “gut genug” ist

 The majority* of agile teams have less than 16 members
How about the larger projects?
 Only 47% of the teams have their members co-located in one room
Ever tried to share a physical taskboard across geographies and time zones?
 34% of the teams have their stakeholders in same building / floor / room
Did you ever have trouble reaching your product owner?
 How many companies participate in your projects?
 Does your company / your industry mandate compliance or auditing?

4 *Source http://www.ambysoft.com/surveys/agileTeams2011.html © 2011 IBM Corporation 4

Unternehmensrealität: Jede Organisationseinheit will ihr ganz
spezielles Werkzeug. Global Delivery (Outsourcing / Multisourcing)
macht es noch schlimmer !
Plan Item
Incident (Macro-)Task
Problem Ticket Change Request
Operations Project Manager
UML Component
HP I3S UML Node MS Project
Tivoli Service Req.Mgr. IBM RTC
Architect

IBM RSA
Borland Together
Requirement Test Plan
Business Process Test Case
Use Case Defect
Wireframe (Micro-)Task
Tester
Analyst Developer
Eclipse Mylyn Bugzilla
IBM RRC MS TFS Mantis
IBM DOORS IBM RTC HP QC
Microfocus Caliber IBM RQM


Bisherige Ansätze haben viele Nachteile

Limited choice and coverage

Single repository Point-to-point integrations

“Can I really expect one vendor “How can I ever upgrade one
to provide all the functionality I tool without breaking
need? And what about my everything else?”
existing tools?”

Universal metadata standard Standard implementations

“How did I ever think all those “Did I really believe that
vendors would be able to every vendor would rewrite
agree?” their tools on a single
framework?”

Slow to emerge and disruptive to adopt
6 © 2011 IBM Corporation

Agenda

 Das Problem


Datenintegration im 21. Jahrhundert
Verknüpfte Artefakte im “Projekt-Web”: lifecycle resources

If the entire Web can connect like this,
 Inspired by Internet principles, implemented would the same idea work for ALM?
with Internet technologies: simple interfaces for
exchange of resources
 Loosely coupled: everything is a “resource”
linked together with URLs
 Technology neutral: treats all implementations
equally
 Minimalist: defines no more than necessary for
exchange of resources
 Agile: deliver value now, add more value over
time
 Openly published standards: free to implement
and irrevocable
RESTful
CRUD
…unlike traditional integrations that are tied to brittle,
proprietary desktop and server technologies


Jazz: Eine offene Architekur zur Integration von Werkzeugen

 Embracing linked lifecycle data
(OSLC) for sharing lifecycle
resources
 Defining Jazz Integration Services
for common capabilities like
administration, reporting,
dashboards, etc.
 Multiple integration points / patterns
– Backend: RESTful CRUD
– Frontend: HTML preview


Jazz ist IBM’s Beitrag zur Verbesserung der Werkzeugintegration

This strategy is executed in three ways:
 An open architecture for lifecycle tool integration
 An open community working together to integrate and develop lifecycle tools
 A catalog of products that support the Jazz initiative

 Standard protocols for linking lifecycle tool data (OSLC)
Architecture
 Jazz Platform consisting of Jazz integration Services and
Protocols to support lifecycle integration patterns

 Jazz.net – A place where stakeholders collaborate
Community  Transparent development of Jazz architecture and
products

 Lifecycle tools that use the Jazz architecture
Products  Developed transparently in the view of the Jazz
community


Open Services for Lifecycle Collaboration
Spezifikation für verlinkte (Projekt-)Lebenzyklus Daten

 An open community of
individuals from industry,
commercial tools vendors,
systems integrators, open
source projects, and
academia.

 Focusing on sharing of
lifecycle data (requirements,
http://open-services.net
test cases, change requests)
between tools and across the
History
2008 Vision lifecycle.
2009 v1.0
2011 v2.0  Taking a technology-neutral
approach based on Internet
standards and protocols.

11 © 2011 IBM Corporation11

Die OSLC Community besteht aus 420+ Mitgliedern
unterschiedlicher namenhafter Unternehmen

Range of interests, expertise, Accenture Oracle
APG QSM (Slim Estimating Suite)
involvement Big Lever Rally Software
Black Duck Ravenflow
Boeing Shell
– 426+ registered community members BSD Group (HPQC) Siemens
(up from 70 people in 2009) Citigroup Sogeti
CESAR SourceGear/Teamprise
EADS SPRINT
– Individuals from 127+ different
Emphasys State Street
companies have participated in OSLC Galorath Tasktop (Eclipse Mylyn)
workgroups General Motors Thales
(up from 5 companies in 2009) IBM Tieto
Institut TELECOM TOPIC Embedded Systems
 Eleven workgroups operating at Integrate Systems
Northrop Grumman
UrbanCode
WebLayers
open-services.net


Die OSLC Arbeitsgruppen fokussieren auf Domänen

Operating Principles
 Transparency – wiki, mail lists
Domain Workgroup Resources
 Scenario driven
 Architecture of the web (w3c - linked data) Requirements Management Requirement, Requirement Set
 Bias toward simplicity/minimalism and Definition
 Time-boxed and incremental Change Management Change Request (work item, defect, task,
 Specification coupled with implementation …)
See: http://tinyurl.com/2bm5zc5 Quality Management Test Plan, Test Case, Test Script, Test
Execution Record, Test Result

Asset Management Asset, Artifact

Architecture Management AM Resource (UML class, UML
component, use case)

Software Configuration Change Set, Baseline, Configuration,
Management Directory/File/Symlink Version

Estimation and Measurement, Project, Scenario
Measurement size, quality, schedule, effort

PLM and ALM Product, Product_version

Automation Build


Agenda

 Das Problem


Im Projekt Miab wurde ein „Zeiterfassungssystem“ entwickelt.
Es waren drei Teams an unterschiedlichen Standorten beteiligt.
Test Result
Require- Defects
Baselines Test Script
ment(set)
Dirs, Files Test Case
Process Tasks
Definition
Config Mgmt Test Plan
Use Cases Agile Project
Test- and
Requirement Management
Quality-
Definition management
RTC
Rational
RRC Team RQM
Rational Concert Rational
Requirements Quality
Composer Manager


Das UML Modell wurde in Dateien* im Projekt-Repository abgelegt.
Wir haben Build- und Test-Automation genutzt.

UML Use Case
Component Realization

UML
Class Source
Executable
Code
Baseline
Build
Dirs, Files Defintion
UML Modeling
Java Dev. Config Mgmt
Agile Project Build Testautomation:
RSA Management
Automation
Rational RTC Test Script
Software Rational RTC
Architect Team
Concert
Rational Defects
*Note: Team
Design Management
was not available in Concert
2010 when we
conducted the project


Der Geschäftsprozeß „Zeiterfassung“ referenziert den
„Erfasse Arbeitszeit“ (Record times) Anwendungsfall


Der Anwendungsfall referenziert das Arbeitspaket (Story) in dem die
Implementierung und der Unittest geplant wird. Unterschiedliche Tools.

Change
Management

Story

Test Case
Quality
Management

Glossary
integration


Arbeitspakete (Stories) wurden in Aufgaben (Tasks) unterteilt und auf dem
Taskboard visualisiert. Für die tägliche Synchronisation (Scrum Meeting)
haben wir Screensharing in LotusLive genutzt.

17985


RTC bietet verschiedene Typen von Arbeitselementen (Stories, Aufgaben,
Fehler). Dreh- und Angelpunkt für agiles Projektmanagement.

Quality
Management

OSLC link Test Case
Glossary
entry
Tasks
- done
Requirements
Management - to do

Use Case


Erfahrungen aus mehreren Projekten

 Gutes Software Engineering ist (weiterhin) die Voraussetzung für Erfolg.
– Anforderungen müssen strukturiert werden.
– Ein formaler und doch leichtgewichtiger Freigabeprozess ist wichtig.
– Die (Nicht-)existenz von OSLC-Links hilft als Vollständigkeitsprüfung.
– Komplexe Projekte benötigen wohldefinierte Baselines.
Wenn alles im Fluss ist, ersticken Teams an den Änderungen.
 OSLC Links sind sehr nützlich – aber nicht überdosieren!
– Man braucht ein (projektspezifisches) Metamodell der Artefakte
– Die Semantik der Links (Children, Implemented By, Validated By, ...)
muss den Nutzern klar sein.
 Webstandards brauchen (Betriebs-)Team mit Erfahrung in Webstandards
– Stabile URLs  Reverse Proxies
– (Verteiltes) Single Sign On  LDAP
– Projekt On-/Offboarding und Berechtigungsmanagement  PMO


Agenda

 Das Problem


2

Mehr OSLC in Aktion – einige ausgewählte Beispiele
3

Who What Description

Siemens Teamcenter & Coordinate product (PLM) and software (ALM) change management. Siemens is integrating change
Rational Team Concert management processes for mechanical, electrical and software systems by creating and linking Rational
Team Concert and Siemens Teamcenter change requests.

Jenkins ( Hudson) The Jenkins OSLC CM Plugin connects to different remote bug trackers via the OSLC protocol
OSLC CM Plugin

Eclipse Mylyn, Tasktop Task-focused collaboration for Eclipse developers and ALM integration. Eclipse Mylyn and Tasktop Dev
Dev Pro & Sync 2.0 // Pro provide developers with a revolutionary task-focused interface that supports one-click multitasking,
Rational Team Concert. workspace focusing, and time tracking for Rational Team Concert work items and ClearQuest change
Rational ClearQuest, … requests. Linking support for Tasktop Certified ALM ecosystem via OSLC-based REST API.

HP Quality Center & Improve collaboration between development and test teams. BSD Group is connecting development and
Rational Team Concert test processes by linking Rational Team Concert work items with HP Quality Center test requirements and
plans.
PLM/ALM traceability Break down barriers between PLM and ALM. General Motors is driving integration scenarios to achieve
scenarios better performance and traceability across the product and software lifecycles.

Microsoft Project & Better collaboration between product managers and agile teams. Ascendant’s Atech Team Connector
Rational Team Concert synchronizes Microsoft project plans with Rational Team Concert release and iteration plans.

iTKO LISA & Rational Reduce time to defect resolution. iTKO LISA creates Rational Team Concert work items or ClearQuest
Team Concert, Rational defects that include detailed, multi-tier trace information from any test executed with LISA Pathfinder.
ClearQuest

dbMaestro Teamwork & Manage change to your database system. dbMaestro TeamWork enables teams to manage database and
Rational Team Concert schema evolution by utilizing Rational Team Concert change management -- linking dbMaestro database
change sets with Team Concert work items.


Softwareentwicklung ist (nur) ein Teil im Gesamtkontext und
hat wiederum Links zu anderen Domänen.

Zusammenarbeit

Software
Development

IT Service Management

Business Analytics

Einfach mal kostenlos ausprobieren:

 https://jazz.net/sandbox
 https://jazz.net/hub
 Spontane Fragen: @tgau


Kernaussagen

 Das perfekte Tool, dass alle akzeptieren, gibt es nicht.
Punkt-to-punkt Integration ist N² / wackelige APIs sind ein Alptraum
 Verlinken ist besser als kopieren
 OSLC Prinzipien:
URLs, Standardisierte Datenformate, RESTful services
 OSLC basiert auf offenen Standards: XML, Dublin Core
… und ist ein offener Standard für kollaboratives Anwendungs-
Lebenszyklus-Management (C/ALM)
 Es existieren bereits diverse nicht-IBM + IBM Integrationen:
HPQC, Mylin, JIRA, Mantis (PoC), Bugzilla (PoC), …
RRC, RTC, RQM, DOORS, ClearQuest, Tivoli Service Request
Manager, RSA, RSysA
 OSLC ermöglicht eine schrittweise Einführung der Werkzeuge
Ein Big Bang ist nicht nötig.

Referenzen

 Open Services for Lifecycle Collaboration
http://open-services.net/
 Jazz Community Site
https://jazz.net/
 Design Management (OSLC linkíng to UML models)
https://jazz.net/blog/index.php/2011/03/31/new-project-at-jazz-net-design-management/
 Selected Videos
– Open Services for Lifecycle Collaboration (OSLC)
http://www.youtube.com/watch?feature=player_embedded&v=B2vqL8fujgE
– Interview with Mik Kersten, Tasktop Technologies (Mylyn)
http://www.livestream.com/ibmrational/video?clipId=pla_f957bfaa-5da7-4769-8f28-3408d49d23c6
– Interview with Martin Nelly, IBM Fellow
http://www.livestream.com/ibmrational/video?clipId=pla_71b3920d-dc14-4e26-b2e8-230d96548239
– Angel Diaz, IBM Vice President, Software Standards
http://www.youtube.com/watch?v=LzSoJDVsCzE

 More bookmarks on OSLC:
https://www.ibm.com/developerworks/mydeveloperworks/bookmarks/html?luserid=110000AF4V&tag=oslc

 Contact info for Thorsten Gau, IBM Distinguished Engineer
https://www.xing.com/profile/Thorsten_Gau

OSLC in Aktion

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie OSLC in Aktion

Ähnlich wie OSLC in Aktion (20)

OSLC in Aktion