SCC Report Out C. Tilton

Workplan PriorityWork ItemLead 1Use CasesS. Shorter 2Standards Adoption PolicyJ. Clark 3aStandards InventoryS. Shorter 3bCatalog of Terms and DefinitionsS. Shorter 4Inputs to the Identity Ecosystem Functional Model G. Whitehead & P. Brown 5IDESG Accepted Terms and DefinitionsP. Brown 6Standards Gap AnalysisTBD 7IDEF Standards RegistryTBD

SCC Role in Use Cases Recognized need & stepped forward as coordinator Like all SCC activities/workproducts, IDESG is the consumer – SCC is the enabler – IDESG must be an active participant (contribute, comment, approve) – Collaborative process must be defined We have provided a starting point

Use Cases Levels/categories Process for development/approval Template/format Criteria

Level/Categories Purpose of use cases – create a baseline set of use cases to guide our collective efforts Original intent – define “high level” (functional) use cases to be used across IDESG Other groups define “lower levels” (overlays) for their particular areas of interest, e.g. – Security overlay – User experience overlay – Etc. All use case contributions accepted – Leveling to be performed later

Use Case Process Detailed, end-to-end process to be defined First phase – collection – Intent is to leverage a Wiki – AHG may create some to jumpstart – Solicit contributions from plenary

Template/Format Strawman template in draft Use Case Plan – Use Case Name/Description – Category – Actors – Goals – Assumptions – Requirements – Process Flow – Success Scenario – Error Conditions

Vocabulary Key element of IDEF 2 steps – – Catalog existing – IDESG glossary Parallel development track Wiki planned AHG formed Vocabulary rapporteurs from other groups sought

Collaboration Participation needed from IDESG groups and plenary