EDIT: The project is about creating an algorithm for Procedural Content Generation for a videogame. The actual game is secondary to the algorithm. It must be something basic to test the Procedural Content Generation. I'm approaching this as a single developer.
Thanks to @ThomasOwens I realize this question is more about how to work combining CRISP (the datamining process model that will help me create the algorithm) with a project management methodology (preferably something agile such as XP).
I'm working on a school project involving an interactive genetic algorithm where the program must create some content in real time based on the user's preferences. Near the end of the project, in order to validate the algorithm and creating the necessary reports, it must be tested by actual users.
My tutor wants me to use CRISP-DM as the methodology for the project, and I'm wondering in which phase will the user tests go. Please don't advice me to change methodology. And also, my tutor isn't available this week, but I want to make some advances in the planning.
So my question is: Regarding the CRISP-DM process model, which phase and tasks relate to User Acceptance Testing?
You can skip the following paragraphs if you have the answer. I'll just try to explain my confusion a little better. The main problem here is my lack of knowledge on CRISP-DM and there's a liiiitle bit of a language barrier. To my udertanding the User Testing would be on the Evaluation phase, but I just want to be 100% sure, so I'm seeking expert advice.
Yes, my project doesn't involve reading data from a database, but it's a data mining problem because my algorithm will have to extract information from some data and analyze it and transform it into something else. This is how I've related the CRISP phases to my project so far:
- Business Understanding will be all about defining a problem that would benefit on the user for finding it's solutions.
- Data Understanding and Data Preparation will be merged on a single phase that involves figuring out how the data will be treated.
- Now, on the Modeling phase, there's the Generate test design task, and this test is performed on the Assess model model task. But this tests don't involve User Acceptance Testing, only Unit Testing or Functionality Testing. I'm right here, right?
- That leaves me with the Evaluation phase, in which it's task Evaluate results says:
This step assesses the degree to which the model meets the business objectives, and seeks to determine if there is some business reason why this model is deficient. Another option is to test the model(s) on test applications in the real application, if time and budget constraints permit.
Is this where it goes? Should I adapt this task to my User Tests? Or would it be better to add another task before this one that specifically refers to executing the user tests?