27.11.11

InfoQ: Paul Clements appointed Vice President of BigLever

  • One of the few companies focusing on product line engineering

Dr. Paul Clements


Paul Clements

Senior Member of Technical Staff

Key Responsibilities

Areas of interest include (1) software architecture, and the selection, evaluation, representation, and documentation of software architectures, and (2) software product lines, and their creation, sustainment and evolution, and the strategic capabilities they bring to an enterprise.

Professional Background

Before coming to the SEI in 1994, Dr. Clements worked for the U. S. Naval Resarch Laboratory in Washington. There, he participated in (and eventually led) the Software Cost Reduction or "A-7" project. SCR produced and validated a methodology for hard-real-time embedded software development for systems with long life-cycles by re-designing and re-implementing the avionics software for the Navys A-7E aircraft. SCR pioneered techniques in modular software design, requirements engineering and specification, software architecture and architectural structures, interface specification and documentation, and real-time performance engineering.

Software Architecture in Practice (2003)
Software Architecture in Practice, 2nd Edition
Constructing Superior Software (1999)
Constructing Superior Software (Software Quality Institute Series)
Software Product Lines: Practices and Patterns (2001)
Software Product Lines: Practices and Patterns
Evaluating Software Architectures: Methods and Case Studies (2001)
Evaluating Software Architectures: Methods and Case Studies
Documenting Software Architectures: Views and Beyond (2002)
Documenting Software Architectures: Views and Beyond

ATAM (Architecture Tradeoff Analysis Method)

The Architecture Tradeoff Analysis Method (ATAM) is a method for evaluating software architectures relative to quality attribute goals. ATAM evaluations expose architectural risks that potentially inhibit the achievement of an organization's business goals. The ATAM gets its name because it not only reveals how well an architecture satisfies particular quality goals, but it also provides insight into how those quality goals interact with each other—how they trade off against each other.

Software Product Line Engineering

SPLC.net l Software Product Line Conferences
Software product line - Wikipedia, the free encyclopedia

Software product lines, or software product line development, refers to software engineering methods, tools and techniques for creating a collection of similar software systems from a shared set of software assets using a common means of production.


Why is that of interest for the software architecture community? Software Product Lines are increasingly gaining momentum within the industry as they foster systematic re-use in program families. So called product families comprise products or solutions that share a common domain, address common markets, and reveal a lot of commonalities. PLE might not be interesting for one-off application development, but it definitely  is for many industrial systems or Common-off-the-Shelf products.

No comments: