• Aucun résultat trouvé

COlllmunication and I/O Software

N/A
N/A
Protected

Academic year: 2022

Partager "COlllmunication and I/O Software "

Copied!
2
0
0

Texte intégral

(1)

XEROX

BUSINESS SYSTElVIS System Development Departmenl

To: Distribution Date: February 12~ 1979"

From: W. C. Lynch

!)v. e~' .

Location: Palo Alto

Subject: Systems Software secti:U

tfe:r::iZatiOn

Organization: . SDD/SS

Archive document #: Ogawa archive number

Filed on: [lris]<Ly,:",ch)ReOrgFeb79.Memo

Copies: Archives Heim Heinrich Herold Lazar

Lynch Miller Szelong Townsend, Weaver

Cc: Belleville ' Bergsteinsson Bewley Bice Clark

Harslem Irby Kennedy Lampson Lauer

Linden Reilly, D. Reiley, J. Sonderegger Wallace , White

Cc: Bishop, P. " Bishop. S.A. Chang Clark Dalal

Garlick Horsley Jarvis McJones Murray

Ogawa Peterson Redell Rentmeesters Schwam

Iniroduction

Liddle , ,Wickham

DeSantis ;, LeCesne Wick

Danielson Ng

As evidenced by the increased headcount in our Operating Plan submission, the planned level of activities within Systems Software. will increase in 1979 by about 50% over the levels of its constituant areas during 1978. This increased activity has not fallen evenly across our areas but rather has been substantially concentrated in the IODU area~ Despite the fine perfonnance , achieved in the past by the IODU area and its management, it is clearly necessary to divide the workload in a more managable distribution. I am therefore announcing a minor reorganization of the Systems Software section so as to cope with this situation.

In ,this new organization all three areas will have increased responsibilities and will require increased resources. Consistant with our Operating Plan and its task breakdown stnlcture, many of the groups in Systems Software will be adding new people so as to be able to discharge their responsibilities.

TIle following sections summarize the changes in, responsibilities.

COlllmunication and I/O Software

Yogen Dalal is assigned as a project leader with responsibility for OIS Communications. Over a period of time TBl) Yogen's group will also assume responsibility for the FTP and RPCP activities now handled by Jim White.

Communication and I/O' Software will assume the -responsibility for 1/0 device controllers, 110 microcode, 110 drivers, and the device dependent portion of the Utilities. Pitts Jarvis and John Ng will report directly to Jim White. Jim will pl~lce major emphasis on t,his activity con~istant with his

(2)

[rris]<Lyn~h)ReOrgFeb79.Memo February 12, 1979 2

rep 0 nsibilities as the manager of Communication and· I/O. Softw?-re and his transition responsibilities with FfP and RPCP. R~sponsibi1ity for the Utilities will be reassigned between Jim and Hugh Lauer.

Pilot

The Pilot area will assume' some additional responsibilities. Tom Horsley has agreed to be responsible not only for the. release mechanics ~nd bookeeping of Pilot but also for those functions for the microcode. and. for Gateway software.

The Pilot area. will take responsibility for the portion of the utilities that are more dependent. on· the internals of Pilot than on .particular I/O devices. This boundry will be negotiated between Hugh

and Jim White. " :,.. . . , ...

"'-'t-

'Peter Bishop will take on the task of implementing a transaction system for- use by Star-l and by Pioneer .. This task, which is expected to continue to about mid-y~ar, will be in the Pilot area and under the management of Hugh Lauer. Peter will return to the Data Management area at the.

comple,lion of the task...· .

. .

Dave Redell has agreed to take on the task of investigating the stnlcturing rules for the microcode, particularly with respect to the timing and pre-emption constraints of the DO. Roy Levin of PARC- - CSL: has agreed to give limited aid with this task. Dave will spend about 60% of his time on this . task,. consistant with his remaining responsibilities to Pilot, and will report directly to me for the

~~ . .

Diagnostics .

and Microcode·

Tne span of Diagnostics and Microcode activities is reduced by the transfer' of the I/O driver activity to Communication and I/O Software, the transfer of the Utilities activities to Communication and I/O Software and Pilot, and the transfer of the Microcode· release activity to h1e' P"Jot are~

I expect the activity in the Diagnostics' group to increase rapidly as we open our dialogue with the newly formed XES service organization. Diagnostics is a challenging and financially important activity absolutely vital to the su.ccess of Star asa business.

Diagnostics and Microcode also retains the responsibility for the design and implementation of several Inicrocode components (eg .. booting) and for the overall integration and. debugging of the microcode.

In . addition to his' activities as manager of Diagnostics and .Microcode, Bill Kennedy per:sonally continues to perfonn the task of coordinating many of the DO activities which occur subsequent to their receipt frorri ED. ~Ibese include the coordination of acceptance testing, upgrades and retrofits,

and of saine mantainance. .

Références

Documents relatifs

Portnov (Eds.), Regional Disparities in Small Countries, 251-266, 2005 which should be used for any reference to this work The original publication is available

Increased population density depresses activity but does not influence emigration in the snail Pomatias elegans Maxime Dahirel, Loïc Menut, Armelle Ansart.. To cite this version:

The design approaches of Communicating Systems are moving from static to dynamic layered and loosely coupled architectures to meet the adaptability needs of future

But the term cannot be accu- rately applied to the situation in the greater Paris metropolitan area, where, at the same scale, only 40% of immigrants from North Africa or

4500–4000 cal BP and 650–450 cal BP (1300–1500 cal AD); (2) coherence between Lake Ledro’s flood record and a large number of flood records available from western and southern

Typical activities (i.e., type of work) traced by VCSs fall under the categories Code, Docu- mentation, Test, etc. Major VCSs like Git and Subversion, do not provide direct support

Focusing on activity paradigm in developing a software system could help the developer in creating such conditions, so that the user’s tasks (the user in this case

In this section, we report formal results to understand how autonomous agents may change the level of assistance in different scenarios. Two main formal results are presented in