Development Process for New Requests and Customizations

Workflow

This is a high level illustration of the development process for new requests and customizations.

Click to Enlarge.

Workflow Details

  1. Request Opened
    Change request ticket created by Functional User using JIRA. Business Requirements Document (BRD) is attached if needed.
  2. Request Assigned
    JIRA ticket is assigned to the BI Manager.
  3. Systems Analyst BRD Review
    Systems Analyst (SA) reviews BRD.
    BRD Archived.
  4. User BRD Review
    Systems Analyst may consult with Functional User for clarification.
  5. Functional Specification
    Functional Requirements Document created by Systems Analyst.
    Functional Requirements Document archived.
    Functional Requirements Documents attached to JIRA.
    1. Peer Review
      Functional Requirements Document reviewed by BI Team.
    2. Peer Review
      Functional Requirements Document reviewed by Functional User.
  6. Technical Specification
    Technical Specification Document created by ETL Developer.
    Technical Specification Document created by OBIEE Developer.
    ETL Technical Specification archived.
    OBIEE Technical Specification archived.
    Technical Specification Documents attached to JIRA.
  7. Technical Specification Review
    Technical Specification Document reviewed by BI Manager.
  8. Development
    Development work begins.
  9. Unit Test
    Unit Test by Developer.
    New code archived.
  10. Peer Review
    New code reviewed by fellow Developer and Systems Analyst.
    Old code in Test archived before migration.
  11. Migration Request
    BI Manager requests or approves migration to Test. If needed, STAT ticket created referencing JIRA ticket.
    JIRA ticket will reference STAT.
  12. Migration to Test
    UTD Developer migrates changes to Test.
  13. OR

  14. Migrate to Test
    ARDC migrates changes to Test.
  15. Systems Analyst Review
    Systems Analyst reviews changes before UAT.
  16. UAT
    User Acceptance Testing beings.
    1. UAT Successful
      User Acceptance Testing successful.
    2. OR

    3. UAT Unsuccessful
      Systems Analyst reviews unsuccessful User Acceptance Test.
      Changes sent back to UAT or Development based on Analysis.
  17. Migration Request
    BI Manager requests or approves migration to Production.
  18. Migrate to Production
    UTD Developer migrates changes to Production.
  19. OR

  20. Migrate to Production
    ARDC migrates changes to Production. STAT closed.
  21. Request Closed
    JIRA closed by BI Manager.

Glossary


Red line represents an unsuccessful procedure.

BRD
Business Requirements Document.

Dev
Development.

Functional Spec
Functional Specification or Functional Requirements Document.

Prod
Production.

Technical Spec
Technical Specification Document.

UAT
User Acceptance Test.