Jump to content

Systems architect: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m →Duties: Added 'a' to a sentence where it seemed to be missing
Tag: Reverted
unsourced information removed; please provide reliable sources
Tag: Reverted
Line 2: Line 2:
<!---None of my content is from any published source! user:normxxx--->
<!---None of my content is from any published source! user:normxxx--->
{{Citations missing|date=December 2006}}
{{Citations missing|date=December 2006}}
{{Infobox occupation
| name= Systems Architect
| image=
| caption=
| official_names= Systems Architect
<!------------Details------------------->
| type= [[Profession]]
| activity_sector= [[Systems Engineering]]
| competencies= [[domain knowledge]], engineering and planning skills
| formation=
| employment_field=
| related_occupation=
| average_salary=
| field_of_study= Systems Engineering
}}


The '''systems architect''' is an [[information and communications technology]] professional. Systems architects define the [[Systems architecture|architecture]] of a computerized system (i.e., a system composed of software and hardware) in order to fulfill certain [[requirements]].
The '''systems architect''' is an [[information and communications technology]] professional. Systems architects define the [[Systems architecture|architecture]] of a computerized system (i.e., a system composed of software and hardware) in order to fulfill certain [[requirements]].

== Duties ==
In [[systems design]], the architects (and engineers) are responsible for:
* Interfacing with the [[User (computing)|user]](s) and [[sponsor (commercial)|sponsor]](s) and all other [[Stakeholder (corporate)|stakeholders]] in order to determine their (evolving) needs.
* Generating the highest level of system requirements''',''' based on the users' needs and other constraints.
* Ensuring that this set of high level requirements is [[consistent]], complete, [[wikt:correct|correct]], and [[operational definition|operationally defined]].
* Performing [[cost–benefit analysis|cost–benefit analyses]] to determine whether requirements are best met by manual, software, or [[computer hardware|hardware]] functions; making maximum use of [[commercial off-the-shelf]] or already developed [[Manufacturing|components]].
* Developing partitioning [[algorithms]] (and other [[process (computing)|processes]]) to [[File allocation table|allocate]] all present and foreseeable requirements into discrete partitions such that a minimum of [[information transfer|communications]] is needed among partitions, and between the users and the system.
* Partitioning large systems into (successive layers of) [[subsystem]]s and components each of which can be handled by a single engineer or team of engineers or a subordinate architect.
* Interfacing with the design and implementation engineers and architects, so that any problems arising during design or implementation can be resolved in accordance with the fundamental design concepts, and users' needs and constraints.
* Ensuring that a maximally [[Robustness (computer science)|robust]] and [[Extensibility|extensible]] design is developed.
* Generating a set of '''[[acceptance test]]''' requirements, together with the designers, [[test engineers]], and the users, which determine that all of the high-level requirements have been met, especially for the [[computer-human-interface]].
* Generating products such as [[sketch (drawing)|sketches]], [[computer model|models]], an early [[user guide]], and [[prototypes]] to keep the users and the engineers constantly up to date and in agreement on the system to be provided as it is evolving.
* Ensuring that all architectural products and products with architectural input are maintained in the most current state and never allowed to seriously lag or become obsolete.


==Architect metaphor==
==Architect metaphor==
Line 38: Line 9:


In the UK the architects registration board excludes the usage of architect (when used in the context of software and IT) from its restricted usage. <ref>{{cite web|url=http://www.arb.org.uk/public-information/regulate-use-title-architect/ |publisher=Architects Registration Board|title=What we do to regulate use of the title 'architect'|access-date=8 July 2019}}</ref>
In the UK the architects registration board excludes the usage of architect (when used in the context of software and IT) from its restricted usage. <ref>{{cite web|url=http://www.arb.org.uk/public-information/regulate-use-title-architect/ |publisher=Architects Registration Board|title=What we do to regulate use of the title 'architect'|access-date=8 July 2019}}</ref>

== See also ==
* [[Enterprise architecture]]
* [[Enterprise architect]]
* [[Hardware architecture]]
* [[Requirements analysis]]
* [[Software architecture]]
* [[Software engineering]]
* [[Systems architecture]]
* [[Systems modeling]]
* [[Systems engineering]]
* [[Systems design]]
* [[Business analyst]]
* [[Service-oriented modeling]] framework (SOMF)


== References ==
== References ==
Line 57: Line 14:


== Further reading ==
== Further reading ==
{{Refbegin}}
* [[Donald Firesmith]] et al.: ''The Method Framework for Engineering System Architectures'', (2008)
* [[Donald Firesmith]] et al.: ''The Method Framework for Engineering System Architectures'', (2008)
* Mark W. Maier and Rechtin, Eberhardt, ''The Art of Systems Architecting'', Third Edition (2009)
* Mark W. Maier and Rechtin, Eberhardt, ''The Art of Systems Architecting'', Third Edition (2009)
Line 63: Line 21:
* [[Jerry Saltzer|J. H. Saltzer]], M. F. Kaashoek, ''Principles of Computer System Design: An Introduction'', Morgan Kaufmann, 2009.
* [[Jerry Saltzer|J. H. Saltzer]], M. F. Kaashoek, ''Principles of Computer System Design: An Introduction'', Morgan Kaufmann, 2009.
* Rob Williams, ''Computer Systems Architecture: a Networking Approach'', Second Edition (December 2006).
* Rob Williams, ''Computer Systems Architecture: a Networking Approach'', Second Edition (December 2006).
{{Refend}}


== External links ==
== External links ==

Revision as of 13:00, 16 February 2022

The systems architect is an information and communications technology professional. Systems architects define the architecture of a computerized system (i.e., a system composed of software and hardware) in order to fulfill certain requirements.

Architect metaphor

The use of any form of the word "architect" is regulated by "title acts" in many states in the US, and a person must be licensed as a building architect to use it.[1]

In the UK the architects registration board excludes the usage of architect (when used in the context of software and IT) from its restricted usage. [2]

References

  1. ^ The term "architect" is a professional title protected by law and restricted, in most of the world's jurisdictions, to those who are trained in the planning, design and supervision of the construction of buildings. In these jurisdictions, anyone who is not a licensed architect is prohibited from using this title in any way. In the State of New York, and in other US states, the unauthorized use of the title "architect" is a crime and is subject to criminal proceedings."Architecture: What's Legal, What's Not" (PDF). AIA New York State. Retrieved 9 July 2012."NYS Architecture:Laws, Rules & Regulations:Article 147 Architecture". Retrieved 9 July 2012.
  2. ^ "What we do to regulate use of the title 'architect'". Architects Registration Board. Retrieved 8 July 2019.

Further reading

  • Donald Firesmith et al.: The Method Framework for Engineering System Architectures, (2008)
  • Mark W. Maier and Rechtin, Eberhardt, The Art of Systems Architecting, Third Edition (2009)
  • Gerrit Muller, "Systems architecting: A business perspective," CRC Press, (2012).
  • Eberhardt Rechtin, Systems Architecting: Creating & Building Complex Systems, 1991.
  • J. H. Saltzer, M. F. Kaashoek, Principles of Computer System Design: An Introduction, Morgan Kaufmann, 2009.
  • Rob Williams, Computer Systems Architecture: a Networking Approach, Second Edition (December 2006).
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Systems_architect&oldid=1072200534"