2008 | ||
---|---|---|
45 | EE | 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 |
44 | EE | 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 |
43 | EE | Len Bass, Paul C. Clements, Rick Kazman, Mark Klein: Evaluating the Software Architecture Competence of Organizations. WICSA 2008: 249-252 |
2007 | ||
42 | EE | 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 |
41 | EE | Paul C. Clements, Rick Kazman, Mark Klein, Divya Devesh, Shivani Reddy, Prageti Verma: The Duties, Skills, and Knowledge of Software Architects. WICSA 2007: 20 |
40 | EE | Paul C. Clements, Rick Kazman, Mark Klein: Working Session: Software Architecture Competence. WICSA 2007: 27 |
39 | EE | Judith A. Stafford, Paul C. Clements: Producing Software Architecture Documentation to Suit Your Needs. WICSA 2007: 33 |
2006 | ||
38 | EE | Paul C. Clements: Future Trends of Software Technology and Applications: Software Architecture. COMPSAC (1) 2006: 16 |
37 | EE | Paul C. Clements: Early aspects at ICSE: workshop in aspect-oriented requirements engineering and architecture design. ICSE 2006: 1013-1014 |
36 | Paul C. Clements: Managing Variability for Software Product Lines: Working with Variability Mechanisms. SPLC 2006: 207-208 | |
35 | David M. Weiss, Paul C. Clements, Kyo Kang, Charles W. Krueger: Software Product Line Hall of Fame. SPLC 2006: 237 | |
34 | EE | 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) |
33 | EE | 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) |
32 | EE | Mary Shaw, Paul C. Clements: The Golden Age of Software Architecture. IEEE Software 23(2): 31-39 (2006) |
2005 | ||
31 | EE | Paul C. Clements: A Competition of Software Product Line Economic Models. SPLC 2005: 136 |
30 | EE | Paul C. Clements: Software Architecture Documentation in Practice Session Report. WICSA 2005: 257-258 |
29 | EE | 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) |
2004 | ||
28 | EE | Linda M. Northrop, Paul C. Clements: An Introduction to Software Product Lines. SPLC 2004: 322 |
27 | EE | 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) |
2003 | ||
26 | EE | Paul C. Clements, David Garlan, Reed Little, Robert L. Nord, Judith A. Stafford: Documenting Software Architectures: Views and Beyond. ICSE 2003: 740-741 |
25 | EE | 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 | ||
24 | EE | Paul C. Clements, Charles Kreuger: Point - Counterpoint: Being Proactive Pays Off - Eliminating the Adoption. IEEE Software 19(4): 28-31 (2002) |
2001 | ||
23 | EE | Paul C. Clements: Process Validation, Session Report. PFE 2001: 388-389 |
22 | EE | Paul C. Clements: On the Importance of Product Line Scope. PFE 2001: 70-78 |
2000 | ||
21 | EE | Paul C. Clements: Product Family Methods. IW-SAPF 2000: 116 |
20 | EE | Paul C. Clements: Product-Line Engineering. IW-SAPF 2000: 253-254 |
19 | EE | 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) |
18 | EE | 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) |
1999 | ||
17 | Rick Kazman, Mark Klein, Paul C. Clements: Evaluating Software Architectures for Real-Time Systems. Ann. Software Eng. 7: 71-93 (1999) | |
1998 | ||
16 | EE | J. Henk Obbink, Paul C. Clements, Frank van der Linden: Introduction. ESPRIT ARES Workshop 1998: 1-3 |
15 | EE | Paul C. Clements, Juan Antonio de la Puente: Session 4: Analysis of Software Architectures. ESPRIT ARES Workshop 1998: 140-142 |
14 | EE | 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 | ||
13 | EE | Rick Kazman, Paul C. Clements, Leonard J. Bass, Gregory D. Abowd: Classifying Architectural Elements as a Foundation for Mechanism Matching. COMPSAC 1997: 14-17 |
12 | EE | Mary Shaw, Paul C. Clements: A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems. COMPSAC 1997: 6-13 |
1996 | ||
11 | EE | 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- |
10 | EE | Kurt C. Wallnau, Paul C. Clements, Edwin J. Morris, Robert Krut: The Gadfly: An Approach to Architectural-Level System Comprehension. WPC 1996: 178-186 |
9 | EE | Rick Kazman, Gregory D. Abowd, Leonard J. Bass, Paul C. Clements: Scenario-Based Analysis of Software Architecture. IEEE Software 13(6): 47-55 (1996) |
1995 | ||
8 | 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 | ||
7 | Paul C. Clements, Constance L. Heitmeyer, Bruce G. Labaw, A. T. Rose: MT: A Toolset for Specifying and Analyzing Real-Time Systems. IEEE Real-Time Systems Symposium 1993: 12-22 | |
1991 | ||
6 | Douglas A. Stuart, Paul C. Clements: Clairvoyance, Capricious Timing Faults, Causality, and Real-Time Specifications. IEEE Real-Time Systems Symposium 1991: 254-263 | |
1986 | ||
5 | 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) | |
4 | 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 | ||
3 | David Lorge Parnas, Paul C. Clements: A Rational Design Process: How and Why to Fake It. TAPSOFT, Vol.2 1985: 80-100 | |
2 | David Lorge Parnas, Paul C. Clements, David M. Weiss: The Modular Structure of Complex Systems. IEEE Trans. Software Eng. 11(3): 259-266 (1985) | |
1984 | ||
1 | David Lorge Parnas, Paul C. Clements, David M. Weiss: The Modular Structure of Complex Systems. ICSE 1984: 408-419 |