Using a Brick to analyze various specific areas of technology is a great way to stay organized and up to date with the software programs and applications available. This initial research could really help in school and classroom planning and practice by collecting past, current, and future states of the type of technology tools required. It will also provide documentation of ideas that could be pitched to the proper committees to allow its use since it is especially important to have full support in implementing new classroom resources.
Furthermore, in constructing the Brick, additional information will come forward that the [potential] user may not have been aware of or may have overlooked. As well, knowing what the program offers, with which specific device models and their operating systems, will determine how long it could be used for teaching. It's preferable to have resources that will be long lived and could be used over again for at least a couple years. This will help plan future lessons and in preparation for the following year[s]. Programs or applications that are already outdated and no longer supported by its own company would waste valuable class time. The worst thing to do, is to teach students something they can't use beyond the classroom.
As a teacher I would like to utilize the most recent and affective tools for my students that could enhance lessons and personalize learning. Limited to existing resources as well, I would need the appropriate information to be able to properly analyze the best options. The Brick is in a template form that could be updated regularly and shared amongst colleagues. It will further help track my own practice and improvement by understanding the state of these tools and in ensuring that I could effectively use the tool before introducing it to students.
Reference:
Berk, Rupert. (2016, January). EA Bricks Reference (Enterprise Architecture). University of Washington: Wikipedia. Retrieved from https://wiki.cac.washington.edu/display/EA/EA+Bricks+Reference
Furthermore, in constructing the Brick, additional information will come forward that the [potential] user may not have been aware of or may have overlooked. As well, knowing what the program offers, with which specific device models and their operating systems, will determine how long it could be used for teaching. It's preferable to have resources that will be long lived and could be used over again for at least a couple years. This will help plan future lessons and in preparation for the following year[s]. Programs or applications that are already outdated and no longer supported by its own company would waste valuable class time. The worst thing to do, is to teach students something they can't use beyond the classroom.
As a teacher I would like to utilize the most recent and affective tools for my students that could enhance lessons and personalize learning. Limited to existing resources as well, I would need the appropriate information to be able to properly analyze the best options. The Brick is in a template form that could be updated regularly and shared amongst colleagues. It will further help track my own practice and improvement by understanding the state of these tools and in ensuring that I could effectively use the tool before introducing it to students.
Reference:
Berk, Rupert. (2016, January). EA Bricks Reference (Enterprise Architecture). University of Washington: Wikipedia. Retrieved from https://wiki.cac.washington.edu/display/EA/EA+Bricks+Reference