| dbo:abstract
|
- RITE Method, for Rapid Iterative Testing and Evaluation, typically referred to as "RITE" testing, is an iterative usability method. It was defined by Michael Medlock, Dennis Wixon, Bill Fulton, Mark Terrano and Ramon Romero. It has been publicly championed by Dennis Wixon while working in the games space for Microsoft. It has many similarities to "traditional" or "discount" usability testing. The tester and team must define a target population for testing, schedule participants to come into the lab, decide on how the users' behaviors will be measured, construct a test script and have participants engage in a verbal protocol (e.g. think aloud). However it differs from these methods in that it advocates that changes to the user interface are made as soon as a problem is identified and a solution is clear. Sometimes this can occur after observing as few as one participant. Once the data for a participant has been collected the usability engineer and team decide if they will be making any changes to the prototype prior to the next participant. The changed interface is then tested with the remaining users. The philosophy behind the RITE method is described as: "1) once you find a problem, solve it as soon as you can, and 2) make the decision makers part of the research team." In this way it is a bridge between a strict research method and a design method...and in many ways it represents a participatory design method. "As Researchers you get a lot of fundamental training on what constitutes actionable proof. That fundamental training focuses on 'completing your research' before drawing conclusions. In publishing RITE we wanted Researchers to acknowledge that in the correct circumstances you can make strong and accurate conclusions and 'complete research' quite quickly. Perhaps more importantly, the standard literature (of the time) on usability testing was indexed on accurate identification of problem areas. The key word in the RITE acronym is Iterative. Through iteration you can prove that something is fixed, which we felt was a more important way to think about research findings. Find a thing. That's nice. Find and fix it. Far better." — Ramon Romero Initially it was documented as being used in the PC games business, but in all truth it has probably been in use "unofficially" since designers started prototyping products and watching users use the prototypes. Since its official definition and naming its use has rapidly expanded to many other software industries. (en)
- RITE 기법은 Rapid Iterative Testing and Evaluation의 앞글자를 딴 것으로 빠르게 연속적으로 테스트와 평가를 수행하여 개발하는 기법을 말한다. 주로 (User Test)를 위한 기법으로 쓰인다. 이 기법은 마이크로소프트사의 마이클 메들락에 의해 처음으로 효과적인 사용자 평가 기법으로 정립되어 쓰이기 시작했다. 각 테스트 참여자가 분석이 바로 되거나 하루의 테스트 일정이 소화된 후 바로 분석이 시작되며 어떤 문제점이 발견되거나 해결방법에 제시되면 바로 적용하고 이를 다시 다음 테스트 일정에서 테스트를 실시하고 다시 평가하는 과정을 나머지 테스트 기간 동안 반복한다. 컴퓨터 게임업계에서 특히 많이 애용되는 개발 방법이었으며 현재는 많은 소프트웨어 개발 프로젝트 과정에서 사용되고 있다. (ko)
|
| dbo:wikiPageID
| |
| dbo:wikiPageLength
|
- 4687 (xsd:nonNegativeInteger)
|
| dbo:wikiPageRevisionID
| |
| dbo:wikiPageWikiLink
| |
| dbp:wikiPageUsesTemplate
| |
| dcterms:subject
| |
| gold:hypernym
| |
| rdf:type
| |
| rdfs:comment
|
- RITE 기법은 Rapid Iterative Testing and Evaluation의 앞글자를 딴 것으로 빠르게 연속적으로 테스트와 평가를 수행하여 개발하는 기법을 말한다. 주로 (User Test)를 위한 기법으로 쓰인다. 이 기법은 마이크로소프트사의 마이클 메들락에 의해 처음으로 효과적인 사용자 평가 기법으로 정립되어 쓰이기 시작했다. 각 테스트 참여자가 분석이 바로 되거나 하루의 테스트 일정이 소화된 후 바로 분석이 시작되며 어떤 문제점이 발견되거나 해결방법에 제시되면 바로 적용하고 이를 다시 다음 테스트 일정에서 테스트를 실시하고 다시 평가하는 과정을 나머지 테스트 기간 동안 반복한다. 컴퓨터 게임업계에서 특히 많이 애용되는 개발 방법이었으며 현재는 많은 소프트웨어 개발 프로젝트 과정에서 사용되고 있다. (ko)
- RITE Method, for Rapid Iterative Testing and Evaluation, typically referred to as "RITE" testing, is an iterative usability method. It was defined by Michael Medlock, Dennis Wixon, Bill Fulton, Mark Terrano and Ramon Romero. It has been publicly championed by Dennis Wixon while working in the games space for Microsoft. It has many similarities to "traditional" or "discount" usability testing. The tester and team must define a target population for testing, schedule participants to come into the lab, decide on how the users' behaviors will be measured, construct a test script and have participants engage in a verbal protocol (e.g. think aloud). However it differs from these methods in that it advocates that changes to the user interface are made as soon as a problem is identified and a solu (en)
|
| rdfs:label
|
- RITE 기법 (ko)
- RITE Method (en)
|
| owl:sameAs
| |
| prov:wasDerivedFrom
| |
| foaf:isPrimaryTopicOf
| |
| is dbo:wikiPageDisambiguates
of | |
| is dbo:wikiPageRedirects
of | |
| is dbo:wikiPageWikiLink
of | |
| is foaf:primaryTopic
of | |
