Internet2 is investigating a security incident involving a compromise to a confluence server that affected https://spaces.at.internet2.edu on April 10, 2019, which was successfully mitigated on April 12, 2019. If you did not receive an email from us, it’s unlikely that any of the content you submitted to the Internet2 Spaces Wiki needs to be re-entered. We apologize for any inconvenience this may have caused. Should you have any questions or require further assistance, please email collaboration-support@internet2.edu.
Page tree
Skip to end of metadata
Go to start of metadata

Overview

Lifecycle projects and core diagrams are being used at several institutions in order to understand all the systems and processes that students interact with.

  1. UW Madison: Advisor Lifecycle
  2. University of Washington: Capability Maps have been used to drive an understanding of Admissions Processes
  3. Penn State: Student Lifecycle has been used to drive analysis of Identity and Access Managemetn Issues
  4. University of British Columbia: A Student Lifecycle Project is being used to provide a high level context for a number of disparate student initiatives

Institutional discussions and artifacts are on the Institutional Lifecycle Management and Analysis Projects\

The use of Core Diagrams

(ITANA call discussion Aug 18 2011)
You can use the core diagram to identify focus areas by:

  1. Identifying projects that impact the diagram in some way. Having them present to the Advisor ARB to align the project with the overall vision for the core services.
  2. Doing a gap analysis between the tasks in the chiclets and the services listed in the Core Services area of the diagram.
  3. Looking across the suite of core diagrams (Student Lifecycle, Researcher, Advisor, Instructor, Employee) for core services that appear on all or most of the diagrams - these are services that should be optimized since they impact the most stuff
  4. Mapping the flow and connections between the services to see where there are issues of business process flow or AuthNZ issues.
  5. Getting agreement on the operational model (Unification, Coordination, etc) then seeing which chiclets are misaligned with desired operational model.
  • No labels