Ibm Systems Journal Impact Factor & Information

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

2015 Impact Factor Available summer 2016
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

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.
    Ibm Systems Journal 07/2008; 47(3):473-488. DOI:10.1147/sj.473.0473
  • [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.
    Ibm Systems Journal 02/2008; 47(1-47):29 - 39. DOI:10.1147/sj.471.0029
  • 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.
    Ibm Systems Journal 02/2008; 47(1-47):53 - 70. DOI:10.1147/sj.471.0053
  • [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.
    Ibm Systems Journal 02/2008; DOI:10.1147/sj.471.0167
  • [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.
    Ibm Systems Journal 02/2008; 47(3-47):433 - 443. DOI:10.1147/sj.473.0433
  • 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.
    Ibm Systems Journal 02/2008; 47(1-47):15 - 27. DOI:10.1147/sj.471.0015
  • [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.
    Ibm Systems Journal 02/2008; 47(4-47):681 - 694. DOI:10.1147/SJ.2008.5386522
  • 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.
    Ibm Systems Journal 02/2008; 47(3-47):357 - 376. DOI:10.1147/sj.473.0357
  • [Show abstract] [Hide abstract]
    ABSTRACT: This paper introduces, at a high level, the key topics relevant to continuous availability of IBM systems infrastructures. After defining terms and identifying what is encompassed in the scope of continuous availability of IBM system infrastructures, we explain the IT (information technology) life cycle of planning and execution through which an IT organization and its infrastructure pass to create and continuously improve the IT infrastructure. Throughout, we show how each of the subsequent papers in this issue, drawing on real-life deployments, technology developments, and research efforts, expands on important aspects of this introductory discussion.
    Ibm Systems Journal 02/2008; DOI:10.1147/SJ.2008.5386519
  • [Show abstract] [Hide abstract]
    ABSTRACT: High-availability service management (HASM) is defined as information technology (IT) service management that is designed to meet the business demand for availability of critical IT and IT-enabled business services. HASM requires the use of the Six Sigma method and analytical tools applied to key service management processes and services; event and incident monitoring and management design; high end and high-quality infrastructure and application configuration; high-availability (HA) architecture and design; and special solutions that implement HA patterns and associated technologies. In this paper, we examine HASM and discuss the process flow for designing and implementing HA technologies.
    Ibm Systems Journal 02/2008; DOI:10.1147/SJ.2008.5386521
  • [Show abstract] [Hide abstract]
    ABSTRACT: Challenges are emerging in testing service-oriented architecture (SOA) systems. Current testing is not sufficient to deal with the new requirements arising from several SOA features such as composition, loose coupling, and code without a graphical user interface. The most critical architecture information of an SOA solution is actually how services are composed and interact with each other. This paper proposes a gray-box testing approach, that is, an approach that involves having access to internal workings, data structures, and algorithms when designing the test cases but tests at the user level as a black box, that is, by applying inputs and observing outputs. This approach leverages business processes and the underlying SOA layered architecture to better test SOA solutions. A commonly used language to model business processes is BPEL (Business Process Execution Language), which is the focus of the approach described in this paper. Among the layered artifacts, the business process view represents the global behavior of the SOA system and thus is a good candidate as supplemental architectural information to the functional requirement or specification in test-case design and generation. This approach has three key enablers: test-path exploration, trace analysis, and regression test selection. BPELTester is an innovative tool that implements this method. It has been piloted in several projects and the initial pilot results are presented in this paper.
    Ibm Systems Journal 02/2008; 47(3-47):457 - 472. DOI:10.1147/sj.473.0457
  • [Show abstract] [Hide abstract]
    ABSTRACT: The current approach to the design, maintenance, and governance of service-oriented architecture (SOA) solutions has focused primarily on flow-driven assembly and orchestration of reusable service components. The practical application of this approach in creating industry solutions has been limited, because flow-driven assembly and orchestration models are too rigid and static to accommodate complex, real-world business processes. Furthermore, the approach assumes a rich, easily configured library of reusable service components when in fact the development, maintenance, and governance of these libraries is difficult. An alternative approach pioneered by the IBM Research Division, model-driven business transformation (MDBT), uses a model-driven software synthesis technology to automatically generate production-quality business service components from high-level business process models. In this paper, we present the business entity life cycle analysis (BELA) technique for MDBT-based SOA solution realization and its integration into service-oriented modeling and architecture (SOMA), the end-to-end method from IBM for SOA application and solution development. BELA shifts the process-modeling paradigm from one that is centered on activities to one that is centered on entities. BELA teams process subject-matter experts with IT and data architects to identify and specify business entities and decompose business processes. Supporting synthesis tools then automatically generate the interacting business entity service components and their associated data stores and service interface definitions. We use a large-scale project as an example demonstrating the benefits of this innovation, which include an estimated 40 percent project cost reduction and an estimated 20 percent reduction in cycle time when compared with conventional SOA approaches.
    Ibm Systems Journal 02/2008; 47(3-47):415 - 432. DOI:10.1147/sj.473.0415
  • [Show abstract] [Hide abstract]
    ABSTRACT: In this paper, we describe an approach to business processes and services which views work practices as recurrent patterns of communication called genres. Although defining work practices in this way is unorthodox, it provides two major advantages. First, the communication resources employed by the parties engaging in a service transaction can be clearly described, understood, and communicated. Business processes and services can be differentiated on the basis of the structural and functional arrangement of their constituent genres. This provides a view of a business process or service that is technology-independent. Second, using this approach means that work practices are defined contextually—an important consideration when trying to understand how business processes and services will influence organizations. Because genres are represented using directed graphs, prototypes can be developed to assist during the analysis of existing services and the design of new ones. Structural and functional change of genres can be used to reveal how a specific service is evolving within an organization. This enables us to determine if business demands have changed, something that is difficult to achieve using conventional service engineering approaches.
    Ibm Systems Journal 02/2008; 47(1-47):129 - 141. DOI:10.1147/sj.471.0129
  • [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.
    Ibm Systems Journal 02/2008; 47(4-47):641 - 652. DOI:10.1147/SJ.2008.5386508
  • 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.
    Ibm Systems Journal 02/2008; 47(3-47):445 - 456. DOI:10.1147/sj.473.0445