Need of Solutions Architect?

What makes a good architect
http://blog.wipro.com/blog/2010/05/20/what-makes-a-good-architect/

Here is brief from this lecture:
1) The first quality that we look for is the ability to quickly grasp complexity and simplify it. What we look for is whether the person is able to break it down to simpler steps that they can address and build a solution.
The second quality that we look for is to taking pride in the work, however small or big. In essence, interest in technology does not mean that it is meant for junior engineers only.
The third quality that is endearing to my team is the ability to “roll up your sleeves and get to work”. We never look for people who my team typically refers to as “powerpoint architects”.
The fourth quality we look for is attention to detail. Most of my team are typically connected to or work with a director or a VP level person in a client organization. Love to work at a detailed level along with having a bigger picture in hand

http://www.cutter.com/content-and-analysis/resource-centers/enterprise-architecture/sample-our-research/ear0810.html


http://msdn.microsoft.com/en-us/architecture/cc505974.aspx


Why do we need Solution Archtects?
Submitted by Andrew Winterburn on 02 Apr 2009

http://www.capgemini.com/technology-blog/2009/03/why_do_we_need_solution_archit.php

http://www.capgemini.com/technology-blog/2009/03/featured_job_role_enterprise_a.php

Introducing the Tellurium Automated Testing Framework

Introduction
The Tellurium Automated Testing Framework (Tellurium) is a framework for testing web applications, which was started in June 2007 by Jian Fang and became an open source project on Google Code in June 2008. It is released on a regular basis and is currently at 0.7.0.
The core of the project was started over two years ago and quickly spawned multiple sub-projects including: UDL, Core, Engine, Widget extensions, Maven Archetypes, Trump, Tellurium IDE, TelluriumWorks, and reference projects.
The framework was developed from the Selenium framework, but with a different testing concept. Most existing web testing frameworks, like Selenium, primarily focus on individual UI elements. Tellurium on the other hand, treats the whole UI element as a widget; calling the element a UI module.

http://www.infoq.com/articles/tellurium_intro

LTO: Boundary value testing: How to crash an airplane's entertainment system

Hugh Thompson has a cool blog entry on how he was able to bring down the gaming/movie console on an airplane. He calls it one of the most interesting examples of an untested boundary condition he has ever seen.
Fortunately the IFE system is totally disjoint from the avionics, so he reached Orlando without incident!

http://blogs.csoonline.com/node/151

Sogeti acquires another company

http://www.siliconrepublic.com/news/news.nv?storyid=single10670

"Irish company Insight Test Services Ltd has been acquired by Sogeti, a provider of local IT professional and test services globally. The acquisition will see Sogeti Ireland grow to 200 staff by the end of 2008. Insight Test Services is a specialist software quality assurance, test and compliance full service provider. It currently offers consulting, managed services, training and resourcing services to over 80 clients."

Support for WinRunner Tool

For those of you who have not yet received word. The End-of-Life support for all versions of WinRunner is now official as of Feb. 2008. No more new versions of WR will be released and current versions will be supported fully until 2009 and at limited bases until 2011. There is a WR to QTP conversion tool called Gallop that does about 70/80% conversion of the scripts that can be leveraged. Please cascade this information to your teams. For more information please see the link below:

https://h10078.www1.hp.com/cda/hpms/display/main/hpms_content.jsp?zn=bto&cp=1-11-127-24^1074_4000_100__

Difference between winsock and wininet level recording

On Fri, Sep 17, 2010 at 11:55 PM, James Pulley wrote:
WinInet “weighs” more in terms of oveall system resources as it is integrated with the Microsoft security APIs. The sockets option, what used to be known as Turboload, was developed to allow for lighter weight virtual users to exist in larger quantities on a given reference hardware definition (Load Generator). The core change is on playback, if you need integration with the Microsoft security infrastructure, i.e. using web_set_user() you will need to use WinInet and you will need to use Windows Load Generators. And yes, these users will use more system resources.

The default is sockets. Unless you need to integrate directly with a security infrastructure for user authentication you will likely not need WinInet. I have yet to find a reason why you would need to alter these options on the recording front from the default of capturing both. I suppose there are some exotic instances where you would want to choose WinInet or Socket but not both (see recording options web+winsock virtual user), but I have yet to encounter those.

James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix

From: lr-loadrunner@googlegroups.com [mailto:lr-loadrunner@googlegroups.com] On Behalf Of Abhishek Banginwar
Sent: Friday, September 17, 2010 1:48 PM
To: LR-LoadRunner@googlegroups.com
Subject: difference between winsock and wininet level recording

hi all,

Can anyone please explain what is winsock, wininet and winsock and wininet level in http/html protocol?
winsock and wininet microsoft apis but how does it affect recording and the script that is generated.

--
Abhishek

Good Blog

http://loadstorm.com/load-testing-downloads