893 resultados para Unified Enterprise
Resumo:
Construcció d'una aplicació web a partir de les especificacions d'un client imaginari. Estudi i utilització del mètode Rational Unified Process, el més habitual actualment en la construcció de software. Disseny d'una base de dades i implementació del model lògic mitjançant un SGBD punter al mercat com Oracle.
Resumo:
Aquest Treball Final de Carrera té per objecte l'anàlisi, disseny i implementació d'una aplicació degestió de menjadors escolars. Aquesta aplicació neix de la necessitat de donar resposta a unademanda dels responsables d'aquests menjadors que es veuen desbordats per controlar totes lesincidències que tenen a veure amb el menjador d'un centre educatiu: des del registre d'un client (alumne, professor o convidat) que entra al menjador a dinar fins al cobrament dels serveiscorresponents.
Resumo:
The technology sector in Ireland is thriving. Employment, through indigenous and multinational technology firms continues to grow strongly year on year. All of the top 10 multinational technology companies have a significant presence in Ireland and the indigenous software sector’s exports are worth well in excess of €1 billion annually. Five of the top 10 exporters in Ireland are technology companies, and the sector is responsible for approximately one-third of Ireland’s total turnover. Since January 2011, over 80 jobs a week have been announced in the sector. This is on foot of 6% employment growth in 2009 and 4% in 2010. A recent global competitiveness report ranks Ireland as the top destination in the world by quality and value of investments. With a growing multinational technology presence in Ireland and a vibrant and innovative indigenous software sector, the future prospects for Ireland’s technology sector are bright.
Resumo:
Aquest document vol explicar en què consisteix el sistema EBP, com pot facilitar la gestió de proveïment d'una empresa i quines eines proporciona.
Resumo:
By using suitable parameters, we present a uni¯ed aproach for describing four methods for representing categorical data in a contingency table. These methods include:correspondence analysis (CA), the alternative approach using Hellinger distance (HD),the log-ratio (LR) alternative, which is appropriate for compositional data, and theso-called non-symmetrical correspondence analysis (NSCA). We then make an appropriate comparison among these four methods and some illustrative examples are given.Some approaches based on cumulative frequencies are also linked and studied usingmatrices.Key words: Correspondence analysis, Hellinger distance, Non-symmetrical correspondence analysis, log-ratio analysis, Taguchi inertia
Resumo:
BACKGROUND Challenges exist in the clinical diagnosis of drug-induced liver injury (DILI) and in obtaining information on hepatotoxicity in humans. OBJECTIVE (i) To develop a unified list that combines drugs incriminated in well vetted or adjudicated DILI cases from many recognized sources and drugs that have been subjected to serious regulatory actions due to hepatotoxicity; and (ii) to supplement the drug list with data on reporting frequencies of liver events in the WHO individual case safety report database (VigiBase). DATA SOURCES AND EXTRACTION (i) Drugs identified as causes of DILI at three major DILI registries; (ii) drugs identified as causes of drug-induced acute liver failure (ALF) in six different data sources, including major ALF registries and previously published ALF studies; and (iii) drugs identified as being subjected to serious governmental regulatory actions due to their hepatotoxicity in Europe or the US were collected. The reporting frequency of adverse events was determined using VigiBase, computed as Empirical Bayes Geometric Mean (EBGM) with 90% confidence interval for two customized terms, 'overall liver injury' and 'ALF'. EBGM of >or=2 was considered a disproportional increase in reporting frequency. The identified drugs were then characterized in terms of regional divergence, published case reports, serious regulatory actions, and reporting frequency of 'overall liver injury' and 'ALF' calculated from VigiBase. DATA SYNTHESIS After excluding herbs, supplements and alternative medicines, a total of 385 individual drugs were identified; 319 drugs were identified in the three DILI registries, 107 from the six ALF registries (or studies) and 47 drugs that were subjected to suspension or withdrawal in the US or Europe due to their hepatotoxicity. The identified drugs varied significantly between Spain, the US and Sweden. Of the 319 drugs identified in the DILI registries of adjudicated cases, 93.4% were found in published case reports, 1.9% were suspended or withdrawn due to hepatotoxicity and 25.7% were also identified in the ALF registries/studies. In VigiBase, 30.4% of the 319 drugs were associated with disproportionally higher reporting frequency of 'overall liver injury' and 83.1% were associated with at least one reported case of ALF. CONCLUSIONS This newly developed list of drugs associated with hepatotoxicity and the multifaceted analysis on hepatotoxicity will aid in causality assessment and clinical diagnosis of DILI and will provide a basis for further characterization of hepatotoxicity.
Resumo:
Even though architecture principles were first discussed in the 1990s, they are still perceived as an underexplored topic in enterprise architecture management research. By now, there is an increasing consensus about EA principles' nature, as well as guidelines for their formulation. However, the extant literature remains vague about what can be considered suitable EA design and evolution guidance principles. In addition, empirical insights regarding their role and usefulness in practice are still lacking. Accordingly, this research seeks to address three questions: (1) What are suitable principles to guide EA design and evolution? (2) What usage do EA principles have for practitioners? (3) Which propositions can be derived regarding EA principles' role and application? Opting for exploratory research, we apply a research process covering critical analysis of current publications as well as capturing experts' perceptions. Our research ontologically distinguishes between principles from nonprinciples, proposes a validated set of meta-principles, and clarifies principles' application, role, and usefulness in practice. The explored insights can be used as guidelines in defining suitable principles and turning them into an effective bridge between strategy and design and a guide in design decisions.
Resumo:
Despite the increasing popularity of enterprise architecture management (EAM) in practice, many EAM initiatives either do not fully meet the expected targets or fail. Several frameworks have been suggested as guidelines to EA implementation, but companies seldom follow prescriptive frameworks. Instead, they follow very diverse implementation approaches that depend on their organizational contingencies and the way of adopting and evolving EAM over time. This research strives for a broader understanding of EAM by exploring context-dependent EAM adoption approaches as well as identifying the main EA principles that affect EA effectiveness. Based on two studies, this dissertation aims to address two main questions: (1) EAM design: Which approaches do companies follow when adopting EAM? (2) EA principles and their impact: What impact does EA principles have on EA effectiveness/quality? By utilizing both qualitative and quantitative research methods, this research contributes to exploring different EAM designs in different organizational contingencies as well as using EA principles as an effective means to achieve principle-based EAM design. My research can help companies identify a suitable EAM design that fits their organizational settings and shape their EA through a set of principles.
Resumo:
Newsletter for Information Technology Department
Resumo:
Newsletter for Information Technology Department
Resumo:
Newsletter for Information Technology Department
Resumo:
Newsletter for Information Tehcnology Department
Resumo:
Newsletter for Information Technology Department
Resumo:
This document is a journey through Semantic Web principles and Microsoft SharePoint in order to come to understand some advantages and disadvantages of theirs, and how Semantic Web principles can be blended into an enterprise solution like Microsoft SharePoint.