1,729,076 research outputs found
a RUP segítségével
No full textDiplomamunkám célja egy szoftverrendszer elemzésén és tervezésén keresztül bemutatni a RUP (Rational Unified Process), az UML (Unified Modeling Language) és az MDA (Model-driven architecture) lehetőségeit és használatának előnyeit.MSc/MAProgramtervező informatiku
Normas de publicación
Get PDFArticles to be published in the Revista Uruguaya de Psicoanálisis (RUP) must meet the following requirements: (...)Los artículos para publicar en la Revista Uruguaya de Psicoanálisis (RUP) deberán cumplir con los siguientes requisitos: (...
EXTREME PROGRAMMING AND RATIONAL UNIFIED PROCESS – CONTRASTS OR SYNONYMS?
Get PDFThe agile movement has received much attention in software engineering recently. Established methodologies try to surf on the wave and present their methodologies a being agile, among those Rational Unified Process (RUP). In order to evaluate the statements we evaluate the RUP against eXtreme Programming (XP) to find out to what extent they are similar end where they are different. We use a qualitative approach, utilizing a framework for comparison. RUP is a top-down solution and XP is a bottom-up approach. Which of the two is really best in different situations has to be investigated in new empirical studies.extreme programming
Agile RUP
No full textThe Rational Unified Processâ (RUP) is the de facto iterative software development process in use today. But it is huge (over 3,200 files), prescriptive, and generic rather than concise, agile, and specific. Organizations moving to RUP are often confused about how to apply it to their culture, unsure how much of it to adopt, and wary of how they can adapt it to their specific software projects. This chapter starts with a brief summary of the traditional waterfall development process, then offers an overview of RUP, its philosophy and distinctive features. Then the general philosophy of agile development is discussed. The body of the chapter defines a small set of activities that have been successfully applied in commercial “Agile” RUP projects by the author. The chapter then discusses how some of the major stakeholder groups on a software project are affected by moving to an agile process.</jats:p
RUP И ГОСТ: ЕДИНСТВО ИЛИ БОРЬБА ПРОТИВОПОЛОЖНОСТЕЙ?
Get PDFThe author has done a comparative analysis of the requirements of Russian State Standards (GOST) and methodology of Rational Unified Process (RUP). The RUP recommendations are more and more used in JSC Russian Railways to create software. The theme is topical, been directly related to the quality of designed management systems.Представлен сравнительный анализ требований ГОСТ и методологий RUP, рекомендациями которой начинают пользоваться в ОАО «РЖД» при создании программных продуктов. Тема обсуждения актуальна, ибо связана с качеством проектируемых систем управления
RUP
No full textRecently, the Rational Unified Process (RUP) has been published as the second part of Rational’s Unified Method project. The RUP is advertised as an “iterative and incremental, use case-driven, architecture-centric” process model and aims to support system designers, builders and managers working with the Unified Modeling Language (UML) by a procedural guideline. In this chapter, a brief review and a critical analysis of the RUP is attempted. Its general aim and its contribution towards more harmonisation in the software process field are acknowledged. However, its ability to reduce the complexity of software development and to clarify its interlaced structure and terminology is doubted. Major problems may result from concepts not clearly specified like workflow or architecture. In particular, RUP core concepts like phase, iteration, workflow and milestone are debated. It is argued that RUP phases and milestones do not support the requirements of modern object-oriented (and, in particular, component-based) software projects. Iteration cycles should be based on software building blocks rather than on phases and activities. As one possible alternative to the RUP, a component-based (and truly architecture-centric) process model is sketched, and a multi-variant approach to software process modelling is recommended.</jats:p
Webalkalmazások módszertanai és navigációja J2EE alapokon
No full textAz UML-based Web Engineering (UWE) és a Rational Unified Process (RUP) részletes leírása egy kis projekttelMscProgramtervező Informatiku
Phase-selective synthesis of self-supported RuP films for efficient hydrogen evolution electrocatalysis in alkaline media
No full textLarge-scale hydrogen production through alkaline water electrolysis requires highly active and less expensive materials to replace platinum as a catalyst for the hydrogen evolution reaction (HER). Ruthenium, as the cheapest platinum-group element, has recently been demonstrated to exhibit excellent activity toward the HER. However, achieving better HER activity of ruthenium-based materials by selecting a more active phase is still unexplored. Herein, we report the fabrication of self-supported RuP and RuP2 catalyst films on carbon cloth (RuP/CC and RuP2/CC) via a facile, potentially scalable, and phase-controllable synthetic method. RuP/CC displays superior catalytic activity with a low overpotential of 13 mV at 10 mA cm(-1), outperforming RuP2/CC (33 mV at 10 mA cm(-1)) and most non-Pt HER catalysts. Moreover, good electrochemical stability and faradaic efficiency of nearly 100% are also demonstrated for RuP/CC. Density functional theory calculations reveal that RuP with a higher charge density at the Ru site is more favorable for the chemisorption of hydrogen, thereby exhibiting better HER activity than RuP2
INT-RUP Security of SAEB and TinyJAMBU
Get PDFThe INT-RUP security of an authenticated encryption (AE)
scheme is a well studied problem which deals with the integrity security
of an AE scheme in the setting of releasing unverified plaintext model.
Popular INT-RUP secure constructions either require a large state (e.g.
GCM-RUP, LOCUS, Oribatida) or employ a two-pass mode (e.g. MON-
DAE) that does not allow on-the-fly data processing. This motivates us
to turn our attention to feedback type AE constructions that allow small
state implementation as well as on-the-fly computation capability. In CT-
RSA 2016, Chakraborti et al. have demonstrated a generic INT-RUP
attack on rate-1 block cipher based feedback type AE schemes. Their
results inspire us to study about feedback type AE constructions at a
reduced rate. In this paper, we consider two such recent designs, SAEB
and TinyJAMBU and we analyze their integrity security in the setting of
releasing unverified plaintext model. We found an INT-RUP attack on
SAEB with roughly 232 decryption queries. However, the concrete analysis shows that if we reduce its rate to 32 bits, SAEB achieves the desired
INT-RUP security bound without any additional overhead. Moreover, we
have also analyzed TinyJAMBU, one of the finalists of the NIST LwC,
and found it to be INT-RUP secure. To the best of our knowledge, this
is the first work reporting the INT-RUP security analysis of the block cipher based single state, single pass, on-the-fly, inverse-free authenticated
ciphers
- …
