It was a busy June for Touchstone Technology Training...
Some people are taking testing to the next level; check out this article http://www.humansinvent.com/#!/7200/cite-the-ghost-city-built-to-test-future-tech/
Fault modeling based testing can be used to detect possible race conditions, processor/memory bandwidth issues, communications issues, and other difficult to debug issues.
Understanding what Quality in Software means to you (and your business) is key to figuring out what you are willing to do to ensure that quality in your end product. It is very well known that the earlier in the software lifecycle a software defect is discovered, the less expensive it is to fix. There is no time better than now to start thinking about how to instill quality in your software from the very earliest part of the software creation process as possible. The longer you wait, the more pain even basic initiatives can become. Notice I am not talking about how to test your software to make it the best quality it can be. I am talking about how to build in the quality when as the software is created.
Part of the Agile Manifesto reads: - Individuals and interactions over processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan Test and Quality Assurance people love a plan; it is how Test and QA folks answer the questions "how do I know if I am done" and "how do I know if I succeeded".
Touchstone Technology Training has announced its Software Quality Assurance and Agile Development training courses in Denver.
Even in an Agile/Scrum environment no aspect of the project work will have a greater effect on the end result than how the work is organized and estimated. Being able to draw the correct information from the Product Road Map and Project Plan is critical to organizing the work effectively and estimating the work accurately.
Quality In Software – How would YOU describe it? For many people in the software business, improving quality is a key piece in a continuous effort to put out better software with less effort. How you answer this question will by its very nature push you in a direction to improve your software. Are you answering it with the right perspective? Read on!
Pages: 1 2