Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Build to Manage use cases"
(→Use Case 1: Select code to instrument) |
|||
| Line 9: | Line 9: | ||
'''Pre-Conditions:''' | '''Pre-Conditions:''' | ||
| − | The developer knows the following information: | + | The developer knows the following information: What methods will be instrumented, what type of instrumentation to use |
| − | Short Description: | + | '''Short Description:''' |
| − | The developer | + | The developer uses a view in Eclipse to select which methods to instrument |
| + | |||
| + | '''Success Post-Condition:''' | ||
| + | The developer receives an indication that the code has been instrumented | ||
| + | |||
| + | '''Failure Post-Condition:''' | ||
| + | The developer receives no indication of success | ||
| + | |||
| + | '''Trigger''' | ||
| + | The developer selects the code to be instrumented | ||
| + | |||
| + | BASIC FLOW | ||
| + | 1. Developer selects class/object to instrument | ||
| + | 2. Developer selects valid options | ||
| + | 3. Developer selects the type of instrumentation, eg ARM/JMX/CBE | ||
| + | 4. System displays instrumentation wizard | ||
| + | 5. Developer selects methods to instrument | ||
| + | 6. Developer selects finish from wizard | ||
| + | 7. System updates instrument list | ||
| + | 8. System makes changes to instrumentation repository | ||
| + | 9. System saves changes | ||
| + | 10. Instrumentation wizard disappears | ||
| + | |||
| + | ALTERNATIVE FLOWS | ||
| + | 1. Developer selects class/object to instrument | ||
| + | 2. Invalid type select | ||
| + | 3. System displays no options | ||
| + | |||
| + | VARIATIONS | ||
| + | 1. Developer selects method from editor view | ||
| + | 2. Developer selects the type of instrumentation, eg ARM/JMX/CBE | ||
| + | 3. System updates instrument list | ||
| + | 4. System makes changes to instrumentation repository | ||
| + | 5. System saves changes | ||
Revision as of 15:51, 25 October 2006
Use Case 1: Select code to instrument
Actor: Software Developer
System: Eclipse
Pre-Conditions: The developer knows the following information: What methods will be instrumented, what type of instrumentation to use
Short Description: The developer uses a view in Eclipse to select which methods to instrument
Success Post-Condition: The developer receives an indication that the code has been instrumented
Failure Post-Condition: The developer receives no indication of success
Trigger The developer selects the code to be instrumented
BASIC FLOW 1. Developer selects class/object to instrument 2. Developer selects valid options 3. Developer selects the type of instrumentation, eg ARM/JMX/CBE 4. System displays instrumentation wizard 5. Developer selects methods to instrument 6. Developer selects finish from wizard 7. System updates instrument list 8. System makes changes to instrumentation repository 9. System saves changes 10. Instrumentation wizard disappears
ALTERNATIVE FLOWS 1. Developer selects class/object to instrument 2. Invalid type select 3. System displays no options
VARIATIONS 1. Developer selects method from editor view 2. Developer selects the type of instrumentation, eg ARM/JMX/CBE 3. System updates instrument list 4. System makes changes to instrumentation repository 5. System saves changes