This best-seller (190,000 copies in 10 languages and 3 editions since 1998) is a short introduction to the RUP software development process developed at Rational Software in the years 1990-1998 and commercialized today by IBM.
Translated in French, Japanese, German, Russian, Chinese (Cantonese), Chinese (Mandarin), Portuguese, Swedish, Korean.
Philippe Kruchten. The Rational Unified Process: An Introduction. 3 ed. Boston: Addison-Wesley, 2003, 272 p. ISBN: 0-321-19770-4
A fine complement to the introduction book above, this practical manual presents the RUP from different perspective: manager, architect, analyst, developer and tester.
Per Kroll and Philippe Kruchten. Rational Unified Process Made Easy: A Practitioner's Guide. Boston: Addison-Wesley, 2003. ISBN: 0-321-16609-4
Based on the RUP, this college text book introduces software engineering from a software development process perspective. The small process derived form RUP is accessible at www.upedu.org, and the companion website for instructors and students is at www.yoopeedoo.org
Pierre Robillard and Philippe Kruchten, Software Engineering Process with the UPEDU, Boston: Addison-Wesley, 2003. ISBN: 0-201-754541
This often-cited paper presents a strategy to organize the description of complex distributed systems alongside several views (or perspectives). The ideas in this paper led ultimately to the IEEE std 1471-2000 on architecture representation. In French.
Ph. Kruchten, “The 4+1 view model of architecture,” IEEE Software, 12 (6) November 1995, pp.42-50.
What makes software engineering different than other engineering disciplines? By casting the process of software design, we identify the difference and similarities, and discover some terminology and scope issues, as well a how we can exploit the soft nature of software to palliate the lack of underlying science.
Philippe Kruchten, "Casting Software Design in the Function-Behavior-Structure (FBS) Framework," IEEE Software, 22 (2), March/April 2005, pp. 52-58.
More than just lots of UML diagrams, architectural knowledge is embodied in the dozen of architectural design decisions, and their numerous relationships. This paper presents a taxonomy of such decisions.
Philippe Kruchten, "An Ontology of Architectural Design Decisions," in: Jan Bosch (ed.), Proc. of the 2nd Workshop on Software Variability Management, Groningen, NL, Dec. 3-4, 2004
Agile methods are gaining some popularity, but not among the development organizations who develop high assurance software, as they rely on the waterfall to apply specific steps to the verification of the design. How can we marry the flexibility and iterative nature of agile processes, with the rigor demanded by security applications?
K. Beznosov and P. Kruchten, "Towards Agile Security Assurance," in Proceedings of New Security Paradigm Workshop (NSPW'2004), White Point Beach, NS, 2004, ACM, pp. 47-54.
Outsourcing software development is a world-wide, and often reviled, phenomenon. But are high speed internet, collaborative tools, video cameras, and other tools sufficient to make global software projects a success? Often such projects failed, and it is easy to blame it on people, technology, distance, when actually the root cause is more subtle: the differences of culture among the participants.
Philippe Kruchten, "Analyzing Intercultural Factors Affecting Global Software Development," in Proceedings of (GSD2004) 3rd International Workshop on Global Software Development, Collocated with ICSE, Edinburgh, Scotland, 2004, IEE, pp. 59-62
A small group of software architects from Rational, Philips, Nokia, Siemens, Lockheed-Martin and IBM pooled their experience in doing software architecture reviews and capturede it in this technical report.
Henk Obbink, Philippe Kruchten, Wojtek Kozaczynski, Rich Hilliard, Alexander Ran, Herman Postema, Dominick Lutz, Rick Kazman, Will Tracz, and Ed Kahane. Report on Software Architecture Review and Assessment (SARA), Version 1.0, February 2002