Use Case: Transitioning from DVD Rental to OTT using JIRA Integration

This case shows how business users and data modelers collaborate to update the data model during the transition from DVD rental to OTT streaming, using ER360 with JIRA integration.

1. Business User Raises a Request

   • A business user suggests adding a new entity called Subscription.

   • The request is added either in JIRA Ticket with a Tag - #MART-TRIGGER.

   • The Model is also associated with the JIRA Ticket.

2. Data Modeler Reviews the Request

   • The data modeler sees the request in JIRA and reviews the status in ER360.

   • They review the suggested changes.

3. Data Modeler Updates the Model

   • The data modeler opens the model in erwin Data Modeler.

   • The Subscription entity is added with relevant fields.

   • The updated model is saved to the Mart.

4. Model is Uploaded to ER360

   • The model is harvested to ER360 using a harvest job.

   • The catalog in ER360 is refreshed to reflect the updated model.

   • The Business user will also receive an email regarding the new entity added in the model.

5. Comments added in ER360

   • The data modeler adds comments in ER360.

   • The same comment is also updated in JIRA Ticket.

   • The business user adds a comment in JIRA Ticket “The New changes look good.”

6. Data Modeler adds certification.

   • The data modeler certifies the model in ER360.

   • Once certified, the linked JIRA ticket is automatically marked as “Done.”

7. Repeat for Future Requests

   • Any future changes (like adding Devices or Streaming History) follow the same steps.

   • Comments and tickets stay in sync between ER360 and JIRA.