Publications

Books / Chapters


E.D. Schabell. OpenShift Primer - Get your code into the Cloud,  Developer.Press, 3 December 2012, 978-1-909264-07-6 (e-book only).

Are you tired of requesting a new development machine for your application? Are you sick of having to setup a new test environment for your application? Do you just want to focus on developing your application in peace without 'dorking with the stack' all of the time? We hear you. We have been there too. Have no fear, OpenShift is here!
This book is all about getting you started, hands-on, with Red Hat OpenShift PaaS. It is developer focused, concentrating on getting you working on your code in the Cloud in the shortest amount of time. It is based on real world examples and covers all of the languages available to you in OpenShift.

[ iTunes Store ] [ Amazon Store ] [ Barnes & Noble ] [ DeveloperPress ] [ Google Play ]


E.D. Schabell, and S.J.B.A. (Stijn) Hoppenbrouwers. BPM Excellence in Practice 2010,  Financial Crisis Front Line: SNS BankFuture Strategies Inc., Lighthouse Point, FL, 2010, 978-0981987064.

SNS Bank (the Netherlands) has made a strategic decision to empower her customers on-line by fully automating her business processes. The ability to automate these service channels is achieved by applying Business Process Management (BPM) techniques to existing selling channels. Both the publicly available and internal processes are being revamped into full scale Straight Through Processing (STP) services. This extreme use of online STP is the trigger in a shift that is of crucial importance to cost effective banking in an ever turbulent and changing financial world. The key elements used in implementing these goals continue to be (Free) Open Source Software (FOSS), Service oriented architecture (SOA), and BPM. In this paper we will present an industrial application describing the efforts of the SNS Bank to make the change from traditional banking services to a full scale STP and BPM driven bank that can survive on the Financial Crisis front lines.


[ Download ]

E.D. Schabell, and S.J.B.A. (Stijn) Hoppenbrouwers. 2009 BPM & Workflow Handbook,  Financial Crisis Front Line: SNS BankFuture Strategies Inc., Lighthouse Point, FL, 2009, 0-9777527-9-8.

SNS Bank (the Netherlands) has made a strategic decision to empower her customers on-line by fully automating her business processes. The ability to automate these service channels is achieved by applying Business Process Management (BPM) techniques to existing selling channels. Both the publicly available and internal processes are being revamped into full scale Straight Through Processing (STP) services. This extreme use of online STP is the trigger in a shift that is of crucial importance to cost effective banking in an ever turbulent and changing financial world. The key elements used in implementing these goals continue to be (Free) Open Source Software (FOSS), Service oriented architecture (SOA), and BPM. In this paper we will present an industrial application describing the efforts of the SNS Bank to make the change from traditional banking services to a full scale STP and BPM driven bank that can survive on the Financial Crisis front lines.

[ Download ]


E.D. Schabell, and S.J.B.A. (Stijn) Hoppenbrouwers. Advances in Enterprise Engineering II, Empowering Full Scale Straight Through Processing with BPM. PRET 2009 / CAiSE 2009, Springer, New York, June, 2009, 3-642-01858-0.

The SNS Bank (the Netherlands) has made a strategic decision to empower her customers on-line by fully automating her business processes. The ability to automate these service channels is achieved by applying Business Process Management (BPM) techniques to existing selling channels. Both the publicly available and internal processes are being revamped into full scale Straight Through Processing (STP) services. This extreme use of on-line STP is the trigger in a shift that is of crucial importance to cost effective banking in an ever turbulent and changing financial world. The key elements used in implementing these goals continue to be (Free) Open Source Software (FOSS), Service oriented architecture (SOA), and BPM. In this paper we present an industrial application describing the efforts of SNS Bank to make the change from traditional banking services to a full scale STP and BPM driven bank.

[ Download ]


E.D. Schabell, E. Amrehn, J. Arndt, D. Bennin, M. Cathcart, R. Higson, C. Laking, R. Lewis, M. MacIsaac, S. Matuszewski, E. Ong, and H. Mertlens. Linux for S/390. September, IBM Corporation, International Technical Support Organization, Poughkeepsie, NY, 2000, 0-7384-1914-1.

The strengths of S/390 are well known: rock-solid reliability, the ability to run multiple diverse workloads, and highly scalable technology make S/390 an ideal choice for hosting key e-business applications. Now Linux has joined the S/390 family of operating systems, bringing a wealth of open source applications, middle-ware, and trained developers to help you respond to your business challenges quicker than ever before. This IBM Redbook is aimed at beginners and intermediate Linux users with a S/390 operating system background. It covers Linux for S/390 Marist distribution (2.2.15) and a pre-release of the SuSE Linux for S/390 distribution. At the time of writing, there was no distribution available from TurboLinux. The first four chapters offer an overview of Linux’s origin, how it fits into the IBM strategy, what open source means, and why using Linux for S/390 is significant from an IBM perspective. These chapters are also suitable as a management overview. The main part of the book will help you install Linux for S/390 in different environments. It discusses basic system administration tasks that can help you manage your Linux for S/390 system. It also introduces a wide range of services, such as Samba, NFS, and Apache. You will learn what each service is, what it is capable of, and how to install it. The services are not covered in detail, since they are very comprehensive; however, sources for more detailed information are documented.

[ Download ]


Conferences


P. van Bommel, B. van Gils, H.A. (Erik) Proper, E.D. Schabell, M. van Vliet, and Th.P. van der Weide. Towards and Information Market Paradigm. In: Forum proceedings of the 17th Conference on Advanced Information Systems 2005 (CAiSE 2005), Edited by: O. Belo, J. Eder, O. Pastor, and J. Falcao e Cunha. Pages: 27-32, June, FEUP, Porto, Portugal, EU, Porto, Portugal, EU, 2005, ISBN 9727520782.

This paper discusses the concept of information market. The authors of this paper have been involved in several aspects of information retrieval research. In continuing this research tradition we now take a wider perspective on this field, and position it as a market where demand for information meets supply for information.


B. van Gils, H.A. (Erik) Proper, P. van Bommel, and E.D. Schabell. Profile-based retrieval on the World Wide Web. In: Proceedings of the Conferentie Informatiewetenschap (INFWET2003), Edited by: P.M.E. de Bra. Pages: 91-98, 2003.

In this article we present a novel architecture for Information Retrieval on the Web called VIMES. This architecture is based on a broader definition of relevance. This broader definition lies in the fact that there is more then just topical relevance. Documents (or: resources) must also confirm to other constraints with regard to form, format and also things like price and quality.


B. van Gils, and E.D. Schabell. User-profiles for Information Retrieval. In: The 15th Belgian-Dutch Conference on Artificial Intelligence (BNAIC`03), Pages: 139-146, October, 2003.

In this position paper we will investigate a novel architecture for profile-based retrieval on the Web called Vimes. This architecture is based on the fact that resources found on the Web should not only be topically relevant to a searcher’s query; other characteristics (such as the file format or structural format) of a resource are equally important. Furthermore, Vimes uses profiles to deal with user characteristics and constraints.

Reports


E.D. Schabell, and S.J.B.A. (Stijn) Hoppenbrouwers. Empowering Full Scale Straight Through Processing with BPM. Technical report: ICIS-R08004, February, SNS Bank, 2009.

The SNS Bank (the Netherlands) has made a strategic decision to empower her customers on-line by fully automating her business processes. The ability to automate these service channels is achieved by applying Business Process Management (BPM) techniques to existing selling channels. Both the publicly available and internal processes are being revamped into full scale Straight Through Processing (STP) services. This extreme use of on-line STP is the trigger in a shift that is of crucial importance to cost effective banking in an ever turbulent and changing financial world. The key elements used in implementing these goals continue to be (Free) Open Source Software (FOSS), Service oriented architecture (SOA), and BPM. In this paper we present an industrial application describing the efforts of SNS Bank to make the change from traditional banking services to a full scale STP and BPM driven bank.


 E.D. Schabell. Taking a peek inside the cmlFramework. Technical report: ICIS-R07008, March, Radboud University Nijmegen, 2007.

This paper will walk you through a demonstration run of the Collaborative Modeling Lab (CML) Framework prototype. This will start with a conceptual overview of the component structure. The reader will then be walked through a processing run in which a Niam Normal Form (NNF) grammar is used to Filter a Logbook, produce a Contract, Distill this into an Essence, and finally using the Builder to generate an eventual Model in ORM.


E.D. Schabell, H.A. (Erik) Proper, and Th.P. van der Weide. IRIS Publication Management System - the first steps towards realization. Technical report: ICIS-R06008, December, Radboud University Nijmegen, 2006.

The IRIS Publication Management System (PMS) has been a long time in coming. It has been a wish of the IRIS department to have a single entry point for dealing with the publications created by its members. The complexities of not only accepting new submissions, but to process these submissions on through the existing institutional publication infrastructure is not a hurdle easily taken. The submission of both internal and external publications generates not only a collection of doc- uments, but also a very valuable and maybe useful repository of publication data. If this data were to be collected, protected from inconsistencies and properly organized then one would only be limited in her imagination as the the uses that it could be put. To start with, one can begin to pro vide a very interesting playground for departmental retrieval experiments, provide various forms of exportable formats (think of HTML, BiBTeX, text, etc.) and generate any type of organizational reporting as deemed necessary (such as yearly overviews of departmental publications). This document discusses the definition and design of the IRIS PMS This includes the motivation (why), the (functional) requirements (what), the key design principles as well as the actual design (how).


L. Klein Holte, M. Jansen, J. Mutter, and E.D. Schabell. It is about time for the AbTLinux dependency engine. Technical report: ICIS-R06013, February, Radboud University Nijmegen, 2006, A result of RE class of 2005/2006 student project.

This document describes the requirements for the ABout Time Linux dependency engine, a component of the AbTLinux package manager. These requirements were obtained by a student project group that participated in the Radboud University Nijmegen course called Requirements Engineering. This document represents the best results obtained from the six participating groups. The basis of the project flows from the main AbTLinux project goals. Clearly documented design, clear development goals leading to each release and just getting them done. Most members of the AbTLinux project have worked on other Linux distribution projects and have grown tired of working on badly documented designs. This requirements documents goal is to provide a structured and clear way of gathering information for the dependency engine project.


E.D. Schabell. ABout Time Linux - the requirements. Technical report: ICIS-R06021, May, Radboud University Nijmegen, 2006.

This document will detail a project that has risen from the desire to create a generic framework for managing the software on a Linux system. It is based on my experiences while working as a developer on a source-based Linux distribution spanning more than three years at the time of this writing. I hope to take my experiences as a developer and package maintainer to create this new package manager. I follow in the footsteps of a few pretty good existing projects such as (micropkg, 2004), (Easinstaller, 2004) and (SMGL, 2004), though I have found these to be lacking in some way or another.


E.D. Schabell. Touring the ICIS Publication Management System (PMS v1.2). Technical report: ICIS-R06031, November, Radboud University Nijmegen, 2006, Sources can also be found in CodeYard project repo.

The Publication Management System (PMS) was initially developed and deployed for usage by the IRIS department within the Radboud University Nijmegen. It was born from a wish to provide extensive services in managing and reporting our publications. This paper takes the reader through a tour of the current version of PMS, from the basic services available to any user, on to specific functionality for our institutes members, through the API and finally leaves the reader with some examples of how to use the more advanced features PMS provides.


E.D. Schabell, and B. van Gils. Implementing Vimes - the broker component. Technical report: ICIS-R05028, Radboud University Nijmegen, 2005.

This document will discuss the Vimes retrieval architecture broker component from the research project Profile Based Retrieval Of Networked Information Resources (PRONIR). It will provide an overview of the development process from requirements investigations done with use cases, on to the actual design and implementation.


E.D. Schabell. Building the PRONIR Conversion Clearinghouse. Technical report: NIII-R0317, Nijmegen Institute for Information and Computing Sciences, University of Nijmegen, Nijmegen, The Netherlands, EU, 2003.

As a vital part of the larger architecture, our document conversion system will need to provide for the transformation of documents to a requested format. The first step on the way to realizing this system is to gather all the various conversion routines in a central location. To achieve this, the Conversion Clearinghouse has been implemented to provide a means for anyone to submit her favorite conversion routines. Our Conversion Clearinghouse also allows anyone to browse through and pick out any of the collected conversions. The following report describes the design and implementation of the various elements that make up our Conversion Clearinghouse. This work is part of the ongoing research project Profile Based Retrieval Of Networked Information Resources (PRONIR).


E.D. Schabell. The DocConversion framework. Technical report: NIII-R0332, Nijmegen Institute for Information and Computing Sciences, University of Nijmegen, Nijmegen, The Netherlands, EU, 2003.

Continuing where the “PRONIR Conversion Clearinghouse” left off, this technical report presents the basic framework of the DocConversion tool. In its first phase our DocConversion tool will support single step document conversions, provide a Broker that negotiates the conversion process and a conversion Server. This is the first of three phases to be traversed on our way to a complete document conversion system. This work is part of the ongoing research project Profile Based Retrieval Of Networked Information Resources (PRONIR).


E.D. Schabell. Profile Based Retrieval Of Networked Information Resources, The Scientific Programmers Workshop. 2003.


E.D. Schabell. Resource Access in Generic Information Retrieval Systems. August, Vrije Universiteit, Amsterdam, Netherlands, 2002.

This thesis looks at the search for a generic information retrieval software architecture. I start with background information on the state of generic information retrieval, the organizations involved in this project and then explain the research goals that my thesis will attempt to reach. The requirements analysis is done through the use of interviews due to a lack of existing systems to examine. By lack of existing systems, I am referring to the lack of existing information retrieval architectures that allow for the modular construction of generic information retrieval systems. The modular construction is important to facilitate the building of research prototypes and this is missing in the existing information retrieval architectural solutions, which tend to focus on single solution domains. The requirements analysis resulted in the narrowing of my scope to resource access. An architectural reference model also grew out of the analysis and the next step was to expand this into a reference architecture. By using the requirements analysis as a starting point, three use cases were generated to use as a basis for creation of the reference architecture. A domain analysis using the three use cases made it possible to take a look at the possible features and a feature diagram was created to show their relationships. The resulting reference architecture was tested in a proof of concept by mapping these features to stubs and plug-ins using the use case map as a notational tool. The final software architecture is presented with stubs and various plug-ins used to denote the options used to fulfill both the functional and non-functional requirements that were set at the beginning of this project. This software architecture is explained and the conclusions are presented with a few suggestions for further development.