Rational Developer for System z
IBM Rational Developer for System z gives IBM System z developers tools for traditional mainframe development and for integrated, mixed workloads. An interactive, workstation-based environment lets you connect to a mainframe and develop mainframe-based applications in COBOL, PL/I, Assembler, C/C++, and Java code, as well as workstation-based applications in COBOL, PL/I, and Java code. The evaluation software is available as a download, on the cloud, or in a sandbox.
It was a packed room today for UrbanCode's DevOps Initiative session where Eric Minick and team provided some brilliant insights especially around streamlined delivery by way of automating deployments.
With so many sessions just under the DevOps and associated tracks, it was an impossibility to attend them all... or even half of them! What I'm really looking forward to is being able to grab the slides from the InnovateSmartSite (found under the "Find Sessions" or "My Agenda" if you added it to your schedule and then clicking on the session details for the icons allowing you to get the slides or even email them to yourself!)
Bruce Douglass' session on Agile Systems Engineering today went far to support the DevOps ideas as well, along with all the other fabulous sessions delivered by clients, business partners, and IBMers alike.
I had the pleasure of meeting Bruce, another of our Blue Galaxy stars, yesterday during a conversation with a group of Lake Brantley high school students participating in a software development program. Unknowingly, Bruce gave me that solid connection and reason for why DevOps is so important. I made the connection at some point while he was talking about the connection between nuclear power plants, MRI devices, and other highly critical systems which can't fail: in this world of high stakes systems engineering DevOps helps to make sure everyone is talking and thinking about the whole of the project to ensure systems like these aren't run with code that is just "good enough". "It works for me" doesn't fly in these environments where disaster or tragic failures would result from a small issue. And this is where I realized that DevOps can take this same kind of systems engineering principles for highly regulated and safety critical industries, and impart the same kind of view to all businesses, businesses who will see success from connecting the pieces, start to finish, and from that holistic view be able to identify and correct risk quickly and in a more agile fashion.
When I found out that our session on Non Traditional Enterprise learning was scheduled for the last time slot on Wednesday afternoon .. right before everyone goes to the Animal Kingdom theme part, my expectations for a lot of live attendees went way down.
Having said that, maybe this is an opportunity to show how non-traditional learning really works. Traditional learning ... which is what we're doing at the conference has it's limitations ... like being scheduled at a time that isn't great ... or like being in Orlando when you live in Sidney ... or being part of a 4 day conference ... which you can't get away from work to attend even if it was in your city.
Here is my presentation that I'll be sharing in about 2 hours ... Would love to engage with people here, or twitter .. or on my profile wall .. or any other way that works for you.
If you tweet .. please use the hashtag #session_SB_1422
DevOps is the soup to nuts* concept for true holistic software lifecycle management which brings continuous deployment combined with communication and deep collaborative integrations between engineering and IT infrastructure to stay ahead.
Today started with Kristoff Klockner and Sal Vella covering the devops ideas and then tossing to individual speakers to cover more specifics in 5 minute lightning talks about Mobile, Cloud, Big Data, and of Social Business.
We then met the SMEs in some awesome afternoon tech talk sessions and demos in the dW Live! space ion the expo floor and, of course, we met UrbanCode CEO and Founder Maciej Zawadzki in the Mini-Main tent sessions where he spoke on the topics of: Staying Ahead with a Smarter Approach to DevOps and Going Agile, Growing Agile and Continuously Delivering to Stay Ahead of the Competition
Business innovation is increasingly being delivered via software with rapid pace of market changes driving the need for business agility and providing great customer experience. How can clients establish an enterprise capability for accelerated delivery of software that enables them to seize market opportunities and reduce time to customer feedback, improving governance while balancing quality and cost: this is DevOps strategy and capabilities. The best place to start, other than Innovate is by reviewing the new white paper called "DevOps: The IBM approach." You'll find it enlightening for yourself AND your team!
Walker Royce gave us a quick overview of what DevOps is in this fun one minute promo video for IBM Innovate 2013. As he says, it is a horrible buzzword, but as we've found in today's sessions and keynotes at IBM Innovate (and in the snippets to be shared later), DevOps really is a holistic and critical piece to staying ahead in your business:
*soup to nuts is an American English idiom conveying the meaning of "from beginning to end".
It's time to start packing for Innovate! For me, that means it's time to start making my packing checklists so I don't forget anything. I leave at 4:30am and The Lad will probably have lacrosse practice the night before so I need to be organized or I'll be up all night throwing everything and anything into my suitcase. The Lad has tryouts for a summer tournament team while I'm away so if you see me on Sunday afternoon and I keep looking at my phone, I'm waiting for my husband to text me his results. But, back to Innovate. Have you checked out the SmartSite and built your agenda yet? You'll get far more out of the conference if you plan ahead. Attending with colleagues, build agendas that complement each other so you can divide and conquer. See you in the Expo Hall!
Successful compliance with IEC 61508 safety standards
By: Irv Badr, Client Technical Specialist, IBM and Patchanee Petprayoon, Software Architect, IBM
Techniques, use cases, and strategy to incorporate IEC 61508 guideline in embedded system and software development
Products: IBM Rational Team Concert, IBM Rational DOORS, IBM Rational Method Composer
Into the Blue Galaxy
By: Kelly Smith, Community Strategist, Practitioner Outreach, IBM
IBM technical experts launch a social media program to reach the universe of software developers and related practitioners
Life is all about learning. To me, the best kind of learning is when others share their experiences with you. This week, Harry Koehnmann shares the experiences of 321 Gang as they worked with agile embedded product-line development with Rational Team Concert.
Agile embedded product-line development with Rational Team Concert
Harry Koehnemann describes the problems that hardware, software, and project management teams at 321 Gang faced, the practices and tool changes that helped them, and what challenges remain in adopting agile methods for development of embedded, product line systems
Product: Rational Team Concert
How to produce a simple report in Rational Publishing Engine 1.2
Learn how to use IBM Rational Publishing Engine to build a simple document template linked to a running data source, IBM Rational DOORS requirements management software. The demo shows steps to generate, test, and fine-tune the report and publish it in PDF, Microsoft Word, and HTML formats.
Introduction to IBM Rational Publishing Engine for beginners
In this introduction to how IBM Rational Publishing Engine works, you'll get an overview of the components and what they do. This demonstration also shows details, such as opening Document Studio, opening a document specification, pointing the document specification to a data source, and generating reports.
Auditory, visual, and kinesthetic. Those are the three types of learning styles. You may learn best from reading an article on developerWorks. Or, maybe you're a kinesthetic learner and need to do the steps listed in the article. If you're auditory you've probably read the articles aloud in order to let the information sink in. Many times, you learn best by mixing the styles together.
However you learn best, the Internet has made it easy to find helpful information tailored to any of the learning styles. On developerWorks we recognize the different learning styles and want to make sure you get the information you need, in the way you need it.
I'm sure you're familiar with all the articles in our technical library. And I'm hoping you've downloaded a few evaluations or have played in a sandbox or two. Have you watched any of our demos? We've published many demos, and add more to our library throughout each month.
Are you a newbie to an IBM® Rational® software application? There are introductory demos for many of our applications. Have you been using a certain software for awhile, but just can't seem to figure out how to do something advanced? We have those demos too.
The great thing about demos is they cater to all learning styles. So whether you're an auditory, visual, or kinesthetic learner, there's a demo for you.
This week we're calling on Arthur Ryman an IBM Distinguished Engineer and the Chief Architect for Rational Reporting and Portfolio and Strategy Management. Arthur speaks at many of the major conferences, has written articles for the IBM Systems Journal as well as many trade journals. He's also the author of two books: Eclipse Web Tools Platform and Java Web Services Unleased. Arthur has worked for IBM since 1982. In addition to being an IBM Distinguished Engineer, he's an IBM software group master Inventor, a member of the IBM Academy of Technology, and a Senior Member of the IEEE.
Arthur recently wrote the featured article Linked Data Interfaces in which he introduces the OSLC Resource Shape specification as a candidate type definition language for Resource Description Framework. This article is bound to make you think and question... it's a must read.
If you have questions for Arthur about the article or his thoughts posted here, leave a comment. Arthur has a question for you: Are you implementing Linked Data systems?
Why wasn't the OWL proposal submitted to W3C?
I had a conversation with Kendall Clark, the founder of Clark & Parsia, about this point. It was a combination of factors, including a perceived lack of emphasis on OWL within the Linked Data community and the rise of SPARQL. However, there is renewed interest in this topic at W3C and a workshop on RDF Data Validation is being planned. See http://www.w3.org/2012/12/rdf-val/. This is an opportunity for Clark & Parsia to submit their OWL proposal.
Did you learn anything from writing your article and what was it?
Yes. I learned about the nuts and bolts of the Pellet reasoner.
What inspired you to write an article on this specific topic?
Within Rational, we are promoting Linked Data as a way to integrate development tools. I saw a lot of our developers misinterpreting OWL. I wanted to promote a better understanding of OWL and to steer our developers away from misapplying it.
What communities, forums, magazines, newspapers, or user groups do you turn to for help or technical insight?
Outside of Rational, Jazz, and developerWorks, I am active on the OSLC lists. I also subscribe to whatever user lists cover the technologies I am using, e.g. Jena and Pellet.
Which is in your opinion the area which lacks standardization most (either because of the absence of standardization or because of insufficient standards)?
Linked Data. Tim Berners-Lee laid out the high level vision, but there is a lot of flexibility in how you design Linked Data-friendly REST services and RDF vocabularies. Rational has contributed some guidelines developed in the context of OSLC to W3C. These are being standardized in the W3C Linked Data Platform working group. See http://www.w3.org/2012/ldp/wiki/Main_Page.
Which (future) standards are seen as important?
I look at the current state of Linked Data as being like the early days of electricity. With electricity, the main problem was how to generate and distribute electric current. This gave rise to the invention of a host of related devices, e.g. transformers, switches, outlets. So with Linked Data, we have the main ideas defined, but we have no standards for how to create Linked Data systems. One of these missing pieces is how to keep a triple store in synch with an operational data source. Rational recently contributed the Tracked Resource Set specification to OSLC. See http://open-services.net/wiki/core/TrackedResourceSet-2.0/.
For Desktop-based testing it’s a no-brainer: Use object-based scripting to maximize reuse across platforms/browsers. In
today’s mobile world it really isn’t that simple. There are many
different platforms, OS versions, form factors and carrier/manufacturer
customizations. Multiply that by mobile web, native app, or some hybrid
in-between and you’ve got yourself a healthy testing matrix. A daunting
task for even the most skilled Automation Engineer.
In order to tackle
this problem, an Automation Engineer cannot simply look at it from a
“one size fits all” perspective to create a set of objects and re-use
them across all combinations of platforms. For example, there are
fundamental differences in how an app behaves on iOS and Android, even
with something as basic as a “back button” has its quirks.
these fundamental differences can be grouped together as a step or
action, they are unique enough to not be able to simply share an object
between the two OS’s.In some cases with mobile testing, you may be able
to get to the object-level, however this usually requires that you
instrument your app, or test on an emulator. While this fulfills a piece
of your testing matrix, you will probably need to seek a couple tools
to get this done across all platforms. In other cases, the content you
are testing might be HTML-based and you can test by WebKit profiling.
Again, part of your testing matrix is fulfilled, however you aren’t
quite there.This may be enough to satisfy a short-term goal, but at some
point you need to be testing on real mobile devices.
In order to
truly automate on mobile, your mobile testing “Utility Belt” needs to be
designed in such a way that allows for testing by object when possible,
element when possible, and also be able to quickly fall back on text or
image verification in order to satisfy all areas of your testing matrix
and assure the highest quality of your mobile product. Having the
flexibility to be able to choose how to get the testing done is
paramount since as an Automation Engineer,you very rarely have a say in
how a particular app or mobile web site is developed. The job requires
you to sometimes understand functionality without necessarily being
privy to the construction, and there is always a tight timeline to
achieve results. The right tool for the job is a tool that takes all of
this into consideration, and provides a platform to consolidate all of
these different types of testing approaches.The first step is to
determine the type of app you are testing. Is it fully native, fully
web, or somewhere in between?
it’s fully native, you may be able to get to some objects on a per
platform basis, but you will probably be falling back on text and image
based verification, especially if you are trying to go cross-platform.
it’s fully web, a lot of testing can be done up front in a WebKit
profiler. When it comes to real devices, element-based testing can be
done cross-platform if you want to instrument, or you can fall back on
text and image verification.
If it’s somewhere in between, you’ll need to mix and match.
second step is to find which pieces or steps of your test cases are
reusable between each other, and can accept parameterization to fulfill
the task. For instance, automating the selection of an item or link on
your main screen of your app or landing page: Maximize reuse by
engineering a parameter to accept different values, and reuse it across
each test case. Although you may need to individually determine what
type of verification you will use to achieve this on a per platform or
device level, you will save time in the long run when you write
additional test cases. The third step is to then group those pieces or
steps together by device screens or pages. This way, as you write the
test cases you have an organizational structure that is easy to identify
by where you are within the app or site and where you need to navigate
to next.Following these steps will provide a structure that can be grown
to accommodate new features within an app or new sections within a
mobile web site. As mobile devices become easier to automate against,
this structure can easily adapt to emerging technologies that allow for
greater reuse across platforms.
Note: This article was recently published in the April, 2013 issue of Automate Software Quality Magazine.
Mobile is about anytime, anywhere access to information. It improves productivity and is driving business innovation in the enterprise. Mobility enables quicker access to customer data, improved customer satisfaction and support, customer access to business and important functionality, and the capability to respond to customer demands.
Mobile is not only one of the most exciting trends affecting IT today, but an inevitable one. Indeed, most companies already have some type of mobile strategy. However, in order to take it to the next level and offer five-star apps, businesses will have to integrate mobile applications with business-critical back-end data sources.
Join us for this complimentary webcast as our subject matter experts discuss a unique IBM solution that combines end-to-end application lifecycle management with both mobile and mainframe development features all integrated into one package. The experts will spotlight a new mobile app that uses the sale of office supplies as an example. They will also show you how to bring a green-screen application into the mobile era using Rational Developer for System z and Worklight.
Fragmentation of devices and platforms
Speed and frequent iteration of the mobile lifecycle and continuous delivery
Connectivity to back-end systems and enterprise clouds
Security to protect corporate data and managing BYOD
Mobile Context taking advantage of unique capabilities such as geo-location
Delivering high-quality apps and rapidly incorporating customer feedback