default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDPaul C. Clements
Paul Clements
Person information
- affiliation: BigLever Software
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
showing all ?? records
2010 – 2019
- 2019
[c71]Paul Clements:
Managing variation: an industrial perspective on product line engineering. ICSE (Companion Volume) 2019: 1- [c70]Charles W. Krueger, Paul C. Clements:
Feature-based systems and software product line engineering: PLE for the enterprise. SPLC (A) 2019: 53:1 - [c69]Charles W. Krueger, Paul Clements:
Feature-based systems and software product line engineering with gears from biglever. SPLC (B) 2019: 66:1-66:2 - [p3]Charles W. Krueger, Paul Clements:
A Feature Ontology to Power Enterprise-Level Product Line Engineering. Software Engineering for Variability Intensive Systems 2019: 227-250 - 2018
- [c68]Charles W. Krueger, Paul Clements:
Feature-based systems and software product line engineering with gears from BigLever. SPLC (2) 2018: 1-4 - [c67]Charles W. Krueger, Paul C. Clements:
Feature-based systems and software product line engineering: PLE for the enterprise. SPLC 2018: 301-302 - 2017
- [c66]Susan P. Gregg, Denise M. Albert, Paul Clements:
Product Line Engineering on the Right Side of the "V". SPLC (A) 2017: 165-174 - [c65]Bobbi Young, Judd Cheatwood, Todd Peterson, Rick Flores, Paul C. Clements:
Product Line Engineering Meets Model Based Engineering in the Defense and Automotive Industries. SPLC (A) 2017: 175-179 - [c64]Charles W. Krueger, Paul C. Clements:
Enterprise Feature Ontology for Feature-based Product Line Engineering and Operations. SPLC (A) 2017: 227-236 - [c63]Charles W. Krueger, Paul C. Clements:
Feature-Based Systems and Software Product Line Engineering: PLE for the Enterprise. SPLC (A) 2017: 253 - 2015
- [c62]Paul Clements:
Keynote Talk III: A formal methods perspective on product line engineering. MEMOCODE 2015: 168 - [c61]Susan P. Gregg, Rick Scharadin, Paul Clements:
The more you do, the more you save: the superlinear cost avoidance effect of systems product line engineering. SPLC 2015: 303-310 - [c60]Len Wozniak, Paul Clements:
How automotive engineering is taking product line engineering to the extreme. SPLC 2015: 327-336 - [c59]Charles W. Krueger, Paul C. Clements:
Second generation systems and software product line engineering. SPLC 2015: 388-389 - 2014
- [c58]Charles W. Krueger, Paul C. Clements:
Systems and software product line engineering with gears from BigLever software. SPLC Workshops 2014: 121-125 - [c57]Susan P. Gregg, Rick Scharadin, Eric LeGore, Paul Clements:
Lessons from AEGIS: organizational and governance aspects of a major product line in a multi-program environment. SPLC 2014: 264-273 - [c56]Charles W. Krueger, Paul C. Clements:
Second generation systems and software product line engineering. SPLC 2014: 358 - 2013
- [c55]Charles W. Krueger, Paul C. Clements:
Systems and software product line engineering with BigLever software gears. SPLC Workshops 2013: 136-140 - [c54]Paul C. Clements, Charles W. Krueger, James Shepherd, Andrew Winkler:
A PLE-based auditing method for protecting restricted content in derived products. SPLC 2013: 218-226 - [c53]Jeremy T. Lanman, Rowland Darbin, Jorge Rivera, Paul C. Clements, Charles W. Krueger:
The challenges of applying service orientation to the U.S. Army's live training software product line. SPLC 2013: 244-253 - [c52]Charles W. Krueger, Paul C. Clements:
Second generation systems and software product line engineering. SPLC 2013: 283-284 - [c51]Paul C. Clements, Julia Rubin, Kentaro Yoshimura:
Barriers for SPL practice and paths to get over them. SPLC 2013: 289 - [p2]Rick Flores, Charles W. Krueger, Paul C. Clements:
Second-Generation Product Line Engineering: A Case Study at General Motors. Systems and Software Variability Management 2013: 223-250 - 2012
- [c50]Charles W. Krueger, Paul C. Clements:
Systems and software product line engineering with BigLever software gears. SPLC (2) 2012: 256-259 - [c49]Rick Flores, Charles W. Krueger, Paul C. Clements:
Mega-scale product line engineering at General Motors. SPLC (1) 2012: 259-268 - [c48]Charles W. Krueger, Paul C. Clements:
Second generation systems and software product line engineering. SPLC (2) 2012: 280 - 2011
- [c47]Andy J. Nolan, Silvia Abrahão
, Paul C. Clements, Andy Pickard:
Managing requirements uncertainty in engine control systems development. RE 2011: 259-264 - [c46]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 - [c45]Silvia Abrahão, Andy J. Nolan, Paul C. Clements, John D. McGregor:
Quantitative methods in software product line engineering. SPLC Workshops 2011: 38 - [c44]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 - [c43]Andy J. Nolan, Silvia Abrahão, Paul C. Clements, Andy Pickard:
Requirements Uncertainty in a Software Product Line. SPLC 2011: 223-231 - [c42]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 - [c41]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 - [p1]Len Bass, Paul C. Clements:
Business Goals and Architecture. Relating Software Requirements and Architectures 2011: 183-195 - 2010
- [j18]Paul C. Clements:
Certified Software Architects. IEEE Softw. 27(6): 6-8 (2010) - [j17]Paul C. Clements, Len Bass:
The Business Goals Viewpoint. IEEE Softw. 27(6): 38-45 (2010) - [c40]Paul C. Clements, Len Bass:
Business goals as architectural knowledge. SHARK@ICSE 2010: 9-12 - [c39]Paul C. Clements, Len Bass:
Using Business Goals to Inform a Software Architecture. RE 2010: 69-78 - [c38]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
2000 – 2009
- 2009
- [j16]Paul C. Clements, Mary Shaw:
"The Golden Age of Software Architecture" Revisited. IEEE Softw. 26(4): 70-72 (2009) - [c37]Paul C. Clements, Stuart R. Faulk, Charles W. Krueger:
Consolidating community consensus in product line practice. SPLC 2009: 303-304 - [c36]Robert L. Nord, Paul C. Clements, David E. Emery, Rich Hilliard:
Reviewing architecture documents using question sets. WICSA/ECSA 2009: 325-328 - 2008
- [c35]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 - [c34]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 - [c33]Len Bass, Paul C. Clements, Rick Kazman, Mark Klein:
Evaluating the Software Architecture Competence of Organizations. WICSA 2008: 249-252 - 2007
- [j15]Paul C. Clements, David E. Emery, Rich Hilliard, Philippe Kruchten:
Aspects in Architectural Description: report on a first workshop at AOSD 2007. ACM SIGSOFT Softw. Eng. Notes 32(4): 33-35 (2007) - [c32]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 - [c31]Paul C. Clements, John D. McGregor, Dirk Muthig:
Predicting Product Line Payoff with SIMPLE. SPLC (2) 2007: 10 - [c30]Paul C. Clements, Rick Kazman, Mark Klein, Divya Devesh, Shivani Reddy, Prageti Verma:
The Duties, Skills, and Knowledge of Software Architects. WICSA 2007: 20 - [c29]Paul C. Clements, Rick Kazman, Mark Klein:
Working Session: Software Architecture Competence. WICSA 2007: 27 - [c28]Judith A. Stafford, Paul C. Clements:
Producing Software Architecture Documentation to Suit Your Needs. WICSA 2007: 33 - 2006
- [j14]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) - [j13]Elisa L. A. Baniassad, Paul C. Clements, João Araújo, Ana Moreira, Awais Rashid, Bedir Tekinerdogan:
Discovering Early Aspects. IEEE Softw. 23(1): 61-70 (2006) - [j12]Mary Shaw, Paul C. Clements:
The Golden Age of Software Architecture. IEEE Softw. 23(2): 31-39 (2006) - [c27]Paul C. Clements:
Future Trends of Software Technology and Applications: Software Architecture. COMPSAC (1) 2006: 16 - [c26]Paul C. Clements:
Early aspects at ICSE: workshop in aspect-oriented requirements engineering and architecture design. ICSE 2006: 1013-1014 - [c25]Paul C. Clements:
Managing Variability for Software Product Lines: Working with Variability Mechanisms. SPLC 2006: 207-208 - [c24]David M. Weiss, Paul C. Clements, Kyo Kang, Charles W. Krueger:
Software Product Line Hall of Fame. SPLC 2006: 237 - 2005
- [j11]Paul C. Clements, Lawrence G. Jones, Linda M. Northrop, John D. McGregor:
Project Management in a Software Product Line Organization. IEEE Softw. 22(5): 54-62 (2005) - [c23]Paul C. Clements:
A Competition of Software Product Line Economic Models. SPLC 2005: 136 - [c22]Paul C. Clements:
Software Architecture Documentation in Practice Session Report. WICSA 2005: 257-258 - 2004
- [j10]Günter Böckle, Paul C. Clements, John D. McGregor, Dirk Muthig, Klaus Schmid:
Calculating ROI for Software Product Lines. IEEE Softw. 21(3): 23-31 (2004) - [c21]Linda M. Northrop, Paul C. Clements:
An Introduction to Software Product Lines. SPLC 2004: 322 - 2003
- [c20]Paul C. Clements, David Garlan, Reed Little, Robert L. Nord, Judith A. Stafford:
Documenting Software Architectures: Views and Beyond. ICSE 2003: 740-741 - [c19]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
- [b2]Paul Clements, Linda M. Northrop:
Software product lines - practices and patterns. SEI series in software engineering, Addison-Wesley 2002, ISBN 978-0-201-70332-0, pp. I-XXX, 1-563 - [j9]Paul C. Clements, Charles W. Krueger:
Point - Counterpoint: Being Proactive Pays Off - Eliminating the Adoption. IEEE Softw. 19(4): 28-31 (2002) - 2001
- [c18]James Bottomley, Paul Clements:
Managing Distributions, from the Software Vendor's Perspective. Annual Linux Showcase & Conference 2001 - [c17]Paul C. Clements:
On the Importance of Product Line Scope. PFE 2001: 70-78 - [c16]Paul C. Clements:
Process Validation, Session Report. PFE 2001: 388-389 - 2000
- [j8]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) - [j7]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) - [c15]Paul C. Clements:
Product Family Methods. IW-SAPF 2000: 116 - [c14]Paul C. Clements:
Product-Line Engineering. IW-SAPF 2000: 253-254
1990 – 1999
- 1999
- [b1]Leonard J. Bass, Paul C. Clements, Rick Kazman:
Software architecture in practice. SEI series in software engineering, Addison-Wesley-Longman 1999, ISBN 978-0-201-19930-7, pp. I-XXIII, 1-452 - [j6]Rick Kazman, Mark Klein, Paul C. Clements:
Evaluating Software Architectures for Real-Time Systems. Ann. Softw. Eng. 7: 71-93 (1999) - 1998
- [j5]Paul C. Clements, Nelson H. Weiderman:
Notes on the second international workshop on development and evolution of software architectures for product families. ACM SIGSOFT Softw. Eng. Notes 23(3): 39-43 (1998) - [c13]J. Henk Obbink, Paul C. Clements, Frank van der Linden:
Introduction. ESPRIT ARES Workshop 1998: 1-3 - [c12]Paul C. Clements, Juan Antonio de la Puente:
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
- [c11]Mary Shaw, Paul C. Clements:
A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems. COMPSAC 1997: 6-13 - [c10]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 Softw. 13(6): 47-55 (1996) - [c9]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- - [c8]Kurt C. Wallnau, Paul C. Clements, Edwin J. Morris, Robert Krut:
The Gadfly: An Approach to Architectural-Level System Comprehension. WPC 1996: 178-186 - [c7]Paul C. Clements:
A Survey of Architecture Description Languages. IWSSD 1996: 16-25 - [c6]Mary Shaw, Paul Clements:
Toward boxology: preliminary classification of architectural styles. ISAW/Viewpoints@FSE 1996: 50-54 - 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
1980 – 1989
- 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
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from 
to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the 
of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from 
, 
, and 
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from 
.
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-06-05 21:34 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by:
