... | ... | @@ -10,23 +10,23 @@ Following the [Phased Proposal](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis |
|
|
|
|
|
### Use case deliverables
|
|
|
|
|
|
These high-level deliverables were provided by NCBI oroject owner (Stacy).
|
|
|
These high-level deliverables were provided by NCBI project owner (Stacy).
|
|
|
|
|
|
1. Use case deliverable 1: Support for Word and XML chapter-processed content: Issue 450
|
|
|
2. Use case deliverable 2: Support for XML and PDF book-processed content: Issue 451
|
|
|
3. Use case deliverable 3: Permissions, Notifications, and Feature Improvements: Issue 452
|
|
|
4. Use case deliverable 4: Production-ready BCMS for internal staff users, Word authoring teams, PDF2XML vendors, and Bookshelf participant administrators: Issue 453
|
|
|
1. Use case deliverable 1: Support for Word and XML chapter-processed content: Issue #450
|
|
|
2. Use case deliverable 2: Support for XML and PDF book-processed content: Issue #451
|
|
|
3. Use case deliverable 3: Permissions, Notifications, and Feature Improvements: Issue #452
|
|
|
4. Use case deliverable 4: Production-ready BCMS for internal staff users, Word authoring teams, PDF2XML vendors, and Bookshelf participant administrators: Issue #453
|
|
|
|
|
|
Coko Project Manager (Dione) has mapped the existing issues for Phase 1 to each deliverable.
|
|
|
|
|
|
### Per issue sign-off criteria
|
|
|
|
|
|
Following Stacy's review of the mapped issues, the sign off criteria are confrimed and agreed on for each issue. These my vary depending on the nature of the issue. When new or significantly adapted UIs are required, an visual walk-though, using roughs designs or demos of development-in-progress, is part of the sign-off process.
|
|
|
Following Stacy's review of the mapped issues, the sign-off criteria are confirmed and agreed on for each issue. These my vary depending on the nature of the issue. When new or significantly adapted UIs are required, an visual walk-though, using roughs designs or demos of development-in-progress, is part of the sign-off process.
|
|
|
|
|
|
#### Sign-off responsibility
|
|
|
|
|
|
* Stacy signs off user stories and their designs
|
|
|
* Evengy or Martin sign off techical specs for integration-related issues
|
|
|
* Evgeny or Martin sign off technical specs for integration-related issues
|
|
|
* Dione confirms the sign-off criteria are complete and sufficiently detailed for the developers to proceed.
|
|
|
|
|
|
In cases where NCBI and Coko teams do not agree on the acceptance criteria, these issues should be floated to the DDWG to resolve together.
|
... | ... | @@ -54,7 +54,7 @@ The **Development phases**: |
|
|
5. QA →
|
|
|
7. Internal review →
|
|
|
8. Dev Done
|
|
|
8. Closed issues (completed work that has been relased and accepted by NCBI according to the sign-off criteria)
|
|
|
8. Closed issues (completed work that has been released and accepted by NCBI according to the sign-off criteria)
|
|
|
|
|
|
When dev issues are ready for NCBI's testing, Dione will create one issue listing all the relevant issues and documentation when relevant.
|
|
|
|
... | ... | |