After graduation, as a software developer and enterprise architect consultant, he dedicated his career to improving business and technological operations of financial institutions in Wall Street.

This included modules for execution of trading applications, persistence methods for large volumes of data, and design of high-speed network and internet software implementations.

He has worked for J.P. Morgan Chase, Citibank, UBS-Paine Webber, Deutsche Bank, American Express, TD Waterhouse, Pfizer, AIG, Prudential.

The multidimensional software architecture construction (MSAC) introduces an ever-evolving quantum production environment, a Topological space that is subject to geometrical structural modifications during run time and/or design-time.

These changes to the fabric's three-dimensional space of the deployment ecosystem are due to the evolution of architectural environment attributes and the unpredictable behavior of software implementations that affect the production landscape as a whole.

This 3D implementation model is devised to increase the level of software design specificity needed for construction, deployment, integration, and sustainment in production landscapes.

[13] The service framework, driven by Discipline-specific modeling, was devised to encourage consolidation of software assets, reduction of systems redundancy, and acceleration of time-to-market.

SOMF [14] includes a modeling language and a life cycle methodology (see image below) suited for narrowing the gap between the business and the information technology organizations in the enterprise.

Traditionally, to promote the establishment and growth of an enterprise end-state architecture, architects, typically senior IT professionals, deliver a diagram that depicts a future production landscape.

Equally important, another related tenet calls for modifying the charter of development organizations: The software construction phase as we know it now, should focus on proving that architecture assumptions would certainly work in production.

The decomposition process is driven by segmenting the enterprise grand design into structural, behavioral, and volatile regions, so developers can prove that these sub-architectures would indeed work in production 3.