Directory Project – Initial Project Report
Project Team Members
Project Manager:
Warren Curry Finance & Administration IS
Software Dev. Mgrs:
Willy Rechsteiner Finance & Administration IS
Barb Sedesse NERDC
Team Members:
Debbie Sams Finance & Administration IS
Alan Rout NERDC
Linda Toral Registrar
Mei Li Cheng JHMHC
Rita Cowan Academic Affairs
Marion Boyle JHMHC–IAIMS
Purpose
The purpose of this initial report is to inform the group of our projects purpose and scope of the initial work. We are working on approximately a 14–month commitment that began in earnest in Mid November 2001 and should conclude near the beginning of calendar year 2003.
Agenda
Explain the project goal
Share the scope and approach of the project team
Encourage input from all areas
Encourage Support of the project and development support in your
areas.
Define mechanisms for providing input and tracking the project
throughout the effort
Question and Answer
The team will be conducting visit with each college and division. These sessions are being focused for a sharing of information and a development of a network of people who can assist us in getting this effort to completion and then used successfully. The team will provide an overview of what the project will entail and the services that will be provided. In addition, would like to receive some input from each area.
Example:
How do you use directories and directory information?
What do you find helpful in your current usage of directories?
How can this use be improved?
What interfaces would you like to see in a new directory?
What do you feel are shortcomings with today’s directories?
If you would like to learn more about the project, please go
to the website
listed below and look at Final Directory Proposal:
Directory Planning Team
The directory development project website is available at http://www.bridges.ufl.edu/directory.
Focus Points for Development Team
Database Structure Update WCGOLD database schema in DB2 and LDAP schema to support standards that are being developed through I2 and other national groups such as EduCause. EduPerson, UF EduPerson, and a support mechanism for unit level extensions if a unit desires.
LDAP Server(s): Evaluate and Recommend improvements if needed to infrastructure of LDAP facility.
Data Maintenance: Without accurate data in the database and a
culture change at UF and it’s DSOs, the entire endeavor of
providing an enterprise directory becomes much less effective.
Application interfaces for units will be provided to enable local
conventions that along with directory policy can allow for an
area to support unit level extensions. Central self–service
routines and entry panel will be produced to maintain a UF
EduPerson and UF Organization data. In conjunction with the
middleware and the standard interface for maintenance,
culture and policies that promote and ensure the authenticity
of data in the directory metadata database must be provided by
the committee’s and organizations that are appointed to
support this development effort.
Data Usage: Standard interfaces (API) will be provided to use
the data in the MetaDatabase and LDAP as authentic. The goal would
be to reduce the
shadow directories, facilitate downloading and accessibility of
directory data.
We will be talking to unit around campus to gain a better
understanding of the best practices for accomplishing this goal.
Person ID: Provide a mechanism to enable the elimination of SSN from standard use throughout campus. A new method pair of identifiers has been proposed by the Provost’s ID committee that will provide for new numbering of individuals. The project will provide a middleware connection for assigning, using and managing the new identifier strategy. This will enable units who utilize the SSN to eliminate it from common usage.
Data Replication Queues: Existing systems in the Registrar, Student Affairs, Finance and Administration and elsewhere will need to receive notification of changes or use the data in place as is appropriately determined by each application system team. The managers of these systems are stakeholders in ensuring the success of this project. The directory data must be moved or accessed from the authentic directory database then fitted or replicated to the various application systems. The source of data is a key policy issue if the concept of directories is to work to it’s potential.
Foundation for Expansion: Provide a data model, LDAP Schema and set of API’s to support functional expansion and growth of new ideas. This flexibility will allow for the basic efforts to support UF’s directory needs for the foreseeable future. Many Internet 2 initiatives, collaborations both at UF, Shands and other institutions should be able to be supported as we move forward from the initial project.
Directory Middleware Framework Slide
EduPerson Target graphic slide
UF Directory Architecture
slide
Implementation Plan
Required Tasks
The planning team identified the following list of tasks needed
to provide effective enterprise directory services:
1. Assess user needs in relation to Directory Services.
2. Identify desired data elements needed in new directory &
LDAP.
3. Develop needed data models.
4. Develop new schema for LDAP.
5. Identify current inventory of API’s and interfaces to
WCGOLD & LDAP.
6. Identify desired data flows and related APIs.
7. Develop or refine related applications and interfaces.
8. Define and create web interface to allow self–service.
9. Determine and implement needed policies, for both service
provider and users, to ensure and manage Directory Services that
are flexible, effective, responsive, and secure.
10. Develop procedures for implementation of new services.
11. Develop maintenance procedures.
12. Develop training.
13. Develop communications/information.
14. Develop tools to use Directory.
Application areas which require directory–originated data,
must be interfaced to directory by those individuals familiar and
responsible for those business systems and services.
Project Tracking
I. S. created a Gannt chart to include project startup / planning
as well as policy issues which require attention prior to design
and construction of the upgraded directory services. We have
indicated our initial impression (best guess) on staff
utilization and assignment within the project. This of course
will change based on individuals assigned and detailed tasks as
they are filled in during analysis tasks.
Planning Assumptions
The following planning assumptions made in the construction of the Gantt chart:
1. Project management expertise is available within UF for this
project
(Will require an existing IS project manager/leader)
2. Effort from related business units will be provided as
indicated to interface.
3. Additional support for the development process is available.
The 4 FTE will be experienced UF staff developers.
4. Ongoing Support for directory is available and will interface
with development effort at implementation task. The 2 FTE will
work alongside developers at implementation time.
5. Facilities, Work Space, Hardware, Training and Materials to
equip and locate team will be provided at a single site.
6. Development team does not convert to new ID numbers it provides
the repository and routines to allow conversions by unit
application owners throughout campus.
Staffing –
Implementation:
In reflection of the proposal estimate, 4 FTE’s on average
over 14–month development period, and 5–6 FTE’s
during peak effort. The proposal also points out the need for
ongoing support requirements of 2 FTE in technical staffing upon
implementation of the directory software. Since this is a
middleware project, skills from the typical IS application project
need to be supplemented with system programmer type knowledge and
access such as those of some NERDC staff members.
Required Skills
• .2 FTE Project Manager (Warren Curry, Finance and
Administration, I.S.)
Individual should have experience managing activities of team
development and have worked closely with managing projects at
UF. Functions as bridge between project developers and campus
administration. Person would be experienced and knowledgeable
of campus issues. Provides administrative over site for the
project. Enables and keeps the focus of the Development manager
to be the issues of development and construction of the new
facility. Maintains scope of deliverable and other issues related
to administration and successful completion of the project. This
project is a prime candidate for scope creep and must have a
clearly defined deliverable agreed upon in order to assure a
successful project.
• 1.0 FTE Software Development CoManagers
(Willy Rechsteiner (IS) or Barb Sedesse (NERDC))
Individual should have experience in running a goodly sized
project thru the design stage and to guide team members to be
productive and work in concert with each other. Should report
directly to Project Manager for the duration of the project for
day to day coordination and assistance. More than likely this
will consume one of IS’s current experience project
managers (a very limited resource). Ability to find experienced
Project managers is very limited and has in recent times not
proven to be practical. Knowledge of IS development procedures
and standards is required.
• 0.25 FTE Database Administration
Debbie Sams (IS), Alan Rout (NERDC )
During the early design stages of the project a great deal of time will be focused on data structure enhancement, edu person implementation and modeling, UF person implementation and modeling. Resources knowledgeable with both relational database design, LDAP schema, stored procedure and messaging interfaces should be involved. Individuals who come to mind are currently at IS and NERDC.
• 2.0 FTE Application Developers
Linda Toral(Registrar), Mei–Li Cheng (JHMHC–CIO)
Knowledge of component based development techniques. Should have
experience with development of application software for
widespread use. Should be able to work in a 4–6 person
development team. Should be familiar with Java, C++, Cobol, CICS,
WWW, and robust transactional application design
–development issues.
• 1.0 FTE Systems Programmers
Barb Sedesse (NERDC ) Alan Rout (NERDC )
LDAP, Authentication, Authorization, Kerboros and message
transport protocol skills will be needed.
• 0.75 FTE Training/Communications/Documentation
Rita Cowan (Academic Affairs), Marion Boyle (JHMHC IAIMS)
Individual will need to produce and deliver training materials, documents etc. to ensure that campus culture migrates to this new paradigm. The individual will need to work closely with technical core team, related departments such as personnel, registrar, and the policy makers for directory services at UF. End user documentation, web site maintenance and campus communication strategy/programs.
• FTE Varies by area : Stake Holder User Area Application
Developers
Critical to the successful deployment is the knowledge of
UF’s application systems which need to utilize the data and
component middleware developed by the team. Those areas which
must use the data to operate systems on UF will need to be
working in parallel to achieve the goals in a timely manner. Most
critical in this area are application systems which need the new
person identifier. In addition, applications will need to
interfaced to the update queues to maintain accurate directory
based info in many core campus applications. These are in
themselves significant changes for the software systems at UF.
The directory will become the single authoritative source that
provides data propagation to today’s existing core
applications. Critical areas are Personnel system, Student
Systems and the current GatorLink/LDAP systems. Others are
named for interfaces in the proposal document. Without a
conceptual change in the origination of identity information
and policy to support the change the directory will be less than
a complete success. The commitment must be garnered from each
critical area and management prior to building the software.
Recommendation
(by major area) Information Systems/Administrative Affairs
Registrar IT
Student Financial Aid
Housing
Sponsored Research/Graduate School
JHMHC CIO
IFAS Administrative systems
NERDC
CIRCA
UFF
UAA
Other college and business unit area systems
Staffing – Ongoing Support and Operations:
Staff – TBA
Two (2.0) FTE will be on staff during the implementation task of the directory middleware project and will assume ongoing support for the developed solution.
