Resumé of Roland F. McKenney
31 Pinewood Avenue
Billerica, MA 01821-1623312
Email: mckenney@gis.net (preferred)
Day: (978) 287-1754
Evening: (978) 362-1222
Contents
Objective
Career Summary
Technical Skills
Experience
Education
Papers
A permanent postition where I can continue to broaden my experience base and contribute at a
senior level in advanced software technology areas.
Over 22 years of software development experience with 10+ years
experience as a development team leader in diverse areas from
distributed file system kernels to computer supported cooperative
work (groupware) systems, object databases, and data warehousing.
Have a demonstrated ability to quickly learn and apply new
technologies.
- Languages
- C++/C, CLOS/Lisp, Java, Smalltalk, PL/I, Prolog, DPS6 Assembly
- Systems
- UNIX (SunOS, AIX, SCO, IRIX, HP-UX, OSF1, Bull BOS); Microsoft Windows NT; GCOS 6 HVS; Multics
- Other
- HTML, CGI, OLE/COM, PCTE, X/Motif, TCP/IP, OLTP, RPC, OODB, VLDB
Sybase, Inc. (1997-PRESENT)
Staff Development Engineer in high-performance data warehousing group
www.sybase.com
- 00-
- Lead engineer for the bitmap team.
- 97-99
- Re-wrote the buffer cache services to implement multi-versioning concurrency control and
substantially modified the db performance monitor.
ONTOS, Inc. (1995 - 1997)
Senior Technical Staff
www.ontos.com
- 96-97
- Project leader for the ONTOS*Desktop development team,
where I:
- established technical direction and project
schedules,
- took over the prototype UNIX server
implementation and brought it to production
quality,
- extended the server from single client to
multi-client capability,
- re-architected the client/server interface for a
smaller footprint & higher performance, and
- used InstallShieldExpress to create installation
kit for alpha users.
- 95-96
- Technical leader for the ONTOS DB development team, where I:
- contributed SMP expertise to the DB server
re-architecture effort,
- prototyped multi-threaded client/server design
alternatives [C++/Solaris],
- worked with marketing to define product direction
and features,
- worked with project management to define and
track schedules,
- developed a demonstration gateway from HTTP to
ONTOS DB [C++/CGI],
- developed a demonstration Java interface to ONTOS
DB using JNI/RMI, and
- developed an automatic Java interface code
generation tool for ONTOS DB applications.
- Additionally I:
- independently developed feature tests and did
performance analysis for ONTOS DB,
- represented ONTOS at the Object Management Group
(OMG) as Technical Representative,
- provided technical support for company use of WWW
technologies, including establishing the intranet
and internet servers (www.ontos.com),
and
- aided in UNIX system administration.
Bull HN Information Systems, Inc. (1979 -1994)
Staff Ladder Engineer, S/W
www.bull.com
- 92-94
- Team Leader for the Metro project, a groupware
application family being developed under a $4.2M contract
for ARPA in collaboration with Columbia University and
the University of Illinois at Urbana-Champaign. This was
the successor to the Scrutiny project, a distributed
system for the collaborative review of documents and
source code built using the ConversationBuilder toolkit
from UIUC.
- As team leader, I:
- directed team members in establishing and
tracking work activities,
- assisted team members in development and
debugging activities,
- implemented C changes necessary for port from
SunOS/BSD to AIX/SysV platforms,
- mentored other staff in UNIX/X/C++ environment,
- prepared technical reports and published papers,
- analyzed and made recommendations for managing
departmental fixed assets and budget,
- maintained the development environment
infrastructure (porting and writing tools), and
- monitored Internet and other resources for new
technologies and exposed them to the group. (For
example, introduced use of WWW to project.)
- 91-92
- Team Leader in the CASE Tools group, responsible for
porting the configuration management, version control,
code analysis, and build tools; the target platforms
included MIPS RiscOS, SCO, Bull DPX/2 and HP-UX. Also
ported a number of X Window clients for our own use.
Mentored junior staff being introduced to UNIX and as a
System Administrator for the group server.
- Member of an inter-departmental CASE Products Design Team
that defined the Bull CASE Product Roadmap, including
definition of the product requirements and architecture.
Evaluated the IBM AIX SDE WorkBench/6000 product on the
RS6000.
- 90-91
- On paid leave to earn a Master of Science degree at The
Gordon Institute of Tufts University. A key component of
this program was the company-sponsored development
project to prototype a test catalog system for supporting
reuse; this prototype utilized the OMS of the GIE
Emeraude implementation of PCTE.
- 89-90
- Systems Engineer for Boston Development, where I
participated in product definition and specification, was
responsible for resolving architectural and design
issues, and provided technical assistance to the
development organizations in the transaction processing
and DPS6000/UNIX hybridization areas. Represented the
Boston Engineering group at the Groupe Bull Transaction
Processing Conference in France. Wrote, and facilitated
the technical coordination between Marketing and
Engineering for, the TP Product Functional Specification.
Co-wrote, and was editor responsible for, the
architectural definition of a proprietary (GCOS 6) to
UNIX hybridization environment.
- 88-89
- Team Leader for the Advanced Software Engineering
Technology group. Developed and deployed UNIX tools
internally. Designed a distributed electronic
conferencing facility. Established UNIX training
sessions, defined and tracked schedules, and supervised
prototype development efforts on Bull UNIX (XPS-100)
systems.
- 86-88
- Team Leader for three groups in the Kernel Development
Department of a B3 secure operating system based on
Multics technology. These teams were: the Storage System
(combined Memory Management and File System), the Kernel
Debugger & Tools, and the Runtime Environment.
Participated in the definition effort as a senior
designer and supervised the design and implementation
phases. Introduced mainframe (Multics) and PC-based
project management tools (MacProject, Time Line) for
resource allocation, project scheduling and tracking.
- Developed a remote kernel-debugging facility hosted on
Multics and utilizing HDLC communications; maintained the
DPS 6 X.25 stub and designed and initially coded the
remote debugger framework.
- 79-86
- Designed, developed and maintained File System components
for the Bull GCOS 6 MOD 400 and MOD 600 operating
systems. Introduced new functions related to data
integrity: record locking, before and after image
journalization, and utilities relating to crash recovery.
Invented new mechanisms to extend these functions for
operation in a distributed environment: specifically,
support for two-level TP, two-phase commit and deadlock
avoidance through use of time-stamps. Was a key
contributor to the design and implementation of the
Remote File Access facility, particularly the request
server. Designed and presented internal training courses
on file system internals and interfaces. Upgraded File
System utilities for internationalization support.
Devised performance analysis tests for File System kernel
functions as well as automated feature tests.
- Wrote a post-link-edit binary processing utility to take
advantage of a virtual memory environment for relocation
of large FORTRAN programs.
- The Gordon Institute of Tufts University, (TGI)
Medford MA (1990 - 1991)
- Master of Science in Engineering Management
- Received Highest Academic Achievement award.
- Massachusetts Institute of Technology, (MIT)
Cambridge MA (1975 - 1979)
- studied Computer Science and Electrical Engineering
J.Gintell, J.Arnold, M.Houde, J.Kruszelnicki, R.McKenney &
G.Memmi, "Scrutiny: A Collaborative Inspection and Review
System", Proceedings of the Fourth European Software
Engineering Conference, Garwisch-Partenkirchen, Germany
(September 13-17, 1993)
Abstract: This paper describes a Bull US Applied
Research Laboratory project to build a collaborative inspection
and review system called Scrutiny using ConversationBuilder from
the University of Illinois at Urbana Champaign. The project has
several distinct aspects: technology oriented research, prototype
building, experimentation, and tool deployment/ technology
transfer. Described are the design of the current operational
version of Scrutiny for inspection-only, the evolutionary design
of Scrutiny to handle various forms of review, and some initial
thoughts on integration with other CASE frameworks and tools. The
problem domain selected, the development environment, lessons
learned thus far, some ideas from related work, and the problems
anticipated are discussed here.
URL: http://www.ics.hawaii.edu/~johnson/FTR/Bib/Gintell93.ps
J.Gintell & R.McKenney, "Building Scrutiny, a
Distributed System for Collaborative Inspection and Review of
Work Products -- Experience and Challenges", CSCW Tools and
Technologies Workshop, ECSCW `93, Milano, Italy.
Abstract: to-be-provided
URL: currently unavailable
J.Gintell & R.McKenney, "A Proposed Structured
Collaboration Architecture derived from the Scrutiny Project,
Proceedings of the 1994 ACM Conference on Computer Supported
Cooperative Work: Workshop on Software Architectures for
Cooperative Systems, Chapel Hill, North Carolina, October, 1994.
Abstract: This position paper describes a proposed
architecture for a family of collaborative applications where the
collaboration is governed by a definable process. The
architecture is derived from lessons learned and generalizations
made from a recently completed three year project to build and
use Scrutiny, a distributed CSCW system for performing software
inspection and review.
URL: http://www.ics.hawaii.edu/~johnson/FTR/Bib/Gintell94.ps
G.Kaiser, S.Kaplan, J.Arnold, J.Gintell, R.McKenney &
G.Memmi, ARPA proposal "Atlantis: An Open Architecture for
Synergy of Process-Centered Environments and Computer-Supported
Cooperative Work", Technical Report RAD/USARL/93044
Abstract: to-be-provided
URL: currently unavailable
J.Gintell, M.Houde & R.McKenney, "Lessons Learned by
Building and Using Scrutiny, a Collaborative Software Inspection
System", Proceedings of CASE `95, Toronto.
Abstract: This is an experience report describing the
results of a project to build and introduce an experimental CASE
tool into a software engineering organization. The tool is
ScrutinyTM, a CSCW system used to manage and
facilitate the performance of software inspection and review by
geographically separated teams. We describe Scrutiny and the
lessons learned while building it and introducing it. The lessons
learned are characterized as tool introduction, process, and user
interface issues.
URL: http://203.162.7.73/ieee/htmls/disk_91/3235/9761/358_367_AVAT,%20a%20CASE%20tool%20for%20sof.htm
Created: March 24, 1997
Last Modified: October 15, 2002
URL: http://www.gis.net/~mckenney/rfm/rfm_resume.html
© 1997-2002 Roland F. McKenney
Contact Information