ⓘ Software architect


ⓘ Software architect

A software architect is a software developer expert who makes high-level design choices and tries to enforce technical standards, including software coding standards, tools, and platforms.


1. History

The software architect concept began to take hold when object-oriented programming or OOP, was coming into more widespread use in the late 1990s and early years of the 21st century. OOP allowed ever-larger and more complex applications to be built, which in turn required increased high-level application and system oversight.


2. Duties

The role of software architect generally has certain common traits:

Architects make high-level design choices based on their programming experience. An architect has thought through all the aspects of a software, just like an architect that builds a house. A construction architect knows where the ducts will be, where the electric connections will be and where the wall outlets will be. A design that a common person sees is just the walls and windows but a detailed design that is abstracted from the outsider are also present with the architect. In addition, the architect may sometimes propose technical standards, including coding standards, tools, or platforms.

Software architects may also be engaged in the design of the architecture of the hardware environment, or may focus entirely on the design methodology of the code.

Architects can use various software architectural models that specialize in communicating architecture.


3. Other types of IT-related architects

The enterprise architect handles the interaction between the business and IT sides of an organization and is principally involved with determining the AS-IS and TO-BE states from a business and IT process perspective. Many organizations are bundling the software architect duties within the role of enterprise architecture.

An application architect works with a single software application.

Other similar titles in use, but without consensus on their exact meaning, include:

  • Solution architect, which may refer to a person directly involved in advancing a particular business solution needing interactions between multiple applications. May also refer to an application architect.
  • System architect singular, which is often used as a synonym for application architect. However, if one subscribes to Systems theory and the idea that an enterprise can be a system, then System Architect could also mean enterprise architect.
  • Systems architect plural, which is often used as a synonym for enterprise architect or solution architect.
  • Cloud architect plural, which is a software architect who deepen knowledge on architecting solutions and applications on cloud-based infrastructures.

The table below indicates many of the differences between various kinds of software architects:

  • Rational Software Architect is a modeling and development environment that uses the Unified Modeling Language UML for designing architecture for C
  • models are typically enterprise architects business architects business analysts, data architects software architects and so forth. This information
  • designing the architecture takes place at the beginning of a software system s lifecycle, the architect should focus on decisions that have to be right the
  • Chief architect may refer to: Architecture Chief Dominion Architect Chief Government Architect of the Netherlands Software architect Chief Architect Software
  • Chief Architect Software is a developer of 3D architectural home design software for builders, interior designers, architects and DIY home enthusiasts
  • this, the Systems Architect is typically a very senior technologist with substantial, but general, knowledge of hardware, software and similar systems
  • category. IEEE Software s November December 2016 issue, The Role of the Software Architect won the 2017 Folio Eddies Digital Award in the Standalone Digital
  • Rational Software Modeler in 2010 and ended support for it in 2015. Much of the same functionality is now available through Rational Software Architect The
  • January 6, 1949 is an American software architect and author. He contributed to the book 97 Things Every Software Architect Should Know ISBN 059652269X
  • systems that require a hardware architect not to require substantial software and a systems architect The hardware architect will therefore normally interface
  • the Keirsey Temperament Sorter Architect software an open source integrated development environment Systems architect a profession in information and
  • tradeoffs inherent in the structure and design of a system or ecosystem. Software architects use architectural models to communicate with others and seek peer