Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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) |
(→Use Case 1: Select code to instrument) |
||
| Line 12: | Line 12: | ||
'''Short Description:''' | '''Short Description:''' | ||
| − | The developer uses a view in Eclipse to select which methods to instrument | + | The developer uses a view in Eclipse to select which methods to instrument for one type of instrumentation |
'''Success Post-Condition:''' | '''Success Post-Condition:''' | ||
| Line 45: | Line 45: | ||
10. Instrumentation wizard disappears | 10. Instrumentation wizard disappears | ||
| − | ALTERNATIVE | + | ALTERNATIVE FLOW |
1. Developer selects class/object to instrument | 1. Developer selects class/object to instrument | ||
| Line 53: | Line 53: | ||
3. System displays no options | 3. System displays no options | ||
| − | + | ALTERNATIVE FLOW | |
1. Developer selects method from editor view | 1. Developer selects method from editor view | ||
| Line 64: | Line 64: | ||
5. System saves changes | 5. System saves changes | ||
| + | |||
| + | == Use Case 2: Select option for instrumentation == | ||
| + | |||
| + | '''Actor:''' | ||
| + | Software Developer | ||
| + | |||
| + | '''System:''' | ||
| + | Eclipse | ||
| + | |||
| + | '''Pre-Conditions:''' | ||
| + | The developer knows what mechanism to use for instrumentation | ||
| + | |||
| + | '''Short Description:''' | ||
| + | The developer changes an option to select what mechanism to use for instrumentation | ||
| + | |||
| + | '''Success Post-Condition:''' | ||
| + | The option view disappears and the selection is saved | ||
| + | |||
| + | '''Failure Post-Condition:''' | ||
| + | The developer receives an indication that the selection cannot be saved | ||
| + | |||
| + | '''Trigger:''' | ||
| + | The developer changes the mechanism to use for instrumentation | ||
| + | |||
| + | BASIC FLOW | ||
| + | |||
| + | 1. Developer selects the BtM options view | ||
| + | |||
| + | 2. Developer selects a mechanism for instrumentation, eg AspectJ, TPTP Probekit, or source editing | ||
| + | |||
| + | 3. Developer pushes the OK button | ||
| + | |||
| + | 4. System saves settings | ||
| + | |||
| + | 5. BtM options view is no longer visible | ||
| + | |||
| + | ALTERNATIVE FLOW | ||
| + | |||
| + | 1. Developer selects the BtM options view | ||
| + | |||
| + | 2. Developer selects a mechanism for instrumentation, eg AspectJ, TPTP Probekit, or source editing | ||
| + | |||
| + | 3. Developer pushes the Cancel button | ||
| + | |||
| + | 4. System does not save settings | ||
| + | |||
| + | 5. BtM options view is no longer visible | ||
| + | |||
| + | ALTERNATIVE FLOW | ||
| + | |||
| + | 1. Developer selects the BtM options view | ||
| + | |||
| + | 2. Developer selects a mechanism for instrumentation, eg AspectJ, TPTP Probekit, or source editing | ||
| + | |||
| + | 3. Developer pushes the Apply button | ||
| + | |||
| + | 4. System saves settings | ||
| + | |||
| + | 5. BtM options view remains visible | ||
Revision as of 16:17, 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 for one type of instrumentation
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 FLOW
1. Developer selects class/object to instrument
2. Invalid type select
3. System displays no options
ALTERNATIVE FLOW
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
Use Case 2: Select option for instrumentation
Actor: Software Developer
System: Eclipse
Pre-Conditions: The developer knows what mechanism to use for instrumentation
Short Description: The developer changes an option to select what mechanism to use for instrumentation
Success Post-Condition: The option view disappears and the selection is saved
Failure Post-Condition: The developer receives an indication that the selection cannot be saved
Trigger: The developer changes the mechanism to use for instrumentation
BASIC FLOW
1. Developer selects the BtM options view
2. Developer selects a mechanism for instrumentation, eg AspectJ, TPTP Probekit, or source editing
3. Developer pushes the OK button
4. System saves settings
5. BtM options view is no longer visible
ALTERNATIVE FLOW
1. Developer selects the BtM options view
2. Developer selects a mechanism for instrumentation, eg AspectJ, TPTP Probekit, or source editing
3. Developer pushes the Cancel button
4. System does not save settings
5. BtM options view is no longer visible
ALTERNATIVE FLOW
1. Developer selects the BtM options view
2. Developer selects a mechanism for instrumentation, eg AspectJ, TPTP Probekit, or source editing
3. Developer pushes the Apply button
4. System saves settings
5. BtM options view remains visible