none
An Architect is... RRS feed

  • General discussion

    • A developer overdue for a promotion
    • Is required in a project to draw Visios with boxes and arrows
    • Is an abstract theoretician with 3 UML binders who is removed from reality
    • Makes the project buzzword-compliant by using words such as ESB, Cloud computing, Web 2.0 etc

    Solution Architect specialised in integration (EAI/SOA/A2A/BizTalk) based in Toronto, Canada. http://blog.percepsys.com
    Tuesday, July 21, 2009 7:11 PM

All replies

  • Pras your post is ironic and funny but I am not agree with you.
    What you are talking about is the Project Manager. LOL

    MCAD - MCSD MCTS Sharepoint 2007 MCTS SQL Server 2005 http://blog.raffaeu.com "If my answer is useful remember to mark it as useful".
    Wednesday, July 22, 2009 5:34 PM
  • I agree with raffaeu, Now you being a solution architect, is this what you do.
    Thursday, July 23, 2009 4:43 AM
  • Pras,

    Not sure what you wanted to convey by this post. Its not about technical jargons and Visio dialgrams most of the time.

    They way I see an Architect is someone:

    1. Who sees a larger/broader picture of the solution/application dev/test team is going to build and work upon.
    2. Responsible for implementing and helping dev team to choose right type of feature/technology while building solutions.
    3. Make sure cross-cutting features like Security, Exception Handling, Logging etc are properly
    4. Planning for Test and Deployment.
    5. Be part of each phase of the project Initiation - Deployment.

    Vidya Vrat Agarwal. MCPD,MCTS, MCT, MCSD .NET, MCAD .NET, MCSD. http://dotnetpassion.blogspot,com
    Monday, May 24, 2010 7:58 PM
  • Pras,

    Not sure what you wanted to convey by this post. Its not about technical jargons and Visio dialgrams most of the time.

    They way I see an Architect is someone:

    1. Who sees a larger/broader picture of the solution/application dev/test team is going to build and work upon.
    2. Responsible for implementing and helping dev team to choose right type of feature/technology while building solutions.
    3. Make sure cross-cutting features like Security, Exception Handling, Logging etc are properly
    4. Planning for Test and Deployment.
    5. Be part of each phase of the project Initiation - Deployment.

    Vidya Vrat Agarwal. MCPD,MCTS, MCT, MCSD .NET, MCAD .NET, MCSD. http://dotnetpassion.blogspot,com


    I would say this is the best and the quickest response for easy understandability. I would appreciate your understanding and request you to post a few more points where AN ARCHITECT is well Described and Meant.

     


    Chandu - SQL Server 2005 - Please mark posts as answered where appropriate.
    Friday, July 30, 2010 8:39 PM
  • Chandu,

    Do you mean to have some description about an Architect, see if this can help http://en.wikipedia.org/wiki/Software_architect

     


    Vidya Vrat Agarwal. http://dotnetpassion.blogspot,com
    Friday, July 30, 2010 9:18 PM
  • A position where senior developers come to finally decide that software development is a bunch of hooey.  
    jad
    Wednesday, March 16, 2011 7:05 PM
  • Hi,

    Pras Biswas being an architect has started the thread in this manner, i think to get the maximum reactions from the architects community.

    I think, the fault is with some of the employers also (along with few architects).  

    • in an organization which has 200 developers there will be 75 solution architects. May be less than 5 of those so called architects does know what is an architecture.
    • This puts the kind of jokes on an architect around the software development community
    • Some organizations give enterprise architect positions like our government give the padmasri awards (to non deservers); They do not know abc of any architecture though.

    I can say architecture is a very big subject, and who ever understands that and practice the techniques he can get the respect of his team.

    An architect is a

    • a senior developer who develops the foundation of your solution
    • a manager who coordinates the team members
    • a leader who inspires the team members and gives them the confidence
    • a business analyst who understands the business, communicates with client 
    • a test lead, who can finalize the testing strategy
    • QA lead, who can control the quality of software through his review of different artifacts (architecture, design, and the code)
    • a guide, who provides the design and development guidance
    • a negotiator, who convinces the client in any conflicts
    • a visionary, who foresees the expansion of the solution in future and makes the placeholders for that
    • integrator, who sees the relations between multiple components in advance and makes the decisions for the future easiness of integrations
    • a documenter, who abstracts the solution and gives the picture of the solution in advance
    • a trouble shooter, who solves the technical problems 
    • a time saver, who provides the understanding of the project to different stake holders with different architectural views
    • a budget consultant, who can estimate the project in advance
    • a service guarantor, who design the non-functional requirements to make sure the service level agreements
    • and many other responsibilities and skills...........simply say 'he is a path provider'

    An Architect is responsible for the success or failure of a project.

    He should warn the management about the feezibility, since he knows it first. 

    May be the sinking of Titanic is the failure of it's architect, i do not know exact reasons though.

    wbr,

    prasadpnvrk

     


    regards, pnvrkprasad
    Saturday, March 26, 2011 10:37 AM
  • 'he is a path provider'...

    I wish i could vote twice for that!


    Peace & Love


    • Edited by adnmaster Monday, May 21, 2012 10:27 PM
    Monday, May 21, 2012 10:26 PM
  • Technically speaking an Entry level software (technical) architect is nothing more than a Good Engineer

    Check out a great video "The Architect by Juval Lowy"at channel 9 

    Tuesday, June 12, 2012 5:43 PM
  • Here are my views on the architects role, he is not simply the smartest developer on the team :-)

    • a senior developer who develops the foundation of your solution

    .....that's the job of a software designer

    • a manager who coordinates the team members

    .....that's the job of a development (resource) manager

    • a leader who inspires the team members and gives them the confidence

    .....that can be any stakeholder of the project

    • a business analyst who understands the business, communicates with client 

    .....That's a BA not an architect

    • a test lead, who can finalize the testing strategy
    • QA lead, who can control the quality of software through his review of different artifacts (architecture, design, and the code)

    .....These are QA folks not an architect

    • a guide, who provides the design and development guidance

    .....Architect can take on that job along with the software designer

    • a negotiator, who convinces the client in any conflicts

    .....Architect would be/should be involeded

    • a visionary, who foresees the expansion of the solution in future and makes the placeholders for that

    .....agree

    • integrator, who sees the relations between multiple components in advance and makes the decisions for the future easiness of integrations

    .....right said

    • a documenter, who abstracts the solution and gives the picture of the solution in advance

    .....agree

    • a trouble shooter, who solves the technical problems 

    .....Not necessary, depending upon where/when the issue occurs, this could production support tasks

    • a time saver, who provides the understanding of the project to different stake holders with different architectural views

    .....Architectural view based communication to the stakeholders, agreed

    • a budget consultant, who can estimate the project in advance

    .....Not sure about this aspect but, an architect can certainly be an influencer on this

    • a service guarantor, who design the non-functional requirements to make sure the service level agreements

    .....This is definitely an architects job to evaluate appropriate QOS attributes for the project

    • and many other responsibilities and skills...........simply say 'he is a path provider'

    .....agree

    Friday, October 5, 2012 5:32 PM
    • A developer overdue for a promotion
    • Is required in a project to draw Visios with boxes and arrows
    • Is an abstract theoretician with 3 UML binders who is removed from reality
    • Makes the project buzzword-compliant by using words such as ESB, Cloud computing, Web 2.0 etc

    Solution Architect specialised in integration (EAI/SOA/A2A/BizTalk) based in Toronto, Canada. http://blog.percepsys.com

    Sorry I do not agree with you.

    I think architect is a very important role in a software development team. It may not be necessary for a small team to have a architect, but if you have more than, say, 20 or 50 developers in your team, you definitely need an experienced architect. In our company, Comm100, before we enter the coding phase, our architects partition the system into different modules and draw out all the classes, interfaces and even the parameters of all the public methods and properties. This way, the maintainability of the implementation/coding part of the whole system can be significantly improved. Or else, the code by different developers will be very different, a disaster for software.

    Just my point.

    Kevin gao

    http://livechat.comm100.com/livesupport/ for your web site

    MCSD, MCDBA, MBA

    Wednesday, November 28, 2012 7:42 AM
  • I do agree with Kevin 
    Monday, December 3, 2012 8:44 AM
  • Prasad has my vote. As another guy with architect in my title, I pretty much have to do all of that stuff to some degree or another.  Less is required when I work with my company's stakeholders and my own software team.  But when you are working on an external project with maybe 2-3 dev teams involved or several contractors, then the more diagrams the better imo.  Just understanding good design principles, decoupling, why some things belong where they do (app/BLL/DAL/DB) is a big chunk of it imo.  That and being able to visually represent the difference of these concepts to a NON software writer is not something every Dev can do well.  Often the DBA type can't see past the DAL since they are looking at it from one direction.  Often the App Dev's don't understand some of the implications to the DB and why queries shouldn't be written a certain way.  An architect needs to understand both sides of the equation.

    But to add my own definition:

    Architect = Developer with alot of experience that has somehow maintained some social skills, has friendly personality, can draw good stick figures, define classes, and quit playing World of Warcraft a long time ago.

    • Edited by GSS138 Thursday, January 3, 2013 8:13 PM
    Thursday, January 3, 2013 8:07 PM
  • But to add my own definition:

    Architect = Developer with alot of experience that has somehow maintained some social skills, has friendly personality, can draw good stick figures, define classes, and quit playing World of Warcraft a long time ago.

    +1 for humor points (following some great, serious & simply-stated points).  I almost choked on my tea laughing at this. :}


    J0e3gan http://stackoverflow.com/users/1810429/j0e3gan

    Tuesday, May 20, 2014 6:38 AM