2 resultados para small groups
em Digital Commons - Montana Tech
Resumo:
Many schools do not begin to introduce college students to software engineering until they have had at least one semester of programming. Since software engineering is a large, complex, and abstract subject it is difficult to construct active learning exercises that build on the students’ elementary knowledge of programming and still teach basic software engineering principles. It is also the case that beginning students typically know how to construct small programs, but they have little experience with the techniques necessary to produce reliable and long-term maintainable modules. I have addressed these two concerns by defining a local standard (Montana Tech Method (MTM) Software Development Standard for Small Modules Template) that step-by-step directs students toward the construction of highly reliable small modules using well known, best-practices software engineering techniques. “Small module” is here defined as a coherent development task that can be unit tested, and can be car ried out by a single (or a pair of) software engineer(s) in at most a few weeks. The standard describes the process to be used and also provides a template for the top-level documentation. The instructional module’s sequence of mini-lectures and exercises associated with the use of this (and other) local standards are used throughout the course, which perforce covers more abstract software engineering material using traditional reading and writing assignments. The sequence of mini-lectures and hands-on assignments (many of which are done in small groups) constitutes an instructional module that can be used in any similar software engineering course.
Resumo:
Signs are used extensively in workplaces and on products to identify hazards and provide instructions for appropriate behavior. A fundamental element of these signs is the signal-word panel located at the top of the sign. The colors and words in this panel are intended to convey information about the hazard identified. One type of hazard information concerns the severity of injury/illness associated with the hazard. The standard of the American National Standards Institute (ANSI) for facility signs uses three severity categories: 1) death or serious injury, 2) minor or moderate injury, and 3) property damage. The standard specifies which signal-word panel format, including color, to use based in part on the severity category. The purpose of this study was to determine if college students associate color with severity. The sample population consisted of 59 students tested in nine small groups. Twelve signs were shown to them in random order. Five of the signs had a color for the background of the signal-word panel. The colors were red, orange, yellow, blue, and gray. The signal word was a nonsense word and the text panel contained repetitions of the letter x in sentence format. Subject rated their impressions of the colors using two ordered rating scales for severity. Results indicated that color had a highly significant effect on severity ratings. Median ratings were generally consistent with the ANSI standard, except for orange. Red rated highest on both scales. Blue and gray rated lowest. Yellow and orange were in between red and blue. According to the ANSI standard, orange should indicate the same severity as red. These results indicated that orange was associated with less severity than red. Apparently, the ANSI standard's use of orange to identify a hazard associated with death or a serious injury is questionable.