IBM i Tutorial: update of IBM i development Strategy

Do you know how it works as a developer of IBM I? Assuming you are responsible for developing and upgrading an operating system, do you know how to determine which parts of the operating system require more investment? How will you learn about today's evolving new technologies, and then determine if these new ideas are being applied to the system, or will they conflict with the functionality already implemented in the system?

Today, I hope to help you know how we do it through my team's work plan for the next few weeks. Of course we are talking about most of the content is IBM Confidential, so I can not share in this blog. However, I think I can give you a general idea of how to take good ideas, how to say no to certain ideas, or keep some ideas in the future before making a decision.

With the advent of summer, the new Year's IBM I development plan is to be set up. In our planning process, we will reflect on the innovative ideas that have emerged in the development of new features such as IBM I,powervm,systems Director and other related products. When planning is complete, most of the work that has already started will continue, but we will make appropriate improvements or add new ideas, or simply stop developing.

Before making a plan, for each new technology, our development team needs to look at its technical field and see if we have enough knowledge and resources to enable it to be implemented in IBM I. We will hold a series of development strategy meetings and invite technical experts from the lab to join with some business architects. During the meeting, the technical experts will introduce these new technologies to the architects and make some suggestions for our development plans. We will listen attentively to each expert's new technology introduction and their recommendations, by considering the interaction of various technologies to measure the priority of the new work.

Let me give you an example. The first one to introduce is Jenny Dervin, who is the chief architect of our POWERHA product. She and her team made a number of important contributions to IBM I 7.1. For example, support for V7000 and SVC in Technical Update 3. Now they are working actively on some of the most important new features in the next generation of IBM I and Powerha. As a leader in its technical field, her speech gives us a good prospect of a new high-availability feature that will be available in the near future through technology convergence.

The next meeting focus is how to meet the needs of our ISVs. The main developers responsible for the largest ISVs will discuss with us the needs of existing ISVs and how to improve IBM I to make it more competitive than the current platform for ISVs, for example, more competitive than the x86 platform. Kent Milligan, who also manages the ISV Advisory board, will help us understand the feedback from other, broader ISVs. By talking together, we want to see what these requirements have in common, which makes it easier for us to create plans that meet the needs of ISVs.

The most complex of these meetings is the discussion of how to integrate cloud-related products, POWERVM virtualization, storage, and SAN. There are some overlaps, but there are different needs in each area. How to get a high-level view while also addressing each of the key directions of their overall interaction will be a good technical challenge. But I'm sure our team will learn a lot from it.

These are just a few examples of how we plan carefully before the planning cycle. You can also look at some of the topics that we are currently considering by focusing on my Twitter.

Original link http://ibmsystemsmag.blogs.com/you_and_i/2012/07/strategy-updates-in-ibm-i-development.html

Original Author: Steve would

Translated by: Liu Yan