H(3)tren (3+) and H(4)tren (4+) fluoride zirconates or tantalates

Four new [H(3)tren](3+) or [H(4)tren](4+) fluoride zirconates and two new [H(3)tren](3+) fluoride tantalates are evidenced in the (ZrF4 or Ta2O5)-tren-HFaq.-ethanol systems at 190 degrees C: the structurally related phases [H(4)tren]center dot(Zr2F12)center dot H2O and alpha-[H(4)tren](center dot)(Zr2F12) (P2(1)2(1)2(1)). beta-[H(4)tren]center dot(Zr2F12) (P2(1/c)), [H(3)tren](4)center dot(ZrF8)(3)center dot 4H(2)O (123). beta-[H(3)tren](2)center dot(Ta3O2F16)center dot(F) (R32) and its monoclinic distortion alpha-[H(3)rren](2)center dot(Ta3O2F16)center dot(F) (C2/m). alpha and beta-[H(4)tren]center dot(Zr2F12) and [H(4)tren]center dot(Zr2F12)center dot H2O are built up from (Zr2F12) dimers of edge sharing ZrF7 polyhedra while isolated ZrF8 dodecahedra are found in [H(3)tren](4)center dot(ZrF8)(3)center dot 4H(2)O. Linear (Ta3O2F16) trimers build et and beta-[H(3)tren](2)center dot(Ta3O2F16)center dot(F); they consist of two (TaOF6) pentagonal bipyramids that are linked to two opposite oxygen atoms of one central (TaO2F4) octahedron. A disorder affects the equatorial fluorine atoms of the trimers and eventually carbon or nitrogen atoms of [H(3)tren](3+) cations. (C) 2011 Elsevier B.V. All rights reserved

2,4,6-Triamino-1,3,5-triazine-1,3-diium aqua­penta­fluoridoaluminate

The title compound, (C3H8N6)[AlF5(H2O)], was obtained by solvothermal synthesis from the reaction of aluminium hydroxide, 1,3,5-triazine-2,4,6-triamine (melamine), aqueous HF and water at 323 K for 48 h. The structure consists of [AlF5(H2O)]2− octa­hedra and diprotonated melaminium cations. Cohesion is ensured by a three-dimensional network of hydrogen bonds

Impact of comorbidity indexes on non-relapse mortality.

Comorbidity indexes (CI) have been reported to predict non-relapse mortality (NRM) and overall survival after allogeneic hematopoietic stem cell transplantation (HSCT) (Charlson's comorbidity index (CCI), hematopoietic cell transplantation CI (HCT-CI) and the pre-transplantation assessment of mortality (PAM) score). Which of these indexes best predict survival is unknown yet. We retrospectively studied 286 patients who underwent allogeneic HSCT. HCT-CI and PAM scores required grading according to pre-transplant pulmonary function tests (PFTs), which were lacking for some patients. We thus designed a reduced HCT-CI and an adjusted PAM, without results of PFTs. Using CCI, 25% of patients had indexes of 1 or more; median reduced HCT-CI score was 1; median adjusted PAM score was 24. The discriminative properties of the three CIs were rather low in our population. Comparison of patients and transplant characteristics between our and Seattle group's cohorts, however, revealed significant differences in more children, in more cord blood HSCT and in HSCT for Fanconi anemia in St Louis. Finally, multivariate analysis of scoring items revealed that age, matched unrelated or mismatched donor and hepatic disease were associated with NRM in our cohort. Translating use for patient's counseling or decision to proceed to transplant of these CIs will need prospective studies in a large independent cohort

Early stage adoption of ISO/IEC 29110 software project management practices: a case study

The ISO/IEC 29110 standard has at its core a Management and Engineering Guide [1] which are targeted at very small entities (enterprises, organizations, departments or projects) having up to 25 people [2], to assist them unlock the potential benefits of using standards which are specifically designed to address their needs. This paper discusses the role and structure of Project Management in the ISO/IEC 29110 standard and the design and development of project management support documentation. In particular this paper describes a case study of an early adopter of ISO/IEC 29110 project management practices and their experiences with implementing these in an industrial context

ROLES TRANSFORMATION WITHIN A SOFTWARE ENGINEERING MASTER BY IMMERSION

Learning the software engineering (SE) profession is a difficult task. Most SE professionals will say that they learned it “by doing”. Hence, the main paradigm used is teaching software engineering by doing. Most academic curricula address this issue through projects, but academic projects are not sufficient to achieve the goal. Beyond the SE learning, more general questions arise: how can we teach/learn engineering? What is a “long-term education”, particularly i

PLATYPUS : A STEP-based integration framework

STEP is an ISO standard (ISO-10303) for the computer-interpretable representation and exchange of product data. Parts of STEP standardize conceptual structures and usage of information in generic or specific domains. The standardization process of these constructs is an approach which can be applied to a data-based integration. Platypus is a STEP-based meta-environment. From the data integration point of view, the STEP technology is primarily used for management. A key point is the automatic generation of a SDAI (a functional interface for STEP-modelled database independently of any particular system and language). Then, at the end of the complex process of defining standardized conceptual structures for the applications to be integrated, the STEP framework will provide a seamless access to data of different applications. Moreover, Platypus can be used to the development of a specific metaenvironment intended to solve specific problems related to the legacy and new systems to be integrated.

Deploying lifecycle profiles for very small entities: an early stage industry view

The recently published ISO/IEC 29110 standard lifecycle profiles for very small entities has at its core a management and engineering guide [1] which is targeted at very small entities (enterprises, organizations, departments or projects) having up to 25 people [2], to assist them unlock the potential benefits of using standards which are specifically designed to address their needs. This paper will also outline this standard and the implementation of a series of pilot project initiative harnessing a set of detailed guidelines known as “Deployment Packages” to assist very small entities in understanding and exploring the potential usage of an international software process standard. This paper will address issues of small entities needs, industry reaction to early pilot projects and highlight the needs for a light weight process assessment mechanism to meet the needs of very small entities and complement this new lifecycle standard

Forward engineering and early model validation with Smalltalk

International audienceSince more than two decades, a lot of work has been achieved around Model Driven Engineering (MDE). One of the main goals of MDE is to improve the software development process productivity thanks to a generative approach. Many MDE environments are available today. These environments allow a designer to specify object oriented meta-models. Meta-models structure can be specified through the definition of statically typed entities and entities relationships. Even if some of these environments also enable specifying meta-model invariants and behavior, two important issues remain unsolved: – regarding meta-model execution, only limited capabilities are exhibited and the development process still relies on code generation into a mainstream language for validation; – because of the generative approach, no causal connection is possible between a meta-model and its conforming models. To deal with these issues, we decided to use Smalltalk as a MDE environment mainly because it provides us with a way of implementing meta-model execution. A Smalltalk system can be used as a modeling system providing out-of-the-box an infrastructure for meta-modeling, browsing, and testing. It also provides a rich system which enables implementing realistic prototypes. Moreover Smalltalk implements a Meta Object Protocol which maintains a causally connected modeling architecture. Smalltalk is known as very powerful for the agile implementation of systems, for continuous testing and finally for early validation through prototyping. Unfortunately, Smalltalk is not a mainstream language and can be rarely used as the final platform. This article shows that it is possible to successfully use Smalltalk as a MDE environment even if the target system is not implemented in Smalltalk. Indeed, the software development process can be adapted to benefit from early validation and to be able to automatically produce or update a target system. For validation purpose, we have developed the Platypus tool, which enables static typing in Smalltalk and makes this MDE approach possible