overview i.reminder of the scenario ii.waiting for the right opportunity iii.process – the...

17
NGA MOVEMENT REQUEST SYSTEM

Upload: kailey-buttrey

Post on 28-Mar-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

NGA MOVEMENT

REQUEST SYSTEM

Page 2: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Overview

i. Reminder of the scenarioii. Waiting for the right opportunityiii. Process – the Projects Methodology

i. (Analysis, Design, Develop/Test, Deploy, etc)

iv. Challengesv. Lessons

Page 3: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Scenario the story so far

Bernard CHEESE (1925)A fisherman's story1956Felix Man Collection, Special Government Grant 1972lithograph, printed in colour, from multiple stones/plates72.509.83

Lots of movements, short turnaround timesSolution: specialist art handlersCSRS built in-house to manage requestsCSRS developer left = no ongoing support/ developmentNot compatible with NGAs SOE Functional limitationsNeeded to replace CSRSDesire to avoid third-party solution (or face the same issues)Made sense to move to EMu

Page 4: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Opportunity waiting for the right moment

Discussed with KE for yearsbut…• NGA lacked internal resources to focus on the project• Weren’t fully across the complexities

– parent-child records– independently moveable functions

• Technology– EMu client interface– Along came IMUJames COOK (1904 - 1960) UK, Europe 1924-27; Australia from 1928

Sandy MCKENRICKCOMMUNITY ARTS PROJECT BY THE CITY OF FREMANTLEPostcard: Opportunity, choice, discovery.Australia 1989Gift of James Cook 1993planographiclithograph, printed in colour, from process plates93.1846

Page 5: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

The Process Project Methodology

http://www.sourceedge.com

Page 6: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Analysis phase concept

• A lot of ‘conceptualising’ of the project had been done over the preceding years.

• Mark’s presentation at 2010 EMu Conference in Brisbane• Documents analysing other EMu customers• Full comparison of CSRS with current EMu client solutions• “Scope” of the project already clear

Roger KEMP (1908 - 1987)BALDESSIN'S STUDIOConcept oneAustralia 1972Gift of Merle Kemp, the artist's widow 1996Intaglio; etching, printed in black ink, from zinc one plate96.571

Page 7: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Design phase• Needs analysis, through

discussion with KE staff• Provided CSRS documentation• Gave demonstration in person,

provided screenshots.• The Spec

– Word document– Collaborative design

George W. LAMBERT (1873 - 1930)Australia from 1921(Costume design for 'The Persian Garden': Man in skull cap)Australia (1922)Gift of John Brackenreg 1977.black pencil77.260.6.1.3

Page 8: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Design phase• WebEx meetings• Importance of visualising

– Interface design using Balsamiq• CSRS as starting point• Design screen• Add notes

– Represent ideas using tools you know (Excel)• Personal meeting to discuss complex issues• Revise the spec (11 versions)

Page 9: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Development phase• Overlap with Testing phase• Required NGA IT environment (webserver)• KE built according to the spec• came to us with questions

– JIRA Ticketing System

• Remote Server– KE hosted environment– More efficient for KE to apply fixes– Web interface testing only Wolfgang SIEVERS (1913 - 2007)

Australia from 1938Building No. 2. Warehouse: Technical development section: Test laboratory. Machine

roomGift of State Library of Victoria (by exchange) 2004.

gelatin silver photograph2004.299

Page 10: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Testing phase• JIRA Tickets

– Separate Queue from general support– Tracking ticket status - new status options:

• Ready to deploy• Deployed• Closed

• Issue – multiple staff accessing ticket list• NGA Local testing install

– Slower deployment of fixes– First time seeing the EMu client module

Wolfgang SIEVERS (1913 - 2007)Australia from 1938

Spinning and draw twist building: test laboratory: British Nylon Spinners, October 1958Gift of State Library of Victoria (by exchange) 2004.

gelatin silver photograph2004.298

Page 11: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Deployment / Release / MaintenanceDeployment soon• Impact on server performance• Impact on licenses• Find out what the users really think

Phase 1.5• Fix things we’ve missed

– In the spec (searching)– Discovered through testing (frame in a holder)– Discovered by users when we go live

Page 12: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

The Process Project Methodology

http://www.sourceedge.com

Page 13: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Deployment / Release / MaintenancePhase 2 and beyond• Exploring which workflows could benefit from an IMU

interface• Prioritising those projects

– According to NGA corporate priorities

Page 14: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Challenges• Distractions from testing

– Annual Report– Council Meetings– Subsequent Projects– General Support– Supporting CSRS

• Scope Creep – devil in the details– Things you can’t anticipate– Only become apparent when you are testing

Page 15: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Challenges• Project Fatigue

Noel COUNIHAN (1913 - 1986) AUSTRALIAN PRINT WORKSHOPSleepAustralia 1978Australian Print Workshop Archive 2, purchased with the assistance of the Gordon Darling Australasian Print Fund 2002relief; linocut, printed in black ink, from one block2002.431.1238

Page 16: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Lessons• Don’t bite off more than you can chew• Can never have too much detail• but where to draw the line?• Acceptance (& Zen)

– Costs will blow out– Timeframes will blow out– Don’t let “perfect” get in

the way of “better”– There’s always Phase 1.5, 2, 3

Seated JinaIndia 1163

Purchased 2003marble

2003.478

Page 17: Overview i.Reminder of the scenario ii.Waiting for the right opportunity iii.Process – the Projects Methodology i.(Analysis, Design, Develop/Test, Deploy,

Contact• See us at the Showcase Your System• Contact us

– Mark Bradley• [email protected]• 02 6240 6539

– Jennifer Drysdale• [email protected]• 02 6240 6568