Talk:Solution architect

This page needs 80-90% of the words removed. -- Resuna (talk) 13:11, 28 September 2013 (UTC)

Possibly the worst wikipedia article I have read in the past decade BesigedB ^(talk) 23:44, 5 February 2017 (UTC)

"Solutions" - Why the plural?

The reference talks about a Solution Architect, which is a term I'm happy and familar with, yet the article for some reason refers to a Solutions Architect.

Was it a conscious switch in writing this article, if so why? The article talks about Solution Architecture, why isn't this practised by a Solution Architect.

Eeeuk (talk) 16:36, 1 December 2009 (UTC)

Honestly it's pure semantics. Personally I prefer the plural, but the two are clearly interchangeable. Acrooney (talk) 13:20, 29 April 2010 (UTC)

You wouldn't say Networks Architect or Buildings Architect even though they also work on many. I think where two terms are interchangable, the more commonly used version should be the standard. — Preceding unsigned comment added by Skipjacker (talk • contribs) 22:00, 1 June 2012 (UTC)

I plan to assert WP:BOLD soon to singularize the title and references within the article. I've confirmed that, once you remove job postings, references on the web to the term are singular at a rate of 8:5. Mostly, though, it is the unassailable convention presented in the previous comment that convinced me to do so. Oh, and that I am a Solution Architect myself obviously helps make the point. Dhugot (talk) 04:38, 11 October 2015 (UTC)

Legal ramifications of using the title of architect

Discussion at Talk:Enterprise_architect#Architect --Ronz (talk) 18:41, 5 July 2012 (UTC)

Quotes about Solution Architect

In these three edits (May 2015) the following three quotes have been used in the text:

• Solutions Architect (SA) - The technical architect is responsible for transforming the requirements created by the Functional Analysts into a set of architecture and design documents that can be used by the rest of the team to actually create the solution. The Solutions Architect is typically responsible for matching technologies to the problem being solved.
  • Robert Bogue, "Anatomy of a Software Development Role: Solution Architect," at developer.com, May 12, 2005.

• The essence of the Solution Architect (SA) role is the conversion of the requirements into an architecture and design that will become the blueprint for the solution being created. This conversion is based largely upon the previous design patterns that the SA has been involved with in the past through reading and staying abreast of the latest techniques, or through personal experience.
  • Robert Bogue, "Anatomy of a Software Development Role: Solution Architect," at developer.com, May 12, 2005.

• The final component to the role of solution architect is the motivation and guidance of the development leads. Development leaders need to buy into and accept the architecture, to know how the pieces will fit together at a high level. They must also see the art portion of the architecture to get an appreciation of the subtle nuances of their portion of the architecture.
  • Robert Bogue, "Anatomy of a Software Development Role: Solution Architect," at developer.com, May 12, 2005.

Now I brought this to the attention of the editor, see here, and he paraphrased the text of one of the quotes, see here. I think the other two should be paraphrased as well, and/or quotation marks should be added. -- Mdd (talk) 09:58, 31 August 2015 (UTC)

Thank you. I have paraphrased two remaining paragraphs and added the reference to developer.com material.Voywiki (talk) 16:13, 31 August 2015 (UTC)

About the source data

In the context of the above subject, there seem to be a disagreement on the source to be added. Voywiki argued "... don't cite blog entries as examples of another source..." (see here) However in my opinion:

• There is the 2005 web article by Robert Bogue first published on developer.com.
• This article seem to have been used in the 2006 Breaking Down Software Development Roles at Developer eBook, 2006 Jupitermedia Corp... but no reference is added in the text.
• The 2005 web article seem to be the original article, which is cited in multiple scientific articles, see here for example in: Tandon, Rakesh. "The Role of Solution Architects in Systems Integration." IT Professional 9.2 (2007): 26-33. which mentions as source data ... Anatomy of a Software Development Role: Solution Architect,” Robert Bogue, http://www.developer.com/ mgmt/article.php/3504496...

In this case I think the 2005 article should be listed here. -- Mdd (talk) 10:17, 31 August 2015 (UTC)

Added the reference per the suggestion above. Voywiki (talk) 16:13, 31 August 2015 (UTC)

Requested move 11 October 2015

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: moved to Solution architect. There's a rough consensus to use the singular per WP:UCN and decapitalise per WP:JOBTITLES. Jenks24 (talk) 09:13, 27 October 2015 (UTC)

---

Solutions Architect → Solution Architect – As User:Eeeuk and User:Skipjacker clearly explained, in the earliest talk page entries, the discipline is singular and the convention for <anything> Architect is to use the singular. This is very clearly supported by the Google ngrams for both the discipline's and the practitioner's terms, as seen [here] and, especially, [here], which clearly show the singular is much more common than the plural in the literature. Dhugot (talk) 05:13, 11 October 2015 (UTC) --Relisted. sst✈ 08:13, 19 October 2015 (UTC)

• Support per nom, and per WP:CONSISTENCY with solution architecture. No such user (talk) 09:24, 19 October 2015 (UTC)
• No opinion on the request, but the title should be lowercase per WP:JOBTITLES. Calidum 03:35, 26 October 2015 (UTC)

---

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.