SoDaR without programming
The goal of modifying SoDaR methodology was to allow me to develop a method where programming was not required to develop software for an educational purpose. This was especially difficult as I had difficulty in locating an existing or traditional methodology that would allow me to do this.
Best practice is achieved as all the steps that needed to be undertaken in the research phase of this project needed to be documented. Documenting this process allows for others to follow how I have done the research for this project. This saves others research time and helps to create a well laid out strategic plan for managing your research.
To achieve these goals I have modified the SoDaR methodology. Modifying the SoDaR methodology has allowed me to me design the ePortfolio systems as a prototype that could be developed in iterations. Qualitative user data would be gathered from the one-on-one interviews and group focus group sessions. The elements of interaction and design evaluated would include, look and feel, ease of use, request for new functions, and feedback and evaluation. Each case study would include a narrative discussion of what was learned from the qualitative data gathered from each iteration. A case study would be developed that would be used to create functional specification document. Ideally the iterations were meant to occur three times (Brown, 2007).