|
|
 |
| A real-life team scenario using TeamWork |
This article will cover a real-world usage scenario of a team of DBAs/Developers that are developing a Recipe Management application, while using TeamWork, the Market's leading Oracle development tool. We will look in on the process of making changes to the application (in particular, changes to the application’s database objects).
Our team consists of:
- Jim : A junior developer who is currently in charge of implementing a number of bugfixes
- Jane : A developer who is in charge of implementing some new features for the next release
- Mary : The deployment manager in charge of integrating all changes to database
- Mike : The team manager
When we pick up the action, Jim has just come in. One of the bugfixes Jim is working on (bug #21223) has to do with performance issues in the application. Jim has determined that he needs to add an index to the RECIPE_2_ING table. Jim logs into Oracle SQL Develper and tries to make the change:
He gets a message from TeamWork that the object is locked and that he needs to check-out the table before he can make the change. He checks-out the table, makes the change and checks-in the table while associating the change to the change-set for this bugfix (bug #21223).
Jane logs in to SQL Developer to make a change she needs to make in order to support some new features for the next version of the application. When she tries to make the change, she gets a message from TeamWork that the object is currently locked by Jim:
Jane calls Jim to make sure he checks-in the object and then she can go on to make her change:
After conferring with the rest of the team, Mary determines that it is time to integrate all the changes made by the team into the QA database. Mary uses the TeamWork Console to review which changes have been made to relevant objects:
Mary runs the TeamWork Deployment Manager and selects the changes she wants to move to the QA database:
The Deployment Manager calculates which changes need to be made and notifies Mary of any conflicts and changes that need to be resolved:
Mary uses the Deployment Manager dialogs to resolve any conflicts and indicate which changes should be migrated. Deployment Manager will then create scripts to implement the changes and allows Mary to save those scripts or execute them automatically:
Mike logs in to TeamWork in order to determine what progress his team is making. He can use the reports section of the Console to determine which objects have been changed, which change-sets the changes are associated with and who’s been making which changes:
Learn more about our solution – TeamWork
|