- CSB - MetaPress - Google - Bing - Yahoo
 | 2012 | |
|---|---|---|
| c46 |      | Charles W. Krueger, Paul C. Clements: Systems and software product line engineering with BigLever software gears. SPLC (2) 2012: 256-259 |
| c45 | | Rick Flores, Charles W. Krueger, Paul C. Clements: Mega-scale product line engineering at General Motors. SPLC (1) 2012: 259-268 |
| c44 | | Charles W. Krueger, Paul C. Clements: Second generation systems and software product line engineering. SPLC (2) 2012: 280 |
| 2011 | ||
| p1 | | Len Bass, Paul C. Clements: Business Goals and Architecture. Relating Software Requirements and Architectures 2011: 183-195 |
| c43 | | Andy J. Nolan, Silvia Abrahão, Paul C. Clements, Andy Pickard: Managing requirements uncertainty in engine control systems development. RE 2011: 259-264 |
| c42 | | Paul C. Clements, María José Escalona Cuaresma, Paola Inverardi, Ivano Malavolta, Eda Marchetti: Exploiting software architecture to support requirements satisfaction testing. SIGSOFT FSE 2011: 484-487 |
| c41 | | Silvia Abrahão, Andy J. Nolan, Paul C. Clements, John D. McGregor: Quantitative methods in software product line engineering. SPLC Workshops 2011: 38 |
| c40 | | Andy J. Nolan, Silvia Abrahão, Paul C. Clements, John D. McGregor, Sholom Cohen: Towards the Integration of Quality Attributes into a Software Product Line Cost Model. SPLC 2011: 203-212 |
| c39 | | Andy J. Nolan, Silvia Abrahão, Paul C. Clements, Andy Pickard: Requirements Uncertainty in a Software Product Line. SPLC 2011: 223-231 |
| c38 | | Silvia Abrahão, Andy J. Nolan, Paul C. Clements, John D. McGregor: First International Workshop on Quantitative Methods in Software Product Line Engineering. SPLC 2011: 341 |
| c37 | | Bedir Tekinerdogan, Paul C. Clements, Henry Muccini, Michel R. V. Chaudron, Andrea Polini, Eoin Woods: Architecture-Based Testing and System Validation - Workshop Summary. WICSA 2011: 341 |
| 2010 | ||
| j17 | | |
| j16 | | |
| c36 | | |
| c35 | | Paul C. Clements, John D. McGregor, Len Bass: Eliciting and Capturing Business Goals to Inform a Product Line's Business Case and Architecture. SPLC 2010: 393-405 |
| 2009 | ||
| j15 | | Paul C. Clements, Mary Shaw: "The Golden Age of Software Architecture" Revisited. IEEE Software 26(4): 70-72 (2009) |
| c34 | | Paul C. Clements, Stuart R. Faulk, Charles W. Krueger: Consolidating community consensus in product line practice. SPLC 2009: 303-304 |
| c33 | | Robert L. Nord, Paul C. Clements, David E. Emery, Rich Hilliard: Reviewing architecture documents using question sets. WICSA/ECSA 2009: 325-328 |
| 2008 | ||
| c32 | | Mónica Pinto, Ruzanna Chitchyan, Awais Rashid, Ana Moreira, João Araújo, Paul C. Clements, Elisa L. A. Baniassad, Bedir Tekinerdogan: Early aspects at ICSE 2008: workshop on aspect-oriented requirements engineering and architecture design. ICSE Companion 2008: 1053-1054 |
| c31 | | Vander Alves, Christa Schwanninger, Paul C. Clements, Awais Rashid, Ana Moreira, João Araújo, Elisa L. A. Baniassad, Bedir Tekinerdogan: Early Aspects: Aspect-Oriented Requirements and Architecture for Product Lines (EA@SPLC.08). SPLC 2008: 382 |
| c30 | | Len Bass, Paul C. Clements, Rick Kazman, Mark Klein: Evaluating the Software Architecture Competence of Organizations. WICSA 2008: 249-252 |
| 2007 | ||
| j14 | | Paul C. Clements, David E. Emery, Rich Hilliard, Philippe Kruchten: Aspects in Architectural Description: report on a first workshop at AOSD 2007. ACM SIGSOFT Software Engineering Notes 32(4): 33-35 (2007) |
| c29 | | Ruzanna Chitchyan, Awais Rashid, Ana Moreira, João Araújo, Paul C. Clements, Elisa L. A. Baniassad, Bedir Tekinerdogan: Early Aspects at ICSE 2007: Workshop on Aspect-Oriented Requirements Engineering and Architecture Design. ICSE Companion 2007: 127-128 |
| c28 |  | Paul C. Clements, John D. McGregor, Dirk Muthig: Predicting Product Line Payoff with SIMPLE. SPLC (2) 2007: 10 |
| c27 | | Paul C. Clements, Rick Kazman, Mark Klein, Divya Devesh, Shivani Reddy, Prageti Verma: The Duties, Skills, and Knowledge of Software Architects. WICSA 2007: 20 |
| c26 | | Paul C. Clements, Rick Kazman, Mark Klein: Working Session: Software Architecture Competence. WICSA 2007: 27 |
| c25 | | Judith A. Stafford, Paul C. Clements: Producing Software Architecture Documentation to Suit Your Needs. WICSA 2007: 33 |
| 2006 | ||
| j13 | | Paul C. Clements, Lawrence G. Jones, John D. McGregor, Linda M. Northrop: Getting there from here: a roadmap for software product line adoption. Commun. ACM 49(12): 33-36 (2006) |
| j12 | | Elisa L. A. Baniassad, Paul C. Clements, João Araújo, Ana Moreira, Awais Rashid, Bedir Tekinerdogan: Discovering Early Aspects. IEEE Software 23(1): 61-70 (2006) |
| j11 | | Mary Shaw, Paul C. Clements: The Golden Age of Software Architecture. IEEE Software 23(2): 31-39 (2006) |
| c24 | | Paul C. Clements: Future Trends of Software Technology and Applications: Software Architecture. COMPSAC (1) 2006: 16 |
| c23 | | Paul C. Clements: Early aspects at ICSE: workshop in aspect-oriented requirements engineering and architecture design. ICSE 2006: 1013-1014 |
| c22 | | Paul C. Clements: Managing Variability for Software Product Lines: Working with Variability Mechanisms. SPLC 2006: 207-208 |
| c21 | | David M. Weiss, Paul C. Clements, Kyo Kang, Charles W. Krueger: Software Product Line Hall of Fame. SPLC 2006: 237 |
| 2005 | ||
| j10 | | Paul C. Clements, Lawrence G. Jones, Linda M. Northrop, John D. McGregor: Project Management in a Software Product Line Organization. IEEE Software 22(5): 54-62 (2005) |
| c20 | | |
| c19 | | Paul C. Clements: Software Architecture Documentation in Practice Session Report. WICSA 2005: 257-258 |
| 2004 | ||
| j9 | | Günter Böckle, Paul C. Clements, John D. McGregor, Dirk Muthig, Klaus Schmid: Calculating ROI for Software Product Lines. IEEE Software 21(3): 23-31 (2004) |
| c18 | | |
| 2003 | ||
| c17 | | Paul C. Clements, David Garlan, Reed Little, Robert L. Nord, Judith A. Stafford: Documenting Software Architectures: Views and Beyond. ICSE 2003: 740-741 |
| c16 | | Günter Böckle, Paul C. Clements, John D. McGregor, Dirk Muthig, Klaus Schmid: A Cost Model for Software Product Lines. PFE 2003: 310-316 |
| 2002 | ||
| j8 | | Paul C. Clements, Charles Kreuger: Point - Counterpoint: Being Proactive Pays Off - Eliminating the Adoption. IEEE Software 19(4): 28-31 (2002) |
| 2001 | ||
| c15 | | |
| c14 | | |
| 2000 | ||
| j7 | | Albert Mo Kim Cheng, Paul C. Clements, C. Murray Woodside: Guest Editors' Introduction-Workshop on Software and Performance. IEEE Trans. Software Eng. 26(11): 1025-1026 (2000) |
| j6 | | Albert Mo Kim Cheng, Paul C. Clements, C. Murray Woodside: Guest Editors' Introduction: Workshop on Software and Performance. IEEE Trans. Software Eng. 26(12): 1121 (2000) |
| c13 | | |
| c12 | | |
| 1999 | ||
| j5 | | Rick Kazman, Mark Klein, Paul C. Clements: Evaluating Software Architectures for Real-Time Systems. Ann. Software Eng. 7: 71-93 (1999) |
| 1998 | ||
| c11 | | J. Henk Obbink, Paul C. Clements, Frank van der Linden: Introduction. ESPRIT ARES Workshop 1998: 1-3 |
| c10 | | Paul C. Clements, Juan Antonio de la Puente: Session 4: Analysis of Software Architectures. ESPRIT ARES Workshop 1998: 140-142 |
| i1 | | Leonard J. Bass, Gary J. Chastek, Paul C. Clements, Linda M. Northrop, Dennis B. Smith, James Withey: Second Product Line Practice Workshop Report. CoRR cs.SE/9811007 (1998) |
| 1997 | ||
| c9 | | Mary Shaw, Paul C. Clements: A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems. COMPSAC 1997: 6-13 |
| c8 | | Rick Kazman, Paul C. Clements, Leonard J. Bass, Gregory D. Abowd: Classifying Architectural Elements as a Foundation for Mechanism Matching. COMPSAC 1997: 14-17 |
| 1996 | ||
| j4 | | Rick Kazman, Gregory D. Abowd, Leonard J. Bass, Paul C. Clements: Scenario-Based Analysis of Software Architecture. IEEE Software 13(6): 47-55 (1996) |
| c7 | | Evan Wallace, Paul C. Clements, Kurt C. Wallnau: Discovering a system modernization decision framework: a case study in migrating to distributed object technology. ICSM 1996: 185- |
| c6 | | Kurt C. Wallnau, Paul C. Clements, Edwin J. Morris, Robert Krut: The Gadfly: An Approach to Architectural-Level System Comprehension. WPC 1996: 178-186 |
| 1995 | ||
| c5 | | Alan W. Brown, David J. Carney, Paul C. Clements, B. Craig Meyers, Dennis B. Smith, Nelson H. Weiderman, William G. Wood: Assessing the Quality of Large, Software-Intensive Systems: A Case Study. ESEC 1995: 384-404 |
| 1993 | ||
| c4 | | Paul C. Clements, Constance L. Heitmeyer, Bruce G. Labaw, A. T. Rose: MT: A Toolset for Specifying and Analyzing Real-Time Systems. RTSS 1993: 12-22 |
| 1991 | ||
| c3 | | Douglas A. Stuart, Paul C. Clements: Clairvoyance, Capricious Timing Faults, Causality, and Real-Time Specifications. RTSS 1991: 254-263 |
| 1986 | ||
| j3 | | David Lorge Parnas, Paul C. Clements: A Rational Design Process: How and Why to Fake it. IEEE Trans. Software Eng. 12(2): 251-257 (1986) |
| j2 | | David Lorge Parnas, Paul C. Clements: Correction to "A Rational Design Process: How and Why to Fake It". IEEE Trans. Software Eng. 12(8): 874 (1986) |
| 1985 | ||
| j1 | | David Lorge Parnas, Paul C. Clements, David M. Weiss: The Modular Structure of Complex Systems. IEEE Trans. Software Eng. 11(3): 259-266 (1985) |
| c2 | | David Lorge Parnas, Paul C. Clements: A Rational Design Process: How and Why to Fake It. TAPSOFT, Vol.2 1985: 80-100 |
| 1984 | ||
| c1 | | David Lorge Parnas, Paul C. Clements, David M. Weiss: The Modular Structure of Complex Systems. ICSE 1984: 408-419 |
Colors in the list of coauthors
Last update Wed May 22 15:57:41 2013 CET by the DBLP Team —
Data released under the ODC-BY 1.0 license — See also our legal information page