• Aucun résultat trouvé

XEROX BUSINESS SYSTEI\tIS

N/A
N/A
Protected

Academic year: 2022

Partager "XEROX BUSINESS SYSTEI\tIS"

Copied!
3
0
0

Texte intégral

(1)

To: W. Shultz From: W. C. Lynch

Location: Palo Alto

XEROX

BUSINESS SYSTEI\tIS System Development Division

February 15, 1978

Subject: Pilot Status Report for February 78

Keywords: Pi lot, Status

File: [Iris]( Lynch> Feb78.Status .

Archive document #: To be assigned by Ode Bi n k ley

Staffing and Equipment

Tom Horsley has returned full time to Pi lot.

A number of staff members have been helping with the Xerox and SOD recruiting. Bill Lynch met with PhD candidates at eMU on February 6th, made a seminar presentation to' interested B.S. and M.S. candidates on the same date and interviewed the B.S. candidates on , February 6th. Paul McJones and Steve Purcell interviewed B.S. candidates at Berkeley on February 15th, and Dave Redell will do the same at M IT on February 17th. Some good prospects have been uncovered.

Pilot

The first production release of Pilot (2.0) is still scheduled for 2Q78, a date which is still compatible with the current DO delivery schedule. It should be noted that over half of the' schedule dependencies listed in the Pilot Design Work Plan have not been met. We are a,nticipating rescheduling the release for the end of June, 1978.

Pilot 'York Plan - 0 J 3

The Pilot Design Work Plan ([lris](Lynch)PilotWp.memo) (approval still pending) is being used for planning purposes. The symbols on the subtitles refer to tasks planned in that document. The work plan will be updated over the next month for release on March 15, 1978.

Pi lot Design Spec - D3

. ,

The primary activity has been on the Pilot Design Specifications. Version 1.0 (draft status) of the Pilot Design Specifications was produced on February 15, 1978. Planning for its

~ review is now under way.

Pilot Functional Spec - 02·

(2)

[I ris]< Lynch) Feb78.Status , 2

Feedback is still being collected from the Pilot Functional Specification. Version 2.0 (draft status) was distributed on September 14, 1977.

Hugh Lauer is organizing the' revision, with his schedule calling for Version 3.0 to be released at the end of March.

'Alto/Pilot Release - 019

Acceptance testing by Product Software during the last half of January has revealed a modest number of difficulties.

Pilot Testing - D 11,D6

Due to Toni Shetler's efforts the Pilot Test Plan is now essentially complete and will be released soon.

Assignments

Bishop: Develop requirements and functions for data management leading to a concepts and facilities document and a functional specification. Aid Richard Moore with Records Processing specification. Work wi th Ed Satterthwaite to develop a proposal enabling better integrated object oriented programming in Mesa.

Gifford: Design and implementation 'of the memory management and file system. ' Only 114

time now.

Horsiey: Organize the filing structure for holding our various development 'documents and code in a way compatible with the Tools Librarian. Work on the Pilot Install facility.

Consult on the construction and integration of Pilot microcode. fv1aintain release 1.0 of AILo/Pilot.

Lauer: Construct a prototype implementation of ByteStreams and make it operational within Alto Pilot. Edit the Pilot Functional Specifications. Edit the DIS Mesa Functional Specifications. Edit the Pilot Concepts and Facilities.

Lynch: Review the Pilot Design Specifications. Help with recruiting new 'personnel for 78.

\York Plans, DO conversion plans, Pilot Functional Specifications. . 1\1cJones: Take 'responsibility for editting the Pilot Design Specifications. Take specific' responsibility, for the memory management portions of the Pilot Design Specifications.

Lead the design effort for the file facilities. '

Purcell: Become intimately familiar with the Pilot process management, memory management and file facilities. Actively participate in the design and specification of the file facilities. Work on Pogo in the background.

Redell: Work with the Mesa group in the implementation of the process structure design for Mesa 4.0. Take responsibil ity for the Process structure section of the Pilot Design Specifications. Take responsibil ity for the Low-level Ivlesa support section of the Pilot Design Specifications. Consult in the design of the file facilities.

Distribution:

Bergstei nsson DeSantis

(3)

Cc:

Harslem Heinrich Irby Lampson LeCesne Liddle Lynch Metcalfe Reilly, D.

Reily, J. . Shultz Simonyi Sonderegger Szelong Thacker Townsend

\Vallace Weaver Wick White

Bishop Lauer Redell Horsley Gifford Purcell Melones

[I ris]< Lynch> Feb78.Status 3

Références

Documents relatifs

normalizing, ambiguity resolving, requirements clustering, NFRs classification and verification using efficient natural language processing, a set of rules, ontology

A functional architecture and specifications of tolerancing data management system have been proposed in order to support this integration at the early stages of the design

This thesis concerns the Ph.D. work done under the supervision of Prof. Mehdi Jazayeri at the University of Lugano. An ontology-based framework for author- learning content

Furthermore, all data needed for products in the product group Requirements and Analyses can be stored and managed in the portal.. The portal processes the data in such a way that

In this paper, we have presented a method for aligning business process modeling and software requirements engineering (ProQAM) and showed how this method fits in the

Independently of the problem at hands, the main issue in MtL con- cerns defining the metafeatures. If the user is able to generate in- formative metafeatures, it is very likely that

In this work we propose a two-stage approach to tackle the real-time scheduling problem. The framework first classifies tasks into groups according to their functional requirements,

The purpose of this paper is twofold, first, we briefly discuss existing limitations in existing business process modelling solution in the context of compliance management,