We take a great deal of pride in the accomplishments of our team members. Whenever contributions are made or are in progress, through publications or presentations, with the permission of the publisher, we present the articles here, with abstracts.
The Connection Series on Git for NonStop
A four-part series by Randall on Git for NonStop describing various topics relating to the Git Distributed Version Control System as it relates to NonStop in general and ITUGLIB in particular.
By the time the investigator was called, it was Tuesday, and forensic evidence was difficult to find. The production installation was scheduled at 2am, the previous Sunday. By the time the dust had settled, it was thirty hours later, and customers were not impacted, but nerves were shattered, and two managers and a director were cleaning out their desks. It was all going according to plan, and yet someone invoked the emergency 3am “Hero” procedure…
First in a series by Randall on Git for NonStop, this article describes the positive contribution that the git Software Configuration Management (SCM) solution, which originated in the LINUX community to manage its kernel, will make to the NonStop Community.
Version control technologies have evolved significantly since the 1970s, particularly as a result of workstation-based development. Processes and policies built around trying to manage how software flows to and from workstations is challenging. With flexible process enablers, like git, different approaches to this problem are available, which has unfortunately led to conflicting development cultures. In the git sub-culture, there is a core question t…
Part two on Git for NonStop, this article describes the level of detail that you might want to consider for storying your development activity.
Deploying changes through an organization requires well-defined processes. In today’s DVCS world, much of the process complexity can be automated so that changes appear in the right place at the right time.
Part three on Git for NonStop, this article describes the Software Change Backbone that you need to build in your company to move code in a timely fashion to the proper systems.
The sum of all fears is that your software has been compromised by a break-in because of hacking and poor role definition. Software stored in Git needs to be protected effectively and correctly.
Part four on Git for NonStop, this article describes the myths and fears about DVCS systems, including Git, and how to deal with solving the problems and those pesky fears.
This seminar addresses issues of launching and maintaining a Zero Latency Enterprise (ZLE), and the pitfalls of resting on an initially successful launch. The primary reason a company moves to a ZLE model is to more effectively serve their customers – both internal and external, including ERP and e-Commerce. But in the sea of Change, the potentially daunting task of ZLE can either serve to energize or paralyze a corporation. Fortunately, there are islands of calm that can help make ZLE an ongoing success. The session presents what is required of the business of rolling out solutions, including: budgets, resources, and scheduling; business and technical processes of developing and deploying solutions into an already operating ZLE; and managing suppliers and vendors.
The influence of John F. Kennedy can be felt forty years later in almost everything we do in computing. The massive logistics required to put a human on the moon required the development of new methodologies to manage intricacies and interrelationships never before seen. This article goes into how this relates to what we do and how we do it today in computing and technology from the lessons garnered from that project.
The purpose of this article is to help senior management understand the organizational structures, infrastructure, practices and procedures, and initial and ongoing decisions that need to be made to implement and maintain the Zero Latency Enterprise (ZLE). Obviously, the first question to ask is why are we interested in ZLE? The answer, not surprisingly, is to more effectively service your customers.
(Published as Are You Ready For The Zero Hour, Randall S. Becker, CIO Canada, September 2000)
Careful planning enables you to successfully manage the ongoing costs of the physical technological infrastructure (telephones, computers, and networks). For months, or years, however, you have watched software development budgets mount while user satisfaction drops and you’re having trouble reconciling the two. Outsourcing worked for a while, during the financial and Enterprise Resource Planning (ERP) system implementations, but it’s not working now that development has branched into custom solutions to deliver on your wisdom on how your business functions. You’ve just told your team that your company is now going to change one or more key subsystems to be developed in-house. This is known as back-sourcing, and it is a growing trend within companies whose primary business is not the development of software. This article lays out some of the key success-related issues you must address to take advantage of this trend.
(Published as Taking Back What Is Ours, Randall S. Becker, CIO Canada, December 1999)
Sometime after the ice retreated from Europe, Humanity started organizing into groups. In northern Africa, some of those transitioned from nomadic hunters into agricultural communities. Building architectures sprang up …
This is a fictional metaphor of how requirements become clouded.