elandings development process jira tool to record, track and resolve issues, bugs, defects,...
Post on 11-Jan-2016
225 Views
Preview:
TRANSCRIPT
eLandings Development ProcessJira Tool to Record, Track and Resolve Issues, Bugs, Defects, Improvements and New Feature Requests
April 2010
The Development Process
Development Roles
Program Management BoardDevelopersYou
Development and You
The ProcessThe 10 Step Program to ‘Done’
Jira Demonstration
The Process
IdentificationHouston, we have a problemYour view of the issue
What, When/How, WhereProvide Examples
Landing Report or Fish Ticket NumberWhat it’s supposed to look likeNew Business Rules?
The Process
Documentation - JiraBecause 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 issuesReporting allows us to prioritize and monitor the
progress of our issues.
The Process
Workflow of an IssueWorkflow capabilities in Jira allow us to map
an issue's lifecycle to match our processes.
JIRA – Open
Reporting the IssueDoes it exist?
SearchingOpen an Issue
https://kiwi.state.ak.us/jiraSummary DescriptionDescriptionAttach documents, screen shots
JIRA – Open
Initial ScopingRepeat the issueGather additional information Initial Business Impact Analysis
Business Rules i.e. calculateAllocationPercents
JIRA – Open
PrioritizeProgram Management BoardAssignments
Coding changesRegulatory changesDocumentation Changes Impact to other systems and assign staff
JIRA - In Progress
Assigned Staff Start WorkScope the Issue
Code to change Impact to other code Impact to interfaces
Do the workChange the Code or write newWrite testsVerify results with reporter
Ready to TestDeploy to TEST
Reporter and Developer TestLarge impact items may require additional
testing efforts in other interfacesCan we Close?
Testing passed?
JIRA – Resolved
JIRA – Closed
Ready to DeployClose the Issue
Reporter should closeSchedule Deployment
Prepare deploymentNotificationDeploy to Production
Follow upData revisions
JIRA – Reopen
OppsSearched and found!Same issue, different untested conditions
Example Issues
• IERS-1091 – Task with linked issues• IERS-1157 – Improvement• IERS-640 – Reopened with Sub-Task
JIRA – Demo
Logging in: http://elandingstest.alaska.gov/ https://kiwi.state.ak.us/jira/browse/IERS
Which Project?Searching for an IssueNotificationsWatching an IssueAdd Comments to an Issue
Agency InteractionWith the eLandings Repository
April 2010
Agency Interaction
Data Flow – Agencies
IPHC
NMFS – SFGroundfish Catch
Accounting System
NMFS – RAMIFQ Halibut/Sablefish
IFQ Crab
CFEC
DOR via ITO
ADF&GFTDB
ADF&G - Land2Fish
Transforms data from eLandings into the Fish Ticket database.Converts ‘Landing Report’ to ‘Fish Ticket(s)’
Simple! Right?L2F Integration with eLandingsDevelopment uses the same Jira processDeployment 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 CalculationState the Business RuleExamples from YouTest 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
NMFSADF&G
AKFIN
IPHC
CFEC
Data Flow ~ ADFG to CFECADF&G Fish Ticket Database Tables and Fields - Source Data for CFEC Gross Earnings Corresponding CFEC Fields
GROUNDFISH BATCH TABLE FIELDS SHELLFISH BATCH TABLE FIELDS SALMON BATCH TABLE FIELDS HERRING BATCH TABLE FIELDS GROSS EARNINGS FIELDS
BATCH_NUMBER BATCH_NUMBER BATCH_NUMBER BATCH_NUMBER ADFG_B_BATCH_NUMBER
BATCH_YEAR BATCH_YEAR BATCH_YEAR BATCH_YEAR ADFG_B_BATCH_YEAR
COMMENTS COMMENTS COMMENTS COMMENTS
DATE_CREATED_VERIFIED DATE_CREATED_VERIFIED DATE_CREATED_VERIFIED DATE_CREATED_VERIFIED ADFG_B_DATE_CREATED_VERIFIED
DATE_KEYED DATE_KEYED DATE_KEYED DATE_KEYED ADFG_B_DATE_KEYED
DATE_PUBLISHED
OFFICE_CODE OFFICE_CODE OFFICE_CODE OFFICE_CODE ADFG_B_OFFICE_CODE
PROOF_DONE PROOF_DONE PROOF_DONE PROOF_DONE ADFG_B_PROOF_DONE
PUBLISHED
TICKET_END TICKET_END TICKET_END TICKET_END ADFG_B_TICKET_END
TICKET_START TICKET_START TICKET_START TICKET_START ADFG_B_TICKET_START
USER_ID USER_ID USER_ID USER_ID ADFG_B_USER_ID
GROUNDFISH HEADER TABLE FIELDS SHELLFISH HEADER TABLE FIELDS SALMON HEADER TABLE FIELDS HERRING HEADER TABLE FIELDS
ADFG_NUMBER ADFG_NUMBER ADFG_NUMBER ADFG_NUMBER ADFG_H_ADFG_NUMBER
BATCH_NUMBER BATCH_NUMBER BATCH_NUMBER BATCH_NUMBER
BATCH_YEAR BATCH_YEAR BATCH_YEAR BATCH_YEAR
CDQ_CODE CDQ_CODE ADFG_H_CDQ_CODE
CREW_SIZE CREW_SIZE ADFG_H_CREW_SIZE
CUSTOM_PROCESSOR CUSTOM_PROCESSOR ADFG_H_CUSTOM_PROCESSOR
DATE_FISHING_BEGAN DATE_FISHING_BEGAN DATE_FISHING_BEGAN DATE_FISHING_BEGAN ADFG_H_DATE_FISHING_BEGAN
DATE_FISHING_ENDED ADFG_H_DATE_FISHING_ENDED
DATE_LANDED DATE_LANDED DATE_LANDED DATE_LANDED ADFG_H_DATE_LANDED
DAYS_FISHED DAYS_FISHED ADFG_H_DAYS_FISHED
DEWATERED ADFG_H_DEWATERED
FROZEN_AT_SEA
GEAR_CODE GEAR_CODE GEAR_CODE GEAR_CODE ADFG_H_GEAR_CODE
INITIAL_PROCESSOR ADFG_H_INITIAL_PROCESSOR
INITIAL_TICKET_NUMBER ADFG_H_INITIAL_TICKET_NUMBER
INTERVIEWED INTERVIEWED ADFG_H_INTERVIEWED
LANDING_REPORT_NUMBER LANDING_REPORT_NUMBER ADFG_H_LANDING_REPORT_NUMBER
LAST_USER_ID LAST_USER_ID LAST_USER_ID 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
top related