Category: Softwares

Categories
Management Software Architect

Amsterdam Information Management Model (AIM)

TL;DR: The Amsterdam framework for information management provides a mapping of the relationships between organization and information.

The Amsterdam Framework for Information Management was created at the University of Amsterdam in 1997 to provide a high-level view of the entire scope of information management. It can be used as a tool for positioning and interrelating information management functions, specifically for business-IT alignment, sourcing, and IT governance. The framework can be applied to analyze organization and responsibilities, and can support strategic discussions in three different ways: descriptive, specification, and prescriptive.

Amsterdam Framework for information Management

The framework distinguishes three domains of governance on the horizontal axis: business, information and communication, and technology. The vertical axis describes the three levels of governance: strategy, structure, and operations. The framework offers a map of the entire information management domain and can be used for positioning specific information management processes in the organization, reorganizing the information management organization, and identifying gaps in an organization’s information management.

This model can help in understanding the complex world of business and IT, and more specific, to understand the role of information management.

'Coz sharing is caring
Categories
HTTP Concepts PHP Software Architect Softwares Technology

MVC vs MVVM vs MVP… What the heck?

When it comes to the architecture design patterns, we have many options to choose from Model-View-Controller (MVC), Model-View-ViewModel (MVVM), Model-View-Presenter (MVP), and keep going… Most often what I hear from the software engineers are :

  • What is MVVM?
  • What is the difference between MVC, MVVM and MVP?
  • How to choose between MVC and MVVM?

Although the answers are simple but to understand the concept in depth and clearly, like always, I would prefer to take a real use case as an example. Let’s think about a music search application, musicoverflow (derived from stackoverflow; hmm a long time programmer).

Fundamentally, MV(X)

Before we dive in the various variants of it, lets understand what MV(X) is? Fundamentally, all these variants, MVC, MVVM, MVP aims to segregate the duties of processing, visualization, we need to understand briefly MVC, MVP, and MVVM architecture before dive into them.

Why Model-View-(C or P or VM)?
The aim of these architectures is to separate the responsibilities of visualizing, processing, and data management for UI applications.

'Coz sharing is caring