QA

Hi-Level notation of Software Test Documentation

Template for assiting with Test Plan creation.

Example Test Plan

A common tool for ensuring test plan coverage is complete - or if incomplete, allows risk to be identified.

 

The main groups of Testing are Functional and Non-Functional..Security Testing could be at this general level as if not part of a specification. If Security Testing is addressed in a specification, it would be deemed part of the functional tests.

 

Functional Testing

1. bases test cases on the specifications of the software component under test
2. The identification of functions that the software is expected to perform
3. The creation of input data based on the function's specifications
4. The determination of output based on the function's specifications
5. The execution of the test case
6. The comparison of actual and expected outputs

 

This should simplify your approach to Agile management. The concept is to stay in the center 'sweet spot'. Gravitating into one state of mind has an equal effect on the Agile balance. Staying in the zone, means the client gets what they need, its built well, and project cost is competitive.

For example: Too much energy on doing the Right Thing(massive feature set?, causes time to market to suffer and it may not be done correctly so updates and maintenance could be a night mare.

FOCUS	Too Much	Too Little
RIGHT THING	Late, Bad Qualty	Wrong Function
THING RIGHT	Late, Wrong Function	Bad Quality
FAST	Bad Quality, Wrong Function	Late

 

 

A down and dirty outline of what's important in the world of scrum. Whereas AGILE is a project management that focuses on 'doing the right things right - and fast', SCRUM is a framework - or process - one can employ to drive results in an AGILE direction. Let's say principle(AGILE) vs process(SCRUM) [MARKUP IN PROGRESS]

[MARKUP IN PROGRESS]

BRD, SRS, and Test Plan

BRD

The Business Requirements Document

This document outlines the Business needs that justify the development of a product, the features required to meet those needs, and how those features should look to end users. This document is not necessarily concerned with HOW to achieve the feature, only that a functionality is required.

SRS

The System Requirements Specification relates back to the BRD and provides the technical details on how to accomplish each BRD requirement.

If the BRD includes an 'Account Deletion' feature, the SRS would typically describe the Account Deletion form fields, authentication rules, and visual elements such as buttons. Authentication architecture might be described elsewhere in the SRS and only referenced in that specific section.

[MARKUP IN PROGRESS]