home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.umcs.maine.edu
/
2015-02-07.ftp.umcs.maine.edu.tar
/
ftp.umcs.maine.edu
/
pub
/
WISR
/
wisr4
/
proceedings
/
tex
/
griss.bib
< prev
next >
Wrap
Text File
|
1991-10-29
|
21KB
|
501 lines
%% bib-strings.bib
%% M. Griss
@string{mlg="Martin L. Griss"}
@string{?="<<unknown>>"}
% From the UISYS compilation
@string{AAAI88 = "Proceedings of the Seventh National Conference on
Artificial Intelligence"}
@string{ACM = "Association for Computing Machinery"}
@string{CACM = "Communications of the {ACM}"}
@string{chi = "Proceedings of the Computer Human Interaction Conference"}
@string{chi88 = "Proceedings of the {ACM} {SIGCHI} 1988"}
@string{chi87 = "Proceedings of the {ACM} {SIGCHI/GI} 1987"}
@string{chi86 = "Proceedings of the {ACM} {SIGCHI} 1986"}
@string{chi85 = "Proceedings of the {ACM} {SIGCHI} 1985"}
@string{cmu = "Carnegie Mellon University"}
@string{cscw88 = "Proceedings of the Conference on Computer-Supported
Cooperative Work 1988"}
@string{cscw86 = "1986 Conference on Computer-Supported Cooperatiave Work"}
@string{d.cs="Department of Computer Science"}
@string{cs.d="Computer Science Department"}
@string{dcs87 = "Proceedings of the Seventh International Conference on Distributed Computing Systems"}
@string{dortmund91 = "Proceedings of the First International Workshop on Software Reuse"}
@string{ecoop89 = "Proceedings of the European Conference on Object-Oriented Programming"}
@string{ecoop88 = "Proceedings of the 1988 European Conference on Object-Oriented Programming"}
@string{ecoop87 = "Proceedings of the 1987 European Conference on Object-Oriented Programming"}
@string{HICSS18=
"Proceedings of 18th Hawaii International Conference on System Sciences"}
@string{HICSS20=
"Proceedings of 20th Hawaii International Conference on System Sciences"}
@string{HICSS22=
"Proceedings of 22nd Hawaii International Conference on System Sciences"}
@string{HPL="Hewlett-Packard Laboratories"}
@string{HPL-STL="Hewlett-Packard Laboratories/Software Technology Lab"}
@string{ICASE9=
"Proceedings of 9th International Conference on Software Engineering"}
@string{ICSE12=
"Proceedings of 12th International Conference on Software Engineering"}
@string{ICSE13=
"Proceedings of 13th International Conference on Software Engineering"}
@string{ICSE14=
"Proceedings of 14th International Conference on Software Engineering"}
@string{ieee="IEEE"}
@string{ieeecom="IEEE Computer"}
@string{ieeeex="IEEE Expert"}
@string{ieeesoft = "IEEE Software"}
@string{ieeetose = "IEEE Transactions on Software Engineering"}
@string{ijmms = "International Journal of Man-Machine Studies"}
@string{ISS91 =
"Proceedings of the 1991 Irvine Software Symposium"}
@string{joop = "Journal of Object-Oriented Programming"}
@string{mit ="MIT"}
@string{oods86 = "Proceedings of the International Workshop on Object-Oriented Database Systems"}
@string{oopsla86 = "{OOPSLA} '86 Conference Proceedings"}
@string{oopsla87 = "{OOPSLA} '87 Conference Proceedings"}
@string{oopsla88 = "{OOPSLA} '88 Conference Proceedings"}
@string{oopsla89 = "{OOPSLA} '89 Conference Proceedings"}
@string{oopsla90 = "{OOPSLA} '90 Conference Proceedings"}
@string{oopsla91 = "{OOPSLA} '91 Conference Proceedings"}
@string{osu="Oregon State University"}
@string{osu.ad="OSU, Corvallis, OR 97331"}
@string{practsoft = "Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments"}
@string{RDNET="R \& D Network"}
@string{scamc89 = "Proceedings of the Thirteenth Symposium on Computer Applications in Medical Care"}
@string{SDE4="Proceedings of the Fourth {ACM} {SIGSOFT} Symposium on Software Development Environments"}
@string{sei="Software Engineering Institute, CMU"}
@string{SEN="Software Engineering Notes"}
@string{SEPC="HP Software Engineering Productivity Conference"}
@string{sigmod87 = "Proceedings of the {ACM} {S}pecial {I}nterest {G}roup on Management of Data"}
@string{tois = "{ACM} Transactions on Office Information Systems"}
@string{UIST = "Proceedings of the ACM SIGGRAPH Symposium on User Interface Software and Technology"}
@string{usenix89 = "Proceedings of the 1989 Winter USENIX Technical Conference"}
@string{vldb85 = "Proceedings of the Eleventh International Conference on Very Large Databases"}
@string{vldb87 = "Proceedings of the Thirteenth International Conference on Very Large Databases"}
@string{vldb88 = "Proceedings of the Fourteenth International Conference on Very Large Databases"}
@string{vldb89 = "Proceedings of the Fifteenth International Conference on Very Large Databases"}
@string{WISR91 = "Proceedings of the 4th Annual Workshop on Software Reuse"}
% File: bus-kits.bib
% Date: Tue Oct 29 15:32:48 PST 1991
% DO NOT edit - made by [bib-subset bus-kits]
@inproceedings{ambras89
,author="Jim Ambras and Pankaj K. Garg and Randy Splitter"
,title="The {W}orkshop: {A} {T}eam {P}rogramming {E}nvironment"
,booktitle="Proceedings of the 1989 HP European Software Engineering
Conference"
,month= may
,year= 1989
,keywords="environment,hypertext,team-support, software-engineering"
,abstract={}
,comments="Also HP Labs report number STL-TM-89-09 (Company
Confidential)"}
@article{cagan90
,AUTHOR="Martin R. Cagan"
,affil="IDE"
,TITLE="The {HP} {Softbench} Environment: {A}n Architecture for a New
Generation of Software Tools"
,journal="Hewlett-Packard Journal"
,year=1990
,month=jun
,pages="36-47"
,note="(See other papers in this issue.)"
,abstract={Fill in}
}
@TECHREPORT{collins91
,TITLE = "Towards a Reusable Domain Analysis"
,AUTHOR = "Patricia Collins"
,affil = "HP CE~"
,INSTITUTION = "Hewlett-Packard Corporate Engineering"
,organization = "~"
,month = sep
,YEAR = 1991
,number = ""
,address = "Porter Drive, Palo Alto"
,entered-by = "Griss"
,found-in = "~"
,status = "~"
,keywords = "~"
,refs = "~"
,comments = {~}
,annote = {~}
,note = {To be presented at 4th Annual Workshop on Software Reuse,
Herndon, VA, Oct 18-22, 1991}
,abstract = {~}
}
@TECHREPORT{griss91
,AUTHOR="Martin L. Griss"
,affil="HP Laboratories"
,TITLE="Software Reuse at {H}ewlett-{P}ackard"
,INSTITUTION="Hewlett-Packard Laboratories"
,organization="Software and Systems Laboratory and Corporate
Engineering Software Development Processes"
,number="SSL-TM-91-01"
,year=1991
,month=jan
,note="Invited submission to the {\em First International Workshop on
Software Reusability}, Dortmund, July 3-5, 1991."
,abstract={In this paper, several software reuse related activities
at Hewlett-Packard are described. The paper focuses on a number in
which author has been involved over the past 6 years. Since November
1989, he has been investigating the opportunities for a systematic,
Corporate Software Reuse program for HP. He is working with HP
Corporate Engineering to define and execute such a program, involving a
combination of consulting, training, methods development, the writing
of a reuse handbook, and several pilot projects. He also leads two
research projects at HP Laboratories, one involving the development of
a prototype hypertext-based reuse library management system (Kiosk),
and the other exploring component-based software construction using
application development frameworks for distributed applications.}
,keywords={software reuse, hypertext, software libraries, C++}
}
@TECHREPORT{purtilo90
,TITLE = "The {P}olyLith {S}oftware {B}us"
,AUTHOR = "James Purtilo"
,affil = "U. MaryLand"
,INSTITUTION = "University of Maryland"
,organization = "Computer Science Department"
,month = ""
,YEAR = 1990
,number = "CSD 2469"
,address = "College Park, MD 20742"
,entered-by = "Griss"
,found-in = "referenced in purtilo91"
,status = "find"
,keywords = "software-bus"
,refs = "0"
,comments = {}
,note = {}
,abstract = {}
}
@INPROCEEDINGS{purtilo91
,TITLE = "A Methodology for Prototyping-in-the-Large"
,AUTHOR = "James Purtilo and Aaron Larson and Jeff Clark"
,affil = "University of Maryland and Honeywell
Corporation"
,BOOKTITLE = "Proceedings: 13th International Conference
on Software Engineering"
,YEAR = 1991
,month = may
,editor = ""
,pages = "2-12"
,organization = "IEEE"
,publisher = "IEEE Computer Society Press"
,address = "Los Alamitos, CA"
,entered-by = "Wosser"
,found-in = "cabinet"
,status = "See also Polylith"
,keywords = "prototyping, reuse, software bus, glue
language, MIC"
,refs = {[1] V. Basili, "Viewing maintenance as reuse-
oriented software development," IEEE Software, vol. 7,
pp.19-25, 1990.
[2] B. Boehm, Software Engineering Economics, Prentice-Hall,
1981.
[3] J. Carciofini et alia, LogLisp Programming System User's
Manual, Honeywell Systems and Research Center, 1987.
[4] F. DeRemer, H. Kron, "Programming-in-the-large versus
programming-in-the-small," IEEE Trans. on Software
Engineering, vol.2, pp. 80-86, 1976.
[5] J. Kimball, A. Larson, "A Change and Configuration
Management Model for the KBSA Framework," KBSA Framework
Final Technical Report, 1990.
[6] J. Purtilo, "New configuration management capabilities
using software toolbus organization," Proceedings of SOFTOOL
Conference on Configuration Management, pp.1-28, 1990.
[7] J. Purtilo, "The Polylith Software Bus," University of
Maryland CSD Technical Report 2469, 1990.
[8] J. Purtilo, E. White, "A Flexible Program Adaptation
System: Case Studies in Ada," To appear Journal of Systems
and Software, 1991.}
,comments = {Introduces {\em Promo}, a MIL, and {\em
Moblog}, a Lips-like exploratory prorgamming language.
These can be used to program and interconnect modules on a
software bus, {\em PolyLith}. }
,note = {}
,abstract = {Just as programming-in-the-small entails
fundamentally different activities from programming-in-the-
large, so is prototyping necessarily different when
performed within very large scale applications. This paper
defines prototyping as an experimental activity intended to
reduce risk of failure in a software product. In this
context, we explore the effect of scale in prototyping, then
describe a methodology for prototyping a large application.
Next we describe a system being developed to evaluate this
methodology, featuring a pair of languages (Promo and
Moblog) to serve both large-scale and component-level
prototyping needs. We conclude with a presentation of how
our methodology would be applied to a sample problem, a
fault-prediction subsystem within the Space Station Freedom
project.}
}
@MANUAL{ATT90
,TITLE = "RAPID/NM, Reusable Architectures for Transaction
Processing and Network Management Applications"
,author = "Doris Ryan"
,affil = "AT\&T"
,organization = "AT\&T"
,address = ""
,edition = ""
,year = 1990
,entered-by = "Wosser"
,found-in = ""
,status = ""
,keywords = "RAPID/NM"
,refs = ""
,comments = {}
,annote = {}
,note = {}
,abstract = {This document describes the RAPID/NM software and
services. The document contains: some background information on
RAPID/NM; descriptions of the new features supported by RAPID/NM
Release 2.1; a complete listing of RAPID/NM software components; a
discussion of the architecture types supported by these components;
two figures showing how components are integrated into architectures
and configurations. }
}
@TECHREPORT{wiederhold90
,TITLE = "Towards Megaprogramming"
,AUTHOR = "Gio Wiederhold and Peter Wegner and
Stefano Ceri"
,affil = "Stanford, Brown, Milano"
,INSTITUTION = "Stanford University"
,organization = "Dept. CS"
,month = oct
,YEAR = 1990
,number = "STAN-CS-90-1341"
,address = "Stanford, CA"
,entered-by = "Wosser"
,found-in = "cabinet"
,status = ""
,keywords = "reuse, mega-programming, mega-modules, glue-
language, databases"
,refs = "27"
,comments = {(Also Brown CS report 90-20)}
,annote = {}
,note = {}
,abstract = {Our goal in this paper is to develop an
architecture and methodology for megaprogramming. We define
megaprogramming as programming with very large modules
called megamodules that capture the functionality of systems
such as these used by banks, airline reservation systems,
and city transportation systems. Megamodules are internally
homogeneous, independently maintained systems whose life
cycle is managed by a software community with its own goals,
knowledge base, and programming traditions. We use the term
"ontology" to denote the declared entities that may
meaningfully be used within a megamodule and their internal
operations. A problem to be dealt with is the interaction
of ontologies.
Computations using megamodules are described by
megaprograms, written in a megaprogramming language. We are
concerned with interfaces of individual megamodules and with
the megaprogramming language for megamodule management.
Each megamodule must describe its externally accessible data
structures and operations; descriptions are stored in
libraries, called megamodule repositories, that have certain
data dictionary facilities. Megaprogramming languages
provide more flexible module management than traditional
methods of combining modules, and in particular may perform
transduction between modules on a variety of computer
systems. Modules will have different data representations.
Databases may be supported within megamodules with complete
autonomy. They are not directly accessed by megaprograms.
Some megamodules may share databases and use their
facilities to resolve conflicts due to concurrent access.
Input-output for human clients is generally performed by
specialized modules.
Megaprogramming allows us to think in terms of larger
abstractions than traditional programming, and is a form of
component-based programming in the large. It has the
potential of substantially increasing modeling power and
software productivity because its powerful encapsulation
allows very large software systems to be managed as
collections of megamodules. Programming within a megamodule
can be handled by traditional techniques for programming,
while interaction of megamodules is governed by
megaprogramming protocols.}
}
@TECHREPORT{beach91
,TITLE = "Connecting Software Components with Declarative Glue"
,AUTHOR = "Brian Beach"
,affil = "Software and Systems Laboratory"
,INSTITUTION = "Hewlett-Packard Laboratories"
,organization = ""
,month = Aug
,YEAR = 1991
,number = "HPL-91-152"
,address = "Palo Alto"
,entered-by = "Wosser"
,found-in = "cabinet"
,status = ""
,keywords = "software bus; software glue; reuse"
,refs = "9"
,comments = {}
,annote = {}
,note = {Submitted to 14th International Conference on Software
Engineering, Melborne, Australia, 1992}
,abstract = {}
}
@TECHREPORT{creech91a
,TITLE = "Using Hypertext In Selecting Reusable Software Components"
,AUTHOR = "Michael Creech and Dennis Freeze and
Martin L. Griss"
,affil = "Hewlett-Packard Laboratories"
,INSTITUTION = "Hewlett-Packard Laboratories"
,organization = "Software and Systems Laboratory"
,month = May
,YEAR = 1991
,number = "SSL-91-59"
,address = "Palo Alto, CA"
,entered-by = "Wosser"
,found-in = ""
,status = ""
,keywords = "software reuse,software libraries, component selection,
hypertext, Kiosk"
,refs = "34"
,comments = {}
,annote = {}
,note = {To appear in {P}roceedings of {H}ypertext'91, Dec 1991}
,abstract = {13}
}
@TECHREPORT{creech91
,TITLE = "KIOSK: {A} Hypertext-based Software Reuse
Tool"
,AUTHOR = "Michael Creech and Dennis Freeze and
Martin L. Griss"
,affil = "Hewlett-Packard Laboratories"
,INSTITUTION = "Hewlett-Packard Laboratories"
,organization = "Software and Systems Laboratory"
,month = Mar
,YEAR = 1991
,number = "SSL-TM-91-03"
,address = "Palo Alto, CA"
,entered-by = "Wosser"
,found-in = ""
,status = ""
,keywords = "reusable-workproducts, interactive browsers,
Cost ++ library import tool, Kiosk, reuse, software-process,
libraries, hypertext"
,refs = "34"
,comments = {}
,annote = {}
,note = {}
,abstract = {Making software reuse a systematic part of HP's software
process is considered to be of great importance. It is widely believed
that several factors influence effective software reuse. Among these, the
preparation and packaging of software workproducts (e.g. code,
documentation, tests, or designs) into libraries that enhance the user's
ability to find, understand and use them is of significant interest, as is
providing ways in which the user can take advantage of these structured
libraries. In this paper, we describe a process and technologies that can
facilitate this activity.
Kiosk is a system that contains and manages libraries of
reusable workproducts. The reusable libraries within Kiosk
have been linked together (via a hypertext representation)
in ways that will enhance a user's ability to find and
understand the components within these libraries. Kiosk
provides interactive browsers that allow the user to browse
and augment the libraries, as well as a tool (Cost++) for
importing existing software into the Kiosk environment.
This paper includes an overview of the software reuse
problem; a description of Kiosk's architecture, features,
benefits; the finding, editing, and presenting of library
information; the Cost++ library import tool, the structure
of reuse libraries within Kiosk; and an indication of future
directions.}
}
@ARTICLE{linton89
,AUTHOR = "Mark A. Linton and John M. Vlissides and Paul R. Calder"
,TITLE = "Composing User Interfaces with {InterViews}"
,JOURNAL = IEEECom
,YEAR = 1989
,month = feb
,pages = "8-22"
,entered-by = "Zarmer"
,found-in = "Zarmer's files"
,status = "found"
,keywords = "InterViews, X, windows, toolkits"
,comments = {Overview of InterViews, a C++ toolkit for building user
interfaces. Goals: per-user customizability, mixed graphical/text UIs,
O.O., separation of UI and semantics. Solution: equip programmers
w/toolkit of primitive UI objects that use common protocols, stress
construction by composition. Three main categories of interface
objects: interactors (composed into scenes), graphics (composed into
pictures), and text (composed into clauses). Four ways to compose
interactors: tiled (boxes and glue), overlapping (trays), stacked
(decks), and singly. Applications consist of subject code (semantics)
and view code (interface). [Comment: InterViews is still too low-level
for real appl. development: need, e.g., standard dialog box instead of
components to build one. JJ]}
}
@TECHREPORT{zarmer89
,AUTHOR = "Craig Zarmer"
,TITLE = "{ACEKit} Overview"
,INSTITUTION = "Hewlett-Packard Laboratories"
,YEAR = "1989"
,month = "nov"
,number = "STL-89-29"
,address = "Palo Alto, Ca."
,entered-by = "Zarmer"
,found-in = "STL library"
,status = "found"
,keywords = "ACEKit, UI Tools, UIMS"
,note = {A brief overview of the ideas in Szekely and how they have
been instantiated in C++ as ACEKit. }
}
@TECHREPORT{zarmer90a
,TITLE = "{ACEKit}: An {A}pplication {C}onstruction
{T}oolkit Version 1.0"
,AUTHOR = "Craig L. Zarmer"
,affil = "Hewlett-Packard Labs"
,INSTITUTION = "Hewlett-Packard Laboratories"
,organization = "Software and Systems Laboratory"
,month = Dec
,YEAR = 1990
,number = "SSL-TM-90-08"
,address = "Palo Alto, CA"
,entered-by = "Wosser"
,found-in = ""
,status = ""
,keywords = "application construction environment, ACEKit, C++, Class Class"
,refs = "4"
,comments = {}
,annote = {}
,note = {}
,abstract = {ACE stands for Application Construction
Environment, and is a research program within HP Labs to
make applications more useful and usable, as well as improve
the process of building them. ACEKit is the lowest layer of
the ACE program, and addresses the needs of programmers. It
is an application architecture and associated software
library that breaks the application design process into a
series of steps, and provides clear abstractions for each.
It has some qualities of a User Interface Management System
(UIMS), some of a UI Toolkit, and some aspects that we
believe are unique.
This report describes in detail the process of building an
application with ACEKit, and the role of each class plays.
We assume familiarity with C++, and some familiarity with
InterViews will be helpful. A less detailed report on
ACEKit is available as (Zarmer 89).}
}