Akari Software Transition to a Product Line Infrastructure
0 likes•546 views
Akari Software transitioned to a product line infrastructure to enhance the creation and maintenance of their software variants, starting the process in 2010. This included adopting an agile development model and focusing on localization, leading to improved production cycles and ongoing enhancements. The transition, though complex and underestimated, has been deemed successful, establishing the product-line concept in the industry.
Akari Software Transition to a Product Line Infrastructure
- 1. P A R A I C H E G A R T Y , E O G H A N O ’ L E A R Y , D A N N Y D I N E E N , A K A R I S O F T W A R E , I R E L A N D , P H E G A R T Y @ A K A R I S O F T W A R E . C O M D A V I D B U S T A R D , A D R I A N M O O R E , U N I V E R S I T Y O F U L S T E R , U K , D W . B U S T A R D @ U L S T E R . A C . U K Transition to a Product Line Infrastructure: Experience at Akari Software
- 2. Summary • A product family had been created without the underlying structure and processes needed to ensure the efficient creation and maintenance of variants • In 2010, the Company began making internal changes to develop a product range infrastructure • Localisation was a particular concern • The Company also took the opportunity to switch to an agile model of software development • Benefits included enhancing the production cycle and facilitation of a general programme of ongoing improvement
- 3. Product Line vs. Traditional Development
- 4. AKARI Solution Overview • Cost per student • Scenario planning • Staff utilisation • User-definable workflows • Escalation & exception handling • Audit trails & Reporting • Supplementary material • Website integration • Paper publications • XCRI-CAP & KIS • RESTful API • Comprehensive course data • Review & Approval • Audit logging Akari Document Akari Publish Akari ResourceAkari Review 4
- 5. Product Line Transition Strategy
- 9. Lessons Learned • Early adoption
- 10. Lessons Learned • Early adoption • Think ahead
- 11. Lessons Learned • Early adoption • Think ahead • Flexibility
- 12. Lessons Learned • Early adoption • Think ahead • Flexibility • Single code base
- 13. Conclusions • Work was significantly underestimated, and is still in progress • The transition has been very successful for Akari Software • Agile adoption a major success factor • Product-line development not just for Large enterprises • The product-line concept is now well established as evidenced by development of ISO/IEC 26550 • Work on further advances in the field continues to be funded
Editor's Notes
- #2: Good aftnernoonUlster – David & AdrianIntertradeIreland
- #3: SMEBespoke project8 additional customersLooking at EHEA
- #4: Schmid & Verlage ‘Software’ IEEEInitally more expensiveThen breaks even & generates additional ROI
- #5: Programmes & modulesConstructive alignment, stages, teaching & learning strategy, resources. ECTS compliancePublishing, workload allocation & academic quality
- #6: Had to bite the bulletNeeded new capabilityPartnered with UlsterSeparate but integrated
- #7: Technical variantsFunctional variants – deliberate & accidentalHad to quantify effect due to refactoring & mix of technologies
- #8: Localisation led to refactoringNor in EHEA but for NUIG1,000 language strings, 50 images & system dialoguesLess code instances but more callsneeded test automationNeeded easy way to configure & deploy
- #9: Needed an approach for the teamDecided on AgileTotal immersionBackground hi-techLow-tech info radsScrum & KanbanSprint efficiencyHalo effect
- #10: We adopted early but should have done even earlier
- #11: Huge debt had built up
- #12: Without over-engineeringe.g. language
- #13: Further debt