Philippe Kruchten

Philippe Kruchten

Auto-generated profile, based on publicly available information

Philippe Kruchten

University of British Columbia, Vancouver, Canada

Research Focus & Metrics

Academic Career Length

43Years (1984-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 January 1995 in IEEE Software
Verified
Journal Article
Closed access
PKP.B. Kruchten
P.B. Kruchten
The 4 + 1 View Model describes software architecture using five concurrent views, each of which addresses a specific set of concerns: The logical view describes the design's object model, the process view describes the design's concurrency and synchronization aspects; the physical view describes the mapping of the software onto the hardware and shows the system's distributed aspects, and the development view describes the software's static organization in the development environment. 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 scenarios, which constitute a fifth view. The architecture is partially evolved from these scenarios.The 4+1 View Model allows various stakeholders to find what they need in the software architecture. System engineers can approach it first from the physical view, then the process view; end users, customers, and data specialists can approach it from the logical view; and project managers and software-configuration staff members can approach it from the development view.

22 October 2012 in IEEE Software
Verified
Journal Article
Closed access
PKPhilippe Kruchten
Philippe Kruchten
RNRobert L. Nord
Robert L. Nord
IOIpek Ozkaya
Ipek Ozkaya
The metaphor of technical debt in software development was introduced two decades ago to explain to nontechnical stakeholders the need for what we call now "refactoring." As the term is being used to describe a wide range of phenomena, this paper proposes an organization of the technical debt landscape, and introduces the papers on technical debt contained in the issue.

7 November 2010
Verified
Conference Paper
Open access
NBNanette Brown
Nanette Brown
YCYuanfang Cai
Yuanfang Cai
YGYuepu Guo
Yuepu Guo
RKRick Kazman
Rick Kazman
MKMiryung Kim
Miryung Kim
NZNico Zazworka
Nico Zazworka
Delivering increasingly complex software-reliant systems demands better ways to manage the long-term effects of short-term expedients. The technical debt metaphor is gaining significant traction in the agile development community as a way to understand and communicate such issues. The idea is that developers sometimes accept compromises in a system in one dimension (e.g., modularity) to meet an urgent demand in some other dimension (e.g., a deadline), and that such compromises incur a "debt": on which "interest" has to be paid and which the "principal" should be repaid at some point for the long-term health of the project. We argue that the software engineering research community has an opportunity to study and improve this concept. We can offer software engineers a foundation for managing such trade-offs based on models of their economic impacts. Therefore, we propose managing technical debt as a part of the future research agenda for the software engineering field.

1 October 2013
Verified
Conference Paper
Closed access
MJMona Erfani Joorabchi
Mona Erfani Joorabchi
AMAli Mesbah
Ali Mesbah
PKPhilippe Kruchten
Philippe Kruchten
Context: Mobile app development is a relatively new phenomenon that is increasing rapidly due to the ubiquity and popularity of smartphones among end-users. Objective: The goal of our study is to gain an understanding of the main challenges developers face in practice when they build apps for different mobile devices. Method: We conducted a qualitative study, following a Grounded Theory approach, in which we interviewed 12 senior mobile developers from 9 different companies, followed by a semi-structured survey, with 188 respondents from the mobile development community. Results: The outcome is an overview of the current challenges faced by mobile developers in practice, such as developing apps across multiple platforms, lack of robust monitoring, analysis, and testing tools, and emulators that are slow or miss many features of mobile devices. Conclusion: Based on our findings of the current practices and challenges, we highlight areas that require more attention from the research and development community.

1 January 2007 in Journal of Systems and Software
Verified
Journal Article
Closed access
CHChristine Hofmeister
Christine Hofmeister
PKPhilippe Kruchten
Philippe Kruchten
RNRobert L. Nord
Robert L. Nord
HOHenk Obbink
Henk Obbink
ARAlexander Ran
Alexander Ran
PAPierre America
Pierre America

1 January 2006
Verified
Book Chapter
Closed access
PDF file
PKPhilippe Kruchten
Philippe Kruchten
PLPatricia Lago
Patricia Lago
HVHans van Vliet
Hans van Vliet