I've just joined the last few months of a multisite, multi consultancy team which has to deliver a complex system in 90 days. I've got to do the business process testing but there's little documentation and there's a lot of politics. I need to produce a plan for this and state what I need from other people - and I'm an electronics engineer not a software specialist. So I need to ask some dumb questions.
This is what I see as immediate requirements:
Risk assessments of processes so that testing can start with the highest business risks.
Decomposed maps showing process transformation.
Data in and data out (including management information) and how it gets there (keyed from paper, data transfer etc).
Format of output.
Interconnections to other processes.
Do you agree with this? What have I overlooked, what else do I need, what suggestions do you have to make this plan a success? I need answers in a hurry and will appreciate any help you can give me.
First of all I donít quite understand your role on that project as you only provide this piece of information: ďneed to produce a plan for a business process testingď well this is a generic description of what we all do I believe, and still we do it so different.
Also donít understand what is that list you provide. Let me guess: it is created by you lists of the information that you want others to write for you, right? Iím afraid this is typically what testers write, so it's your job not requirements.
OK, perhaps you could ask to provide: process map, risk and environment. I would add use cases including supposed input as desired output (by customers).
?:the art of a constructive conflict perceived as a destructive diagnose.
Presumably you are charged with exercising the product stem-to-stern following all business paths? Yes? Are you also expected to exercise interfaces with external systems? Is this system for internal use by the organization developing it or is it to be a commercial application?
Based on your home page, I presume you are a contractor/consultant for hire - I'm a bit surprised the expectations were not more clearly defined while the contract was being drawn up...
If you are supposed to test the "business process" a basic requirement is to know either the industry or the organization. If this product is a commercial application for sale to other companies, I expect that someone SOMEWHERE has an idea on what a logical process flow, as well as design expectations for each logical unit - whatever they may be. Without those, the test plan would consist of :
See if it works (cross fingers for luck).
As for the rest, I'd suggest checking some of the books on testing mentioned in the forums - I hand people Rex Black's book on testing, as well as "Lessons Learned in Software Testing" by Kaner, Bach, et al. Don't worry about not being a software specialist - the requirement here is THINKING.