Philippe kruchten electrical and computer engineering ubc. Philippe kruchten born 1952 is a canadian software engineer, and professor of software engineering at university of british columbia in vancouver, canada, known as director of process development rup. Philippe kruchten university of british columbia robert nord ipek ozkaya this book is for every software professional who wants to accelerate innovation in existing systems or build new systems. He has more than thirty years of experience in the development of large software. Abstract this article presents a model for describing the architecture of software intensive systems, based on the use of multiple, concurrent views. An ontology of architectural design decisions in software. A general model of software architecture design derived from. We see increasing industry interest and the emergence of related practices in an effort to handle maintainability, degrading quality, and strategic timeto market tradeoffs that the technical debt metaphor reifies.
The logical view describes the designs object model, the process view describes the designs concurrency and synchronization aspects. The tao of the software architect the tao of the software architect. The architecture of a software system is a metaphor, analogous to the architecture. Software architecture encompasses the set of significant decisions about the organization of a software system, the selection of the structural elements and their interfacesby which the system is. The tao of the software architect laotsu, revisited by philippe kruchten this is a very liberal reading of laotsu.
Paper published in ieee software 12 6 november 1995, pp. Decisionmaking techniques for software architecture. The architecture of a software intensive system can be defined as the set of relevant. How to agilely architect an agile architecture cutter. Professor philippe kruchten architecture of largescale, software intensive systems. Architects capture their design decisions in four views. One of the most critical questions about software architecture is what is its actual value. Philippe kruchten on architecture and technical debt. As software development processes focus more and more on value delivered to endusers and timetomarket, the difficulty in assigning an actual value on the effort spent working on the architecture makes it much harder for software architects to convince project. Philippe have set an example for a lifetime what a system software architect means for a team, a product, and foremost an enterprise. In the last few years, i have been interested in architectural design decisions and architectural knowledge. We offer 2 courses, directly or through our partner organizations softed, spc and zuhlke. At a recent workshop, at xp 2014, we looked into practices that support scaling up agile, and in particular the role of architecture one conjecture we arrived at is that architects typically work on three distinct but interdependent structures. A general model of software architecture design derived.
Philippe kruchten faculty member researcher supervisor. There are many different stakeholders related to a software system. Logical view process view development view physical view scenarios the iterative process remarks. Philippe is a professor of software engineering at the university of british columbia in vancouver. Each structure comprises software elements, relations among them, and properties of both elements and relations. Here are some recent publications on this topic most recent first. But unfortunately, we have come to realize that only a small fraction applies to software. But there isnt any wellaccepted definition of software architecture. Software architecture is not only concerned with structure and behavior, but also with usage functionality performance kruchten. Common misconceptions about software architecture by philippe kruchten rational fellow rational software canada references to architecture are everywhere. All content in this area was uploaded by philippe kruchten on nov 06, 2018.
Nord c, henk obbink d, alexander ran e, pierre america d a lehigh university, bethlehem, pa, usa b university of british columbia, 2332 main mall, vancouver, bc, canada v6t 1z4 c software. Kruchten, rational software many books and articles in which a e all have single diagram attempts to capture the seen gist of a system architecture. Software project management software architecture software project management with rup there is a wealth of information available on project management. Also i am interested on to marry lightweight processes and architecture.
Philippe kruchten is a professor of software engineering at the university of british columbia ubc, in vancouver, canada, where he holds an nserc chair in design engineering. The views are used to describe the system from the viewpoint of different stakeholders, such as endusers, developers, system engineer, and project managers. Software designers can organize the description of their architectural decisions around these four views and then illustrate them with a few selected use cases, or. Philippe kruchten is professor of software engineering in the department of electrical and computer engineering. Philippe kruchten is the lead architect of the rational unified process. Thanks philippe you were and still are an icon for me. Kruchten joined ubc in 2004 after a 30plusyear career in industry, where he worked in large software. An ontology of architectural design decisions in software intensive systems. At a recent workshop, at xp 2014, we looked into practices that support scaling up agile, and in particular the role of architecture one conjecture we arrived at is that. This software architecture document sad describes the software architecture for version 1. The paper presents a model for presenting software architectures. Building up and reasoning about architectural knowledge.
Philippe kruchten of university of british columbia vancouver, vancouver ubc read 277 publications contact philippe kruchten. Software architecture is not only concerned with structure and behavior, but also with usage functionality performance kruchten 2009. This article presents a model for describing the architecture of softwareintensive systems, based on the use. Kruchten, documentation of software architecture from a knowledge management perspectivedesign. As software development processes focus more and more on value delivered to endusers and timetomarket, the difficulty in assigning an actual value on the effort spent working on the architecture makes it much harder for software. The missing value of software architecture philippe. International conference on the quality of software architectures. Software process expert philippe kruchten offers a meditation on the role of the software architect based on an ancient chinese text.
781 1156 456 109 548 987 655 660 363 577 1092 1334 622 530 863 158 735 1113 1139 283 844 77 839 995 1078 1076 797 710 776 75 1188 828 692 210 940 1369 1077 149