Thursday, July 2, 2009

Software Quality Assurance Policy









This document is a draft version of JISC policy and guidelines for software quality assurance in JISC funded projects. It is intended that the policy and guidelines outlined in this document be piloted with the Distributed eLearning Programme’s eTools projects allowing the refinement of the policy/guidance.

for more details visit link
http://www.macrotesting.com

Software Engineering Metrics









We hear too often that few companies establish measurement programs, that fewer succeed with them, or that many of the companies who have established metrics programs have them in order to conform to criteria established in the Capability Maturity


for more best practices plz visit
http://www.macrotesting.com

Client/Server Software Testing











Client/Server system development is the preferred method of constructing cost-effective department- and enterprise-level strategic corporate information systems. It allows the rapid deployment of information systems in end-user environments.

for more information visit
http://www.macrotesting.com

Software Testing – A Novel Approach










Testing is in integral activity for any type of product development, be it software product development or any other. This paper attempts to identify various issues related to testing that a typical software development company faces.

you can visit this link to download the entire document
http://www.macrotesting.com

Testing a Complete J2EE










Sheldon Wosnick published an article on completing and testing a complete J2EE application using WebSphere Studio. That article was based on the very first beta of WebSphere Studio

You can download complete document at http://www.macrotesting.com

Wednesday, July 1, 2009

Software Testing Techniques 2E











Every professional and commercial software development organization spends a great deal of time in the testing and validation of their software. The testing process, driven either by legal or financial requirements, can be expensive and may thwart the planned deployment of the application.
Many studies indicate that the testing process can even take three times as long as the actual coding itself.







for more information visit
htp://www.macrotesting.com

Comments