Ibm Systems Journal (IBM SYST J)

Publisher: International Business Machines Corporation

Journal description

The IBM Systems Journal is a quarterly, refereed technical publication, featuring the work of authors from systems and software fields in information science and the computer industry. The papers are written for a technically aware readership in the software and systems professional community worldwide: technical professionals, researchers, and users. Each paper is peer-reviewed for content, currency, and value by recognized experts in the field. The Web version of the journal is free but the printed version has a subscription fee.

Current impact factor: 1.79

Impact Factor Rankings

2016 Impact Factor Available summer 2017
2010 Impact Factor 1.792
2009 Impact Factor 1.289
2008 Impact Factor 1.883
2007 Impact Factor 1.214
2006 Impact Factor 0.747
2005 Impact Factor 1.255
2004 Impact Factor 1.636
2003 Impact Factor 1.97
2002 Impact Factor 1.128
2001 Impact Factor 0.729
2000 Impact Factor 0.635
1999 Impact Factor 0.492
1998 Impact Factor 0.71
1997 Impact Factor 0.48
1996 Impact Factor 0.452
1995 Impact Factor 0.5
1994 Impact Factor 0.461
1993 Impact Factor 0.253
1992 Impact Factor 0.441

Impact factor over time

Impact factor
Year

Additional details

5-year impact 1.98
Cited half-life 8.60
Immediacy index 0.00
Eigenfactor 0.00
Article influence 0.38
Website IBM Systems Journal website
Other titles IBM systems journal, International business machines systems journal
ISSN 0018-8670
OCLC 1445487
Material type Periodical, Internet resource
Document type Journal / Magazine / Newspaper, Internet Resource

Publications in this journal

  • [Show abstract] [Hide abstract]
    ABSTRACT: Most organizations understand the need to address service-oriented architecture (SOA) governance during SOA adoption. An abundance of information is available defining SOA governance: what it is and what it is not, why it is important, and why organizational change must be addressed. Increasingly business and information technology (IT) stakeholders, executive and technical, acknowledge that SOA governance is essential for realizing the benefits of SOA adoption: building more-flexible IT architectures, improving the fusion between business and IT models, and making business processes more flexible and reusable. However, what is not clear is how an organization gets started. What works and what does not work? More importantly, what is required in SOA governance for organizations to see sustained and realized benefits? This paper describes a framework, the SOA governance model, that can be used to scope and identify what is required for effective SOA governance. Based on client experiences, we describe four approaches to getting started with SOA governance, and we describe how to use these four approaches to make shared services (services used by two or more consumers), reuse, and flexibility a reality. We also discuss lessons learned in using these four approaches.
    No preview · Article · Jul 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: The increasing market demand for systems characterized by low-latency, deterministic behavior and the emphasis on the use of commodity hardware and software have led to a new breed of real-time operating systems (OSs), known as enterprise real-time OSs. In response to the demand for accelerated access to such features in a Linux™ kernel, the IBM Linux and Java™ Technology Centers collaborated to provide the first commercially available enterprise real-time Linux kernel with real-time Java support. Extending the PREEMPT RT patch from Ingo Molnar of Red Hat, Inc., the kernel contains additional features that were required to meet the demands of enterprise real-time OS customers. This paper describes how IBM developers helped to direct, implement, and test the real-time Linux kernel, bringing it from software patches to a finished product in nine months.
    No preview · Article · Apr 2008 · Ibm Systems Journal
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: This paper introduces responsive systems: systems that are real-time, event-based, or time-dependent. There are a number of trends that are accelerating the adoption of responsive systems: timeliness requirements for business information systems are becoming more prevalent, embedded systems are increasingly integrated into soft real-time command-and-control systems, improved message-oriented middleware is facilitating growth in event-processing applications, and advances in service-oriented and component-based techniques are lowering the costs of developing and deploying responsive applications. The use of responsive systems is illustrated here in two application areas: the defense industry and online gaming. The papers in this special issue of the IBM Systems Journal are then introduced. The paper concludes with a discussion of the key remaining challenges in this area and ideas for further work.
    Preview · Article · Apr 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: This paper presents a conceptual model of an event-processing network for expressing the event-based interactions and event-processing specifications among components. The model is based on event-driven architecture, a pattern promoting the production, detection, consumption, and reaction to events. The motivation is the lack of standardization in the areas of configuring and expressing the event-processing directives in event-driven systems. Some existing approaches are through Structured Query Language, script languages, and rule languages, and are executed by standalone software, messaging systems, or datastream management systems. This paper provides a step toward standardization through a conceptual model, making it possible to express event-processing intentions independent of the implementation models and executions. It is a unified model serving as a metamodel to these existing approaches.
    No preview · Article · Apr 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: We apply pattern language methodology to describe design and integration patterns for real-world-aware and real-time solutions, i.e., software solutions that integrate business information processing with sensor and actuator manipulations of the external world. Efficient engineering of such solutions depends on the definition and reuse of components whose real-time characteristics can be specified. Other nonfunctional characteristics, such as throughput and reliability, may also be constrained and critical for correct behavior of a design element. We present a pattern language comprising a basic catalog of design patterns for component-based real-time solutions.
    No preview · Article · Apr 2008 · Ibm Systems Journal
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Read-copy update (RCU) is a synchronization mechanism in the Linux TM kernel that provides significant improvements in multiprocessor scalability by eliminating the writer-delay problem of readers-writer locking. RCU implementations to date, however, have had the side effect of expanding non-preemptible regions of code, thereby degrading real-time response. We present here a variant of RCU that allows preemption of read-side critical sections and thus is better suited for real-time applications. We summarize priority-inversion issues with locking, present an overview of the RCU mechanism, discuss our counter-based adaptation of RCU for real-time use, describe an additional adaptation of RCU that permits general blocking in read-side critical sections, and present performance results. We also discuss an approach for replacing the readers-writer synchronization with RCU in existing implementations. INTRODUCTION In this paper we focus on environments in which real-time applications are running on shared-mem-ory multiprocessor systems with the Linux** oper-ating system. Such environments require both real-time response and multiprocessor scalability. Real-time response means that the hardware and the operating system perform within real-time con-straints; that is, the response times to certain events are subject to operational deadlines. Multiprocessor scalability means that the system can process growing amounts of work when the level of multiprocessing is proportionally increased. Tech-niques exist for meeting these requirements inde-pendently, but real-time response is often attained at the expense of multiprocessor scalability, and vice versa. Given the recent advent of low-cost multi-processor systems, techniques that address both requirements are now needed.
    Preview · Article · Apr 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: Telecommunications service providers (TSPs) are currently faced with a significant number of threats to their core business models. In addition to competition from traditional TSPs, they must also face increasing competition from Internet service providers such as Google, Yahoo!, and eBay, which have succeeded in implementing a variety of very useful communications services, including voice services, for a fraction of the traditional cost. This new set of threats is causing TSPs to reexamine their business models, explore ways of reducing their operational expenses, and devise a means of reducing the typical service life cycle (from concept to delivery, typically more than a year) to a few weeks. To help address these issues, IBM has created an SOA-centric (service-oriented-architecture-centric) reference architecture called the telecommunications service delivery platform (SDP). In this paper, we present three case studies involving field deployments to the networks of three major wireless TSPs and describe the role of the IBM SDP and its key benefits. We highlight the architecture and key use cases involved in these carrier-grade deployments, and articulate the best practices and valuable lessons gleaned from them.
    No preview · Article · Feb 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: Designing and implementing a business resilience (or disaster recovery) plan is a complex procedure for customers, and the impact of implementing an incorrect or incomplete plan can be significant. For some customers, being able to recover their data center functionality in a short period of time may be of the utmost importance; for others, recovering in a short period of time may be worthless if the data with which their database is restored is hours or days old. Also of importance is the impact to business-critical applications when copies of data are being made. This paper presents the IBM TotalStorage™ Productivity Center for Replication (TPC-R), a tool designed to help customers implement cost-effective data replication solutions for continuous availability and disaster recovery. We give an overview of TPC-R, describe recent enhancements to TPC-R that are available on all supported platforms (as well as those that are unique to the z/OS™ platform) and discuss the ways in which customers can exploit TPC-R to implement business resilience solutions, with a focus on the various trade-offs customers must consider when choosing between different storage replication technologies.
    No preview · Article · Feb 2008 · Ibm Systems Journal
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: The primary objective of service-oriented architecture (SOA) is to use information technology to address the key goals of business today: innovation, agility, and market value. Agility in SOA is achieved by use of the principles of encapsulation, modularity, and loose coupling, which facilitates a cleaner separation of concerns. While loose coupling enables customers to rapidly reuse services in new applications, strong coherency must be maintained to achieve the primary business objectives of the application. When applications are composed of loosely coupled services that are independent (owned by different parts of the organization, based on disparate technology assumptions, and evolving on independent schedules and with diverse priorities) the coherency of the composite application can be undermined. In this paper, we examine how coherency can be created and maintained in loosely coupled applications. We examine, in this context, various techniques and design approaches, such as service management, the use of service buses, the role of industry models and semantic ontologies, and governance, to achieve and maintain coherency of composite applications using SOA.
    Preview · Article · Feb 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: Providers of highly reliable information technology (IT) services have historically adopted multiple service delivery quality standards and have obtained certificates of registration or certification associated with these standards. In this paper, we present a case study involving a provider of IT infrastructure services and solutions. We describe the business context of the service provider, its approach to the analysis of the requirements of multiple standards, process integration efforts (both local and global), and the reuse of documentation and other evidentiary data in the context of obtaining certificates of registration or certifications. We compare the evidentiary data (e.g., documentation, observations, and interviews) used in the diagnostics of the International Standards Organization 9001:2000 standard and the eSourcing Capability Model for Service Providers standard to evaluate the unique value that each standard contributes to IT service delivery. The case study also provides initial examples of measures resulting from the adoption of these two quality standards that may be used to improve service delivery.
    No preview · Article · Feb 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: For a service delivery system to produce optimal solutions to service-related business problems, it must be based on an approach that involves many of the traditional functional areas in an organization. Unfortunately, most business school curricula mirror the older traditional organizational structure that dominated businesses throughout most of the twentieth century. This structure typically consisted of vertically organized functions (or silos), such as production, marketing, and finance, with each silo operating largely independently of the others. Similarly, business schools today are usually organized by functional departments—such as marketing, finance, accounting, and operations management—with little interaction among them. Within this traditional silo-structured environment, it is very difficult to properly develop a curriculum, or even a course, in service management. Consequently, a significant gap exists between the education received by business school graduates and the skills that they need to succeed in today's service-intense environment. This paper explores the underlying causes of this gap and suggests ways in which the emerging field of service science can facilitate the changes in business school curricula that will make them more relevant in meeting the needs of today's businesses and organizations.
    No preview · Article · Feb 2008 · Ibm Systems Journal
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: This paper relates our experiences at the University of California, Berkeley (UC Berkeley), designing a service science discipline. We wanted to design a discipline of service science in a principled and theoretically motivated way. We began our work by asking, “What questions would a service science have to answer?” and from that we developed a new framework for understanding service science. This framework can be visualized as a matrix whose rows are stages in a service life cycle and whose columns are disciplines that can provide answers to the questions that span the life cycle. This matrix systematically organizes the issues and challenges of service science and enables us to compare our model of a service science discipline with other definitions and curricula. This analysis identified gaps, overlaps, and opportunities that shaped the design of our curriculum and in particular a new survey course that serves as the cornerstone of service science education at UC Berkeley.
    Preview · Article · Feb 2008 · Ibm Systems Journal
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: This paper explores how service value is created in a network context and how the structure and dynamics of the value network as well as customer expectations influence the complexity of the services ecosystem. The paper then discusses what transformative role information and communication technology (ICT) plays in coordinating and delivering value and managing this complexity. A conceptual model is developed for understanding and investigating the nature, delivery, and exchange of service value and assessing the complexity of a service value network. Three central arguments are presented. First, value in the services economy is driven and determined by the end consumer and delivered through a complex web of direct and indirect relationships between value network actors. Second, the complexity of service value networks not only depends on the number of actors but also on the conditional probabilities that these actors are involved in delivering the service to the consumer. Third, ICT plays a central role in reducing complexity for consumers by providing greater levels of value network integration, information visibility, and means to manage and anticipate change.
    Preview · Article · Feb 2008 · Ibm Systems Journal
  • [Show abstract] [Hide abstract]
    ABSTRACT: A common problem observed on mainframe installations, and one which presents a significant challenge for resiliency and high availability, involves soft failure incidents. n contrast to catastrophic failures, soft failures involve some degree of system shutdown without an obvious cause. This has been described with the phrase: “Systems don't break; they just stop running, and we don't know why.” Extending a medical paradigm, this paper proposes a new method for solutions deployed on IBM z/OS™ systems to respond when either the system or the application stops running. The current approach is to treat the “disease,” by determining the cause of he problem and taking action to prevent its recurrence. The new approach is to determine whether the system or application is behaving abnormally, identify the cause of this abnormal behavior, and take action to treat the “symptom.” This new approach uses machine learning and mathematical modeling to identify normal behavior, enabling the detection of abnormal behavior before it impacts the customer. Based on an analysis of critical problems and preliminary modeling work, the types of abnormal behavior identified are assigned to broad categories. In this paper, we describe the progress being made to address the challenge of soft failures by implementing this new paradigm.
    No preview · Article · Feb 2008 · Ibm Systems Journal
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: The complexity that telecommunications companies are faced with in their business processes and their information technology (IT) systems is especially apparent in their billing systems. These systems are required not only to handle large volumes of data and frequent changes in business rules, but also to ensure that the billing be done accurately and on time. This paper describes a solution that was developed to address this problem. It consists of an operations support system that is compliant with NGOSS (Next Generation Operations System and Software) and it implements a service-oriented architecture (SOA) that relies on an enhanced enterprise service bus (ESB). This enhanced ESB, referred to here as an adaptable service bus (ASB), makes it possible to carry out changes to business rules at runtime, thus avoiding costly shutdowns to the billing application. An implementation of this system has been operational in ChungHwa Telecom Company, Taiwan, since January 2008 and provides complete support to its billing application. As a result, the billing process cycle time has been reduced from 10–16 days to 3–4 days, which cleared the way for further growth of the business.
    Preview · Article · Feb 2008 · Ibm Systems Journal