The Rational Unified Process: An Introduction

By P. Krutchen. 2000

2,012 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/63a94cb28fd2f8197fc76bee54a2463a67401746

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Customising agile methods to software practices at Intel Shannon (2006, background): “Many different methods have been labelled as agile, such as eXtreme Programming (XP) (Beck, 1999), Dynamic Systems Development Method (DSDM) (Stapleton, 1997); Scrum (Schwaber & Beedle, 2002); Crystal (Cockburn, 2001); Agile modelling (Ambler, 2002); Feature Driven Design (Coad et al., 1999); Lean P”
Eliciting security requirements with misuse cases (2000, methodology): “Most of the fields in the use - case templates of Kulak and Guiney [ 5 ] , Cockburn [ 3 ] , and RUP [ 29 ] are also relevant for describing misuse cases , but some adaptations are necessary and some new fields must be introduced .”
O-MaSE: a customisable approach to designing and building complex, adaptive multi-agent systems (2010, methodology): “For instance, O-MaSE has been used to support modern iterative, incremental approaches as proposed by Royce (1998) and as implemented in the popular rational unified process (RUP) (Kroll and Kruchten, 2003; Kruchten, 2000).”
Does risk management contribute to IT project success? A meta-analysis of empirical evidence (2010, methodology): “Over the last decade, there appears to have been a growing interest in the development of new methodologies for the management of IT projects, such as e.g. Agile (see e.g. Schwaber and Beedle, 2002) and RUP (see e.g. Kruchten, 2004).”
A view of 20th and 21st century software engineering (2006, methodology): “Space limitations make it infeasible to discuss these in detail, but the best approach evolved so far involves, in Rational Unified Process terms: 1.”
Key principles for user-centred systems design (2003, methodology): “The deﬁnition and key principles may also be used when specifying a UCSD process or when customizing a commercial development process, such as Rational Uniﬁed Process – RUP (Kruchten 1998).”
Model-driven engineering: A survey supported by the unified conceptual model (2015, methodology): “For this classification we considered the following disciplines, as defined in Rational Unified Process (RUP) [35]: business”
of Model-Based Systems Engineering ( MBSE ) Methodologies (2008, methodology): “A textbook by Kruchten exist for the baseline RUP methodology that details core tenets and elements of the methodology and provides tailoring guidelines [40].”
Metamodel Adaptation and Model Co-adaptation (2007, background): “eXtreme Programming [12] and Rational Unified Process [13].”
Agile Requirements Engineering: A systematic literature review (2017, methodology): “On one hand, there are iterative process models like Rational Unified Process [14,15].”
The Rational Unified Process Made Easy - A Practitioner's Guide to the RUP (2003, unknown): “The process has two structures or, if you prefer, two dimensions: [3] See OMG 2001.”
Automatic test generation: a use case driven approach (2006, unknown): “In standard development processes [10] based on the UML, each use case is to be documented with several sequence diagrams.”
Empirical studies of agile software development: A systematic review (2008, methodology): “Only DSDM and the Rational Unified Process [38] were found to give full coverage to all phases of development, while Scrum mainly covers aspects related to project management.”
Ontologies: How can They be Built? (2004, background): “Evaluation is performed along the whole life 3 Only very recently, for instance, in the rational unified process (Krutchen 2000), is knowledge acquisition beginning to take part in software engineering processes.”
An Ontology of Architectural Design Decisions in Software-Intensive Systems (2004, background): “1 " (Kruchten, 1998; IBM, 2003) For many years we have focused on the result, the consequences of the design decisions we made, trying to capture them in the " design " or the " architecture " of the system under consideration, using often graphics.”
Agile Software Development Methods: Review and Analysis (2017, methodology): “(Kruchten 2000) claims that RUP can often be adopted, in whole or in part, “out of the box”.”