You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Agenda
Agenda for next call
- Roll Call (by timezone - East to West)
- Scribe Shout-out - It's easy to scribe: How To Scribe Itana Notes
- Agenda Bash
- Topic: Applying the Itana Methods - Case Studies
- Itana Org Updates
- Working Group Updates
- API Working Group
- Business Architecture Working Group
- EA Maturity Model
- 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
Process Mapping, Semantic Data modeling
Overview
- 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