I am writing an action plan for a personal software project, which I will do research on before and during development. I think the name "action plan" does a decent job describing what it is used for. The research report that will be written after the action plan, will be finished at the same time the application is done. UML diagrams are part of the research, but what about requirements? Is knowing the requirements part of the plan or do you need to have done some decent research before knowing what they are?
Here are headings of my action plan so far, excluding general purpose report headings such as 'Introduction' and the like, to give some context of what, I think, is supposed to be in the plan:
- Problem analysis
- Goal (research question)
- Research method
- Stakeholders (me)
- Strategy (version control, tools, testing, etc)
- Risk analysis (time, costs, etc)
I guess the 'Requirements' heading would be inbetween the headings 'Strategy' and 'Risk analysis', but I am not sure if they should be in the report at all.