Page History
...
Section | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
The purpose of this document is to collect, analyze, and define high-level needs and features of the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) caCORE LexEVS Release 6.0. This document focuses on the functionalities proposed by the product stakeholders and target users in order to make it a better product. The use-case and supplementary specifications document will detail how the framework will fulfill these needs. Vision and NeedsThe objective of this release of the LexEVS API is to design and construct a reference implementation of the CTS2 specification, leveraging LexEVS as the basis for the design and code base. This release will address support for value sets, mappings between code sets, support for creation of local extensions to code sets and support related to content creation and editing. Current SolutionLexEVS 5.1 currently supports much of the functionality called for by the CTS2 Specification. Proposed SolutionsLexEVS 6.0 will provide the additional functionality to enhance LexEVS to meet the goals of a CTS2 Reference Implementation and requirements of the user communities. Functional RequirementsEach enhancement, modification or new feature is described in detail below.
Functional Bug FixesEach bug fix included in this release is described in detail below.
Non-Functional RequirementsThis section describes in detail all the related requirements which must be met for this release but do not add functionality. These requirements are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.
General Support ActivitiesThis section describes in detail all the related activities which must be performed for this release but do not add functionality. These activities are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.
Stakeholder Summary
Technical EnvironmentThis product uses the following technical components which have been derived from the current NCICB Technology Stack.
|
...
|
...
|
...
|
...
|
...
Product DependenciesThis release is dependent on the caCORE components or products documented in the CORE Product Dependency Matrix. Out of Scope ItemsItems that are out of scope were evaluated as part of the initial scoping activities for this release, and subsequently not included in the final approved scope. These items are also documented in the cumulative backlog of requirements found on the product GForge site. They include out-of-scope functional requirements (enhancements or new features), bug fixes, non-functional requirements, and general support activities.
Document History
Project Information
|
Section |
---|