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.
Corona Use Case Project Open
Revision as of 16:01, 23 June 2006 by Dennis.oflynn.compuware.com (Talk | contribs)
| Home | Wiki Home | Requirements |
Contents
Description
A new team member joins a Project. The development group is using eclipse, and the Project consists of a number of sub-projects (corresponding to Eclipse projects). The new member installs Eclipse, installs the Corona Client plugin, and configures it to talk to the workgroup's Corona server. The new member then selects the workgroup's Project from a list, and watches in amazement as Eclipse initializes the project settings and checks the appropriate sub-projects out of CVS.
Actors
- Team Member – A member of team that performs some action (create, update, delete) upon a project.
Assumptions
- The Eclipse Workbench has been enabled with Corona and ECF plug-ins
- The Workbench has a local projects ‘A’ defined
- Workbench project ‘A’ has a Project Collaboration Nature assigned to it.
- Workbench project ‘A’ belong to the Corona ProjectContainer context named ‘Acme’
Steps
The following illustration is referenced by this use case. Each box in the illustration is labled (A-L) and is referenced by each use case step that it is involved with.
- A team member open an Eclipse Workbench project
- The Eclipse Workbench publishes a IResourceChangeEvent notifying interested plug-ins that the project is being opened.
Variations
Non-Functional
Performance
- Performance is expected to meet a normal user experience.
Frequency
- A team member is expected to occasionally open a project.