Date: 15 August 2018
Version: 1.0.3
Source document: http://poumataaho.boh.tepapa.govt.nz/otcs/llisapi.dll?func=ll&objaction=overview&objid=3941405
...
Te Papa has created an open-source Digital Language System or DLS (https://dls.tepapa.govt.nz/) which defines a design language of patterns and principles for use in designing digital products. This will be made available to vendors engaged by Te Papa and should be considered for use where suitable patterns exist, in order to provide a consistent visitor experience throughout the museum.
Te Papa requires vendors to use a source control system for managing any source code and recommend that best practices such as Test-Driven Development, Continuous Integration and user testing are used to ensure quality deliverables.
...
Te Papa does not operate under the “Good code does not need comments” mantra. Te Papa requires that all functionality needs to be clearly documented. We recommend using Javadoc to document functions and classes. Where possible, all documentation should be built from the documentation comments.
...
Te Papa expects a level of experience consistent with that which would be expected from the national museum. Animation Animations should be smooth, and the execution of design should be of a high standard.
Functional and integration testing should be provided as part of the code basecodebase. Continuous Integration service should run all tests during any build process.
...
All technologies employed, whether it be BrightSign, DEDS player, any other PC application or hardware, should be configured to boot directly into the ready state without any user intervention.
...
- Any products should meet Te Papa’s security needs, and any data collected from our visitors need to meet the industry best practices on privacy- and security policy.
- Interactive products should have no gestures, “hot corners” or other ways to access an admin console or debug mode from the visitor side of the experience.
- Any network access required should not require an external IP address or ports translated through NAT to the product.
- Right-click/long-tap, context menu access, and text selection should be disabled in any interactive products.
- Hotkey combinations may be used to quit from digital products where no keyboard is available to the visitor.
- Any input fields should sanitise against HTML or code-injection attacks.
...
Te Papa encourages vendors to discuss architectural and technology decision at key stages throughout the project cycle. Te Papa would seek conversations with vendors regarding the proposed solution and product - design.
If possible, new products should consume existing services or products. Te Papa already uses a number of products and services and would be happy to share those resources with vendors. We encourage the use of existing Te Papa infrastructure, services or products.
...
Your product should support open standards to support interoperability. Open-source software shall be compared and considered alongside commercial software for your technology solutions.
...
Preferred and supported technology and frameworks for the client-side Single Page application for this product are:
...
Te Papa’s would like to be able to manage, deploy, re-deploy and alter the product over its live-timelifetime. This will enable Te Papa to adopt changes and ongoing support of the product over the lifecycle of the exhibition.
...
- A period of “High Care” should be allowed for in the period immediately after releasing products to the floor. Typically 10-15% of the development budget is recommended for this period.
- Consideration should be given to tasks and budget required to manage products each year that they are in operation, typically this is a period of 5 to 10 years.
- Content should be easily updated, either through a simple CMS, flat file or a JSON file.
- Updates to content should be possible over the network, avoiding the need to physically access the hardware on the floor.
- Remote access for vendors to manage interactives is by default not provided by Te Papa but would be open discussing remote management options with the vendor.
...