Introducing NAAF

1
Introducing NAAF

• Natty Agile Architecture Framework

2
Current frameworks problems

• Missing agility
• Complexity (comparing TOGAF to Jane Karbones
  book)
• Based on OODA mindset not SOA
• Too wide less specific to types of enterprises
• Organization are like people, they might look the
  same but they're different
• One monolithic process

3
NAAF

• Based on TOGAF
• Architecture is "How" and not "What"
• A task is EA work if it's done using EA
  methodology.
• In the centrer, repository of all building blocks
  and their relations
• Information is separate architecture domain
• and probably the most important

Infrastructure
Repository
Information
Systems
Business
4
NAAF

• Each domain can
• Be anchor for architecture activity
• Has current and target mapping
• Enrich the Repository and use it
• Explicit separation between Business,
  Information, Systems, Infrastructure and
  Technology

Infrastructure
Repository
Information
Systems
Business
5
NAAF Agility

• EA is composite from
• Mission task - two months.
• Version all missions in 6 calendar months.
• Tasks can be
• - Planned EA task
• - Staff-work assigned
  by management
• - Urgent tasks

Task
Version
6
NAAF Agility

• Each task enrich the repository and serve as
  input to next task
• Task might deal with just one domain
• Enable one EA instead of EA silos
• Serve long term EA targets as well as urgent
  management demands
• Each task / version might change previous work
  outcomes
• Must be done with supportive tool

7
NAAF Structure

• ADM (Architecture Develop Method)
• Continuum
• Packages

8
NAAF ADM

• Used by each EA version / task

Repository
9
NAAF ADM

• Vision Version scope
• List of known tasks
• Detailed project plan
• Business
• Business concept
• Objectives and goals
• Process decomposition
• Business process modeling
• Serve as base for BPEL

10
NAAF ADM

• Information
• Conceptual model
• Management model
• Logical model
• Services, their QoS and SLA
• Serve as the base to SOA services.
• Systems
• Hosted services
• Interfaces
• Map to users
• Information flow

11
NAAF ADM

• Infrastructure
• Conceptual model
• Logical model
• Physical model
• Standards
• Solutions
• All domains gaps
• Available solutions/technology
• Choosing solutions/technology

12
NAAF ADM

• Migration plane
• Convert selected solution into projects
• Governance
• Simple model
• Formal activity such as reviews
• Passive activities such as monitoring EA
  compliance and publish results
• Active participate in running projects to
  influence as much as I can.
• Monitoring
• Change in each domain might cause new task.

13
NAAF Continuum

• Building blocks
• Principles, constraints, etc
• EA patterns
• Given building blocks (and relations) from all
  domains for certain business type
• Deals with framework wide attitude
• Can be community or vendor donation

14
NAAF Packages

• Step by step instructions to go through EA
• For now the packages include
• Initial
• Business
• Information
• System
• Infrastructure
• Solutions
• Governance

15
For more details

• Natty Gur
• natty_at_theeagroup.net
• 607-330-1744