E. James Whitehead Jr’s research while affiliated with University of California, Irvine and other places

What is this page?


This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.

Publications (9)


Fig. 1. The essence of hypermedia support for software development environments. An airspeed gauge from an active flight simulator is linked (Link 1) to its source code on the left and its requirements document on the right. A more specific link (Link 2) relates a design requirement to the line of code which implements the specified constraint. 
Fig. 2. Chimera's hypermedia concepts. A user interacts with one or more views, generated by viewers. Each client has at least one viewer active within it. Viewers access objects via a storage mechanism (e.g., file system, database, object management system) and create one or more graphical views depicting them. Anchors can be created on these views either automatically by the viewer or explicitly by the user. Links define relationships between these anchors. Chimera's links are modeled as sets of anchors with each anchor in the set accessible by link traversal to the others. Attributes can be associated with each concept, but are not shown on the diagram to avoid clutter. A hyperweb consists of all of these elements.
Fig. 3. Chimera's conceptual architecture. Chimera uses a client-server architecture. Each user has a set of Chimera clients running in a distinct user space. These clients are typically interactive, although that is not a requirement, and may consist of multiple viewers running in separate threads. A client communicates with the Chimera server through the use of an API. Clients may also interact with other systems in a user's environment. Each user may run a process invoker which can activate clients needed to complete link traversals. The process invoker receives an invocation request from the server and maps the requested client to an executable in the user's environment.
Fig. 4. Chimera server's internal architecture. The Chimera server's responsibilities are distributed over a set of threads and ADTs which handle incoming requests from both clients and process invokers, generate and handle hypermedia notifications/events, maintain a model of the external world, and update the persistent state of the managed hyperweb.
Fig. 5. XEmacs integration. The Chimera Shell contains a communications translator which converts between the text stream communication of XEmacs and the API-based communication of Chimera. XEmacs and the Chimera Shell together implement the Chimera 'texted' (text editor) client. XEmacs possesses the ability to create sockets for use in interprocess communication, but the XEmacs/Chimera integration does not use this capability.
Chimera: Hypermedia for heterogeneous software development environments
  • Article
  • Full-text available

July 2000

·

291 Reads

·

95 Citations

ACM Transactions on Information Systems

·

Richard N. Taylor

·

E. James Whitehead Jr

Emerging software development environments are characterized by heterogeneity: they are composed of diverse object stores, user interfaces, and tools. This paper presents an approach for providing hypermedia services in this heterogeneous setting. Central notions of the approach include the following: anchors are established with respect to interactive views of objects, rather than the objects themselves; composable, n-ary links can be established between anchors on different views of objects which may be stored in distinct object bases; viewers may be implemented in different programming languages; and, hypermedia services are provided to multiple, concurrently active, viewers. The paper describes the approach, supporting architecture, and lessons learned. Related work in the areas of supporting heterogeneity and hypermedia data modeling is discussed. The system has been employed in a variety of contexts including research, development, and education.

Download

WebDAV: IEFT standard for collaborative authoring on the Web

October 1998

·

18 Reads

·

108 Citations

IEEE Internet Computing

The World Wide Web Distributed Authoring and Versioning (WebDAV) working group is extending HTTP1.1 to provide a standards-based infrastructure for asynchronous collaborative authoring on the Web. The WebDAV extensions support the use of HTTP for the interoperable publishing of a variety of content, providing a common interface to many types of repositories and making the Web analogous to a large-grain, network-accessible file system. By supporting mechanisms for both shared and exclusive write locking, WebDAV can accommodate a wide range of collaborations.


Web-Based Development of Complex Information Products

August 1998

·

130 Reads

·

94 Citations

Communications of the ACM

Roy T. Fielding

·

E. James Whitehead Jr

·

·

[...]

·

Richard N. Taylor

The World-Wide Web connects islands of information, along with the people seeking that information, from within corporate intranets and across the global Internet, easily and effectively. Sharing information without regard to physical location has prompted new forms of virtual business and social endeavors. A virtual enterprise is an organization unconstrained by geographic location, and a membership intersecting multiple traditional organizations. Virtual enterprises can be formed within large corporations (consisting of groups at distributed sites), as parts of business alliances or task forces [4], and even among individuals working independently of any corporate connection. Indeed, all that is needed to form a virtual enterprise is at least one common goal, a shared information space, a means of coordinating users’ efforts, and people willing to share the work.



An Architectural Model for Application Integration in Open Hypermedia Environments

January 1997

·

21 Reads

·

55 Citations

This paper provides an architectural framework for modeling third-party application integrations with open hypermedia systems, which collects and extends the integration experience of the open hypermedia community. The framework is used to characterize applications prior to integration, and describe the qualities of a complete integration. Elements of the architectural model are artists, which are used to manipulate anchors, links, and native application objects; communicators, which manage information flow to and from the open hypermedia system; and containers which group the other elements. Prior integration experience is collected in a standard way using the model. Guidance in selecting the final integration architecture is provided by this prior integration experience, in conjunction with the degree of difficulty of an integration, which is related to the integration architecture.



Fig. 2. The Internal Architecture of a C2 Component.
Fig. 3. A partial C2 architecture.
Fig. 12. The SkyBlue constraint management system is incorporated into KLAX by placing it inside the Layout Manager component. Layout Manager's dialog handles all the C2 message traffic.
Fig. 13. Screenshots from Argo. Left: Conceptual architecture. Center: To-do list with item indicating a problem with Status_Logic. Right: Implementation Architecture. Small shapes attached to components are user interface affordances for making connections.
Fig. 14. The C++ object-oriented framework used in the development of KLAX. VII. OPEN ISSUES Many issues crucial to the C2 style have been explored in detail and several applications completed. Nonetheless, assessing any new architectural style takes many years. When pipe and  
A component- and message-based architectural style for GUI software

July 1996

·

464 Reads

·

529 Citations

IEEE Transactions on Software Engineering

While a large fraction of application code is devoted to graphical user interface (GUI) functions, support for reuse in this domain has largely been confined to the creation of GUI toolkits (“widgets”). We present a novel architectural style directed at supporting larger grain reuse and flexible system composition. Moreover, the style supports design of distributed, concurrent applications. Asynchronous notification messages and asynchronous request messages are the sole basis for intercomponent communication. A key aspect of the style is that components are not built with any dependencies on what typically would be considered lower-level components, such as user interface toolkits. Indeed, all components are oblivious to the existence of any components to which notification messages are sent. While our focus has been on applications involving graphical user interfaces, the style has the potential for broader applicability. Several trial applications using the style are described



A Component- and Message-Based Architectural Style for GUI Software

April 1995

·

35 Reads

·

176 Citations

Proceedings - International Conference on Software Engineering

While a large fraction of application system code is devoted to user interface (UI) functions, support for reuse in this domain has largely been confined to creation of UI toolkits ("widgets"). We present a novel architectural style directed at supporting larger grain reuse andjexible system composition. Moreover, the style supports design of distributed, concurrent, applications. A key aspect of the style is that components are not built with any dependencies on what typically would be considered lower-level components, such as user interface toolkits. Indeed, all components are oblivious to the existence of any components to which notification messages are sent. Asynchronous notification messages and asynchronous request messages are the sole basis for inter-component communication. While our focus has been on applications involving graphical user interfaces, the style has the potential for broader applicability. Several trial applications using the style are described.

Citations (8)


... Just a few examples are Alloy [11], ArchStudio [12], Titan [13], and Archie [14]. In this section, we highlight two archipelagos: the ARCADE family of projects developed between 2009 and present [15]- [17], and the c2.fw family of projects developed between 1995 and 2015 [18]- [21]. Both families have publicly available code bases. ...

Reference:

Architectural Archipelagos: Technical Debt in Long-Lived Software Research Platforms
A Component- and Message-Based Architectural Style for GUI Software
  • Citing Conference Paper
  • April 1995

Proceedings - International Conference on Software Engineering

... is development initiated the era of Open Hypermedia Systems (OHS). e focus of integrating third party applications was a focal point, aaempting to bring hypermedia services to users' everyday computing environment [21,63]. ese eeorts gave birth to systems such as Devise [29] (demonstrating the integration of Microsoo Word with an hypermedia system), HyperDisco [66] (successfully integrating XEmacs), or Microcosm [32] (integrating Microsoo Calendar, WAIS, and Gopher). ...

An Architectural Model for Application Integration in Open Hypermedia Environments
  • Citing Conference Paper
  • January 1997

... Nevertheless , it is not evident how Microcosm could be extended in order to support some of the other important features. It is worth mentioning that a number of open hypermedia systems have been used to enrich the Web with external links by considering the Web as a client for these open hypermedia solutions [4, 6]. The XLink standard supports so-called extended links which can be stored in linkbases and be used to realise bi-and multi-directional links. ...

Chimera: Hypermedia for heterogeneous software development environments

ACM Transactions on Information Systems

... According to Ref. [15], the Web-based environment has the potential to be the infrastructure for a global software engineering environment which can support software evolution in all steps of its lifecycle, regardless of the number of individuals involved in the software project and their stations. The easy recruitment of human resources for software projects is considered an encouragement and outcome of this process. ...

Web-Based Development of Complex Information Products

Communications of the ACM

... Several reasons led to this evolutionary step. One was that the design of the OHP turned out to be complicated [2]. Moreover, e orts were concentrated on supporting di erent structure paradigms within the same system, such as taxonomic or spatial hypertext as well as making their development and tailoring easier. ...

A Critique of the Open Hypermedia Protocol.

... Once a task has been selected, the simulation uses the estimates made by the developer to generate an associated distribution, and simulates the actual effort required for the completion of the task. If the task cannot be accomplished within the available time, and if the developer is unwilling to work beyond the allocated shift time, then that phase is abandoned and remains open for the next 12 developer. It is also possible for the developer to work overtime. ...

World Wide Web Distributed Authoring and Versioning (WebDAV): An Introduction
  • Citing Article
  • March 1997

StandardView

... Although the lack of Graphical User Interface [26] in the software makes its usage difficult to some extent, the software can be used along with many GUI programs as a powerful simulator motor. In other words, users can use other GUI software programs to provide text inputs for Energy Plus and facilitate their required results [27]. ...

A component- and message-based architectural style for GUI software

IEEE Transactions on Software Engineering