53 resultados para RUP
Resumo:
Servicios registrales
Resumo:
By H.H.B." [Harley H. Bartlett?
Resumo:
This negative seems taken at same time as similar print inscribed per title / description - perhaps taken by H.H.B. [Harley H. Bartlett?]
Resumo:
1. Little is known about the role of deep roots in the nutrition of forest trees and their ability to provide a safety-net service taking up nutrients leached from the topsoil. 2. To address this issue, we studied the potential uptake of N, K and Ca by Eucalyptus grandis trees (6 years of age - 25 m mean height), in Brazil, as a function of soil depth, texture and water content. We injected NO(3)(-)- (15)N, Rb(+) (analogue of K(+)) and Sr(2+) (analogue of Ca(2+)) tracers simultaneously in a solution through plastic tubes at 10, 50, 150 and 300 cm in depth in a sandy and a clayey Ferralsol soil. A complete randomized design was set up with three replicates of paired trees per injection depth and soil type. Recently expanded leaves were sampled at various times after tracer injection in the summer, and the experiment was repeated in the winter. Soil water contents were continuously monitored at the different depths in the two soils. 3. Determination of foliar Rb and Sr concentrations and (15)N atom % made it possible to estimate the relative uptake potential (RUP) of tracer injections from the four soil depths and the specific RUP (SRUP), defined as RUP, per unit of fine root length density in the corresponding soil layer. 4. The highest tracer uptake rates were found in the topsoil, but contrasting RUP distributions were observed for the three tracers. Whilst the RUP was higher for NO(3)(-)- (15)N than for Rb(+) and Sr(2+) in the upper 50 cm of soil, the highest SRUP values for Sr(2+) and Rb(+) were found at a depth of 300 cm in the sandy soil, as well as in the clayey soil when gravitational solutions reached that depth. 5. Our results suggest that the fine roots of E. grandis trees exhibit contrasting potential uptake rates with depth depending on the nutrient. This functional specialization of roots might contribute to the high growth rates of E. grandis trees, efficiently providing the large amounts of nutrients required throughout the development of these fast-growing plantations.
Resumo:
Most of the traditional software and database development approaches tend to be serial, not evolutionary and certainly not agile, especially on data-oriented aspects. Most of the more commonly used methodologies are strict, meaning they’re composed by several stages each with very specific associated tasks. A clear example is the Rational Unified Process (RUP), divided into Business Modeling, Requirements, Analysis & Design, Implementation, Testing and Deployment. But what happens when the needs of a well design and structured plan, meet the reality of a small starting company that aims to build an entire user experience solution. Here resource control and time productivity is vital, requirements are in constant change, and so is the product itself. In order to succeed in this environment a highly collaborative and evolutionary development approach is mandatory. The implications of constant changing requirements imply an iterative development process. Project focus is on Data Warehouse development and business modeling. This area is usually a tricky one. Business knowledge is part of the enterprise, how they work, their goals, what is relevant for analyses are internal business processes. Throughout this document it will be explained why Agile Modeling development was chosen. How an iterative and evolutionary methodology, allowed for reasonable planning and documentation while permitting development flexibility, from idea to product. More importantly how it was applied on the development of a Retail Focused Data Warehouse. A productized Data Warehouse built on the knowledge of not one but several client needs. One that aims not just to store usual business areas but create an innovative sets of business metrics by joining them with store environment analysis, converting Business Intelligence into Actionable Business Intelligence.
Resumo:
Dissertação de mestrado integrado em Engenharia e Gestão de Sistemas de Informação
Resumo:
Aquesta memòria sintetitza el treball de desenvolupament d¿una aplicació per realitzar el filtrat de pàgines web.Els objectius principals del projecte han estat d¿una banda obtenir una aplicació que permeti realitzar el filtrat i de l¿altra aprofitar el projecte per construir un model complet de desenvolupament de programari per a industrialitzar futurs projectes. En quant a la metodologia, s¿ha emprat el cicle de vida RUP de forma incremental en les tres parts de l¿aplicació, (proxy, filtres i log). En la seqüència de quatre fases s¿executen iterativament una sèrie de processos. Pel que fa al producte obtingut, es tracta d¿un servidor proxy, que realitza la funció de filtrat de pàgines web, mitjançant dues utilitats, ¿llista negra¿ d¿adreces i ¿llista negra¿ de continguts, ames de disposar d¿un registre d¿activitat log.
Resumo:
La proposta d'aquest treball és realitzar un projecte que produeixi una solució de programari per a un hipotètic negoci de fleques de pa. Aquest projecte inclou la recollida i documentació de requisits així com l'anàlisi, el disseny i la implementació d'un prototip funcional per a un sistema capaç de rebre i gestionar comandes de pa i productes derivats (pastisseria, rebosteria, etc...).
Resumo:
Este artigo visa a apresentar um contributo para a reflexão acerca da integração de Cabo Verde na CEDEAO (Comunidade Económica dos Estados da África Ocidental) e sobre a aproximação de Cabo Verde às RUP (Regiões Ultraperiféricas) e, posteriormente, à União Europeia, tirando-se proveito da realidade de uma Nação que se gerou e se vai consolidando a partir da cooperação de povos e culturas oriundos dos dois espaços geográficos referidos. A discussão não se deve somente à posição geográfica privilegiada do arquipélago, mas, igualmente, liga-se a aspectos de ordem cultural, política, económica, comercial e de segurança, com especial destaque para a estruturação do Estado-Nação em Cabo Verde.
Resumo:
Este artigo procura compreender a integração regional do Arquipélago de Cabo Verde, na base do debate contemporâneo sobre a Nação. Resultado de cruzamento e convergência entre povos e culturas oriundos de dois espaços geográficos (África e Europa), a Nação cabo-verdiana afirma-se e consolida-se na margem dos debates perspetivados e delineados por diferentes gerações de intelectuais, políticos e académicos nacionais e estrangeiros. Estes procuram compreender e analisar a integração de Cabo Verde na Comunidade Económica dos Estados da África Ocidental (CEDEAO), a aproximação às Regiões Ultraperiféricas (RUP) e a Parceria Especial com a União Europeia (UE). A análise expressa no presente artigo, além de distinguir a posição geográfica privilegiada do arquipélago, enfatiza também aspetos de ordem cultural, política, económica, comercial e de segurança, relevantes para a construção da Nação em Cabo Verde.
Resumo:
The software development industry is constantly evolving. The rise of the agile methodologies in the late 1990s, and new development tools and technologies require growing attention for everybody working within this industry. The organizations have, however, had a mixture of various processes and different process languages since a standard software development process language has not been available. A promising process meta-model called Software & Systems Process Engineering Meta- Model (SPEM) 2.0 has been released recently. This is applied by tools such as Eclipse Process Framework Composer, which is designed for implementing and maintaining processes and method content. Its aim is to support a broad variety of project types and development styles. This thesis presents the concepts of software processes, models, traditional and agile approaches, method engineering, and software process improvement. Some of the most well-known methodologies (RUP, OpenUP, OpenMethod, XP and Scrum) are also introduced with a comparison provided between them. The main focus is on the Eclipse Process Framework and SPEM 2.0, their capabilities, usage and modeling. As a proof of concept, I present a case study of modeling OpenMethod with EPF Composer and SPEM 2.0. The results show that the new meta-model and tool have made it possible to easily manage method content, publish versions with customized content, and connect project tools (such as MS Project) with the process content. The software process modeling also acts as a process improvement activity.
Resumo:
Formal software development processes and well-defined development methodologies are nowadays seen as the definite way to produce high-quality software within time-limits and budgets. The variety of such high-level methodologies is huge ranging from rigorous process frameworks like CMMI and RUP to more lightweight agile methodologies. The need for managing this variety and the fact that practically every software development organization has its own unique set of development processes and methods have created a profession of software process engineers. Different kinds of informal and formal software process modeling languages are essential tools for process engineers. These are used to define processes in a way which allows easy management of processes, for example process dissemination, process tailoring and process enactment. The process modeling languages are usually used as a tool for process engineering where the main focus is on the processes themselves. This dissertation has a different emphasis. The dissertation analyses modern software development process modeling from the software developers’ point of view. The goal of the dissertation is to investigate whether the software process modeling and the software process models aid software developers in their day-to-day work and what are the main mechanisms for this. The focus of the work is on the Software Process Engineering Metamodel (SPEM) framework which is currently one of the most influential process modeling notations in software engineering. The research theme is elaborated through six scientific articles which represent the dissertation research done with process modeling during an approximately five year period. The research follows the classical engineering research discipline where the current situation is analyzed, a potentially better solution is developed and finally its implications are analyzed. The research applies a variety of different research techniques ranging from literature surveys to qualitative studies done amongst software practitioners. The key finding of the dissertation is that software process modeling notations and techniques are usually developed in process engineering terms. As a consequence the connection between the process models and actual development work is loose. In addition, the modeling standards like SPEM are partially incomplete when it comes to pragmatic process modeling needs, like light-weight modeling and combining pre-defined process components. This leads to a situation, where the full potential of process modeling techniques for aiding the daily development activities can not be achieved. Despite these difficulties the dissertation shows that it is possible to use modeling standards like SPEM to aid software developers in their work. The dissertation presents a light-weight modeling technique, which software development teams can use to quickly analyze their work practices in a more objective manner. The dissertation also shows how process modeling can be used to more easily compare different software development situations and to analyze their differences in a systematic way. Models also help to share this knowledge with others. A qualitative study done amongst Finnish software practitioners verifies the conclusions of other studies in the dissertation. Although processes and development methodologies are seen as an essential part of software development, the process modeling techniques are rarely used during the daily development work. However, the potential of these techniques intrigues the practitioners. As a conclusion the dissertation shows that process modeling techniques, most commonly used as tools for process engineers, can also be used as tools for organizing the daily software development work. This work presents theoretical solutions for bringing the process modeling closer to the ground-level software development activities. These theories are proven feasible by presenting several case studies where the modeling techniques are used e.g. to find differences in the work methods of the members of a software team and to share the process knowledge to a wider audience.
Resumo:
Banco del conocimiento
Resumo:
Banco del conocimiento