...
To support this, the specification itself needs to be on a collaboration platform. We may be able to offer e.g. Teams / Sharepoint / Excel as a collaboration platform to certain customers, and if not, we may be able to use yours.
...
Example
The following example specification has been designed to be read by a script during the migration process…
...
...
| View file | ||
|---|---|---|
|
Specification Sections
The specification is broken up into sections ( tabs in the workbook ), where each section tab is a different place in the ClinSpark UI that can potentially receive volunteer information.
For each section, the following areas must be included:
Migration Specification
List the followingexample:
Source System Table/Screen
Source System Column/Atttibute
CS Table/Screen
CS Column/Atttibute
Migrate (Y/N)?
Status (Dev Ready/Dev Complete/Validated)
Migration Instructions/Rules
Comments
...
If required, provide the SQL in a textual form which can be copied and later executed by engineers as examples. Provide the execution output showing the test data highlighted in this section’s example to demonstrate it is correct.
...
Iterations of specifications and implementations
Each iteration starts with the completion of the dedicated specification document. The first iteration tends to be by far the biggest, since this is where the full scope of the migration is spec’d out and a first comprehensive implementation is attempted.
...
The specification changes for later iterations should focus on particular issues, and they should clearly articulate the change and most importantly, reference test cases with specific examples from the test data.
Data Without an Existing Field in ClinSpark
Frequently a source system will have a field for volunteer data which doesn’t have an explicit field in ClinSpark.
...