Criteria for component's approval

Acceptance criteria

For Design system the main output is Components' library. To define if developed component is aligned with initial design and requirements, for each story set of Acceptance criteria is submitted. It includes the following levels:

1. Design. All styles and variations should be taken into account (included into MVP scope). We need to check:

• variants,

• states,

• constituent components of the lower order;

• other design related points.

2. Functionality. If the component has functionality it should be stated in a rules-based form (short statements that can result in a pass or fail and operate as a checklist).

3. Properties. Description of added properties (props) is provided to check if they work properly.

4. Accessibility. Criteria is covered by checklist for all components that includes WCAG 2.1 compliance. In some cases we should add specific standards to be checked.

Definition of Done

There is also a set of criteria that applies across all stories and can therefore be applied to each story, but not repeated within each story. Relevant DoD criteria are listed below:

1. Code is peer-reviewed;

2. Code is checked-in;

3. Design & Code meets WCAG 2.1 AA;

4. Security standards have been met;

5. Coding standards have been met;

6. Performance standards have been met;

7. Code is deployed to test environment;

8. HTML is validated;

9. Code/feature passes regression testing;

10. Code/feature passes smoke testing;

11. Cross-browser testing is passed;

12. Code is documented;

13. UAT and BUAT are passed;

14. Documentation is updated;

15. Feature is signed off by stakeholders;

16. Feature is released to AWS Code Artifact.