Conference vaxuum::online_bookbuilding

354.0. "Phase 0 open for Bookreader Version 4.0" by DECWET::TARDIFF (It's all rock-and-roll to him.) Wed Jun 27 1990 06:44

 






          DIGITAL       INTEROFFICE MEMORANDUM


          TO:      Interested Parties        DATE: 27 June 1990
                                             FROM: Michael J. Tardiff
                                             DEPT: Bookreader Prod-
                                                   uct Management
                                             EXT:  (206) 865-8728
                                             LOC:  ZSO
                                             ENET: rust::tardiff


          SUBJECT: Announcing Opening of Phase 0 for Bookreader Ver-
                   sion 4.0

          Phase 0 for Bookreader Version 4.0 is now open; we solicit
          your suggestions and requirements as we plan Bookreader's
          evolution into an industry-leading online information ac-
          cess tool. This memo briefly describes Bookreader's his-
          tory and status; appended to this memo is a template that
          you can use to organize and submit your requirements and
          comments. Along with the template are instructions on where
          to send your input.

          Bookreader is an online information access tool designed
          to make the use and reading of technical documentation and
          other information easy and convenient. Digital currently
          ships documentation for over fifty products in Bookreader
          online format, and plans to ship all software technical doc-
          umentation for ULTRIX, VMS, and Digital layered products
          in the coming months. We intend to make the authoring tools
          we use available to our business partners and customers so
          that they can supplement the existing pool of online in-
          formation available to Bookreader. We further plan to ex-
          tend the number and range of authoring tools that produce
          Bookreader-compatible output.

 


                                                           Page 2



          Bookreader first was available with VMS Version 5.1 as a
          DECwindows out-of-the-box application; since that time, we
          have added additional functionality and features. Version
          2.1, which currently ships with VMS Version 5.4, and will
          ship with a release of ULTRIX Worksystem Software at the
          end of this year, represents the accomplishment of Bookreader's
          original design goal: to make it possible to ship and use
          the mass of VMS and VMS layered product hardcopy documen-
          tation in online form on CDROM while retaining all the in-
          formation, attributes, and usability of the printed ver-
          sion.

          Bookreader Version 3.0 is currently under development, and
          will be available with DECwindows Version 3.0 in Spring 1991
          on both ULTRIX and VMS. The changes in Bookreader Version
          3.0 begin the next stage of development: taking advantage
          of the fact that we have all this information online and
          doing things that couldn't be done with hardcopy. The pro-
          ject plan for Bookreader Version 3.0 is available in var-
          ious formats at the following location:

               BULOVA::DECW$PUBLIC:[PLANS]BOOKREADER_V3_PLAN.DECW$BOOK
                                                                .DECW$BOOKSHELF
                                                                .MEM
                                                                .PS

          We hope to ship Version 4.0 in the later part of
          calendar 1991; given that ambitious goal, we will close
          this phase and move into Phase 1 planning soon. Please
          submit your requirements and suggestions as soon as
          possible, so that we can properly consider your input.

          To submit a suggestion or requirement for Bookreader
          Version 4.0, use the template below to organize your
          input, then mail the completed template (beginning on
          28 June 1990) to

 


                                                           Page 3



                  DECWET::BOOKREADER-REQUIREMENTS

          Your input will be posted as a base note in the

          DECWET::BOOKREADER-REQUIREMENTS notes conference; you
          are invited to examine and comment on the requirements
          posted in that conference.

          If you have questions about Bookreader or this phase
          process, contact me by telephone in Bellevue,
          Washington, or by electronic mail.

          Thank you.

 


                                                           Page 4



                   Requirements Input Form for Bookreader

          Please extract this template to a file, complete it,
          and mail it to DECWET::BOOKREADER-REQUIREMENTS. An
          ASCII version of this template can be obtained in note
          2.0 of the DECWET::BOOKREADER-REQUIREMENTS notes
          conference, or copied from the following location:

                  DECWET::DOCLIB$:[OSPTG-PUBLIC]BOOKREADER-PHASE0-INPUT-FORM.TXT

          Contact Michael Tardiff at (206) 865-8728 (Pacific
          time), or send electronic mail to rust::tardiff if you
          have any questions.

          1. Submittor:

          2. Designated Responsible Individual:

                DTN:
                Node:
                Loc/Mail Stop:
                Position:

          3. Engineering or Marketing Group Supporting
             Requirements Request:
             Include the name and a brief description of the
             group.

          4. Abstract:
             Include a brief, single-paragraph, description of
             each requirement.

          5. Description:
             Include a detailed description of each requirement
             and an indication of what you hope to achieve.

          6. Schedule:
             Note any schedule concerns for dependent products.

                Specification available (as much detail as is
                appropriate):
                Prototype Available:

 


                                                           Page 5



                Test Schedule:
                Planned FRS:

          7. Benefit:
             Description of benefit, including substantiating
             data such as installed base, yearly revenue, and so
             on.

          8. Impact of Not Meeting Requirement:
             Describe impact to Digital if this requirement is
             not met. Explain with details in terms of lost
             opportunities and markets.

          9. Justification:
             Include here any other reasons for this request.

          10.Known Issues:
             Include statement of risks to either schedule or
             content.

          11.Support Documents:
             Identify any documents that add detail to the
             request.