This report summarizes how to systematically analyze a software
architecture with respect to a quality attribute requirement of
extensibility. The report introduces extensibility and common forms of
extensibility requirements for software architectures. It provides a set
of definitions, core concepts, and a framework for reasoning about
extensibility and satisfaction (or not) of extensibility requirements by
an architecture and, eventually, a system. It describes a set of
mechanisms—such as patterns and tactics—that are commonly used to
satisfy extensibility requirements. It also provides a method by which
an analyst can determine whether an architecture documentation package
provides enough information to support analysis and, if so, to determine
whether the architectural decisions made contain serious risks relative
to extensibility requirements. An analyst can use this method to
determine whether those requirements, represented as a set of scenarios,
have been sufficiently well specified to support the needs of analysis.
The reasoning around this quality attribute should allow an analyst,
armed with appropriate architectural documentation, to assess the risks
inherent in today’s architectural decisions, in light of tomorrow's
anticipated needs.
History
Publisher Statement
This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute.
This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100.
NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.
[DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution.