This document discusses increasing development team velocity through continuous engineering using an Internet of Things (IoT) architecture. It notes that development complexity has increased as teams use many tools and repositories. An IoT approach pushes critical data and alerts to developers in real-time to make the right information available at the right time. The presentation demonstrates connecting an IBM tool to analyze and push event data to external services like Twitter to notify users. It aims to streamline continuous engineering processes using IoT concepts.

1. InterConnect
2017
Increase Your Agile Velocity!
Integrate Your Development
Tools with IBM IoT and
Analytics
M. Kevin McHugh
Kirk Woods
1 3/22/2017

2. 2 3/22/2017
Please note
IBM’s statements regarding its plans, directions, and intent
are subject to change or withdrawal without notice at IBM’s
sole discretion.
Information regarding potential future products is intended to
outline our general product direction and it should not be relied
on in making a purchasing decision.
The information mentioned regarding potential future products
is not a commitment, promise, or legal obligation to deliver
any material, code or functionality. Information about potential
future products may not be incorporated into any contract.
The development, release, and timing of any future features
or functionality described for our products remains at our sole
discretion.
Performance is based on measurements and projections
using standard IBM benchmarks in a controlled environment.
The actual throughput or performance that any user will
experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in
the user’s job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no
assurance can be given that an individual user will achieve
results similar to those stated here.

3. Agenda
• The Key Point
• The Big Picture
• Increasing Complexity
• The Dev/Ops Speed Limit
• Continuous Engineering using an IoT Architecture
• Demonstrate
• Q&A
3/22/2017 3

4. The Key Point
4 3/22/2017

5. 3/22/2017 5
Communication Delay
• How many times have you seen a delay between a developer
finishing their work and the tester being notified it is ready for
test?

6. The Big Picture
6 3/22/2017

7. 3/22/2017 7
Continuous Engineering with IoT
IoT-enabled
products/systems
Business
Leaders,
Engineers
and Developers

8. 3/22/2017 8
Continuous Engineering

9. Increasing Complexity
9 3/22/2017

10. 3/22/2017 10
Whole product development involves many tools,
repositories, vendors
A very simplified look
DOORS &
DOORS NG
Rhapsody
& RDM
Team Concert, ClearCase
Maximo
Engineering Lifecycle Manager
Quality
Manager

11. 3/22/2017 11
OSLC Linked data
RM Project Area RTC Project Area
RM Project Area
RQM
Project Area
Requirements
Tests
Design
Implementation

12. 3/22/2017 12
Cross-tool “global configurations”
• Multi-tool configurations in a federated, linked data system
• Each tool auto-configures so that you see and work with the correct artifacts
• Link / navigate across tools in the right context
• Create all team deliverables in a configuration context
This is about transforming from a “single system”
solution to “multi-variant”, adding a variant
dimension to the entire development lifecycle
Variant 1
Variant 2
Variant N
Function
Requirements
Tests
Design
Implementation
Requirements
Tests
Design
Implementation
Requirements
Tests
Design
Implementation
Variation
Requirements
Tests
Design
Implementation
Reuse
Variant

13. 3/22/2017 13
How do we handle this today?
• Tools
• Application Lifecycle Management
• Enables independent process and data lifecycles
• Global Configuration
• Enables whole V model branching and merging
• Audience: How do you receive/retrieve your information today?
• Three different examples
• Techniques
• CE/DevOps: improve and manage feature flow
• Agile: isolate complexity, produce feature

14. The Dev/Ops Speed Limit
14 3/22/2017

15. 3/22/2017 15
New methods increase our speed
How frequently do you get updates for your mobile phone apps?
Waterfall Incremental Iterative

16. 3/22/2017 16
We’ve hit a speed limit
• Complexity – product
• Instead of carrying a single plate...
• Speed
• Instead of walking...
• Complexity – product
• We are juggling....
• A bowling ball
• A chainsaw
• And an egg...
• Speed
• We are sprinting
... and... the PM’s still want status....

17. 3/22/2017 17
How can we improve?
• Reduce waste in your overhead / control mechanisms
• Sprint Planning
• Daily Stand up
• Retrospective
• Backlog grooming
• Demo
• Dev to Ops
• Automate test and delivery

18. Continuous Engineering
using an
IoT Architecture
18 3/22/2017

19. 3/22/2017 19
Internet of Things (IoT)
• A network of interconnected devices and systems that collect and
exchange data between them. The data they generate is collected,
analyzed and acted upon.*
* Yianna Papadakis Kantos - A developer's guide to the Internet of Things (IoT)

20. 3/22/2017 20

21. 3/22/2017 21
Thinking about an IoT Architecture
How does this apply to you as a software engineer?
• If we think about the tools, methods and systems that have arisen to
support that definition, we see a new architecture. This architecture is
extremely distributed. It takes advantage of trends and techniques
such as:
• Client / Server
• Mark up languages
• Publish / Subscribe
• Message Queues
• And more

22. 3/22/2017 22
Physical
• The ‘thing’ is a physical device
• Relevant space: washing machines, automobiles, weather
stations....
• This is relatively easy to conceptualize. Devices experience an
event and transmit data accordingly. The data is analyzed and
acted upon.

23. 3/22/2017 23
IT
• The ‘thing’ is an IT system element. This might be a router, a physical
or virtual computing units.
• Relevant space: Asset management, system and network operations

24. 3/22/2017 24
Data??
• The ‘thing’ is a data element
• Some say ‘no’
• Can we treat data as a ‘thing’?
• Data does not have a processor
• Database technology solved this decades ago

25. 3/22/2017 25
Data!!
• I say ‘yes’!!
• Data has a processor
• It is shared across a lot of data
• Database triggers available for decades
• Plugins
• Event driven User Interface software techniques

26. 3/22/2017 26
Continuous Engineering

27. 3/22/2017 27
Continuous Engineering Data
• The ‘thing’ is an element in the CE/DevOps flow
• Systems: physical or virtual
• Requirements
• Design elements (UML become important here)
• Change and source control
• Builds
• Defects
• Test assets
• Test Execution results
• Deployment: physical or virtual
• Logging (instead of log files, send an event)
• System monitoring
• Asset management
• Customer support (another sensor)
Requirements
Tests
Design
Implementation

28. 3/22/2017 28
Today
• We “pull” information.
• Dashboards and data warehouses
• We “push” information on overloaded channels such as email.
• How many of you use email filters/rules to manage this?
• Information grows stale waiting for a decision maker to access it and
take action. This represents lost opportunity and waste which means
lost revenue and wasted budget

29. 3/22/2017 29
Continuous Engineering with IoT
• IoT “pushes” information in the hands of a decision maker
• More concisely – right information
• More accessibly – right place
• More promptly – right time
• Reduces several Wastes
• Waiting
• Motion
• Defects
• Over Processing
• IoT links and correlates divergent, separate information and
knowledge domains

30. Demonstrate
30 3/22/2017

31. 3/22/2017 31
IBM Rational Team Concert
• IBM Rational Team Concert
• Rational Team Concert is a software development team
collaboration tool developed by the Rational Software brand of IBM,
who first released it in 2008. The software is available in both client
versions, a web version, and on Cloud. It provides a collaborative
environment that software development teams use to manage all
aspects of their work—such as plans, tasks, revision control, build
management, and reports.
• https://en.wikipedia.org/wiki/Rational_Team_Concert

32. 3/22/2017 32
Demonstration – Let’s see a quick demo in action
• Update a work item
• See Twitter
• Hear the mobile phone
PLEASE ASK QUESTIONS WHEN YOU HAVE THEM
☺

33. 3/22/2017 33
Demonstration – How we did it
...pardon us as we switch laptops...

34. 3/22/2017 34
Demonstration – How is this done
• An RTC plugin that sends event data to Node-RED on Bluemix
• Node-RED flow to conduct (minor) analysis on the event data
• Push an alert to an end user (in this case on Twitter)
• Twitter blocks duplicate messages

35. 3/22/2017 35
Summary
• Continuous Engineering with IoT:
• Critical data and alerts pushed to (smartphones, feed readers, web
pages, ...)
• Right Data, Right Place, Right Time
• Leverage Social Media concepts to streamline, to “lean” CE

36. 3/22/2017 36
Q&A

37. 3/22/2017 37
Backup Slides

38. 3/22/2017 38
IBM Managed Continuous Engineering deployed
on a virtual single tenant private cloud
Provides the core
Continuous Engineering
solution, uniquely
configurable for each client
On IBM SoftLayer secure
infrastructure
Provides 99.9% availability
(SLO)
IBM IoT services solution
IBM SoftLayer Infrastructure
IBM Watson IoT Services
IBM Managed Continuous Engineering products include*:
IBM Rational Team Concert
IBM Rational DOORS Next Generation
IBM Rational Quality Manager
IBM Rational Design Manager
IBM Rational Engineering Lifecycle Manager
*Software licenses sold separately

39. 39 3/22/2017
Notices and disclaimers
Copyright © 2017 by International Business Machines Corporation (IBM).
No part of this document may be reproduced or transmitted in any form
without written permission from IBM.
U.S. Government Users Restricted Rights — use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to
products that have not yet been announced by IBM) has been reviewed
for accuracy as of the date of initial publication and could include
unintentional technical or typographical errors. IBM shall have no
responsibility to update this information. This document is distributed
“as is” without any warranty, either express or implied. In no event
shall IBM be liable for any damage arising from the use of this
information, including but not limited to, loss of data, business
interruption, loss of profit or loss of opportunity. IBM products and
services are warranted according to the terms and conditions of the
agreements under which they are provided.
IBM products are manufactured from new parts or new and used parts.
In some cases, a product may not be new and may have been previously
installed. Regardless, our warranty terms apply.”
Any statements regarding IBM's future direction, intent or product
plans are subject to change or withdrawal without notice.
Performance data contained herein was generally obtained in a
controlled, isolated environments. Customer examples are presented
as illustrations of how those customers have used IBM products and
the results they may have achieved. Actual performance, cost, savings or
other results in other operating environments may vary.
References in this document to IBM products, programs, or services
does not imply that IBM intends to make such products, programs or
services available in all countries in which IBM operates or does
business.
Workshops, sessions and associated materials may have been prepared
by independent session speakers, and do not necessarily reflect the
views of IBM. All materials and discussions are provided for informational
purposes only, and are neither intended to, nor shall constitute legal or
other guidance or advice to any individual participant or their specific
situation.
It is the customer’s responsibility to insure its own compliance with legal
requirements and to obtain advice of competent legal counsel as to
the identification and interpretation of any relevant laws and regulatory
requirements that may affect the customer’s business and any actions
the customer may need to take to comply with such laws. IBM does not
provide legal advice or represent or warrant that its services or products
will ensure that the customer is in compliance with any law.

40. 40 3/22/2017
Notices and disclaimers
continued
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products in
connection with this publication and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products. IBM does not warrant the
quality of any third-party products, or the ability of any such third-party
products to interoperate with IBM’s products. IBM expressly disclaims
all warranties, expressed or implied, including but not limited to, the
implied warranties of merchantability and fitness for a particular,
purpose.
The provision of the information contained herein is not intended to, and
does not, grant any right or license under any IBM patents, copyrights,
trademarks or other intellectual property right.
IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS,
ClearCase, Cognos®, DOORS®, Emptoris®, Enterprise Document
Management System™, FASP®, FileNet®, Global Business Services®,
Global Technology Services®, IBM ExperienceOne™, IBM SmartCloud®,
IBM Social Business®, Information on Demand, ILOG, Maximo®,
MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower,
PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®,
PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®,
PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®,
SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli® Trusteer®,
Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and
System z® Z/OS, are trademarks of International Business Machines
Corporation, registered in many jurisdictions worldwide. Other product
and service names might be trademarks of IBM or other companies. A
current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at: www.ibm.com/legal/copytrade.shtml.

41. InterConnect
2017
41 3/22/2017