Workflows, scenarios and use cases

Other than catching up after the computer crash I have been working on the prototype design, which will be released next week. Just have a few more code tests to do to make some of the more intricate bits are going to work. Focused on a client-side applications to start with which should transfer to web services with a minimal of code generation. The client-side applications will make mass user testing easier, theoretically less technology to go wrong.

 

I have also been doing some more use case diagrams from the workflows and scenarios various project members have written. So far I have diagrammed Meg’s podcasting workflow which is nice and straightforward and the use case model was built fairly quickly. Its interesting to see how it compares to the more specific scenarios/models developed back in September. They are focused on different user groups and specific software. The new one is more general that takes into account all the stages that need to be considered to complete any type of podcast (I have used wordpress’s AnswersLinks here let me know if you think this is a good idea?). I have numbered each so it can be related back to the original workflow and you can see where I have made changes to the logical flow. However order is not necessary a consideration in this type of development, except where there are obvious prerequisites.

 

Stuart’s scenario encompassed both organisational concerns as well as podcast LO development scenario. This also depicts a specific means of presenting podcast material via a student discussion. I have dived this into two diagrams. The first use case presenting the organisation considerations that need to be taken into account when moving a team into the realms of podcasting as a means of teaching. The second use case depicts the podcasting process and considerations for presenting a student discussion.

 

I think the organisational concerns are an interesting issue and could be worked into some form of formal guidelines. The Web2Rights workshop on Monday will add the legal aspects and I will focus my questions around podcasting and repository issues.  I have one more set of use cases to produce, based on the repository workflows from Jill. Once this is complete it might be a good idea to compare all the workflows/scenarios concerning LOs and podcasting. As well as the repository workflows against the repository report to identify issues for further exploration.

 

Use case Diagrams of Podcasting and Learning Object Production

Having analysed the data from the podcasting scenarios we have developed initial use case diagrams capturing the processes described by the users. A high-level diagram was developed identifying the overall process and decisions a user is required to consider. Some of the process are specific to our editing application iMovie, but can be applied to other editing processes.

From this, specific scenarios were modelled to show the changes required, for the user, in the decision process:

• How a podcast can be used to deliver material in preparation for a tutorial.
• Recording a lecture for student reference
• Creating persistent materials for instruction and advice, with student input

A second set of scenarios were developed by an eCat tutor. These were more closely focused on the production of learning objects by lecturers and other staff. A high-level diagram was produced showing the processes and decisions of producing a learning object using the eCat system. We then used the scenarios above to examine the differences in requirements between an experienced lecturer and a lecturer at the start of their teaching profession.