🚀 go-pugleaf

                         CALL FOR PAPERS
			 ===============
             OBJECT CURRENTS ONLINE HYPERTEXT JOURNAL             
	        NEW MONTHLY OBJECT-ORIENTED FORUM
                                   
                  Editor:           Bob Hathaway
                  Publisher:        SIGS
                  Premier Issue:    January 1996
                  Jan Articles Due: December 1 (3-5pp, 12/5 latest)
                  Submissions To:   75027.1663@compuserve.com
                    After 11/14/95, Use Contact Points:
                          bob_hathaway@notesgw.compuserve.com
                          ph:  312.327.2121

Bob Hathaway and SIGS are proud to announce Object Currents - the first
significant hypermedia journal devoted to object-oriented technology.
This is the first call for papers for the premier January issue, and
article summaries may be sent early for possible prior approval.

Object Currents' Policy and Contributors' Guidelines are included below
and should be read in full prior to article submission.  Articles may not
have been previously published, but papers and articles on the net are
welcome.

Object Currents will present a complete new free journal with Departments,
Columns, and Feature Articles, along with 8 to 10 *new* articles from SIGS'
Journals - JOOP, ROAD, C++ Report, Object Magazine, Smalltalk Report, X
Journal, etc.  Advertisers' queries are most welcome.

Send email for a discussion of honorarium (Authors' fees).

Object Currents provides unique opportunities to authors, readers, and
advertisers with WWW hypertext multimedia, such as access to home pages
and databases, and in advanced object-oriented coverage.

Object Currents' unique hypertext media provides for advances over earlier
journals - links to home pages, sites, databases and information servers,
interaction, graphics, code retrieval and execution, expanded pages, and
video - and this superior medium should be exploited to its fullest possible
extent.  This not only presents a unique opportunity to authors and
advertisers, but to Object Currents' readership as well.  From the
Guidelines below:

  Authors should capitalize on the unique multimedia and hypermedia  
  nature of Object Currents, as Object Currents is the first significant
  WWW journal for software development.   Hypermedia provides a unique
  opportunity for  the innovation of superior articles and information
  systems technology. 
 
  All forms of hypermedia links and multimedia are strongly encouraged in  
  submissions including text, images, audio, video, and true interactivity.   
  CGI bridges to external databases and information servers are also  
  encouraged, although commercial uses will be judged along strict  
  relevance criteria. 


  [...] First priority is given to new and advanced topics of real importance
  to the object community, including applied research and development and new
  techniques and systems.  Advanced topics and techniques include but are not
  limited to delegation languages, advanced programming techniques and idioms,
  advanced use of methodologies, reflective meta-systems, new visual systems,
  GUI and hypermedia, and new methods, processes, and metrics.  New systems
  and their use include but are not limited to programming languages, CASE
  and meta-CASE, databases, operating systems, and distributed systems.  All
  articles should have emphasis on new technology and their use, but can  
  include the full range of traditional topics in object technology from  
  analysis to design and implementation, research and theory to practical[...]


Object Currents Issue Inventory: 
  SIGS articles: 	    8 to 10 articles from current SIGS Publications
			      per issue (JOOP, ROAD, Obj Mag., C++ Rpt, etc.)
  Object Currents Articles: 2 to 4 per issue. 
  Columns:                  Several columns will appear from regular
			      columnists on important topics. 
  Newsgroup Dialog:         Extrapolated subjects with commentary. 
  Fun and Games:            Puzzles to be picked up from the C++ Report  
                              and the net (Obfs. C++). 
  Questionnaire:            W/compiled results from last issue.   
  SIGS Bookshelf:           Book reviews and summary. 
  Movers & Shakers:         Interview or profile of object industry VIPs. 
  Code Watch:               Source code, from both SIGS journals and  
                              elsewhere, such as on the net. 
  Editorial Comments:	    By both authors and readers are encouraged. 
  This week in OT:	    Prepared by SIGS News Editor. 

Several columnists have already been selected including:
  Watts Humphrey:     SEI Process Director, CMM & PSP Inventor
  Bertrand Meyer:     Eiffel, Object-Oriented Design and Software Engineering
  Peter Coad:         Leading OO Methodologist
  David Shang:        OO Programming Language Designer, Motorola Labs
  Francois Bancilhon: President, O2 Technology, Leading ODBMS
  Others to be announced...


Articles for the Premier January issue are due by December 1; however,
with prior approval may arrive by December 5.  Thereafter articles are due
5 weeks before the first of the month of issue, on the 23rd.

Good luck!

Best Regards,
Bob Hathaway


OBJECT CURRENTS HYPERTEXT JOURNAL
  POLICY AND CONTRIBUTORS' GUIDELINES 
Editor:    Bob Hathaway 
Publisher: SIGS 
Date:      10/22/1995 
Copyright SIGS/Bob Hathaway 1995 
 
Authors' Guidelines 
Object Currents presents the first significant hypermedia journal to provide  
developers and managers of object-oriented systems with a full range of   
articles covering the entire spectrum of object technology.  Object Currents 
articles are accompanied by several articles from SIGS' journals, but are set  
apart by their "eye on the future" perspective.  First priority is given to
new and advanced topics of real importance to the object community, including  
applied research and development and new techniques and systems.  
Advanced topics and techniques include but are not limited to delegation  
languages, advanced programming techniques and idioms, advanced use of  
methodologies, reflective meta-systems, new visual systems, GUI and  
hypermedia, and new methods, processes, and metrics.  New systems and  
their use include but are not limited to programming languages, CASE and  
meta-CASE, databases, operating systems, and distributed systems.  All  
articles should have emphasis on new technology and their use, but can  
include the full range of traditional topics in object technology from  
analysis to design and implementation, research and theory to practical  
applications advice for real engineering and commercial environments, all  
relevant object-oriented programming languages, including but not limited  
to C++ and Smalltalk, and other relevant areas including interoperability  
to X Windows and GUI. 
 
Authors should capitalize on the unique multimedia and hypermedia  
nature of Object Currents, as Object Currents is the first significant WWW
journal for software development.   Hypermedia provides a unique
opportunity for  the innovation of superior articles and information
systems technology. 
 
All forms of hypermedia links and multimedia are strongly encouraged in  
submissions including text, images, audio, video, and true interactivity.   
CGI bridges to external databases and information servers are also  
encouraged, although commercial uses will be judged along strict  
relevance criteria. 
 
Audience 
Object Currents' intended audience comprises all involved in and effected by  
object-oriented technique and technology, such as programmers, software  
engineers, systems and applications developers, progressive students,  
project leaders, managers, and users of object-oriented systems, with the  
purpose of providing more quick and effective acceptance and  
improvement of existing object practice, strategy, technology, and  
understanding. 
 
Vision 
A software development community utilizing the best known practice and  
experience of object-oriented technology.  A hypermedia network  
supporting object-oriented technology transfer and the continual  
improvement of object technology with the ultimate aim of fostering  
continued progress within the software community. 
 
Mission 
To present the latest in object-oriented theory, practice, and experience in a 
way that is most immediately useful to the intended audience; and to 
encourage the highest levels of quality and excellence within the software 
development community through object technology - to achieve  
Object Currents' vision - through innovative use of the latest in hypermedia
and multimedia technology. 
 
Objectives 
1) To be the primary conveyance of object-oriented information, resource,  
    technique, and technology. 
 
2) To provide an exemplary hypermedia medium through Object Currents;
to  be a leader on the "Information Superhighway".  Object Currents' authors  
should be innovative in the use of hypermedia in submissions. 
 
3) To link Object Currents and the Official WWW/Internet Object-Oriented  
FAQ for the purpose of fulfilling Object Currents' vision and mission. 
 
4) To provide a weekly online news service on new and important  
developments in object technology. 
 
5) Contributors' Objective: To support successful widespread acceptance  
and growth of object technology by authoring Object Currents' articles and  
through use of  multimedia and hypermedia composition. 
 
Editorial Outline and Features 
 
Contents 
Object Currents presents a full range of object-oriented articles pertaining
to  new and advanced object technology.  This includes all areas from  
programming languages, methodologies, software engineering,   
breakthrough ideas, theory and experience from the software industry, and  
etc.   Reviews of existing products, problem/solution papers. and other  
important areas from the object domain will also be considered. 
 
Format 
Color, 40 to 60 page on-line magazine.  
Html preferred, with creative use of multimedia and hypermedia strongly
encouraged. 
Frequency: 12 times/year. 
 
  Issue Inventory: 
 
    Feature articles: 	 8 to 10 articles from  SIGS Publications per  
                         issue. 
    Object Currents Articles: 2 to 4 per issue. 
    Columns:             Several columns will appear from regular   
                         columnists on important topics. 
    Newsgroup Dialog:    Extrapolated subjects with commentary. 
    Fun and Games:       Puzzles to be picked up from the C++ Report  
                         and the net (Obfs. C++). 
    Questionnaire:       W/compiled results from last issue.   
    SIGS Bookshelf:      Book reviews and summary. 
    Movers & Shakers:    Interview or profile of object industry VIPs. 
    Code Watch:          Source code, from both SIGS journals and  
                         elsewhere, such as on the net. 
    Editorial Comments:	 By both author and readers are encouraged. 
    This week in OT:	 Prepared by SIGS News Editor. 
 
Description of Contents 
 
Object Currents accepts articles in the following classifications: 
 
Articles (3 - 5 pages) 
All submitted articles must satisfy some genuine need in the software  
community with respect to object-oriented development, be highly  
informative and lucid, and be appropriate to the intended Object Currents 
audience.  Articles containing new and advanced technology or method, with 
an "eye on the future"  perspective, and making best use of hypermedia will 
receive highest priority.  
 
Article sections should be numbered.  Articles must have a brief one or two  
paragraph abstract/summary. Recommended are sections on   
introduction/background, goals and audience, unique contribution,  
problems, benefits, issues and related works, conclusion, and     
acknowledgements and references, as appropriate.  Diagrams and examples, 
including code fragments and complete programs, should be plentiful to 
exemplify concepts. 
 
 
Series (3-5 pages, 2-8 installments) 
A series is a collection of articles offering the author an opportunity to  
address a topic in great depth.  The series may run from two to eight  
installments.  Series should be clearly partitioned into subtopics. 
 
Column (2-3 pages) 
Columns are designed to provide an ongoing discussion of a topic area,  
offering the columnist an opportunity to cover a topic in great breadth over  
an extended period of time, and to track changes and trends in the topic  
area as the technology matures.  Over time, the readers of a column should  
gain an    appreciation for the approach and style of the columnist and be  
able to identify the people, companies,  and products involved.  Editorial  
comments by both the author and readers are encouraged. 
  
Newsgroup Dialog 
The editor will take a thread or threads from the comp.object newsgroup  
and provide commentary.  Such threads may be started by the Editor and  
may be related to the current issue. 
 
Fun and Games 
Puzzles to be picked up from the C++ Report and the net.  Puzzles can  
include obfuscated programming  code, preferably from a well-known  
language, or any other sort. 
 
Questionnaire 
A questionnaire will appear in each issue raising questions of importance  
to the object community, typically concerning the issues raised by that  
issue.  The results from the last questionnaire will appear in the next issue
of Object Currents. 
 
SIGS Bookshelf (2-3 pages) 
Reviews of books, videos, and conferences.  These should have the "eye on  
the future" perspective of Object Currents.  A review should describe the  
purpose, content, and intended audience of the item and make critical  
comments on its accuracy and success in fulfilling its purpose.  If  
appropriate, the author    should comment on the suitability of the item for 
educational purposes. 
 
Movers & Shakers 
Interview or profile of object industry VIPs.  An interview or profile should
discuss the "movers" background, such as research interests, current line of  
work and primary contributions, primary work today, object of interview or  
profile, and conclusion.  An "eye on the future" perspective should be    
maintained, including a discussion on where the "movers" contribution  
will bring the object community in the near future. 
 
Code Watch 
Source code will be provided at the SIGS site, possibly mirrored from  
another.  This code may come from SIGS journals or anywhere, such as on  
the net. 
 
Editorial Comments 
Comments on the previous Object Currents issue, including other editorial  
comments, provides a means of feedback and interaction for both author  
and reader. 
 
 Potential topic areas are enumerated below; this list is not exhaustive and  
creativity is encouraged.  Topics should be drawn from new and advanced  
areas of  object technology.  SIGS topics are very similar, but Object Current
articles emphasize the latest and most advanced technology, how it should  
be incorporated today, and where it is leading tomorrow. 
 
Applications 
Authors should discuss how advanced object technology should be used to  
improve current practice.  Successes and failures can provide valuable  
feedback on future directions and what to follow and what to avoid.  How  
new or advanced techniques improve quality, productivity, or problem  
solving should be reported.  Learning curves, obstacles and their removal,  
required support, metrics optimization, and other issues where  
improvement is needed in the software industry today should be addressed.   
Transitioning from old to new technology can be addressed. 
 
Example Topic Areas: 
- Commercial, engineering, and scientific applications. 
- Systems support and impediments 
- GUIs, visual programming, hypermedia 
- Application frameworks and patterns 
- Purchased class libraries 
- New class library ideas 
- Application portability 
- New standards 
 
Hypermedia 
The World Wide Web has been described as object-oriented.  New approaches 
to hypermedia, especially the World Wide Web, are desired.  New and  
innovative use of the Web and/or hypermedia by object-oriented applications.
 
Example Topic Areas: 
- The object-oriented WWW 
- Better approaches to hypermedia with object technology 
- Innovative use of hypermedia and the WWW by object-oriented applications 
 
Idioms, Languages, Environments, and CASE 
More powerful and expressive idioms and techniques in object-oriented  
programming are desired.  New languages and environments can be
discussed,  including research languages. New paradigms in OO, such as 
delegation,  and new environments, such as metacase, are of importance
today.   Compare different approaches and implementations.  Issues of  
expressiveness, flexibility, orthogonality, power, correctness,  
portability, availability, suitability, and style are of interest.
Subjectivity is a factor in the choice and acceptance of languages and
environments, and  should be kept in mind. 
 
Example Topic Areas: 
- New constructs in OO 
- Best use of new language or environment - Is it for the reader? 
- New CASE and why it should be used in real development 
- New Idioms or advanced programming techniques to follow 
- Reflective systems and extensibility 
- Metasystems 
- Advanced use of polymorphism 
- Advanced uses of inheritance: multiple, dynamic, shared, etc. 
- Designing for reuse 
- Utilizing reuse 
- Prototyping 
- Migration and coexistence 
- Efficiency/optimization vs. power expressiveness 
- New Standards 
 
Databases 
New developments and advanced topics in OODBs can be addressed.   
Where, when, and why a new technology is required.  Reasons for  
transition to and acceptance of object databases including advantages (over
older and/or other approaches) and new ideas should be presented. 
 
Example Topic Areas: 
- New OODB technology 
- New and novel uses of OODBs, such as for business objects 
- Distribution, concurrency, reliability, security 
- Advanced Languages support 
- Uses and  Integration with other object systems - E.g. languages, CASE,
  business objects 
- New object query languages and use and 4GLs 
- Schema evolution and its importance 
- Superiority of new OODB approaches over others 
- New standards and ideas 
 
Analysis And Design Methodology 
New techniques in analysis and design are always being devised.  Older  
methods are evolving and fusing into newer methods.  The need to utilize  
the new methodologies and how to best achieve their acceptance is of real  
importance today.  Identifying future trends is of interest to readers.   
Comparisons between the new methodologies and what they imply, or at  
least why the new technique is superior. 
 
Example Topic Areas: 
- New and better methodologies and their use 
- Best or creative uses of OOA/D, perhaps in new application domains, such as
  business. 
- Most relevant domains of use, strengths and weaknesses 
- New techniques proven to be effective 
- CASE/METACASE support 
- Extensibility and reuse 
- Prototyping 
- Use in processes 
- New ways to perform reviews and walkthroughs 
- Improved cost drivers, moving effort upstream 
- Standards, including new fusion efforts 
 
Process 
Software engineering processes are a hot topic today.  The SEI's CMM  
level 1.0/2.0, ISO SPICE and the modern management practice of process  
improvement are of great relevance to today's software development.   
Discuss how object methodologies and technologies fit in with and better  
support modern software engineering processes, such as Boehm's Spiral  
Model of development. 
 
Example Topic Areas: 
- New and better development processes - how they relate to OO 
- OO's basis in modern and flexible processes, especially in analysis and
  design 
- Experience with modern process and OO 
- Handling the transition to modern from legacy processes, such as the
  waterfall model 
- Novel use of analysis models 
- Metrics and process 
- Process optimization 
- Process and methodology, suitability of various methods to various processes
  of development 
- Process specialization and generalization - what should be tailored and what
  should be standardized intra- and inter- organizationally. 
- Standards - ISO/SPICE, SEI, etc. 
 
Management - OD - Project Management - Testing 
Nontechnical issues affecting OO transition and operationalization include  
how developers, managers and users, respond to and are affected by the  
introduction of object technology.  Psychology of transition and change,  
organizational improvement, individual, team, and organizational  
learning, and other "people" issues can be addressed.  Also how new  
object-oriented technologies can affect project management: planning and  
estimating, SCM, quality, and testing. 
 
Example Topic Areas: 
- Reduced cycle time, reduced time to market 
- Improved metrics 
- Applying ISO 9000, TQM,  CMM, ISO/SPICE with object development 
- Improved business measures, e.g.  ROI 
- Introduction of new techniques, innovative approaches 
- New management techniques for object development and integration 
- Better individual, team, and enterprise-wide learning, coordination, and  
  integration 
- For developers, successfully managing upwards.  Bringing improvement to
  your organization. 
- For managers, successfully managing the development staff. 
- Obstacles of resistance to new object technology and overcoming them 
- Pitfalls and errors to avoid 
- Organizational support during the learning period, and minimizing the  
  learning curve. 
- Quelling overanticipation of reuse or the "silver bullet" syndrome with OO. 
- Benefits and drawbacks of empowerment to object development 
- Staffing for OO development - e.g. Boehm's 5 principles 
- Corporate object management 
- Strategic object modeling: enterprise-wide objects 
- Enterprise modeling and design 
- Objects as a corporate resource 
- The changing role of developers in shops in which the product is not  
  technology 
- Project resourcing: changes in developers roles 
- Benefits, drawbacks, management of prototyping 
- Managing, controlling development, discovering/sharing of reusable  
  components 
- Dealing with user needs and expectations 
- Standards 
- How do object-oriented systems call for a new testing paradigm? 
 
Education and Training 
How the new OO techniques are best taught and how training should be  
provided is of real importance today.  One Level 5 organization provides  
45 days training to all developers before starting, is this best?  What are
the alternatives?  The need for improved education and training in both  
academia and industry, especially with regards to real-world development,  
is of importance.  How should new OO techniques be taught or used in  
initial development efforts? 
 
Example Topic Areas: 
- Application of new learning techniques to object education; such as learning
  tools 
- Teaching/learning object technology 
- Experience reports 
- Making the transition from procedural to object environments 
- Transitioning from programming to object-oriented analysis, design, and  
  programming 
- Learning curves.  How long does it take to reach proficiency, or various 
levels of expertise? 
- How can the learning curve be optimized? 
- Humphrey's PSP 
 
 
Contributors' Guidelines Object Currents 
 
Submissions 
All submissions must be sent directly to the Editor on diskette or via email.
All articles are subject to peer review by the Editorial  
Board and selected members of the object community.  Notification of  
acceptance and assignment to an issue will shortly follow the review process.
All submissions are final; material will not be returned.  Authors  
are required to assign copyright to SIGS publications.  Copyright forms  
will be sent upon notification of acceptance. 
 
Style 
We request the following elements of style for all submissions: 
- Liberal use of WWW hypermedia facilities and multimedia are strongly  
  encouraged.  Object Currents provides a unique opportunity to present
  information in a superior way to readers, and this should be taken advantage
  of to the fullest extent possible. 
- Open articles with a few strong paragraphs to attract readers' attention.
  An introductory abstract is preferred. 
- Highlight possible pull-quotes.  Keep pull-quotes in mind when writing. 
- No double spaces, even after periods. 
- No double returns, even after paragraphs. 
- Clearly mark major and minor subheads <1>, <2>, etc., if possible. 
- Use tabs instead of spaces for formatting tables, lists, code, etc. 
- Do not manually hyphenate; the page layout software will do this 
- Omit headers and footers. 
- Literature citations should be placed numerically in order of appearance at
  the end of the article; text citations should appear in parenthesis. 
- Footnotes should appear directly under the callout in the text. 
- Charts or other graphics should be submitted in clear, reproducible hard
  copy. 
 
Format 
 
The preferred format for files is html in ASCII or Microsoft Word (V 6.0 or 
later preferred).  ASCII and Microsoft Word format will also be accepted,
preferably with hypertext formatting.  Please note format clearly on
diskette.
Media: Disks accepted: 
  DOS 3.5" 
  Email: RTF or ASCII files sent over Compuserve, 75027,1663   
  (75027.1663@compuserve.com). 
 
Contact Bob Hathaway, 75027.1663@compuserve.com, with trouble on submissions.
Alternate contact points are rjh@geodesic.com, and in the last case, try 
312.871.4807 or lotech@inch.com. 

After 11/14/95, use contact points:
  312.327.2121
  bob_hathaway@notesgw.compuserve.com
   
Manuscript Submission Schedule 
 
1996 ISSUE
  Articles are due 1 week and one month prior to issue, subject to change. 
  January	- December  1 - Premier Issue
  February	- December  23 
  March		- January   23 
  April		- February  23 
  May		- March     23
  June		- April     23 
  July		- May       23 
  August	- June      23
  September	- July      23
  October	- August    23 
  November	- September 23
  December	- October   23