Service Manuals, User Guides, Schematic Diagrams or docs for : xerox sdd memos_1977 19770415_April_Status_Report_For_Common_Software

<< Back | Home

Most service manuals and schematics are PDF files, so You will need Adobre Acrobat Reader to view : Acrobat Download Some of the files are DjVu format. Readers and resources available here : DjVu Resources
For the compressed files, most common are zip and rar. Please, extract files with Your favorite compression software ( WinZip, WinRAR ... ) before viewing. If a document has multiple parts, You should download all, before extracting.
Good luck. Repair on Your own risk. Make sure You know what You are doing.




Image preview - the first page of the document
19770415_April_Status_Report_For_Common_Software


>> Download 19770415_April_Status_Report_For_Common_Software documenatation <<

Text preview - extract from the document
                                          XEROX
                                   Jnror,mation Technology Group
                                   Systems Development Division
                                          April 15, 1977



To:               Wendell Shultz

Copies to:        David Liddle, Chuck Thacker, Ron Rider, Bob Metcalfe, C. Simonyi,
                  S. Wallace, D. Stottlemyre, J. Szelong, P. Heinrich, L. Bergsteinsson

From:             Charles Irby
Subject:          April Status Report for Common Software

Filed on:         Progress.Apr



User Interface:
Work continues on the Diamond User Interface Specification. Progress has been somewhat
slower than expected because of unexpected distractions, vacations and sick leave. Work to
date has focused on the user's conceptual model of the overall system. Although there
remain open issues in this area, we are now turning our attention to scenarios based on that
model and then on to details of the command language. This process should clarify the
issues and allow more reasoned decisions possible at the model level.

The user interface as specified is more grandios than is necessary for Janus-I. We feel it is
necessary to take this step and then to scale back to Janus-l to insure that the user
interface will extend gracefully to Janus-2 and beyond.            Consequently, when this
specification is complete, we will have to determine the appropriate subset of the facilities
for Janus-l Early Bird and help the Prototype Software Group implement that. The
Applications Software Group will assist in the subset selection and we will help them write
the Janus-l Funtional Specification. Activities are just beginning in these areas.

Some resources have gone toward .helping Harold Hall staff the Functional Test Group,
helping to select and interview prospective people. We are also helping t.o write a
follow-up action plan for assessing the need for and specifics of a pointing device for
Janus-I.

The desktop and graphics prototype built by Bob Ayers (in Mesa) has contributed very
significantly to the development of a conceptual model and command language for these
areas. This program is complete enough to be used as the basis of some user tests and
demonstrations of the ideas we have been exploring.


Data Management:
 The data management group is participating heavily in the newly organized file and data
 management working group. Several meetings have taken place to date. The series is
 expected to last about two months and to result in possible modifications to the Pilot
,funtional Specification and contribution to the Data Management Funtional
 Specifications plus a design for the file and data mangement facifities.



◦ Jabse Service Manual Search 2024 ◦ Jabse PravopisonTap.bg ◦ Other service manual resources online : FixyaeServiceinfo