To confirm whether the technology traceability is carried out within a reliable boundary based on the top requirements, system requirements, sub system requirements, and component requirements of the derived PRIDE system, an experiment was done with an Ar (Argon) cooling system as a target.
We can define the sub-requirements of DP1.1 again as follows.
Therefore, rather than simply stating that a sub-requirement is desirable, we have drawn attention to specific examples, which we hope, will be useful to future CGS developers.
Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable.
The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008.
We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context.
We have addressed some of the sub-requirements of guideline repositories in the Introduction: security and management of user privileges, version control and audit trail of changes, and searchable content (possibly assisted by controlled vocabularies).
The contribution of this paper is two-fold: It discusses in detail the sub-requirements that become critical during implementation of production clinical guideline systems, in accordance with the framework outlined in Table 1.
For example, while practically all systems claim to support guideline repositories, production-level sub-requirements include whether and how such repositories support secure access to authorized users, how permissions (read/write vs. read-only, user groups, roles, etc).
We will then focus on sub-requirements that, we believe, have either not been considered in the literature at all (i.e., are novel), or which may have been proposed but whose implications may have not been adequately explored: here, either supporting or (occasional) contrary evidence from existing projects will be presented.
In existing CGS-related systems, HeCaSe2 [ 8] has a security model, and the Vaidurya search engine [ 9] supports search (in part by using standard biomedical vocabularies), but we are not aware of a repository that supports all of the above sub-requirements).
