...
III. In Scope/Out of Scope
In Scope
- Developing a plug-in for the Vips image library that uses Kakadu for reading and writing JPEG2000 images.
- Integrating the plug-in into the currently developed imgconv project.
- Maintaining the plug-in up to speed with future Vips upgrades
- Documentation and tests for the developed code
Note that this project is limited to still images. Other media may need a different workflow and approach.
Out of Scope
The following items are out of scope because they are achievable without this project; however, an optimized HTJ2K converter would significantly improve their quality:
- Development of a microservice for converting images based on configurable profiles (imgconv)
- Integration of imgconv into an automation framework for large scale processing (drs-pipelines)
- Conversion of defective and/or substandard delivery images into delivery-optmized HTJ2K
IV. Deliverables and Work Products
- Code, documentation and tests for a Kakadu plugin for Vips in a Git repository.
Definition of Done
This project will be considered done once:
- The Vips Kakadu plugin code is completed and committed to a Harvard-owned Git repository
- We are consistently able to compile and run the plugin
- Comprehensive tests are written for the key functions
- All tests pass
- Exhaustive relevant documentation is provided
- We are able to integrate the delivered code into our imgconv project and verify that the features and options satisfy our needs.
V. Stakeholders
...
VI. Project Team
...
Software engineers
...
QA
...
Stefano Cossu, Brian Hoffman
...
Functional documentation
...
John Cupitt
...
Scrum Master
...
Stefano Cossu
...
Project Manager
...
Vitaly Zakuta (LTS)
* Pierre-Anthony Lemieux deferred to John Cupitt for carrying out the development, remaining available for advising on Kakadu-specific topics. We have not yet established whether such consulting will be pro bono or for a fee. In the latter case, we should request a cost estimate, but ideally we would like to have one contractor billing for the whole project.
VII. Estimated Schedule (tentative)
...
Development & Release
...
Develop code
...
Development & Release
...
Unit and integration tests
...
Development & Release
...
Complete & validate documentation
...
Development & Release
...
imgconv integration and release
VIII. Assumptions, Constraints, Dependencies, and Risks
Project Assumptions
- The code delivered by the contractor will be agnostic to external integrations.
- Integration with imgconv and DRS pipelines, including deployment infrastructure and long-term maintenence, will be the DRS Futures engineering team.
- Stakeholders will be available to participate in project activities and to complete tasks as requested.
- The Executive Sponsor and other stakeholders are empowered to make the decisions required for the project to be a success.
- The code delivered by the contractor will be agnostic to external integrations.
Project Constraints
- Contractor availability
- DRS Futures team availability
- Scope
- Time
- Budget
Project Dependencies
- The plugin developer will be need a Kakadu SDK license to perform development, testing, and long-term maintenance of the requested software. Kakadu Software has agreed to provide John Cupitt a free and renewable Kakadu SDK license. The handing-off of that license is underway.
Project Risks
...
IX. Acceptance
Accepted by [ TODO ]
Prepared by Stefano Cossu
...
- [ To Do ]
Out of Scope
- [ To Do ]