Magazine Search
3 results found
Issues
Issues
All (54)
Fall 2006 (1)
Fall 2007 (1)
Fall 2008 (1)
Fall 2009 (1)
Fall 2010 (1)
Fall 2011 (1)
Fall 2012 (1)
Fall 2013 (1)
Fall 2014 (1)
Fall 2015 (1)
Fall 2016 (1)
Fall 2017 (2)
Fall 2018 (1)
Fall 2019 (1)
Fall 2020 (1)
Fall 2021 (1)
Fall 2022 (1)
Fall 2023 (1)
Summer 2006 (1)
Summer 2007 (2)
Summer 2009 (1)
Summer 2010 (1)
Summer 2011 (1)
Summer 2012 (1)
Summer 2013 (1)
Summer 2014 (1)
Summer 2015 (1)
Summer 2016 (1)
Summer 2018 (1)
Summer 2019 (1)
Summer 2020 (1)
Summer 2021 (1)
Summer 2022 (1)
Summer 2023 (1)
Winter 2003 (1)
Winter 2007 (1)
Winter 2009 (1)
Winter 2010 (1)
Winter 2011 (1)
Winter 2012 (1)
Winter 2013 (1)
Winter 2014 (1)
Winter 2015 (1)
Winter 2016 (1)
Winter 2018 (1)
Winter 2019 (1)
Winter 2020 (1)
Winter 2021 (1)
Winter 2022 (1)
Winter 2023 (1)
Winter 2024 (1)
Imagine hacking into a Furby, picking a lockbox, shooting targets with Nerf guns, diving into piles of (clean) trash, and sliding under string “laser beams,” all with the end goal of identifying—and then fixing—vulnerabilities in a wireless computer security system.
Signs mark the entrance: Production Area, Authorized Personnel Only. Inside, observers stand behind a line of caution tape, taking notes intently. In front of them a rumbling machine shuffles orange, green, and yellow balls along conveyor belts, through tubes, and down ramps.
An average person attending a lecture about “model-driven system development” would likely be lost and confused within minutes. Likewise, as Stephen Liddle has attempted to teach this concept in his ISys 532 class, he is often met with blank stares.