133
edits
Changes
Digital Enablement Development Release Cycle (view source)
Revision as of 09:55, 15 October 2018
, 09:55, 15 October 2018no edit summary
If the open-source application being tested is unsuitable, a different application will be pilot tested.
If the open-source application being tested is unsuitable, a different application will be pilot tested.
Currently the following tools are in pilot:
'''Currently the following tools are in pilot:'''
*Message
*Message
===Alpha===
===Alpha===
After the appropriate application is selected, the tool undergoes alpha development.
After the appropriate open-source application is selected, the tool undergoes Alpha development and testing. During this phase the features and design of the tool are developed based on the user needs determined in pilot testing.
Alpha testing is done by select users to test the usability and user experience of the tool in development, as well as to find major bugs which affect the functionality of the tool[https://www.softwaretestinghelp.com/alpha-testing/].
When in Alpha the tool is functional, but does not include all of the features which will be in the official release.[https://techterms.com/definition/alpha_software]. Alpha is complete when all of the necessary features and design are developed and tested, and the tool is ready to be released to the entire user base.[https://techterms.com/definition/alpha_software]
'''Currently the following tools are in pilot:'''
*Aurora design system
===Beta===
After Alpha testing has ended, the tool enters the Beta stage of development and testing. The DCD uses open Beta testing to test its tools, meaning that the tool can be used and tested by every user in a real environment. The tool [https://www.softwaretestinghelp.com/beta-testing/].
the testing carried out by real users in a real environment.