Training Products
Contact Us
Customer Services: +44 (0) 2081 229 150
Email: sales@architecting-the-enterprise.com
Queries: Enquiry Form
Alternatively please view our Contact Us
page for further contact information.
Getting Started with Enterprise Architecture
Getting Started with TOGAF
Value to your organisation of the "Getting Started With TOGAF" programme.
This first stage will prepare an organisation for successful TOGAF architecture projects based on validated business requirements. It will align the IT strategy with the business goals and drivers. We will get people inside and outside an organisation to work together effectively in collaborative, integrated teams. Architecting the Enterprise TOGAF best practise will minimise the cost of IT development through increased reuse and better utilisation of resources.
Objectives for the programme
This programme will establish an Enterprise Architecture practice in your organisation. By the end of this programme you will have customised TOGAF to meet the needs of your organisation, selected and evaluated your architecture tools and established a governance framework for ensuring Business and IT delivery projects conform to the enterprise architecture and principles for your organisation.
Objectives
- Set the scope of the Enterprise Architecture
- Assess the current Architecture Capability Maturity of the organisation
- Develop a set of Architecture Principles
- Define the "Architecture Footprint" for the organisation - the people responsible for performing the architecture work, where they are located, and their responsibilities
- Define the Architecture Governance framework
- Customise TOGAF and define an organisation-specific architecture framework
- Evaluate, select and implement an EA toolset
- Establish the Enterprise Architecture Practice
Outputs
- Organizational Model for Enterprise Architecture
- Scope of organizations impacted
- Maturity assessment, gaps, and resolution approach
- Roles and responsibilities for architecture team(s)
- Constraints on architecture work
- Re-use requirements
- Budget requirements
- Requests for change
- Governance and support
- Tailored Architecture Framework
- Tailored architecture method
- Tailored architecture content (deliverables and artefacts)
- Taxonomy
- Metamodel
- Architecture principles
- Configured and deployed tools
- Enterprise architecture tool strategy identified and documented.
- Tools identified, selected and implemented.
Customise TOGAF and define your specific architecture framework
Objectives for the step
The TOGAF Preliminary Phase is about defining "How we do Architecture" in the enterprise concerned.
There are several main aspects that TOGAF focuses on, one being:
- Defining the changes to the framework to align with the organizations needs
As with any architecture framework, it is recognized that TOGAF 9 will need to be mapped or tailored to the specific requirements of the client organisation involved. This is because:
- The scale of the task in hand varies between small organizations, and global organizations, and the complexity of the existing business and IT landscape
- The maturity of the architecture discipline within organizations varies, creating different pressures and focus for different engagements
- An organization may have their own specific processes and terms that need to be integrated into the approach
- An organization may have an existing EA tools repository which has its own specific terminology and approach inherent within it
- The specific architecture pressure points and issues in organizations vary; some may have already developed a detailed "to be" architecture and roadmap but have no Architecture Governance in place; others may have no "to be" architecture in place and be about to undergo a merger with another organization.
Content tailoring: Content Framework customization if required including a customised metamodel
- Determine the TOGAF extensions most appropriate to the organization's requirement
- Determine the metamodel structure and content that the project will use
The key questions to resolve are:
- Based on the terminology agreed, do metamodel entities need to be added, removed or changed?
- Based on the extensions required, what metamodel entity extensions are needed?
- Are there existing tools that need to be mapped to the metamodel?
Outputs
The main output of the service is a specific Architecture Framework Definition that the engagement will use in the client organization.
This will include:
- An agreed premise that TOGAF will be used
- An agreed shape and scope for the Architecture Engagement
- An agreed set of TOGAF extensions that will be used
- An agreed metamodel structure for the development of Enterprise Architecture
- A clear definition of how the Architecture project will link into existing client governance and change management processes
These can then be used in the Architecture Vision phase when agreeing the Engagement Project Plan, Deliverables, and Statement of Architecture Work.