His primary scientific interests are in Software engineering, Software architecture description, Software architecture, Reference architecture and Software construction. His Software engineering research includes elements of Software system, Software, Software development, Software development process and Documentation. His study in the field of Software design is also linked to topics like Reuse.
Paul Clements works mostly in the field of Software architecture description, limiting it down to topics relating to Architectural pattern and, in certain cases, Systems analysis and Rational Unified Process. His research combines Systems engineering and Software architecture. His study looks at the relationship between Reference architecture and fields such as Applications architecture, as well as how they intersect with chemical problems.
Paul Clements mainly focuses on Software engineering, Software architecture, Software, Systems engineering and Software development. The various areas that Paul Clements examines in his Software engineering study include Software architecture description, Software system, Resource-oriented architecture, Software construction and Software product line. As part of the same scientific family, he usually focuses on Software architecture description, concentrating on Enterprise architecture framework and intersecting with Data architecture.
He combines topics linked to Architectural pattern with his work on Software architecture. The Software design research Paul Clements does as part of his general Software study is frequently linked to other disciplines of science, such as Reuse, therefore creating a link between diverse domains of science. Paul Clements interconnects Risk analysis, Requirements analysis and Software requirements specification in the investigation of issues within Systems engineering.
Paul Clements focuses on Domain engineering, Software engineering, Software product line, Product engineering and Systems engineering. His Domain engineering research also works with subjects such as
His Software architecture research is multidisciplinary, relying on both Resource-oriented architecture, Software system, Formal methods, Software sizing and Social software engineering. His Product engineering research integrates issues from Product design specification and Feature-oriented domain analysis. The study incorporates disciplines such as New product development and Feature model in addition to Product design specification.
His main research concerns Product engineering, Product design specification, New product development, Domain engineering and Software product line. In his study, Requirements engineering, System of systems engineering, Mechatronics and Computer-automated design is inextricably linked to Feature-oriented domain analysis, which falls within the broad field of Product engineering. His Product design specification study integrates concerns from other disciplines, such as Requirement and Product management.
His work focuses on many connections between Product management and other disciplines, such as Software engineering, that overlap with his field of interest in Core product. His Domain engineering research focuses on Systems engineering and how it relates to Procurement. His Software product line study incorporates themes from Corporate governance, Weapon system and Process management.
This overview was generated by a machine learning system which analysed the scientist’s body of work. If you have any feedback, you can contact us here.
Software Architecture in Practice
Len Bass;Paul Clements;Rick Kazman.
Software Product Lines: Practices and Patterns
Paul Clements;Linda M. Northrop.
Documenting Software Architectures: Views and Beyond
Paul Clements;David Garlan;Reed Little;Robert Nord.
Evaluating Software Architectures: Methods and Case Studies
Paul Clements;Rick Kazman;Mark M. Klein.
A rational design process: How and why to fake it
David Lorge Parnas;Paul C. Clements.
IEEE Transactions on Software Engineering (1986)
ATAM: Method for Architecture Evaluation
Rick Kazman;Mark Klein;Paul Clements.
Scenario-based analysis of software architecture
R. Kazman;G. Abowd;L. Bass;P. Clements.
IEEE Software (1996)
Software Architecture in Practice: Addison-Wesley
Leonard J. Bass;Paul C. Clements;Rick Kazman.
The Modular Structure of Complex Systems
D. L. Parnas;P. C. Clements;D. M. Weiss.
IEEE Transactions on Software Engineering (1985)
A survey of architecture description languages
Paul C. Clements.
international workshop on software specification and design (1996)
Profile was last updated on December 6th, 2021.
Research.com Ranking is based on data retrieved from the Microsoft Academic Graph (MAG).
The ranking d-index is inferred from publications deemed to belong to the considered discipline.
If you think any of the details on this page are incorrect, let us know.
We appreciate your kind effort to assist us to improve this page, it would be helpful providing us with as much detail as possible in the text box below: