By 2020, the EU aims to have 10% of the transport fuel of every EU countries come from renewable sources such as biofuels. Fuel suppliers are also required to reduce the greenhouse gas intensity of the EU fuel mix by 6% in comparison to 2010. The thermophysical properties of biofuels are, therefore, required for the efficient design of every step in their production, distribution, and utilization. Despite of these needs, high pressure thermodynamical characterization of biofuels is not still exhaustive. Next generation injection systems work with pressure up to 300 MPa, but available measurements are limited to 200 MPa. Measurements extrapolation generally are not recommended at these pressure because it can hide freezing phenomena here documented at temperature of (20 and 30) degrees C. In this work, density and viscosity of pure and blended FAME (SME and RME) biofuels have been measured up to 300 MPa. Since the scope of the work is both to investigate cold start conditions found in engines and the thermal behaviour of fuels in tanks of cars, petrol station and dispenser, the temperature interval is limited to (0-60) degrees C. In particular, it has been observed a partial freezing even for temperature up to 30 degrees C. Density and viscosity values were obtained by direct experimental measurements, while heat capacities have been calculated using density and speed of sound results previously obtained. At ambient pressure conditions, the uncertainty in density measurements was between 0.005% and 0.01% (k=2) and for viscosity measurements the uncertainty was between 0.2% and 1.3% (k=2). At elevated pressures the uncertainty in density measurements was 0.08% (k=2), while for viscosity and heat capacity it was 2% (k=2). (C) 2016 Elsevier Ltd. All rights reserved.

Salinity is a key variable in the modelling and observation of ocean circulation and ocean-atmosphere fluxes of heat and water. In this paper, we examine the climatological relevance of ocean salinity, noting fundamental deficiencies in the definition of this key observable, and its lack of a secure foundation in the International System of Units, the SI. The metrological history of salinity is reviewed, problems with its current definitions and measurement practices are analysed, and options for future improvements are discussed in conjunction with the recent seawater standard TEOS-10.

Water in its three ambient phases plays the central thermodynamic role in the terrestrial climate system. Clouds control Earth's radiation balance, atmospheric water vapour is the strongest 'greenhouse' gas, and non-equilibrium relative humidity at the air–sea interface drives evaporation and latent heat export from the ocean. On climatic time scales, melting ice caps and regional deviations of the hydrological cycle result in changes of seawater salinity, which in turn may modify the global circulation of the oceans and their ability to store heat and to buffer anthropogenically produced carbon dioxide. In this paper, together with three companion articles, we examine the climatologically relevant quantities ocean salinity, seawater pH and atmospheric relative humidity, noting fundamental deficiencies in the definitions of those key observables, and their lack of secure foundation on the International System of Units, the SI. The metrological histories of those three quantities are reviewed, problems with their current definitions and measurement practices are analysed, and options for future improvements are discussed in conjunction with the recent seawater standard TEOS-10. It is concluded that the International Bureau of Weights and Measures, BIPM, in cooperation with the International Association for the Properties of Water and Steam, IAPWS, along with other international organizations and institutions, can make significant contributions by developing and recommending state-of-the-art solutions for these long standing metrological problems in climatology.

Agile methods like eXtreme Programming (XP, cf. [2]) are grass rooted. They derive from practicioneers and focus on their needs. Therefore, at the beginning, project controlling was not in the focus of agile methods. The paper shows how to integrate simple mechanisms for project controlling. These mechanisms address both developers and management needs.

Using methodological extensions to adapt extreme programming (XP) for major projects offers a high security and reliability without limiting software development's advantages. The authors describe their use of XP extensions that focus on development's planning and controlling aspects, demonstrating that a suitably adapted agile development process is applicable to long-term, large-system projects.

From the Publisher: Real-life experience of eXtreme Programming from XP programmers. eXtreme Programming (XP) is a hot new development methodology for building software systems quickly without sacrificing quality. Authors Lippert, Wolf and Rook have three years' experience of working on professional XP projects. The projects range from application via prototype to framework development and cover project sizes from one person month to more than 400 person months. Until now XP has been described in outline by those promoting its advantages, this book provides objective examples of how it can be used in practice. An objective assessment of XP, grounded in real world experience, and not written by those championing this methodInvaluable combination of theory and practiceCovers advanced topics such as project organization, team roles and integrating legacy systems

Publisher UPGRADE is published on behalf of CEPIS (Council of European Professional Informatics Societies, http://www.cepis.org/) by Novática (http://www.ati.es/novatica/) and Informatik/Informatique (http://www.svifsi.ch/revue/) Chief Editors François Louis Nicolet, Zurich Rafael Fernández Calvo, Madrid Editorial Board Prof. Wolffried Stucky, CEPIS President Gloria Nistal Rosique and Rafael Fernández Calvo, ATI Prof. Carl August Zehnder and François Louis Nicolet, SVI/FSI English Editors: Mike Andersson, Richard Butchart, David Cash, Arthur Cook, Tracey Darch, Laura Davies, Nick Dunn, Rodney Fennemore, Hilary Green Roger Harris, Michael Hird, Jim Holder, Alasdair MacLeod, Pat Moody, Adam David Moss, Phil Parkin, Brian Robson Cover page designed by Antonio Crespo Foix, © ATI 2002 Layout: Pascale Schürmann E-mail addresses for editorial correspondence: and E-mail address for advertising correspondence: Copyright © Novática and Informatik/Informatique. All rights reserved. Abstracting is permitted with credit to the source. For copying, reprint, or republication permission, write to the editors. The opinions expressed by the authors are their exclusive responsibility. The European Online Magazine for the IT Professional http://www.upgrade-cepis.org Vol. III, No. 2, April 2002

We started using the XP techniques for designing and implementing the JWAM framework since the beginning of 1999. With the help of these techniques we succeeded in evolving the JWAM framework from a „student’s project“ into a real-life professional application framework which is used in several commercial applications today. In this paper we report on our experiences with XP in general and with XP for framework development in particular for more than one year. The following sections describe how we use the XP techniques and how we have adapted them to our specific programming domain – the development of application frameworks for large-scale application software. This paper also discusses some of the problems encountered during XP and their potential solutions. History of JWAM JWAM is a Java framework supporting the development of large scale interactive software systems according to the tools & materials approach . T e foundation of the JWAM framework was laid in 1997 by research assistants and students of the Software Engineering Group at the University of Hamburg and it was a pure University project. We used it as a sandbox for gaining some experience with new concepts and with framework development in general. We also used it for teaching purposes. In 1998 we felt that JWAM had the potential for professional software development. We thought it to be a solid technical base for large-scale software development giving support to developers with a proven design. Important steps to commercialize the framework were a redesign of parts of the framework and the explicit definition of a framework development process and its management. Early in 1999 we began to use XP techniques in a team of seven framework developers and redesigned parts of the framework. First, we used refactoring (cf. [Opdyke92], [Fowler99]), pair programming (cf. [Beck99]) and test classes ([Firesmith96], [Junit99]). Then we added the planning game and continuos integration (cf. [Beck99]). The redesign of the framework had one major goal: simplifying the framework. With this goal in mind we refactored the framework and introduced a separation of the framework core from framework components based on this core. Before we began refactoring there was one framework compound with more than 600 classes. After refactoring we had a framework kernel with about 100 classes plus test classes. The rest of the original classes were divided into separate framework components or had become useless during the refactoring process. 1 WAM is the German acronym for tools, automatons, materials. More information about WAM can be found in [RiehleZüllighoven95]. The framework can be downloaded from [JWAM]. Now, in January 2000 three application projects use JWAM. Two of these projects have already shipped operational client/server applications based on JWAM. We use all of the XP techniques and we were quite successful in introducing them to our team. Of course we had to adapt some of the techniques to our situation. Currently, we further develop the JWAM framework in pairs only and nearly every framework class has a test class. If you want to know more about the JWAM framework take a look at [JWAM]. The Setting The JWAM framework is both rooted in the university and has its commercial context. Within the university we use JWAM for teaching and as a sandbox for trying out new concepts. Within the commercial context we have founded the Apcon Workplace Solutions Ltd. The company uses JWAM for professional application development. This combination of an academic and industrial setting gives us the chance to use leading edge concepts in commercial projects very fast. On the other hand the requirements of the industrial projects trigger the research activities at the university. Figure 1 shows the business use case for the development and usage of the JWAM framework. Note that the different actors may map to the same persons.

XP has one weakness when it comes to complex application domains or difficult situations at the customer’s organization: the customer role does not reflect the different interests, skills and forces with which we are confronted in devel opment projects. We propose splitting the customer role into a user and a client role. The user role is concerned with domain knowledge; the client role defines the strategic or business goals of a development project and controls its financial resources. It is the developers’ task to integrate users and clients into a project that builds a system according to the users’ requirements, while at the same time attain the goals set by the client. We present document types from the Tools&Materials approach (cf. [6]) which help developers to integrate users and clients into a software project. All document types have been used successfully in a number of industrial projects together with the well-known XP practices.

Companies have to adapt to changing environments and business requirements in short cycles. They seek to address their customers via various channels involving new (net-based) technologies. This poses an interesting question: How can we support multiple channels with various user front ends without at the same time duplicating business functionality? We present an elegant solution in the form of an architectural approach based on so-called domain services. Domain services are related to core business functions or concepts and they abstract from any type of UI (user interface) or interaction style. Domain services also are independent of database systems, concrete work flows and technical prerequisites like host systems. When designing domain services, we focus on the tasks of an application domain because they are the most stable elements in enterprises. The core tasks of an enterprise remain the same as long as an organization stays in its business domain. However, the concrete work flows at the different workplaces and the (technical) front ends of the application systems will change. Consequently, it is important to identify the underlying tasks and model them as "faceless" services. Thus, one domain service can be combined with various channels, their user front ends and interaction styles may differ. Such a service may even be used by other software applications of business partners within the net of a virtual company. This paper discusses business-oriented as well as technical implications and solutions. We present our architectural design and concrete experiences gained from professional software projects.

One problem with the XP development process is its fragility. If developers use the XP techniques in an unintended way or not at all, the XP process is likely to break down: The misused techniques affect the other XP techniques in a negative way, breaking the whole process. We believe that it is possible to stabilize the XP process using specialized artifacts to reify the XP techniques. We discuss the reification of the XP technique Continuous Integration using the JWAM IntegrationServer as an example. We present our experience with this tool and analyze its effects on the other XP techniques.

Chemie Ingenieur TechnikVolume 71, Issue 6 p. 602-605 Wissenschaftliche Kurzmitteilungen Auslegung und Scale up bei der Produktion von Tabletten auf der Basis von Direkttablettierhilfsmitteln† Dr.-Ing. Heike Schuchmann, Dr.-Ing. Heike Schuchmann NESTLÉ PRODUCT & TECHNOLOGY CENTER ORBE, CH-1350 OrbeSearch for more papers by this authorDr.-Ing. Reinhard Polke, Dr.-Ing. Reinhard Polke BASF-AG, ZAT/P, D-67056 LudwigshafenSearch for more papers by this authorIng.(Grad) Robert Heinz, Ing.(Grad) Robert Heinz BASF-AG, ZAT/P, D-67056 LudwigshafenSearch for more papers by this authorDr. Karl Kolter, Dr. Karl Kolter BASF-AG, ME/DP, D-67056 LudwigshafenSearch for more papers by this authorDipl.-Ing. Henning Wolf, Dipl.-Ing. Henning Wolf DANONe, D-97199 OchsenfurtSearch for more papers by this author Dr.-Ing. Heike Schuchmann, Dr.-Ing. Heike Schuchmann NESTLÉ PRODUCT & TECHNOLOGY CENTER ORBE, CH-1350 OrbeSearch for more papers by this authorDr.-Ing. Reinhard Polke, Dr.-Ing. Reinhard Polke BASF-AG, ZAT/P, D-67056 LudwigshafenSearch for more papers by this authorIng.(Grad) Robert Heinz, Ing.(Grad) Robert Heinz BASF-AG, ZAT/P, D-67056 LudwigshafenSearch for more papers by this authorDr. Karl Kolter, Dr. Karl Kolter BASF-AG, ME/DP, D-67056 LudwigshafenSearch for more papers by this authorDipl.-Ing. Henning Wolf, Dipl.-Ing. Henning Wolf DANONe, D-97199 OchsenfurtSearch for more papers by this author First published: 03 February 2004 https://doi.org/10.1002/cite.330710611 † Vorgetragen bei der GVC-Fachausschußsitzung Agglomeration, 12./14. Mai 1997 in Weihenstephan. AboutPDF ToolsRequest permissionExport citationAdd to favoritesTrack citation ShareShare Give accessShare full text accessShare full-text accessPlease review our Terms and Conditions of Use and check box below to share full-text version of article.I have read and accept the Wiley Online Library Terms and Conditions of UseShareable LinkUse the link below to share a full-text version of this article with your friends and colleagues. Learn more.Copy URL Share a linkShare onEmailFacebookTwitterLinkedInRedditWechat Literatur 1 SCHMIDT, P. C.; RUBENSDÖRFER, C. J. W. Evaluation of Ludipress as a „Multipurpose Exipient”︁ for Direct Compression. Part I: Powder Characteristics and Tableting Properties, Part II: Interactive Blending and Tableting with Micronized Glibenclamid, Drug Dev. Ind. Pharm. 20 (1994) 18, S. 2899/2925, S. 2927/2952. 2 SELMECZI, B.; LÉNÁRT, J. Der Einfluß von Form und Größe der Tabletten auf einige physikalische Eigenschaften, Pharmazie 23 (1968) 10, S. 577/578. 3 LERK, C. F. Consolidation and Compaction of Lactose, Drug Dev. Ind. Pharm. 19 (1993) S. 2359/2398. 4 VAN KAMP, H. V.; BOLHUIS, G. K.; KUSSENDRAGER, K. D.; LERK, C. F. Studies on Tableting Properties of Lactose, Int. J. Pharm. 28 (1986) S. 229/238. 5 MBALI-PEMBA, C.; CHULIA, D. Lactose Texture Monitoring During Compaction 1. Mechanical Properties and Texture Parameters, Drug Dev. Ind. Pharm. 21 (1995) 2, S. 199/214. 6 VROMANS, H.; BOLHUIS, G. K.; LERK, C. F.; KUSSENDRAGER K. D. Studies of Tabletting Properties of Lactose, IX The Relationship between Particle Structure and Compactibility of Cristalline Lactose, Int. J. Pharm. 39 (1989) S. 207/220. 7 WHITEMAN, M.; YARWOOD, R. J. The Evaluation of Six Lactose-based Materials as Direct Tablet Excipients, Drug Dev. Ind. Pharm. 14 (1988) 8, S. 1023/1040. 8 Technisches Merkblatt Ludipress,BASF AG, Ludwigshafen 1990. Volume71, Issue6June 1999Pages 602-605 ReferencesRelatedInformation

Die Anbindung von Benutzungsoberflachen mit Hilfe von GUI-Toolkits hort sich in der Theorie ganz einfach an, bereitet in der Praxis jedoch haufig Probleme. In diesem Papier wird eine Kapselung in Interaktions- und Prasentationsformen vorgeschlagen, mit deren Hilfe von der konkreten Realisierung derart abstrahiert werden kann, da? bei der Entwicklung Interaktiver Systeme lediglich uber den Umgang reflektiert, nicht aber die konkrete Realisierung berucksichtig werden mu?. Es ergibt sich als Moglichkeit fur den Weiterentwicklung sogar eine getrennte Modifizierbarkeit der Oberflache, ohne die eigentlichen Umgangsformen zu tangieren.