1.What is Zachman Framework ?
The Zachman Framework is a framework for Enterprise Architecture developed by IBM in the 1980s.
It provides a way of defining an enterprise according to a 6×6 matrix of architecture documentation. The columns of this matrix ask the questions why, how, what, who, where, when. The rows look at these questions from different levels of detail: contextual, conceptual, logical, physical and detailed.
The Zachman Framework provides a view for Planners, Owners, Designers, Builders and Subcontractors. The basic idea is that the same thing can be described for different purposes in different ways. This creates a holistic view ― it allows different people to look at the Enterprise from different perspectives.
The Zachman Framework has been incorporated into many Enterprise Architecture frameworks. (often as a reference model)
2.What is SOA ?
SOA is a set of design principles for building a suite of interoperable, flexible and reusable services. These design principles include discoverable service contract, loose coupling, service abstraction, service reusability, service autonomy, service statelessness and service compos ability.
A successful SOA implementation can reduce IT costs by increasing reusability. SOA’s flexible mesh of services can also reduce time to market. SOA also helps to leverage existing investments by wrapping legacy applications in a mesh of reusable services.
3. How can you evaluate if a solution conforms to the Enterprise Architecture?
It is important to engage projects during the initiation phase to ensure that architecture compliance processes are included in the project planning.
Once the solution architecture has been defined a compliance assessment should be performed. The compliance assessment ensures the project conforms to the defined Enterprise Architecture. It is also an opportunity to engage project members and get feedback for the Enterprise Architecture.
The compliance assessment includes checklists for hardware, software, applications, information, security, system management and methods and tools. It also documents an overview of the project architecture / design
4. What Are The Inputs To The Migration Planning Phase?
The inputs to the Migration Planning phase include: Architecture reference materials Requests for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Governance models and frameworks Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document Draft Architecture Requirements Specification Change Requests Consolidated Architecture Roadmap Transition Architectures Implementation and Migration Plan.
5. What Are The Outputs Of The Requirement Management Process?
The output of the requirements management process consists of: Requirements Impact Assessment Updated Architecture Requirements Specification Updated Requirements Repository.
6. What Are The Contents Of The Transition Architecture?
The contents of the Transition Architecture are: Opportunity portfolio Work package portfolio Milestones Implementation Factor Assessment and Deduction Matrix Consolidated Gaps, Solutions, and Dependencies Matrix.
7. What Is Preliminary Phase?
The Preliminary Phase prepares the organization for development of the architecture, ensuring: Commitment to the process Principles and constraints are defined Scope and assumptions are defined Development team is established Framework and methodologies identified Criteria set.
8. What Are The Security Related Activities Within The Technology Architecture Phase Of The Adm?
Security related activities within the Technology Architecture phase of the ADM are: Assessing the security-specific architecture elements for a baseline perspective Revising assumptions about interconnecting systems Identifying and evaluating applicable guidelines and standards Identifying methods for regulating resource consumption Engineering a method for continuously measuring and communicating security measures Identifying the clearance level of users, administrators, and interconnecting systems Identifying minimal privileges required to achieve a technical or business objectives Identifying mitigating security measures Performing threat analysis.