Software Quality Assurance
Home Page | Project Management | Software Testing | Software Quality Assurance | About Me

Software Quality Assurance.


Click here to see the Software Testing Life Cycle - Prepared by Natarajan S.

Use this template for any additional information you need such as products, pictures, fan clubs, links or just more information It's important to regularly change the content on your site and make updates to the information that you display. Doing this will help you to get more return visitors.

Magazines, Publications

  • Software Quality Professional Magazine - Published by the American Society for Quality; web site includes table of contents and full text of selected articles.
  • Software Testing and Quality Engineering Magazine - Web site has full text of each print issue's featured article.
  • Software Testing Institute - The Online STI Resource Guide, Automation Handbook, Software Testing Newsletter, Software Testing Discussion Forum

  • What makes a good QA or Test manager?

    A good QA, test, or QA/Test(combined) manager should:

    • be familiar with the software development process
    • be able to maintain enthusiasm of their team and promote a positive atmosphere, despite what is a somewhat 'negative' process (e.g., looking for or preventing problems)
    • be able to promote teamwork to increase productivity
    • be able to promote cooperation between software, test, and QA engineers
    • have the diplomatic skills needed to promote improvements in QA processes
    • have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or QA processes are not being adhered to
    • have people judgement skills for hiring and keeping skilled personnel
    • be able to communicate with technical and non-technical people, engineers, managers, and customers.
    • be able to run meetings and keep them focused

    What is 'configuration management'?

    Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes.

    ISO and CMM

     

    Go to :  ISO - Go to : ISO Official Website

     

    International Organization for Standardization ISO was founded in 1946. It is an international federation of national standards organizations from over 100

     countries. ISO is a word, not an abbreviation, derived from the Greek isos, "equal", found in terms such as "isometric" and "isonomy". It was created in an attempt to avoid creating even more abbreviations for the members' national languages (eg IOS in English or OIN in French for "Organisation internationale de normalisation").

     

    An organization that operates an electric-transmission system that it does not own. Usually, the transmission system it operates includes transmission lines owned

    by more than one electric utility. An ISO's responsibilities include insuring that there is enough generation available at all times so that if one generating plant fails, others

    will pick up the load immediately without interrupting service to customers. Electric transmission systems do not have valves that can control the flow of electricity

    over the transmission lines. Therefore, an ISO operates the transmission system by controlling the amount of electricity that is generated at each point in


     

    CMM - Go to : CMM Official Website

     

    A descriptive model of the stages through which organizations progress as they define, implement, evolve, and improve their processes. This model serves as a guide for selecting process improvement strategies by facilitating the determination of the

    current process capabilities and the identification of issues most critical to quality and process improvement within a particular domain, such as software engineering (SW-CMM), software acquisition (SA-CMM), or systems engineering (SE-CMM).

     

    The Capability Maturity Model (CMM) is a method for evaluating the maturity of organisations on a scale of 1 to 5. The CMM was developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. It has been used extensively