Item |
Who |
Description |
Supporting materials |
1. |
Assess |
Product management |
Gain a high level understanding of the SBR program and its scope with a view to assessing the value that SBR can provide to your customer base. |
http://www.sbr.gov.au |
2. |
Decision point |
Executive |
Proceed to business case development |
|
3. |
Register |
Product management |
Register with the SBR program as a software developer to receive further information, and support services |
SBR software developer engagement program, email to sbr@Treasury.gov.au |
4. |
Learn XBRL |
Lead developer |
Read XBRL training material and attend XBRL / SBR Taxonomy training provided by the SBR program. This will provide the knowledge and confidence to estimate the implementation effort. |
XBRL Materials |
5. |
Understand the work required to have your software support SBR |
Product management and business management/strategy |
Covered in the above table |
|
6. |
Define form scope |
Product management |
Review the SBR forms in scope and select which ones you will support in your product. Use the Message Implementation Guides (MIGs) to gain a good understanding of how to implement each form. |
SBR forms in scope MIG Index |
7. |
Solution Blueprint |
Product management and lead developer |
Prepare a high level solution blueprint for implementing SBR within your product. Define key features and identify which government SDK components can be re‑used: § Data mapping solution § Forms rendering solution § XBRL processor § Authentication and keystore § Web Service messaging § SBR taxonomy |
The SBR SDK will provide you with § An XBRL processor § Authentication and keystore tooling. § Web Service Specifications (WSDL) The SBR taxonomy will provide you with § Form structure and validation rules. You will need to develop the mapping and rendering capability. |
8. |
Implementation Plan |
Product management |
Build an implementation plan and schedule with approximate costs. Include capacity building, design, build, and test of solution components, transformation & mapping for selected forms. Use the SBR master schedule to determine when you will implement support for specific forms. |
SBR Software developer sample implementation plan. SBR program master schedule. |
9. |
Business Case |
Product management |
Develop a business case for implementation of SBR services within your product. Prioritise forms to be implemented. |
SBR Software developer business case template. |
10. |
Decision Point |
Executive |
Proceed to detailed design & prototype |
|
11. |
Capacity Building |
Architect & developers |
Develop the capacity within your organisation - or via outsourced providers in XBRL, the SBR taxonomy and how to leverage it, and other SBR technical services. |
SBR Training curriculum. SBR Knowledgebase and forum. |
12. |
Prototype |
Developers & product management |
Develop a prototype implementation to test mapping and lodgement of one form - typically one for which your product can already create a printed version. |
SBR SDK, documentation, knowledgebase and support services |
13. |
Design |
Lead developer & product management |
Develop a detailed design for commercial implementation of the SBR solution within your product suite |
Reference client implementation |
14. |
Decision Point |
Executive |
Proceed to implementation |
|
15. |
Solution Build |
Architect / developer |
Build production quality solution. |
SDK and support services. |
16. |
Mapping |
Developer / business analyst |
Develop transformation and mappings necessary to create valid XBRL report instances. Effort depends on complexity of form and level of alignment between the taxonomy and your product data store. |
Message Implementation Guides, SBR AU Taxonomy. |
17. |
Rendering / User interface |
Developer / business analyst |
Develop report presentations (to allow user to review / edit before lodgement). The level of effort depends on complexity of form and extent to which you leverage government provided templates. |
Form presentation templates |
18. |
Test |
Product management & QA |
Test solution against SBR test services |
SBR testing. Self assessment & compliance program. |
19. |
Document |
Product management, tech writer |
Prepare administrator and user documentation. |
|
20. |
Operations |
Product management, support staff |
Define and implement operational support process. Typically this will include a server based mechanism to automate distribution of taxonomy updates to your customers - alongside other product updates. |
SBR taxonomy architecture and version / release strategy. SBR knowledge repository & Taxonomy server. |
21. |
Decision Point |
Executive |
Release to market |
|
22. |
Release |
Product management |
Market the "SBR compliant" version of your product and release to your customers. |
SBR marketing support |
23. |
Support |
Support staff |
On-going support including: § bug fix and patches § new forms and mappings § new reference data (eg tax tables) |
SBR customer support |
