Overview

Below are the notes that were collected during the workshop.

The group made great progress on the development of capabilities for three of the selected roles:

Additional notes from the workshop

Goal: accelerate the creation of the architectural artifacts that describe the learning ecosystem:

  1. Core diagrams
  2. Capability maps

Location: Madison Wisconsin. Campus meeting rooms.
Dates: May 20 - May 22. 2.5 days.

Agenda

Day

Time

Topic

Facilitator

Scribe

Location

Monday May 20

9:00 - 9:30

Review agenda and deliverables

Jim, Leo

 

Pyle center, Room 225

 

9:30 - 10:30

Normin: Review terminology, structure of capability maps

Jim

Scott

Pyle center Room 225 , Webex

 

10:30-12:00

Learners: review object model and scenarios

Jim

Scott

Pyle center, Room 225, Webex

 

12:00-12:30

Review parking lot items

Jim 

Scott

 

 

12:30-1:30

Lunch

 

 



1:30-2:30

Instructors: review object model and scenarios

Jim

Leo

Pyle center Room 225, Webex

 

2:30-4:30

Capabilities that supportinstructors

Jim 

Leo

Pyle center, Room 225

 

4:30-5:00

Review and action items and parking lot items

Jim 

Leo

Pyle center, Room 225

Tuesday May 21

9:00 - 9:30

Review agenda and deliverables

Jim, Leo

 

Pyle center, Room 225

 

9:30 - 10:30

Mentors: review object model and scenarios

Jim 

Laura

Pyle center Room 225, Webex

 

10:30-12:00

Capabilities that support mentors

Jim 

Laura

Pyle center, Room 225

 

12:00-12:30

Review parking lot items

 

 

 

 

12:30-1:30

Lunch

 

 



1:30-2:30

Content developers: review object model and scenarios

Jim

Rich

Pyle center Room 225, Webex

 

2:30-4:30

Capabilities that support content developers

Jim

Rich

Pyle center,Room 225

Wednesday May 22

9:00 - 12:00

Review workshop accomplishments.  Determine next steps:

  • Possible video session with wider ITANA group
  • Rich's presentation
  • A possible publication
  • Wiki artifacts next steps
  • Maturity survey
  • Engagement with other groups (eg ELI)

Jim, Leo


Pyle center, Room 225

Organization of topics

The key organizing principle for the capabilities is the concept of a role (instructor, learner, content developer). Capabilities support a role in a particular process. A concrete illustration of the process is a scenario. Examples:

  1. A content developer creating a video
  2. A learner accessing a wiki
  3. A learner completing a test
  4. An instructor delivering a lecture

Scenario = role+learning context. Capabilities support scenarios.

Procedures and mechanics

  1. Each session has a facilitator who is responsible for:
    1. Time tracking
    2. Staying on topic
    3. One conversation at a time
    4. Parking lot
  2. Each session has a scribe who puts the narrative straight into a Google doc
  3. Parking lot is and easel pad (scribe can transcribe these items after the session)
  4. Diagrams are done on whiteboards and/or easel pads. After the session these can be photgraphed and transcribed to out tool of choice (to be determined)

Workshop session checklist.

The workshop is divided into 4 sections: Learner, Instructor, Mentor and Content Developer. For each role we will be developing a capability map. For each we need to ensure we cover these topics:

  1. Capabilities:
    1. Strategic: Students' educational goals
    2. Operational: Eg: Class scheduling, grades collection
    3. Infrastructure: Eg: IAM, workflow
  2. Scenarios. Have we identified a set of scenarios that illustrate the salient features of the problem space
  3. Data elements. Calling out any obvious data elements from the problem space
  4. We should call out any obvious applications that are relevant (registration, degree audit etc)

Attendees

Attending f-2-f

  1. Jim Phelps.Enterprise Architect University of Wisconsin--Madison, Chair ITANA (jamesphelps@wisc.edu)
  2. Jeanne Blochwitz (blochwitz@doit.wisc.edu)
  3. Jeff Bohrer Sr. Learning Technology Consultant & Manager, Learn@UW-Madison (jbohrer@doit.wisc.edu)
  4. Jim Helwig Portal Project Manager. University of Wisconsin--Madison. (jim.helwig@doit.wisc.edu)
  5. Leo Fernig. Enterprise Architect. University of British Columbia. (leo.fernig@ubc.ca)
  6. Scott Fullerton. Senior IT Architect. University of Wisconsin--Madison. (sfullerton@wisc.edu)
  7. Richmond Stevenson, Assistant Vice President, Enterprise Architecture and Strategy UMUC (richmond.stevenson@umuc.edu)
  8. Laura Gekeler LMS Administrator, University of Notre Dame (LGekeler@nd.edu)

Attending remotely (webex)

  1. Carol F. Bershad University of Washington (cbershad@u.washington.edu)
  2. Steve diFilipo VP/CIO Cecil College. Leader of the Mobile Technologies constituent group (sdifilipo@cecil.edu)
  3. Glenn Donaldson. Senior Application Architect, OCIO Enterprise Applications/Ent. Architecture. The Ohio State University. (donaldson.6@osu.edu)

Day 1 - Session 1 9:30-10:30 Learner lifecycle and capabilities - https://umuc.webex.com/umuc/j.php?ED=179545817&UID=490851762&RT=MiMxMQ%3D%3D
Day 1 - Session 2 1:30-2:30 Instructor lifecycle and capabilities - https://umuc.webex.com/umuc/j.php?ED=179546267&UID=490851762&RT=MiMxMQ%3D%3D
Day 2 - Session 1 9:30-10:30 Mentor lifecycle and capabilities - https://umuc.webex.com/umuc/j.php?ED=179546262&UID=490851762&RT=MiMxMQ%3D%3D
Day 2 - Session 2 1:30-2:30 Content developer lifecycle and capabilities - https://umuc.webex.com/umuc/j.php?ED=179546587&UID=490851762&RT=MiMxMQ%3D%3D

If you wish to join by phone:
1-650-479-3208

Access Codes are: