Article Index
These are a number of articles explaining some important aspects of software testing. The articles are split into six main areas:
- User Acceptance Testing - what it is.
- Project Management - what it is and how it affects you.
- V-Model Development - what it is and why it is important.
- Requirements - what you need to do to get what you want.
- Testing Documentation - what you need to do document the testing.
- Software Issues - what they are for specific software areas.
User Acceptance Testing
Just before a system is delivered you will be asked to do some testing, usually called Users Acceptance Testing or UAT. This section gives advice UAT.
- What Is UAT, And Why Do It? - This is an overview of why you should do User Acceptance Testing.
- UAT Definition - explains the formal definition of UAT testing.
- Five reasons not to do UAT and how they affect the project plan.
Project Management
Whoever is developing your IT system you will no doubt be using project management principles. This section of papers explains some of the key issues involved in planning a project.
- Why Projects Fail - six key issues about why projects fail.
- Project Success - advice about how to have a successful project.
- Basics of a Project Plan - the core principles behind a balanced project plan.
- Project Risk Management - what you need to consider to do project risk management.
V-Model Development
The V-Model is one of the most important models for showing the development process and the links between development and testing. This section explains those various issues.
- Software Development Life Cycle - explains the basic principles of what a software development life cycle is.
- Waterfall Model the seven stages of a waterfall model and how they match the four phases of a SLDC.
- Types of Testing - gives an overview of all types of testing that should be employed during a project.
- Verification and Validation - Definitions and diagrams showing what each term means for testing and the key differences between them.
Requirements
At some time you will need to draw up requirements for a new system, or an extension to an existing system. This section gives some advice on preparing requirements.
- Requirements and Design - covers what should included in the Business Case, requirements documents, and design documents.
- Eight Characteristics of Good Requirements - where the eight characteristics fit into the three sets of communication, control and construction.
- User Requirements - covers what makes a good set of user requirements.
- MoSCoW Prioritisation - prioritising requirements using the MoSCoW technique.
- Performance Testing - explains Performance Testing and the match against non-functional requirements.
Testing Documentation
Testing like any other process has to be documented. This section covers what documents are required.
- IEEE 829 Documentation - is an overview of the international documentation standard that can be used for all types of testing.
- Test Plans - explains the key features of preparing an IEEE 829 test plan.
- Testing Process - This describes the six steps of the testing process for running any type of testing including the six activities involved in the Develop Tests step.
- Software Testing Entry Criteria - seven to include in a test plan.
- Software Testing Exit Criteria - five to include in a test plan.
System Issues
Particular types of system and development methods have specific problems. This section deals with them.
- Legacy System Integration - key issues when merging legacy systems from different organisations.
- Document Management Software Definitions - basic guidelines for Document Management Software.