1a. Input Use Case
ID and Name |
UC-01 Input Use Case |
Summary: |
This use case is about how a user request, containing Boolean guards selected, is sent to the Selector Engine. |
Priority: |
Essential |
Use Frequency: |
Often
|
Direct Actors: |
User Request |
Pre-requisites |
• Must have ArchStudio 3 • Must have Java 1.4 or later version |
Main Success Scenario: |
• The user request is sent to the system. • The user request already has a Boolean guard selected as a true state. • The user request is send to the Selector Engine. |
Alternative Scenario Extensions: |
• If the user request has a Boolean guard unselected, then the request containing the unselected Boolean guard is send to the Selector Engine. |
Notes and Questions |
|
1b. Input Use Case Diagram: 
2a. Ouput Use Case:
ID and Name |
UC-03 Output |
Summary: |
This use case is going to show the actions and events it takes to derive the final output from the repository. |
Priority: |
Essential |
Use Frequency: |
Frequently/Often |
Direct Actors: |
User Request |
Pre-requisites |
• The user requests has to be of True Value and should come from the repository. • Must have ArchStudio 3. |
Main Success Scenario: |
• True user requests come from the Selector engine to the Repository. • In the Repository, the components are searched till the correct architecture with the same component is found. • Once it finds the correct architecture components, it sends it to the output. |
Alternative Scenario Extensions: |
• If the Boolean guard is the false value then selector ignores it. |
Notes and Questions |
• The user requests have to be of True value and not false. |
2b. Ouput Use Case Diagram:
