You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Shared Services Team Page

At the January 2012 F2F in Phoenix, a new workstream was identified and called "Shared Services".  This workstream involves several work items or capabilities that represent common needs or services across all the other workstreams of registries, provisioning, authentication and access management.  This page defines in more detail the high level expectations of what the common needs are.   The following is the high level gap analysis of required shared service capabilities originally identified at the F2F meeting.

 Timeline

Shared Services

Est

< 3 months

- Convene standards/API team

Low

< 6 months

- Convene cross stream project steering team - Publish initial standards - Publish baseline policy & lifecycle use cases

Low

< 12 month

- Establish UI mgmt console team and environment - Establish QA/Integration team and environment - Establish Audit/Report team requirements

High

< 18 months

- Create baseline management console - Create baseline QA/Integration tests - Create baseline data warehouse and reporting - Establish training & support team

High

< 24 months

- Create 2nd version of audit/reports - Create 2nd version of mgmt console - Create baseline training & support program

Med

Gimme

KEW Developer tools

 

Resources Estimates assume 1 FTE for Low, 3 FTE for Med, and 5 FTE for High.  This is the estimated number of development or support resources needed for the specified tasks / deliverables per period.

The following is a breakdown on the major services and capabilities with assumptions of approach and features required. 

Service Capability

Work / Features

Drivers / Assumptions

Standards / API

  1. Convene Work Team
  2. Create Standards / API Site
  3. Document Standards / API
  4. Create governance process
  1. Need architect type representatives from each workstream.  Must be knowledgeable in current industry practices and standards.
  2. Common wiki site for documenting, format styles, templates developed
  3. Define and document existing and new standards and APIs for each workstream and existing products.  Must be open standards as this is key selling point.
  4. Determine how standards / APIs will be reviewed and refined and who will audit for compliance.  This may need to turn into a certification process to ensure products have the OSIdM4HE seal of approval.  Establish policies and lifecycle procedures.

IAM Console

  1. Convene Work Team
  2. Establish development tools, frameworks and methods
  3. Project Management and Planning
  4. Analysis and Design
  5. Coding and Testing
  1. Work team composition is typical software development team.  PM, Architect, Business Analyst, UX Designer, Coders, Tester, etc.
  2. Assume use of Kuali Rice for app dev (KRAD) and middleware services (KEW, KSB, etc.).  Development environment includes Java, Intellij, Spring, Subversion, Maven, etc.
  3. Establish governance processes for determining feature, milestone, build and test cycles.  Requires cross workstream representatives.
  4. Research and design of IAM console will require in depth review of existing UI of current products.  Will need to provide requirements back to existing products on how to instrument so they can be easily plugged into the console.  Console will need to provide SSO to plugin components.  Easy navigation, search and view across plugin components.  Batch load and review of plugin audit logs.  Will require workflow capabilities with action lists for administrators.  Easy access to help system and standards and API documentation.  Access to provisioning cookbooks and instructions, etc.
  5. Will use agile iterative coding and testing style.  Need to setup test harnesses and jira bug tracking.  Create sample applications and baseline reference implementations of products. 

Integration Testing

 

 

Data Warehouse and Reporting

 

 

Training and Support

 

 

 

 

 

 

 

 

 

 

 

 

 

 
  • No labels