What Is An Architectural Framework


Published on

The world has not really settled on precise definitions of IT architecture or architecture description as these terms relate to the enterprises and its systems or software

Published in: Technology
1 Comment
  • Yes, this is very good thank you!

    I just deployed a portal on Enterprise Architecture Resources, feel free to visit it .

    You'll find free TOGAF 9 examination tests and other EA resources : http://theopenarch.com


    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • What Is An Architectural Framework

    1. 1. What is an “Architectural Framework ”
    2. 2. Definitions <ul><li>“ Architecture frameworks address what it means to define and document an architecture” </li></ul><ul><li>The world has not really settled on precise definitions of architecture or architecture description as these terms relate to the enterprises and its systems or software. </li></ul><ul><li>We can generally agree that architecture is about the structure of important things (systems or enterprises), their components, and how the components fit and work together to fulfill some purpose. </li></ul>
    3. 3. Why, a Framework? <ul><li>It all boils down to, communication </li></ul><ul><li>A framework provides a generic universe and a common vocabulary within which we can all cooperate together - to address a specific issue. </li></ul><ul><li>Frameworks do not have to be comprehensive, but they should be leveraged to provide at least a starter set of the issues and concerns that must be addressed in the development of an architecture. </li></ul>
    4. 4. The Framework Components <ul><li>Views/Presentation </li></ul><ul><ul><li>Provide the mechanisms for communicating the information about the relationships in the architecture </li></ul></ul><ul><li>Methods </li></ul><ul><ul><li>Provide the disciplines for gathering and organizing the data </li></ul></ul><ul><ul><li>Construct the views in a way that helps insure integrity, accuracy and completeness </li></ul></ul><ul><li>Knowledge </li></ul><ul><ul><li>Support the application of the methods and the use of tools for views </li></ul></ul>
    5. 5. The Framework Evolution
    6. 6. The Types of Frameworks <ul><li>TOGAF </li></ul><ul><li>FEAF </li></ul><ul><li>DODAF </li></ul><ul><li>Zachman </li></ul><ul><li>* There are more framework vendors out there - but for the sake of discussion, we’ll look at the major four (4). </li></ul>
    7. 7. TOGAF <ul><li>TOGAF intends to provide a practical, freely available, industry standardized method of designing an EA, leveraging all relevant assets in the process. </li></ul><ul><li>TOGAF is sufficient for an organization to use &quot;as-is&quot; or to adapt as an EA development method for use with other deliverables-focused frameworks. </li></ul><ul><li>It provides a context for the use of multiple frameworks, models, and architecture assets in conjunction with the TOGAF Architecture Development Method. </li></ul>
    8. 9. FEAF <ul><li>An overriding goal of OMB is to improve interoperability within the United States Government by creating one FEA. The FEA integrates the separate architectures of the various Federal Agencies. </li></ul><ul><li>In support of this goal, the Government needs a collaboration tool for collecting and storing common architecture information. The FEAF is the current version of that tool and allows the Federal Government to: </li></ul><ul><ul><li>Organize Federal information for the entire Federal Government </li></ul></ul><ul><ul><li>Promote information sharing among Federal organizations </li></ul></ul><ul><ul><li>Help Federal organizations develop their architectures </li></ul></ul><ul><ul><li>Help Federal organizations quickly develop their IT investments processes </li></ul></ul><ul><ul><li>Serve customer needs better, faster, and more cost-effectively </li></ul></ul>
    9. 10. FEAF <ul><li>The scope of application for the FEAF includes all organizations throughout the Federal Government and all their partners, including: </li></ul><ul><ul><li>Large, major Federal Departmental systems </li></ul></ul><ul><ul><li>Departmental Divisions and Bureau systems </li></ul></ul><ul><ul><li>Other Federal Agency systems </li></ul></ul><ul><ul><li>Systems where substantial investments are involved with international, State, or local Governments </li></ul></ul>
    10. 13. DODAF <ul><li>The DoDAF is intended to ensure that the architecture descriptions are relatable between and among each organization ’ s operational, systems, and technical architecture views and are comparable and integrable across organizational boundaries. </li></ul><ul><li>The framework provides both the rules and guidance for developing and presenting architecture descriptions. </li></ul>
    11. 14. DODAF <ul><ul><li>The products defined by the framework are the work products of architecture development - the descriptive artifacts that communicate the architecture. </li></ul></ul><ul><ul><li>The framework provides direction on how to describe architectures; it does not provide guidance in how to construct or implement a specific architecture or how to develop and acquire systems or systems-of-systems. </li></ul></ul>
    12. 16. Zachman <ul><li>The Zachman Framework describes a holistic model of an enterprise's information infrastructure from six perspectives </li></ul><ul><li>There is no guidance on sequence, process, or implementation of the framework. The focus is on ensuring that all aspects of an enterprise are well-organized and exhibit clear relationships that will ensure a complete system regardless of the order in which they are established. </li></ul>
    13. 18. What Now? <ul><li>Remember - unless required by corporate or governmental mandates - no one framework does it all. </li></ul><ul><li>An integration of two or more frameworks may be required to satisfy your needs and organizational requirements. </li></ul>