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

Compare with Current View Page History

« Previous Version 3 Next »

Agenda

https://spaces.at.internet2.edu/display/itana/Architecture+Methods
Agenda for next call
  1. Roll Call (by timezone - East to West)
  2. Scribe Shout-out - It's easy to scribe: How To Scribe Itana Notes
  3. Agenda Bash
  4. Topic:  Applying the Itana Methods - Case Studies
  5. Itana Org Updates
    1. Working Group Updates
      1. API Working Group
      2. Business Architecture Working Group
      3. EA Maturity Model
    2. Steering Committee Update


Attendees

(insert screen shot of the Adobe Connect list of attendees or type)


Announcements - Itana News, Working Group Report out

Architecture Methods

Itana methods case study: Financial aid modernization

Process Mapping, Semantic Data modeling

  • Overview

    • Alec Sharp

    • LEAN practices and teams not included in exercise

  • Process workshops
    • start with semantic data modeling
      • at whiteboard, identify terms and hash out early before they become a source of confusion.
    • move to process mapping
      • process activities
      • group into flows, distinct flows
      • identify triggers, results, steps
      • focus on happy path, don't get bogged down in exceptions
      • Jim: even having this level is very clarifying
      • this level defers the swim lanes
  • process landscape
    • all the major business processes and hand-offs between them
    • data that is involved
    • you might think it looks like a capability map – and in many ways it is, but it highlights the flow and steps
    • expect the process to quite constant;
    • as you get into systems, and map systems against the process landscape, it becomes a useful and reusable reference document.
  • process pain points
    • a way of using the landscape reference document to focus effort
  • enabler's analysis
  • Jim: 1:1, 1:many – indicator of cardinality
    • e.g. mass application to individual student – helps people designing solutions later.
    • also helps people to understand changing processes because you are teasing apart multiple processes

Case for Action

  • leverage the output of the process analysis to focus on what needs to happen next and provide stakeholders with what they need to know


  • No labels