John Ockerbloom
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
John Ockerbloom has a total of 5 co-authors. Here are the top co-authors by number of shared publications:
David Garlan
Carnegie Mellon University
4 shared publicationsRobert Allen
4 shared publicationsD. Garlan
Sch. of Comput. Sci., Carnegie Mellon Univ., Pittsburgh, PA, USA
1 shared publicationJ.M. Wing
Carnegie Mellon Univ., Pittsburgh, PA
1 shared publicationR. Allen
Sch. of Comput. Sci., Carnegie Mellon Univ., Pittsburgh, PA, USA
1 shared publication
Latest Publications
- Open Access
- 26 October 2010
- Published by Association for Computing Machinery (ACM)
- p. 1-2
The metadata challenge
- 26 October 2010
- Published by Association for Computing Machinery (ACM)
- p. 1-2
Open AccessThe metadata challenge
- 19 June 2009
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 26 (4) , 66-69
Architectural Mismatch: Why Reuse Is Still So Hard
In this article, David Garlan, Robert Allen, and John Ockerbloom reflect on the state of architectural mismatch, a term they coined in their 1995 IEEE Software article, "Architectural Mismatch: Why Reuse Is So Hard." Although the nature of software systems has changed dramatically since the earlier article was published, the challenge of architectural mismatch remains an important concern for the software engineering field.
- 19 June 2009
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 26 (4) , 66-69
Architectural Mismatch: Why Reuse Is Still So Hard
In this article, David Garlan, Robert Allen, and John Ockerbloom reflect on the state of architectural mismatch, a term they coined in their 1995 IEEE Software article, "Architectural Mismatch: Why Reuse Is So Hard." Although the nature of software systems has changed dramatically since the earlier article was published, the challenge of architectural mismatch remains an important concern for the software engineering field.
- 1 July 2000
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 26 (7) , 579-593
Respectful type converters
In converting an object of one type to another, we expect some of the original object's behavior to remain the same and some to change. How can we state the relationship between the original object and converted object to characterize what information is preserved and what is lost after the conversion takes place? We answer this question by introducing the new relation, respects, and say that a type converter function $C: A \rightarrow B$respects a type $T$. We formally define respects in terms of the Liskov and Wing behavioral notion of subtyping; types $A$ and $B$ are subtypes of $T$. We explain in detail the applicability of respectful type converters in the context of the Typed Object Model (TOM) Conversion Service, built at Carnegie Mellon and used on a daily basis throughout the world. We also briefly discuss how our respects relation addresses a similar question in two other contexts: type evolution and interoperability.- 1 July 2000
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 26 (7) , 579-593
Respectful type converters
In converting an object of one type to another, we expect some of the original object's behavior to remain the same and some to change. How can we state the relationship between the original object and converted object to characterize what information is preserved and what is lost after the conversion takes place? We answer this question by introducing the new relation, respects, and say that a type converter function $C: A \rightarrow B$respects a type $T$. We formally define respects in terms of the Liskov and Wing behavioral notion of subtyping; types $A$ and $B$ are subtypes of $T$. We explain in detail the applicability of respectful type converters in the context of the Typed Object Model (TOM) Conversion Service, built at Carnegie Mellon and used on a daily basis throughout the world. We also briefly discuss how our respects relation addresses a similar question in two other contexts: type evolution and interoperability.- Open Access
- 1 August 1999
- Published by Association for Computing Machinery (ACM)
- p. 237
Managing diverse data formats in digital libraries
- 1 August 1999
- Published by Association for Computing Machinery (ACM)
- p. 237
Open AccessManaging diverse data formats in digital libraries
- 1 November 1995
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 12 (6) , 17-26
Architectural mismatch: why reuse is so hard
Why isn't there more progress toward building systems from existing parts? One answer is that the assumptions of the parts about their intended environment are implicit and either don't match the actual environment or conflict with those of other parts. The authors explore these problems in the context of their own experience with a compositional approach.<>
- 1 November 1995
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 12 (6) , 17-26
Architectural mismatch: why reuse is so hard
Why isn't there more progress toward building systems from existing parts? One answer is that the assumptions of the parts about their intended environment are implicit and either don't match the actual environment or conflict with those of other parts. The authors explore these problems in the context of their own experience with a compositional approach.<>
- 1 August 1995
- Published by Defense Technical Information Center (DTIC)
Exploiting Structured Data in Wide-Area Information Systems,
Information produced by outside parties, such as ill the World Wide Web, is increasingly important in many software applications. Effective use of this information requires the ability to exploit its semantic structure. Unfortunately, existing wide-area information systems force data to be distributed in either a lowest-common-denominator form, or in a form meaningful only to programs designed around a particular application. The former results in significant loss of information, while the latter severely limits the information available. One solution is to develop a way to describe information types with rich semantics, allow new type descriptions to be easily added and related to existing ones, and construct agents that can distribute and interpret this type information. The extra weight of general-purpose network object systems like CORBA and OLE is not required. Providers can create and manage their data and data types as they wish, and clients can adapt them to their needs. The Typed Object Model (TOM) implements such a solution. It treats information as typed abstract data objects, with encodings defined for compatibility with existing infosystems, such as the Web. Mediator agents register and relate new data types, and locate agents that can interpret or convert unfamiliar data formats.
- 1 August 1995
- Published by Defense Technical Information Center (DTIC)
Exploiting Structured Data in Wide-Area Information Systems,
Information produced by outside parties, such as ill the World Wide Web, is increasingly important in many software applications. Effective use of this information requires the ability to exploit its semantic structure. Unfortunately, existing wide-area information systems force data to be distributed in either a lowest-common-denominator form, or in a form meaningful only to programs designed around a particular application. The former results in significant loss of information, while the latter severely limits the information available. One solution is to develop a way to describe information types with rich semantics, allow new type descriptions to be easily added and related to existing ones, and construct agents that can distribute and interpret this type information. The extra weight of general-purpose network object systems like CORBA and OLE is not required. Providers can create and manage their data and data types as they wish, and clients can adapt them to their needs. The Typed Object Model (TOM) implements such a solution. It treats information as typed abstract data objects, with encodings defined for compatibility with existing infosystems, such as the Web. Mediator agents register and relate new data types, and locate agents that can interpret or convert unfamiliar data formats.
- Open Access
- 1 January 1995
- Published by Association for Computing Machinery (ACM)
- p. 179-185
Architectural mismatch or why it's hard to build systems out of existing parts
- 1 January 1995
- Published by Association for Computing Machinery (ACM)
- p. 179-185
Open AccessArchitectural mismatch or why it's hard to build systems out of existing parts
- Open Access
- 1 December 1994
- Published by Association for Computing Machinery (ACM)
- Vol. 19 (5) , 175-188
Exploiting style in architectural design environments
- 1 December 1994
- Published by Association for Computing Machinery (ACM)
- Vol. 19 (5) , 175-188
Open AccessExploiting style in architectural design environments
- Open Access
- 1 December 1994
- Published by Association for Computing Machinery (ACM) in ACM SIGSOFT Software Engineering Notes
- Vol. 19 (5) , 175-188
Exploiting style in architectural design environments
As the design of software architectures emerges as a discipline within software engineering, it will become increasingly important to support architectural description and analysis with tools and environments. In this paper we describe a system for developing architectural design environments that exploit architectural styles to guide software architects in producing specific systems. The primary contributions of this research are: (a) a generic object model for representing architectural designs; (b) the characterization of architectural styles as specializations of this object model; and (c) a toolkit for creating an open architectural design environment from a description of a specific architectural style. We use our experience in implementing these concepts to illustrate how style-oriented architectural design raises new challenges for software support environments.
- 1 December 1994
- Published by Association for Computing Machinery (ACM) in ACM SIGSOFT Software Engineering Notes
- Vol. 19 (5) , 175-188
Open AccessExploiting style in architectural design environments
As the design of software architectures emerges as a discipline within software engineering, it will become increasingly important to support architectural description and analysis with tools and environments. In this paper we describe a system for developing architectural design environments that exploit architectural styles to guide software architects in producing specific systems. The primary contributions of this research are: (a) a generic object model for representing architectural designs; (b) the characterization of architectural styles as specializations of this object model; and (c) a toolkit for creating an open architectural design environment from a description of a specific architectural style. We use our experience in implementing these concepts to illustrate how style-oriented architectural design raises new challenges for software support environments.