Discover Products Requirements
§ To know/identify what types/strategies of testing should be done
Define the importance of Quality to the Project
To determine how much time and effort would be required [ or can be applied] to testing
Define a test plan, including release criteria
§ To verify different people’s understanding about the product
§ To know when we are ready to ship
I Discover Requirements
Gather Data -> Transform -> Requirement Specs -> Filter -> equirements
§ Requirements are the reasons that drive design choices
§ Learn/Get enough about the product requirements to decide what to test and at what depth
§ Use design decisions to solve the problem occurred with the product
§ Categorize customer requirements into
Users
Attributes
Functions
Users
Who will the product affect? Directly as end-users or indirectly by its existence and by others who are using it.
Attributes
What characteristics do the users need?
How reliable does the product have to be
How fast? What else?
Functions
What does the product do for the users?
Interaction process [ Actor – Action – System ]
The following are the important questions to remember while categorizing the requirements
What got discussed in the initial meetings/forums?
What decisions were made?
Did the requirement actually get implemented in the product without the intent being spoiled?
Gather Data
§ Read the related documents
§ Examine the product’s architecture
§ Run the Product
§ Ask the developers
§ Ask the project manager
Transform Data into Requirements
§ Identify the essence of each statement
§ Is it about the users, attributes or function?
§ Categorize the requirements list by type as users, attributes and functions to distill out the essence of the system [ Note: However/Whatever is collected, would be a subset of normally what would have obtained i.e., a snapshot]
§ Derive a set of specific instances of each of the attributes, which will then be the basis for testing and release criteria
§ Verify the requirements for adequacy with the developers or from whomever the information was collected to make sure the requirements are properly implemented
II Importance of Quality for the Product
§ It has to be figured out, how hard should the product be tested
§ Define the metrics in terms of
Defects
Features
Functionality
Time to market/release
Reliability
This forms the basis for a prioritized Test Plan
III Define Test Plan including Release Criteria
§ Plan what will be tested and what will not be tested
§ Consider each requirement in the context of the entire product
§ If need be, develop use-cases or scenarios to illustrate how to test each requirement/set of requirements
§ Specify the release criteria, to emphasize the specific testing goals
§ Define critical release criteria by first drafting them and negotiating them with the project team
Is it a must to meet the requested release date?
List the consequences if not
§ Get a review from the management and the project team
§ Release the product based on the release criteria and no other criteria.
§ To know/identify what types/strategies of testing should be done
Define the importance of Quality to the Project
To determine how much time and effort would be required [ or can be applied] to testing
Define a test plan, including release criteria
§ To verify different people’s understanding about the product
§ To know when we are ready to ship
I Discover Requirements
Gather Data -> Transform -> Requirement Specs -> Filter -> equirements
§ Requirements are the reasons that drive design choices
§ Learn/Get enough about the product requirements to decide what to test and at what depth
§ Use design decisions to solve the problem occurred with the product
§ Categorize customer requirements into
Users
Attributes
Functions
Users
Who will the product affect? Directly as end-users or indirectly by its existence and by others who are using it.
Attributes
What characteristics do the users need?
How reliable does the product have to be
How fast? What else?
Functions
What does the product do for the users?
Interaction process [ Actor – Action – System ]
The following are the important questions to remember while categorizing the requirements
What got discussed in the initial meetings/forums?
What decisions were made?
Did the requirement actually get implemented in the product without the intent being spoiled?
Gather Data
§ Read the related documents
§ Examine the product’s architecture
§ Run the Product
§ Ask the developers
§ Ask the project manager
Transform Data into Requirements
§ Identify the essence of each statement
§ Is it about the users, attributes or function?
§ Categorize the requirements list by type as users, attributes and functions to distill out the essence of the system [ Note: However/Whatever is collected, would be a subset of normally what would have obtained i.e., a snapshot]
§ Derive a set of specific instances of each of the attributes, which will then be the basis for testing and release criteria
§ Verify the requirements for adequacy with the developers or from whomever the information was collected to make sure the requirements are properly implemented
II Importance of Quality for the Product
§ It has to be figured out, how hard should the product be tested
§ Define the metrics in terms of
Defects
Features
Functionality
Time to market/release
Reliability
This forms the basis for a prioritized Test Plan
III Define Test Plan including Release Criteria
§ Plan what will be tested and what will not be tested
§ Consider each requirement in the context of the entire product
§ If need be, develop use-cases or scenarios to illustrate how to test each requirement/set of requirements
§ Specify the release criteria, to emphasize the specific testing goals
§ Define critical release criteria by first drafting them and negotiating them with the project team
Is it a must to meet the requested release date?
List the consequences if not
§ Get a review from the management and the project team
§ Release the product based on the release criteria and no other criteria.
No comments:
Post a Comment