eLandings Development Process Jira Tool to Record, Track and Resolve Issues, Bugs, Defects, Improvements and New Feature Requests April 2010 The Development Process

Development Roles Program Management Board Developers You

Development and You The Process The 10 Step Program to ‘Done’ Jira Demonstration

The Process Identification Houston, we have a problem Your view of the issue What, When/How, Where Provide Examples Landing Report or Fish Ticket Number What it’s supposed to look like New Business Rules?

The Process Documentation - Jira Because we’ve got issues JIRA lets us prioritize, assign, track, report and test our 'issues,' whatever they may be — from software bugs and hardware defects, to improvement and change requests. Because we need to track issues Reporting allows us to prioritize and monitor the progress of our issues.

The Process Workflow of an Issue Workflow capabilities in Jira allow us to map an issue's lifecycle to match our processes.

JIRA – Open Reporting the Issue Does it exist? Searching Open an Issue Summary Description Description Attach documents, screen shots

JIRA – Open Initial Scoping Repeat the issue Gather additional information Initial Business Impact Analysis Business Rules i.e. calculateAllocationPercents Business Rules

JIRA – Open Prioritize Program Management Board Assignments Coding changes Regulatory changes Documentation Changes Impact to other systems and assign staff

JIRA - In Progress Assigned Staff Start Work Scope the Issue Code to change Impact to other code Impact to interfaces Do the work Change the Code or write new Write tests Verify results with reporter

Ready to Test Deploy to TEST Reporter and Developer Test Large impact items may require additional testing efforts in other interfaces Can we Close? Testing passed? JIRA – Resolved

JIRA – Closed Ready to Deploy Close the Issue Reporter should close Schedule Deployment Prepare deployment Notification Deploy to Production Follow up Data revisions

JIRA – Reopen Opps Searched and found! Same issue, different untested conditions

Example Issues IERS-1091 – Task with linked issuesIERS-1091 IERS-1157 – ImprovementIERS-1157 IERS-640 – Reopened with Sub-TaskIERS-640

JIRA – Demo Logging in: Which Project? Searching for an Issue Notifications Watching an Issue Add Comments to an Issue

Agency Interaction With the eLandings Repository April 2010 Agency Interaction

Data Flow – Agencies IPHC NMFS – SF Groundfish Catch Accounting System NMFS – RAM IFQ Halibut/Sablefish IFQ Crab CFEC DOR via ITO ADF&G FTDB

ADF&G - Land2Fish Transforms data from eLandings into the Fish Ticket database. Converts ‘Landing Report’ to ‘Fish Ticket(s)’ Simple! Right? L2F Integration with eLandings Development uses the same Jira process Deployment usually with eLandings cycle

ADF&G - Land2Fish Assemble it

ADF&G - Land2Fish The Landing Report

ADF&G - Land2Fish The Transformation

ADF&G - Land2Fish - Effort Effort Calculation State the Business Rule Examples from You Test the Business Rules with Examples Create tests

ADF&G - Land2Fish - Effort Eligibility for Effort Determine the itemized catch lines for crab which are eligible to receive effort when extracted to the fish ticket database. This pertains to the statistical area worksheet only. If there is effort on the line item already, it takes precedence over any/all rules. If all items are dead-loss (79), then all items are eligible to receive effort. Else if sold items (60) exist then sold items (60) are eligible to receive effort. Else if overage items (62) and/or confiscated items (63) exist, then either/both items are eligible to receive effort. Else if personal use (95) items exist then personal use (95) items are eligible to receive effort. Distribution of Effort After determining which line items are eligible for effort (see above), distribute the effort (pot lifts) indicated in the statistical area worksheet. For each line item stat area, IF it's an eligible item: 1. Determine the total weight on the Landing for that species and disposition code (A) 2. Determine the total weight on the Fish Ticket for that species and disposition code (B) 3. Calculate the percentage: (A / B) * 100 (C) 4. Get the effort for that stat area from the worksheet (D) 5. Calculate and return that item's effort: (C * D) / 100

ADF&G - Land2Fish - Effort Program it! Assemble the Landing Report object Determine ‘effort eligible items’ Are all items deadloss? Does any sold items exist? Does personal use exist? Does overage or confiscated exist? Get the stat area worksheet, grab the effort values and calculate for each stat area worksheet item Total LR Pounds for Species Disposition this Stat Area Total Fish Ticket Pounds for Species Disposition this Stat Area Iterate through all ‘line items’ to build a collection of ‘line item stat area’ objects

ADF&G - Land2Fish - Effort Set the lineItemStatArea's effort to result of the calculated effort. To calculate effort: Get the stat area effort from the worksheet Get the total weight of all items eligible to receive effort on the landing report for each species, and dispo, split up by stat area.(totalLRWeight) Get the total weight of all items eligible to receive effort on the landing report for each ticket, species and dispo, split up by stat area(totalFTWeight) For each effort eligible item Create a key variable for each species + disposition code (LRKey) 1. Determine the total weight on the Landing for that species and disposition code (A) 2. Determine the total weight on the Fish Ticket for that species and disposition code (B) 3. Calculate the percentage: (A / B) * 100 (C) 4. Get the effort for that stat area from the worksheet (D) 5. Calculate and return that item's effort: (C * D) / 100

Data Flow – Beyond Agencies North Pacific Fishery Management Council NMFS ADF&G AKFIN IPHC CFEC

Data Flow ~ ADFG to CFEC ADF&G Fish Ticket Database Tables and Fields - Source Data for CFEC Gross EarningsCorresponding CFEC Fields GROUNDFISH BATCH TABLE FIELDS SHELLFISH BATCH TABLE FIELDS SALMON BATCH TABLE FIELDS HERRING BATCH TABLE FIELDSGROSS EARNINGS FIELDS BATCH_NUMBER ADFG_B_BATCH_NUMBER BATCH_YEAR ADFG_B_BATCH_YEAR COMMENTS DATE_CREATED_VERIFIED ADFG_B_DATE_CREATED_VERIFIED DATE_KEYED ADFG_B_DATE_KEYED DATE_PUBLISHED OFFICE_CODE ADFG_B_OFFICE_CODE PROOF_DONE ADFG_B_PROOF_DONE PUBLISHED TICKET_END ADFG_B_TICKET_END TICKET_START ADFG_B_TICKET_START USER_ID ADFG_B_USER_ID GROUNDFISH HEADER TABLE FIELDSSHELLFISH HEADER TABLE FIELDSSALMON HEADER TABLE FIELDSHERRING HEADER TABLE FIELDS ADFG_NUMBER ADFG_H_ADFG_NUMBER BATCH_NUMBER BATCH_YEAR CDQ_CODE ADFG_H_CDQ_CODE CREW_SIZE ADFG_H_CREW_SIZE CUSTOM_PROCESSOR ADFG_H_CUSTOM_PROCESSOR DATE_FISHING_BEGAN ADFG_H_DATE_FISHING_BEGAN DATE_FISHING_ENDEDADFG_H_DATE_FISHING_ENDED DATE_LANDED ADFG_H_DATE_LANDED DAYS_FISHED ADFG_H_DAYS_FISHED DEWATEREDADFG_H_DEWATERED FROZEN_AT_SEA GEAR_CODE ADFG_H_GEAR_CODE INITIAL_PROCESSORADFG_H_INITIAL_PROCESSOR INITIAL_TICKET_NUMBERADFG_H_INITIAL_TICKET_NUMBER INTERVIEWED ADFG_H_INTERVIEWED LANDING_REPORT_NUMBER ADFG_H_LANDING_REPORT_NUMBER LAST_USER_ID ADFG_H_LAST_USER_ID

Data Flow ~ ADFG and Beyond ADFG CFEC at the end of calendar year COAR/GROSS EARNINGS REPORTS Public reports, AMR’s, Board of Fish reports AKFIN summarized data to PACFIN NPFMC unsummarized and summarized