User talk:Voywiki

Welcome!

Hello, Voywiki, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few links to pages you might find helpful:

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or click here to ask for help here on your talk page and a volunteer will visit you here shortly. Again, welcome! Mdd (talk) 22:07, 20 June 2014 (UTC)[reply]

Enterprise architecture

Hi Voywiki,

Thank you for undoing a revision on the Enterprise Architecture page that added framework specific information to the main page. Just a small note... as a courtesy, please add a section to the TALK page when you undo someone's edits, so that they can learn why you did it.

Nickmalik (talk) 20:57, 5 June 2014 (UTC)[reply]

Solutions Architect

Hi Voywiki, in this edit (17 May 2015) the following text was added:

The essence of the solutions architect 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 on several factors: previous, successful design patterns that the solutions architect has been involved with, reference architectures and enterprise architecture guidance. It involves careful balance of project concerns with enterprise concerns.<ref name="2006 Jupitermedia"/><ref name="Mistrik 2013">Mistrík Ivan, Antony Tang, Rami Bahsoon, Judith A. Stafford. (2013), Aligning Enterprise, System, and Software Architectures. Business Science Reference.</ref>

While there is the following 2005 text "Anatomy of a Software Development Role: Solution Architect," by Robert Bogue, 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.

Almost 1.5 sentences are practically copy/pasted here without the use of quotation marks, and this is not allowed here. Now today I noticed a similar edit here, which I just corrected here. I think this cannot continue. Do you understand the problem here? -- Mdd (talk) 00:38, 30 August 2015 (UTC)[reply]

Thank you Mdd for pointing it out and for correcting my entry on EAM page. I will try to be more careful in the future. As to your remarks on the Solution Architect page, please don't cite blog entries as examples of another source. Better speak with Robert Bogue and ask him to put quotations in his articles. While I agree with the overall premise of your comments, please consider different tone when making them. Voywiki (talk) 02:00, 30 August 2015 (UTC)[reply]

Now there is a possible copy-vio in the Solutions Architect lemma is detected, this should be fixed. Can you fix it, or should we added a {{Copyvio}} tag, so that others can take over? -- Mdd (talk) 19:19, 30 August 2015 (UTC)[reply]

Done. I chose to paraphrase the text from the references provided. 22:51, 30 August 2015 (UTC)

Thanks, it is indeed another possible solution. For me personally, I find it very difficult to determine when a quote is paraphrases enough... so I prefer using quotation marks... which I realize doesn't always give the best solution. Now there are two more issues here, which I further explained at the articles talk page, see here. -- Mdd (talk) 10:29, 31 August 2015 (UTC)[reply]