The aim of the ITANA Reference Architecture for Learning is to assemble a set of artifacts that provide an architectural description of the learning ecosystem. This is an area where there is huge technology churn. Consequently, there is a temptation to grasp at technology solutions without a clear roadmap of the entire problem space. This project is designed to provide such a roadmap.

Reference architecture for teaching and learning

Terms of reference

Purpose
The aim of the ITANA Reference Architecture for Learning is to:

  1. Assemble a set of artifacts that provide an architectural description of the learning ecosystem.
  2. Create a survey or other tool which can be used as an instrument for measuring maturity of the learning ecosystem.

This is an area where there is huge technology churn. Consequently, there is a temptation to grasp at technology solutions without a clear roadmap of the entire problem space. This project is designed to provide such a roadmap.

Scope
The term “learning ecosystem” is used in the broadest sense to encompass everything that is required to support learning in Higher Education:

  1. Curriculum development and management
  2. Resourcing the learning process
  3. Learning tools (LMS and tools)
  4. The student’s learning plan
  5. Advising and assessment (including automated recommendation engines)
  6. Analytics

Deliverables
The project aims to complete 2 bodies of work:

  1. Architectural work
    The architectural work builds on tools that ITANA has successfully used in the past:
    1. Capability maps
    2. Core diagrams
    3. A simplified TOGAF ontology
  2. A survey
    Like the 2012 ITANA SOA survey, this exercise is designed to measure current maturity levels

Organization and schedule
An ITANA working group meets on-line on a regular basis and works through the various deliverables.
There may be a need/opportunity for a f-2-f workshop in mid 2013.
The project should be complete before EDUCAUSE 2013

Project work spaces

Statement of scope

  1. Capability maps
    1. Summary capability map
    2. Instructional designer perspective v0.1
    3. Instructional designer perspective v0.2
    4. Instructor perspective
    5. Learner perspective
    6. Administrator perspective
    7. Mentor perspective
  2. Data models
    1. Simplified conceptual data model
    2. Detailed conceptual data model
  3. Scenarios
  4. List of actors and activities
  5. Roles and responsibilities
    1. IMS LTI role vocabulary
    2. IMS LTI role vocabulary v0.2
  6. Inventory of tools
  7. Inventory of MOOCs
  8. Standards in the learning ecosystem
  9. Learning ecosystem maturity survey
  10. Related work at our home institutions
  11. Parking lot

Working group members

  1. Carol F. Bershad University of Washington (cbershad@u.washington.edu)
  2. Pattie Boettger Senior Data Architect University of Michigan (boettger@umich.edu)
  3. Rob Carter. Duke University (robert.carter@duke.edu)
  4. Steve diFilipo VP/CIO Cecil College. Leader of the Mobile Technologies constituent group (sdifilipo@cecil.edu)
  5. Glenn Donaldson. Senior Application Architect, OCIO Enterprise Applications/Ent. Architecture. The Ohio State University. (donaldson.6@osu.edu)
  6. Christopher Eagle University of Michigan (ceag@umich.edu)
  7. Paul Erickson Enterprise Architect Information Services University of Nebraska--Lincoln (phe@unl.edu
  8. Leo Fernig. Enterprise Architect. University of British Columbia. (leo.fernig@ubc.ca) (Facilitator)
  9. John Fontaine. Blackboard Inc. as Senior Director of Platform Evangelism. http://www.johnfontaine.com/ (john.fontaine@me.com)
  10. Laura Gekeler System Administrator at Notre Dame specializing in Learning Management Systems. Notre Dame (LGekeler@nd.edu)
  11. Scott Fullerton. Senior IT Architect. University of Wisconsin--Madison. (sfullerton@wisc.edu)
  12. Mark McCahill. Duke University (mccahill@duke.edu)
  13. Richmond Stevenson, Assistant Vice President, Enterprise Architecture and Strategy UMUC (richmond.stevenson@umuc.edu)
  14. Bob Winding University of Notre Dame (rwinding@nd.edu)

Meeting information

Topic: ITANA Reference Architecture for Teaching and Learning
Meetings happen alternating Wednesdays and Mondays
For the Wednesday meetings
Date: Every 4 weeks on Wednesday, from Wednesday, July 31, 2013 to Wednesday, September 25, 2013
Time: 1:00 pm, Pacific Daylight Time (San Francisco, GMT-07:00)
Meeting Number: 319 015 378
Meeting Password: (This meeting does not require a password.)

1. Go to https://umuc.webex.com/umuc/j.php?ED=43365928&UID=75835138&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting does not require a password.)
4. Click "Join".
5. Follow the instructions that appear on your screen.

For the Monday meetings
Date: Every 4 weeks on Monday, from Monday, January 28, 2013 to Monday, October 7, 2013
Time: 11:00 am, Pacific Standard Time (San Francisco, GMT-08:00)
Meeting Number: 648 776 210
Meeting Password: (This meeting does not require a password.)
1. Go to https://umuc.webex.com/umuc/j.php?ED=168499442&UID=1310526822&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: (This meeting does not require a password.)
4. Click "Join".

Schedule, agendas and minutes

Schedule
Agendas and minutes

f-2-f workshop

A f-2-f workshop was held May 20 - 22 in Madison Wisconsin. See details.

Resources

Miscellaneous links and artifacts

Archived materials

Archived artifacts have been moved here.