Frank Lloyd Wright, The Illinois

Rich Hilliard's Papers

This page provides partial list of recent papers and some works-in-progress. It is out of date, but will improve with time.

On Architecture

• Characterizing relations between architectural views, with Nelis Boucke, Danny Weyns, Tom Holvoet and Alexander Helleboogh. in Proceedings of the Second European Conference on Software Architecture (ECSA 2008), Lecture Notes in Computer Science, volume 5292. preprint: PDF
  Note: this reflects work in progress, comments appreciated!
• Updating IEEE 1471: Architecture frameworks and other topics, with David Emery. In Proceedings Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008). preprint: PDF slides: PDF
• Aspects in architectural description, with Paul Clements, David Emery, and Philippe Kruchten. Summary of March 2007 workshop at AOSD, ACM SIGSOFT Software Engineering Notes, volume 32. preprint: PDF
• Using Aspects in Architectural Description. Early Aspects @ AOSD. Springer, LNCS 4765. preprint: PDF slides: PDF
• Bibliography on software and systems architecture using IEEE 1471 (ISO/IEC 42010). updated occasionally. PDF
• IEEE 1471 at age 5. PDF
• Understanding perspectives. An unpublished response to Woods, Emmerich and Rozanski's (unpublished) ``Using architectural perspectives'' in light of the conceptual framework of IEEE Std 1471. PDF
• ANSI/IEEE 1471 and Systems Engineering, Mark Maier, David Emery and Rich Hilliard. In: Systems Engineering: the Journal of the International Council on Systems Engineering (INCOSE), 7(3) 2004. Preprint: PDF
• "Don't Ask, Don't Tell" Inference: architectural views and their interfaces. Position paper in Proceedings of the 2nd International Workshop on Living with Inconsistency. PDF
• Introducing IEEE 1471, Mark Maier, David Emery and Rich Hilliard. IEEE Computer, April 2001.
• Viewpoint modeling. Position paper in Proceedings of the 1st ICSE Workshop on Describing Software Architecture with UML. PDF

  Abstract. If architecture representation is the problem (P), and the UML is the solution (S), how do we get from P to S? In this paper, I introduce the idea of viewpoint modeling as a part of the answer. A viewpoint, as defined in IEEE 1471, defines a set of architectural concerns and the resources needed to address those concerns. A viewpoint gives an architect the resources with which to construct an architectural view. These resouces may include notations, techniques, and guidance. Viewpoint modeling is then a kind of metamodeling to bundle up useful sets of modeling resources for the architect. The main result of this paper is a proposed template for documenting viewpoints. I then conclude with some observations relating this to the UML.

• Three Models for the Description of Architectural Knowledge: Viewpoints, Styles, and Patterns. (Withdrawn -- after disappointing a couple folks who requested it: I'm not happy with current draft. Someday this may reappear.)
• IEEE Std 1471 and Beyond. Position paper for SEI Workshop on Software Architecture Representation, 16-17 January 2001. PDF
• Views as modules. Position paper for the Fourth International Software Architecture Workshop (ISAW-4), 4 and 5 June 2000, Limerick, Ireland. PDF

  Abstract. Views are a much talked about, frequently misunderstood, notion in current software architecture. Views are used to separate concerns and increase understandability of architectural descriptions, but there is a tradeoff between increased understandability and the need to integrate multiple views for consistency. This paper explores applying the metaphor Views as modules to this problem.

• Impact Assessment of IEEE 1471 on The Open Group Architecture Framework, 30 March 2000. PDF

  Abstract. At the request of John Spencer, this note was prepared to assess the expected im-pact of adopting IEEE 1471, Recommended Practice on Architectural Description on The Open Group's Architecture Framework (TOGAF).

• Building blocks for extensibility in the UML. Response to Object Management Group's Request for Information for Unified Modeling Language 2.0. Available from OMG as: ad/99-12-12 (See also: ad/99-12-13, ad/99-12-14)
• Patterns of Practical Architecting. Position paper for OOPSLA'99 Workshop on Patterns in Software Architecture: The Development Process, 2 November 1999. PDF
• Aspects, Concerns, Views, ... Position paper for OOPSLA'99 Workshop on Multi-Dimensional Separation of Concerns in Object-oriented Systems, 1 November 1999. PDF
• Using the UML for architectural description. In Proceedings of «UML»'99 The Unified Modeling Language, Second International Conference, Lecture Notes in Computer Science volume 1723, Springer, 1999. PDF Slides
• Views and viewpoints in software systems architecture. Position paper from the First Working IFIP Conference on Software Architecture, San Antonio, February 1999. PDF
• R. Hilliard and T. Rice, Expressiveness in Architecture Description Languages. In Proceedings of the 3rd International Software Architecture Workshop, ACM Press, Orlando Florida, 1-2 November 1998. PDF
• Rich Hilliard and Vivian E. Sovinsky, Architecture Description Framework (ADF) Workbook. The MITRE Corporation, 1997.
• "C4ISR Architectures" and "Software Architectures"—Compared. Invited talk comparing DOD's C4ISR Architecture Framework with industry and academic approaches to "software architecture". Presented 25 March 1997, at Software Engineering Institute, Washington as part of the PLIAT Workshop on Architecture Standards in Product Line Acquisition. PDF
• Operational Architectures (the very idea!). A briefing prepared in November for an EFX architecture interchange meeting, on the topic of 'operational architectures.'
• The Architect's Job. Briefing for the US Air Force, June 1997. (To be updated 2006, for SEI Essays on Software Architecture page.) PDF
• R. Hilliard and T. Rice, Comments on C4ISR Architecture Framework. Originally, MITRE Corporation memo D510-M-013, dated 5 June 1997. The C4ISR Architecture Framework was a proposed approach to documenting architectures for the DoD. This memo provides detailed comments on version 1.0 of the framework. Note: Version 2.0 of the C4ISR Architecture Framework is now available and in use by the DOD. It hasn't fixed any of the problems cited in this memo. PDF
• R. Hilliard, M. Kurland and S. Litvintchouk, MITRE's Architecture Quality Assessment. Paper given at the 1997 MITRE Software Engineering and Economics Conference, April 2-3, 1997. PDF

  Abstract. MITRE's Architecture Quality Assessment (AQA) is intended to provide an objective and repeatable technique for the evaluation of system architectures. This paper describes the scope of AQA and its intended use; the evaluation methodology embodied in the AQA; the process of conducting an architecture assessment using the AQA; the current status of the AQA; and a comparison with other approaches to architectural assessment.

• R. Hilliard, Architecture Description Framework. Overview briefing of the Architecture Description Framework (ADF) MSR.
• Walter J. Ellis, Rich Hilliard, Peter T. Poon, David Rayford, Thomas F. Saunders, Basil Sherlund and Ronald L. Wade, Toward a Recommended Practice for Architectural Description. Paper in Proceedings of 2nd IEEE International Conference on Engineering of Complex Computer Systems Montreal, Quebec, Canada, October 21-25, 1996. PDF
• Rich Hilliard, Michael J. Kurland, Steven D. Litvintchouk, Timothy B. Rice and Stephen C. Schwarm, Architecture Quality Assessment (version 2.0) This version was developed while at The MITRE Corporation, and is dated August 7, 1996. For the most recent version, contact Rich Hilliard. PDF

  Abstract. This document describes an Architecture Quality Assessment (AQA) instrument for the evaluation of system architectures. The AQA is intended to provide an objective and repeatable basis for assessing an architecture's quality in both generic and program-specific aspects. The AQA may be used to: evaluate a candidate architecture; review the technical progress of an on-going architecture development; assess a complete, delivered architecture prior to its acceptance and system implementation; or, compare two or more alternate architectures in a consistent fashion. This version is the product of a three month proof of concept phase and has been tested in limited trial use. Future versions will increase the depth and breadth of architectural coverage.

• Representing Software Systems Architectures or, components, connections and (why not?) first-class constraints and views. Appears in Joint Proceedings of the SIGSOFT '96 Workshops, ACM Press 1996 2nd International Workshop on the Architecture of Software Systems, October 15-16, 1996, San Francisco. PDF

  Abstract. As software systems architectural practice moves from the informal to the disciplined, a key challenge is architectural description. Despite substantial on-going work in "architecture description languages," have we found that existing languages are not rich enough to handle the software systems engineering concerns needed to specify and procure large Command and Control(C²) or other defense information systems. This position paper articulates requirements on architectural description in-the-large, reviews the limitations of current architecture description languages (ADLs) and outlines work in progress toward a framework for architectural description meeting these requirements.

• R. Hilliard, M. Kurland, S. Litvintchouk, Architecture Quality Assessment (AQA) Proof-of-Concept Phase, briefing to the Bedford Software Center, September, 1996. PDF

  Overview of the AQA, at the end of the proof-of-concept phase.

• R. Hilliard and D. Emery, Patterns : Design :: Blueprints : Architecture, 1996 PDF

  Abstract. Patterns have become an important paradigm in software design. We explore the limits of design patterns as applied to software architecture, and suggest another metaphor - blueprints - for architecture and outline a theory for their use. Work in progress. Comments appreciated!

• D. Emery, R. Hilliard, T. Rice, Experiences Applying a Practical Architectural Method. In Reliable Software Technologies — Ada Europe '96, Alfred Strohmeier (editor), Springer-Verlag, Lecture Notes in Computer Science, volume 1088. PDF

  Abstract. Software architecture has come to be recognized as a discipline distinct from software design. Over the past five years, we have been developing and testing a practical software architecture method at the MITRE Software Center. The method begins with an initial statement of system goals, the purchaser's vision for the system, and needs, an abstraction of the system's requirements. Multiple views of the system are then developed, to address specific architectural concerns. Each view is defined in terms of components, connections and constraints and validated against the needs. This paper briefly introduces the method and describes our experiences with its "alpha" and "beta" applications to two U.S. Army management information systems.

• R. Hilliard, Architectural View Selection, ESC Second Architecture Technical Interchange Meeting, Gunter AFB 5 December 1995.
• S. Schwarm, T. Rice, R. Hilliard, The Architectural Metaphor as a Foundation for Systems Engineering. Proceedings of Sixth Annual International Symposium of the International Council on Systems Engineering. PDF

  Abstract. Over the history of systems engineering, there have been numerous attempts to establish the foundations of that field on other disciplines. In this paper, we explore another approach, founding systems engineering on an architectural metaphor based upon our work over the past five years to establish a discipline of systems architecture. We outline the key principles of our approach and discuss their relevance for the broader field of systems engineering.

• R. Hilliard, Comments on Kogut and Clements (SEI), Features of Architecture Representation Languages. Comments available as: PDF
• R. Hilliard, J. R. Knisley, R. A. Ringdahl, RCAS final assessment. (U) MITRE Working Note 95W0000177, September 1995. 204 p. Order from MITRE Library

  Abstract. The Reserve Component Automation System (RCAS) is to provide automated support of management of the Reserve Components (RCs). A Red Team was chartered to investigate the software delays and cost increases associated with the program. The Red Team identified cost drivers associated with the program, validated the requirements associated with the cost drivers, and recommended an alternative based upon validated requirements. A Validation Assessment Team (VAT) was assembled to validate the recommended Red Team architecture, system design and life cycle costs. This working note is an assessment of the VAT process and the resulting VAT products.

• Dimensions of Architectural Thinking PDF

  Abstract. The purpose of this paper is to survey the conceptual space where "architecture" plays a role in software and systems thinking. I do this by asking a series of questions and attempting to review the answers given to those questions in the literature on architecture. Along the way, I introduce terms to help clarify the discussion of this space, introducing names for the various dimensions of architecture. Occasionally, I will appeal to the analogy of architecture with real building architecture. Paper has an extensive annotated bibliography included. Work in progress - comments appreciated!

• C. Byrnes, R. Baldwin, R. Hilliard and T. Rice, Software Architectures as They Relate to Software Maintenance. Proceedings of the MITRE Washington Conference on Software Maintenance.
• T. Rice and R. Hilliard, The SBIS Architecture Method. Briefing at the ESC Technical Interchange Meeting on Software Architectures, June 14-15, 1995.
• T. Rice, et al., The SBIS Software Architecture.
• D. Emery and R. Hilliard, "Architecture," methods and open issues. Paper presented at the First International Workshop on Software Architectures (ISAW-1), Seattle, WA, April 24-25 1995. Workshop Proceedings available from CMU
• The notion of 'architecture' in model-based software engineering. Proceedings of the Workshop on Domain-Specific Architectures Hidden Valley, PA, July 1990.

Other Writings

• Meta-level Design
• Linguistics: There are a couple of papers from my MIT linguistics days perhaps worth recovering. My undergraduate thesis, "Thematic considerations of English verbs" (does that title sound academic, or what!) and my work on "articlelessness" with Haj Ross, and work on poetics.
• Rich's Reflection bibliography: Somewhat dated. Submissions welcomed!