George M. Galambos

Last updated

George Galambos (born in Budapest) is a computer engineer. He is an IBM Fellow (2003), [1] an IBM Distinguished Engineer and a member of the IBM Academy of Technology. [2]

Contents

He graduated the Budapest Technical University (Budapest University of Technology and Economics) in 1972, with a Ph.D. in chemical engineering. Prior to which, he studied chemical engineering at the Leningrad Technology Institute (Saint Petersburg State Institute of Technology).

He holds the office of CTO, Global Services (IGS) IBM Canada. Galambos was a designer on the team that built the Interac network connecting bank machines. [3] Galambos advises companies on advanced systems design and strategic IT plans. His current interest includes system design patterns, with a focus on integration.

Galambos holds a patent for 'System and method for transforming an enterprise using a component business model' (Patent #20070174109, Class: 705010000 (USPTO)), A system and method are described for using a Component Business Model (CBM) to transform a business. A CBM map is used to identify components that collaborate to provide a specified capability, and a repository supporting the CBM map is filtered to provide a view of the identified components that highlights how they collaborate. The view is used to identify component features contributing to the specified capability. The specified capability is then enhanced by a transformation strategy that includes re-engineering particular components, identifying a pattern characterizing the collaboration between components and adding a component to perform the collaborative pattern, or adding another feature to the collaboration and adding component to perform the additional feature. The CBM repository provides exemplar best practices that can be adapted for use in a re-engineered component.

Publications

Related Research Articles

In software engineering, service-oriented architecture (SOA) is an architectural style that supports service orientation. By consequence, it is as well applied in the field of software design where services are provided to the other components by application components, through a communication protocol over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. SOA is also intended to be independent of vendors, products and technologies.

Enterprise architecture (EA) is an analytical discipline that provides methods to comprehensively define, organize, standardize, and document an organization’s structure and interrelationships in terms of certain critical business domains characterizing the entity under analysis. The goal of EA is to create an effective representation of the business enterprise that may be used at all levels of stewardship to guide, optimize, and transform the business as it responds to real-world conditions. EA serves to capture the relationships and interactions between domain elements as described by their processes, functions, applications, events, data, and employed technologies.

The Open Group Architecture Framework Reference model for enterprise architecture

The Open Group Architecture Framework (TOGAF) is the most used framework for enterprise architecture as of 2020 that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. TOGAF is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.

Department of Defense Architecture Framework Enterprise architecture framework

The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views. These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal, graphical, probabilistic, or alternative conceptual means. The current release is DoDAF 2.02.

A mashup, in web development, is a web page or web application that uses content from more than one source to create a single new service displayed in a single graphical interface. For example, a user could combine the addresses and photographs of their library branches with a Google map to create a map mashup. The term implies easy, fast integration, frequently using open application programming interfaces and data sources to produce enriched results that were not necessarily the original reason for producing the raw source data. The term mashup originally comes from creating something by combining elements from two or more sources.

Component-based software engineering Branch of software engineering

Component-based software engineering (CBSE), also called component-based development (CBD), is a branch of software engineering that emphasizes the separation of concerns with respect to the wide-ranging functionality available throughout a given software system. It is a reuse-based approach to defining, implementing and composing loosely coupled independent components into systems. This practice aims to bring about an equally wide-ranging degree of benefits in both the short-term and the long-term for the software itself and for organizations that sponsor such software.

A software factory is a structured collection of related software assets that aids in producing computer software applications or software components according to specific, externally defined end-user requirements through an assembly process. A software factory applies manufacturing techniques and principles to software development to mimic the benefits of traditional manufacturing. Software factories are generally involved with outsourced software creation.

Enterprise architecture framework Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

Service-orientation is a design paradigm for computer software in the form of services. The principles of service-oriented design stress the separation of concerns in the software. Applying service-orientation results in units of software partitioned into discrete, autonomous, and network-accessible units, each designed to solve an individual concern. These units qualify as services.

Amanda Elizabeth Chessell is a computer scientist and a Distinguished Engineer at IBM. She has been awarded the title of IBM Master Inventor. She is also a Member of the IBM Academy of Technology.

Kerrie Holley American research computer scientist

Kerrie Lamont Holley is an American software architect, author, researcher, consultant, and inventor. He recently joined Industry Solutions, Google Cloud. Previously he was with UnitedHealth Group / Optum, their first Technical Fellow, where he focused on ideating healthcare assets and solutions using IoT, AI, graph database and more. His main focus centered on advancing AI in healthcare with an emphasis on deep learning and natural language processing. Holley is a retired IBM Fellow. Holley served as vice president and CTO at Cisco responsible for their analytics and automation platform. Holley is known internationally for his innovative work in architecture and software engineering centered on the adoption of scalable services, next era computing, service-oriented architecture and APIs.

Service-oriented modeling is the discipline of modeling business and software systems, for the purpose of designing and specifying service-oriented business systems within a variety of architectural styles and paradigms, such as application architecture, service-oriented architecture, microservices, and cloud computing.

Service Component Architecture (SCA) is a software technology designed to provide a model for applications that follow service-oriented architecture principles. The technology, created by major software vendors, including IBM, Oracle Corporation and TIBCO Software, encompasses a wide range of technologies and as such is specified in independent specifications to maintain programming language and application environment neutrality. Many times it uses an enterprise service bus (ESB).

In information systems, applications architecture or application architecture is one of several architecture domains that form the pillars of an enterprise architecture (EA).

View model

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of a whole system from the perspective of a related set of concerns.

Service-orientation design principles are proposed principles for developing the solution logic of services within service-oriented architectures (SOA).

The Accelerator is a collection of development solutions for IBM i and Windows platforms using .NET Framework, and/or LANSA, technologies provided by Surround Technologies. The Accelerator development architecture is a tool for building Windows and Web apps within a structured framework.

A microservice architecture – a variant of the service-oriented architecture (SOA) structural style – arranges an application as a collection of loosely-coupled services. In a microservices architecture, services are fine-grained and the protocols are lightweight. The goal is that teams can bring their services to life independent of others. Loose coupling reduces all types of dependencies and the complexities around it, as service developers do not need to care about the users of the service, they do not force their changes onto users of the service. Therefore it allows organizations developing software to grow fast and big, as well as use off-the-shelf services easier. Communication requirements are reduced. These benefits come at a cost to maintaining the decoupling. Interfaces need to be designed carefully and treated as a public API. One technique that is used is having multiple interfaces on the same service, or multiple versions of the same service, so as to not disrupt existing users of the code.

The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.

In software engineering and software architecture design, architectural decisions are design decisions that address architecturally significant requirements; they are perceived as hard to make and/or costly to change.

References

  1. "Montrealer wins IBM Fellow award". The Gazette. 2003-06-21. p. 43. Retrieved 2020-08-26 via Newspapers.com Open Access logo PLoS transparent.svg .
  2. IBM Honors and Rewards Elite Technical Employees Archived June 25, 2011, at the Wayback Machine
  3. Interac architect sounds off on SOA Archived May 27, 2011, at the Wayback Machine
  4. Patterns for e-business A strategy for reuse Archived November 8, 2012, at the Wayback Machine
  5. cherbaut.html Archived August 18, 2007, at the Wayback Machine