Certified Enterprise Architect Professional (CEAP) : Module 20 : Architecture of Technology

Technology Architecture creates technology components from application components.

Technology components can be software and/or hardware components, obtainable from the market or organised within the company.

Technology architecture is a subset of enterprise architecture that focuses on the technical aspects of an organization's technology systems. It's concerned with the hardware, software, networks, and databases that support an organization's business processes.

Technology architecture's role in enterprise architecture includes:

Supporting applications and data

Technology architecture ensures that the organization's IT systems have a strong, reliable technological foundation.

Meeting business requirements

Technology architecture translates business requirements into technical specifications and ensures that the systems are designed and implemented to meet those requirements.

Providing a concrete view

Technology architecture provides a more concrete view of how application components will be deployed and realized.

Evaluating responses to constraints

Technology architecture helps evaluate how well an organization responds to constraints, such as by estimating hardware and network sizing needs.

Ensuring business integration

Technology architecture ensures that the application components work together and support the required business integration

Comments

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday? • What will I do today? • What obstacles are impeding my progress? Some people are talkative and tend to wander off into Story Telling . Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting. Here are few tips for running a smooth daily meeting: • Everyone should literally stand-up and no one should sit down ...

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

High-Tech Yuga

Search This Blog