nhsbsa-data-analytics/nhsbsa-analytical-code-assurance-playbook

Scope requirements for low/no-code solutions

Open

#4 opened on Jan 30, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Lua (1 fork)auto 404
help wantedplanning

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

Agree requirements to support low/no-code solutions with relevant business areas.

Through discussions we have agreed that the playbook should decouple (language-agnostic) principles / best practice from (language-specific) implementation.

The same principles should apply everywhere (e.g. anything to produce analytical outputs should be formally tested, regardless of code/no/low code) but the implementation guidance will be different.

We need to work out who our key user groups our and how we intend to support them.

Contributor guide

Research direction
Identify key user groups for low/no code solutions within analytical workflows and determine how the playbook can provide guidance for these groups, possibly through personas or use cases.
Tech stack
None
Domain
data
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60