EDET 703 - Design and Development Tools II
This artifact was created during the Spring 2022 semester as the planning document for a short elearning course based on the 3Cs model of branching scenarios (Snegirev, 2021). At the time of this report’s writing, I intended to use a program called Twine to create all of my branching scenarios, but decided during development to change to Articulate.
This artifact was created primarily for EDET 703, but the subject matter allows for it to be adopted in a work context. I could use this course to train individuals I work with how to use the mapping software I use for my job. This treatment report was created fairly early in this program and demonstrates the initial stages of planning out a course. It includes the style guide and storyboard for the project as well as content information.
I was the instructional designer, developer, and SME for this project.
This treatment report is part of the Design phase of ADDIE (“Addie Model,” 2012). It prescribes the user interface, layout, navigation, and aesthetics of the course to be developed. The course is designed to follow the 3Cs model of branching scenarios which can be summed up as “challenge, choice, consequence” (Snegirev, 2021). This is a basic framework for branching logic in course assessments that increases interactivity, which can be particularly effective in individualized computer-based instruction (Morrison et al., 2019).
This artifact fulfills the requirements for AECT Standard #2 - Content Pedagogy (AECT, 2012). This artifact mainly falls into the assessing/evaluating and creating indicators. This report lays out the guidelines for the visual creation and framework of the course to be created, and uses the 3Cs model to assess student knowledge and increase participation.
This treatment report is one of the earliest reports I wrote of this type and is less detailed than the reports I would write later on in this program. This report was one of my introductions to writing prescriptive documents for a module, and focused mostly on platforming and aesthetic decisions rather than content sequencing or analysis. Several decisions about the direction of the course had not been made yet, as evident in this report’s mention of multiple software platforms and design choices. Although courses naturally develop and change over the course of the design and development process, starting with a more solidified idea would have helped streamline the development process.