Solution Decision |
||||
|
Produce a plan for testing the application from a business and technical perspective | |||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
In preparing the functional component, start with the business processes. Each of the processes should be examined and where functionality is required, that should be checked. For example, if the process flow is to set up a new customer, put into the document 'Set up new customer'. If functionality required is to associate customers with a company, then add that as something to check. The existing data modeling worksheet should be modified to include new columns for 'Available' and 'Issues'. This can be used to ensure the system stores the information we want to track. Collect all current reports and decide what reports need to be generated from the new system. This may include some additional reports. List the reports in the Report Evaluation Document. The Business Evaluation User Guide gives more comprehensive information on these activities. In terms of a technical assessment, a workshop should be held to review what technical aspects need to be checked. A checklist is available below. Remember to look at implementation as well as operational issues. It is useful to have the vendor run through a dummy installation on your system, and try migrating data. Part of the technical assessment is also used to estimate the effort to set up the new system and convert data. An examination should take place of current data to understand where there might be data cleansing or data conversion problems. The Technical Evaluation User Guide gives more comprehensive information on these activities. |
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||