|
|
 |
|
 |
Volume 37, Number 2, 1998
San Francisco Frameworks |
|
Table of contents:  HTML ASCII |
|
This article: HTML ASCII |
Copyright info |
|
|
|
|
| |
|
An evolutionary approach to application development with object
technology - References |
|
by R. A. Henders |
|
|
|
Cited references and notes
- I. Jacobson, M. Christerson, P. Jonsson, and G.
Overgaard, Object-Oriented Software Engineering,
Addison-Wesley Publishing Co., Reading, MA (1992).
- B. F. Webster, Pitfalls of Object-Oriented
Development, M&T Books, New York (1995).
- A. H. Lindsey and P. R. Hoffman,
"Bridging
Traditional and Object Technologies: Creating Transitional
Applications," IBM Systems Journal 36, No. 1, 32-48
(1997).
- T. E. Potok and M. A. Vouk,
"The Effects of the
Business Model on Object-Oriented Software Development Productivity,"
IBM Systems Journal 36, No. 1, 140-161 (1997).
- D. A. Taylor, "The Use and Abuse of Reuse,"
Object Magazine 6, No. 2, 16-18 (April 1996).
- P. G. Basset, "The Paradox of Reuse," Object
Magazine 6, No. 2, 58-63 (April 1996).
- D. A. Taylor, Object-Oriented Technology: A
Manager's Guide, Addison-Wesley Publishing Co., Reading, MA
(1991).
- According to the APICS Dictionary, published
by the American Production and Inventory Control Society, Inc. (1987),
engineer-to-order products are "products whose customer
specifications require unique engineering design or significant
customization. Each customer order then results in a unique set of part
numbers, bills of material, and routings."
- According to the APICS Dictionary, with
mixed-mode manufacturing "the system supports coexistent manufacturing
capabilities of repetitive, process, and discrete manufacturing,"
where repetitive means "production of distinct units,
planned and executed to a schedule, usually at relatively high speeds
and volumes," process means production that "adds value
by mixing, separating, forming, and/or chemical reactions," and
discrete means "production of distinct items such as
automobiles, appliances, or computers."
- System APIs (application programming interfaces),
user spaces, and the User Interface Manager are available as part of the
OS/400™ operating system.
- References to servers and server protocols are from
Acacia Technologies Application Servers Users' Guide,
Release 8.4 (October 1995); available from Acacia Technologies.
- The Open Applications Group (OAG) was formed in 1995 as a
nonprofit organization dedicated to promoting open applications
integration (connectivity and multiple-source integration among
enterprise software applications). For more information, see Open
Applications Group Integration Specification; available from
http://www.openapplications.org.
- In conjunction with our investigation of Java and
our involvement with San Francisco, we have used J++™ from
Microsoft, Visual Cafe™ from Symantec, JBuilder™ from Borland,
and VisualAge™ for Java from IBM, as well as JDK from SunSoft,
versions 1.0.2 through 1.1.3.
- The San Francisco reference group consists of ten
software vendors who have collaborated with the San Francisco developers
and are early adopters of the frameworks.
- We did, however, see this as an advantage in the
development cycle. We were involved in testing two external drivers
(early versions of San Francisco) and were comfortable assuming that
development effort expended in working in Microsoft's Windows NT™
would be transferable to an AS/400 platform when the Java Virtual
Machine was available there.
- This figure is adapted from a presentation provided
by Paula Richards of IBM, when she was project manager for the San
Francisco project.
- For more information, see
http://www.sun.com.
- For more information, see
http://www.as400.ibm.com.
|
|
|
|
