Versions Compared

Old Version 12

changes.mady.by.user Piet Niederhausen (washington.edu)

Saved on

compared with

New Version Current

changes.mady.by.user Luke W Tracy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Architecture Hats has a new name, MESA. Which stands for Michigan Enterprise Strategic Assessment.

Logistics

Travel, parking, hotels, etc.

Program

Schedule and agendas

Workspace

Working documents and links

Models and Methods

Enterprise Architects use a variety of conceptual models and tools to convey their ideas, such as:

Post Conference Notes

Captured flip-charts and notes

Tasks

TaskAddedAssigned toStatus
Copy the scratchpad drafts into wiki pages, and draft a Method Contributor Guide.Apr 24Piet, Rupert(tick) Complete
Draft the Architecture Methods home page in the ITANA Library.Apr 24Piet(tick) Complete

Draft overviews/narratives describing how the methods could be used in context.

May 1Piet, Rupert, Leo, anyone else who'd like to try(warning) Starting

Clean up the wiki page for each method.

May 1Stewards for each page(warning) Starting
Share the Architecture Methods library with ITANA members on the May 8 conference call.May 1Jim 

Methods Index

 The "official" web site for this content is now: Architecture Methods.

Method Template for adding wiki pages | Google Drive folder for file sharing

 Model/MethodWorkspaceStewardsStatus
1Brick Diagrams
 Model/MethodStarting ReferencesWorkspaceSummary
1Brick Diagrams
  • Columbia explanation and examples
  • NIH EA site
  • Wisconsin site
    • Washington site
    • Goals: Give IT teams (and potentially their customers) a shared framework for change in technology solutions; gain agreement on solutions that will be explored, planned, implemented, or phased out.
    • Context: IT service management; changing technology solutions over time and across teams.
    • Scope: Multiple IT teams across an organization.
    • Rupert Berk
    		v1 in wiki
    2Pace Layers2Pace Layers
  • Gartner Glossary
  • Link to Gartner special report
    • ITANA Face2Face 2012 presentation (slides 8-12)
    • José Cedeño
    • Jason Myers
    		v1 in wiki 
    3Capability MapsITANA capability map (as an example) 
    • Dana Miller
    • Dave Roberts
    		v1 in wiki
    4Core Diagrams 
    • Rupert Berk
    • José Cedeño
    		v1 in wiki
    5TIME models
    • J.J. Du Chateau
    • Jason Myers
    		v1 in wiki 
    6RoadmapsITANA roadmaps resources resource page
    • J.J. Du Chateau
    • Rick Tuthill
    		v1 in wiki 
    7Dot Diagrams2012 presentation (PDF) by Jim Phelps
    • José Cedeño
    • Bob Dein
    • Scott Fullerton
    		v1 in wiki 
    8Engagement Investment Value Matrix
    • Bob Dein
    		v1 in wiki 
    9Semantic Data Models
    • Leo Fernig
    • Paul Schurr
    		v1 in wiki 
    10Process Maps
    • Dana Miller
    • Piet Niederhausen
    		v1 in wiki
    11

    MESA - Michigan Enterprise
    Strategic Assessment 

    • MESA - Michigan Enterprise Strategic Assessment Process Maps wiki page
    • Scratchpad in Google Drive
    • Goals: Give business and IT stakeholders a shared framework for understanding business processes; gain agreement on the context and scope of business processes.
    • Context: Project or service scoping; assessing business pain points and process improvement needs.
      • Scope: A business domain or subdomain, usually involving multiple organizational units.
    • Luke Tracy
    		v1 in wiki
    12Case for Action
    • J.J. Du Chateau
    • Jenni Laughlin
    		v1 in wiki

    Collaboration Tools