Agenda

Demystifying Frameworks, Reference Models, and Taxonomies

  1. Roll Call (5m)
  2. Overview of Topic and Cultural Fit (8m, J. J. & Robert)
  3. Use Cases
    1. University of Aukland–CAUDIT, (7m jeff kennedy)
    2. Oregon State University–CAUDIT, (10m, Melody Riley)
    3. University of Miami, Ohio–CAUDIT, (10m, Dana Miller)
  4. Discussion (10m, Louis King)
  5. Wrap Up (5m, Jim Phelps)

Attendees

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


Announcements - Itana News, Working Group Report out


Demystifying Frameworks, Reference Models, and Taxonomies




Pre-call Planning Notes

See Agenda Above

Notes from January 29th Planning Call

Dana Miller (CAUDIT), Melody Riley (CAUDIT), J.J. Du Chateau (Many Frameworks), Jim Phelps, Saneel Vasram(CAUDIT), Robert Snyder, Laurence Harvilchuck (BIAN), jeff kennedy


  1. Dana: Recommendation materials towards an organizational redesign. Feeding into a group working on this to align teams towards the business capabilities.
  2. Melody, OSU: Share around customer service capabilities. Diversification of investments applied to the business model. Apply what we have done. Look for horizontal opportunities across the University with the CAUDIT model.
  3. J.J.: Start call framing this. What is the scope of the discussion. Differences between taxonomies, frameworks, and reference models. We may want to scope and clarify. We are using these terms interchangeably.
  4. Robert: Initiative 1 Penn State 2025. Working on digital transformation. Have high level conversations but not translating that into effective ways to translate and design. We don't have a lot for that communication.
  5. Melody: Looking at practical application of Enterprise Architecture. Had implemented Zachman. Sent people to TOGAF. Focused on practical application of EA. Why EA. Understanding what framework works best.
  6. Laurence: Feel your pain being a recent arrival in the public sector. We have 1 WVU. What is the value that EA brings for digital transformation. Bringing it to the next level of resolution with functional building blocks. And giving the University a picture back of the University on a page from a functional perspective. We need a way to make this actionable. We are using BIAN that does all of that.
  7. J.J.: Hearing some common threads that appear in the different list serves. What are people doing and how are they having success with them. How have people been able to connect dots between strategy and services. Examples of this would be interesting.
  8. Robert: Yes. This makes system. What I am looking for from bottom up, anything that communicates with a customer when abstracting their ambitions and translating them into a more holistic view.
  9. Jim: Plus one on what works. I had to simplify from Zachman. What is going to work is about your culture and what you are thinking about.
  10. Melody: Never subscribed holistically to just one framework.
  11. J. J.: Not picking one over the other. Be aware of them and use what will be helpful at any particular time.
  12. Dana: It would be helpful to talk about the differences between the three types of structures for EA.
  13. Laurence: The Practice of Enterprise Architecture, Kotusev
  14. Robert: Need to really understand the audience in order to communicate
  15. Is CAUDIT a reference model? No it is a taxonomy.
  16. Robert: Many domains have different taxonomies? Does anyone else have that problem. I try to resolve this through relationships that give insights into viewpoints.


Preso 2/21/2020

  1. Demystify Framework, Reference Model, and Taxonomies, What are they? What do you use them for? (5 minutes, review from email) J. J. & Robert (Louis Review)
  2. We use pieces of these tools to drive outcomes so that they will fit our audience and culture? (2 minutes) Robert
  3. Round Robin (3x10)
    1. Melody, 10m
    2. Dana, 10m
    3. jeff, 5m (1st)
  4. Conversation (Louis)
  5. Wrap Up


Start a shared slide deck. See link in agenda.

See chat notes.

Presos

  1. Culture
  2. Goal: What are you trying to do?
  3. Outcomes: Stories of things that worked and didn't work