Если у вас возникли сложности с курсовой, контрольной, дипломной, рефератом, отчетом по практике, научно-исследовательской и любой другой работой - мы готовы помочь.
Предоплата всего
Подписываем
The SC-BAT usability testing is designed to achieve the following goals:
Participants in the usability test should be chosen according to their persona, experience level, and knowledge of the Composite UI Application Block (CAB):
SC-BAT targets three primary personas, each of which will use the deliverable in different ways.
Note that each of these personas is assumed to be capable .NET developer, even though their experience levels differ. In this exercise all should be capable C# developers (a VB.NET version of SC-BAT is not yet available.)
In addition to choosing participants to fit the personas, we would also like to choose participants with varying experience with the CAB:
Note that here we are talking only about the participants’ experience with CAB – an ‘inexperienced’ CAB user should still be a capable .NET developer.
The table below show the suggested number of participants (the cells in the table), and the number of days that each will participate in the study (numbers in the first column):
|
CAB Experienced |
CAB Inexperienced |
|
|
Art (2 days) |
5 |
5 |
|
Bert (1 day) |
3 |
2 |
|
Mort (1 day) |
3 |
2 |
Total participants:
Participants will be asked to complete several scenarios using the most current build of SC-BAT. Since architects and developers are expected to use the SC-BAT in different ways, the two audiences will be given different scenarios to complete. Bert and Mort will be given the same scenarios – even though their roles are not identical.
The scenarios for both groups will be based on exercises developed for the SC-BAT Customer Lab, although they will be rewritten to reflect a real-world environment where BAT users = will be given requirement but no step-by-step instructions.
The developer audience will be given additional context to simulate the type of advice that they would likely receive from their project architect.
The detailed scenarios will be provided closer to the time of the usability study, but the exercises will include the following:
Architects
Each participant to complete all 3 tasks
Evaluation
Exercise: For a realistic customer requirements, ask the participant to analyze if SC-BAT would be a good choice for them (and why), and to map the requirements to the SC-BAT features and architecture. Timebox the activity to 4 hours.
Measures:
Time taken to arrive at recommendation
Confidence & accuracy of recommendation
Confidence & accuracy of requirements-feature map
Log of evaluation steps and a list of resources/artifacts used
Verbatim feedback on resources used (what made sense, what was confusing, what was missing, etc)
Analysis and Baselining
Exercise: Ask the participant to create an architecture/design for their system based on the SC-BAT artifacts. This should include description of the proposed solution in terms of the CAB/EntLib concepts and architecture patterns. Timebox activity to 8 hours
Measures:
Time taken to complete architecture description (or how far they got in the time allowed)
Level of confidence with generated architecture/design
List of resources used
Verbatim feedback on resources used (what made sense, what was confusing, what was missing, etc)
Technical challenges faced
BAT Customization
Exercise: Ask the participant to make a relatively small customization to the Guidance Package, and repackage the BAT so it’s ready to be used by a developer. Timebox activity to 4 hours.
Measures:
Time taken to complete baseline (or how far they got in the time allowed)
List of resources used
Verbatim feedback on resources used (what made sense, what was confusing, what was missing, etc)
Technical challenges faced
Developers
Each task to be performed by half of the developers (each including a mix of experienced and inexperienced CAB developers)
Development with SC-BAT
Exercise: Provide users with both requirements and a design document showing how the BAT architecture addresses the requirements (as may be expected to come from an architect). The developer is asked to start building an application using SC-BAT that addresses a specified subset of these requirements (this will include the architecture plus additional development to complete some of these use cases). Timebox activity to 8 hours.
Measures:
Time taken to complete application (or how far they got in the time allowed)
Level of confidence with application
List of resources used
Verbatim feedback on resources used (what made sense, what was confusing, what was missing, etc)
Technical challenges faced
Development with CAB (control group)
Exercise: As above, but solution is to be generated using CAB without the SC-BAT. Timebox activity to 8 hours.
Measures:
Time taken to complete application (or how far they got in the time allowed)
Level of confidence with application
List of resources used
Verbatim feedback on resources used (what made sense, what was confusing, what was missing, etc)
Technical challenges faced
Each scenario will be given a hard time limit. After completing each scenario each participant will be asked to fill out surveys including:
Each participant will also be asked to provide some background on themselves and their experience (once only). The exact surveys will be provided at a later stage.
The usability tests should be run as soon as possible, to maximize our ability to incorporate feedback into the v1 release. Realistically this should be by the end of April.