CLIENT REFERENCE · INSEE
The INSEE reference concerns R package development. It highlights this aspect of TransformR expertise: developing R components organised as packages.
Scope presented here
This reference covers package development. Package names, processed data, distribution arrangements and engagement results are not detailed here.
Your project: turning functions into a business package
For a comparable project, scoping may cover the functions to group, their users, calculation rules, dependencies and reuse requirements. The aim is to distinguish the package interface from behaviour that belongs to a particular application.
Testing, documentation, versioning and distribution are topics to discuss for your project. Their scope should reflect your environment and team responsibilities.
Preparing the first discussion
- Which functions or workflows need to be grouped?
- Who will use and maintain the package?
- Which environments and R versions are involved?
- How should changes be checked, documented and distributed?
A description of the use cases and existing code is enough to start scoping the engagement. Confidential data is not needed in the first message.