Atch_2 _Appendix_A.pdf

Nonfunctional Requirements ID Requirement Priority Level

Objective 1: Architecture NF‐A‐01 Users shall access the web-based system without software installation on any device (i.e. web-based, not web-enabled) 2

NF‐A‐02 The platform shall have a Graphical User Interface (GUI) meeting HTML5 standards that is mobile compliant 2

NF‐A‐03 The platform shall operate on a virtual computing environment configuration (i.e., VMware ESX 5.1) and will scale horizontally on commodity hardware as the number of users and data streams grow 2

NF‐A‐04 The platform shall support stand-alone configuration on which to run a client as a separate, disconnected unit, with auto-sync enabled once re-connected 2

NF‐A‐05 The platform shall meet Section 508 compliance requirements 2 NF‐A‐06 The platform shall have 99% availability 1 NF‐A‐07 The system data shall be maintained in a CDC-supported relational database 1 NF‐A‐08 The platform shall have the ability to interact with multiple relational databases of various types 2

NF‐A‐09 The platform shall provide CDC administrators functionality for tracking, acquiring, installing, and monitoring license usage 3

NF‐A‐10 The platform shall implement WebGL APIs to enable 3D and 2D dynamic graphics without plug-ins 1 NF‐A‐11 The platform shall have the ability to either embed or integrate external third party APIs 2 NF‐A‐12 The platform shall be compatible with the previous three versions of supported browsers 1

NF‐A‐13 The platform shall have the ability to send and consume data via web services (i.e., server-to-server communication) 2

NF‐A‐14

The platform shall implement service-oriented architecture to deliver platform functions (e.g., data ingestion, visualization, and export) as a “service” with a Representational state transfer (REST) and Web Services Description Language (WSDL) to provide server-to-server interface via the web.

Objective 2: Performance Requirements NF‐P‐01 The application/browser response time (excluding calls to third party apps, data imports/exports) shall average < 5 seconds 1

NF‐P‐02 The querying/searching response time of data in the system shall average < 5 seconds 1

NF‐P‐03 Response time shall average < 60 seconds for completion of data import, generation of exported dataset, and generation of reports (assumptions: 10 concurrent users; 2500 records per export/report) 1

NF‐P‐04 The platform shall be capable of supporting at least 100 concurrent users without performance issues or the need for scaling up platform infrastructure 2

NF‐P‐05 The system shall be capable of scaling up to at least 300 concurrent users without delay in response times or performance issues 2

NF‐P‐06 The system shall be capable of scaling data volumes up to 2 terabytes 2

NF‐P‐07 The system shall be able to process data sets larger than server memory 1

NF‐P‐08 For response times expected to take longer than 60 seconds, the system shall provide backend processing to allow the user to continue working in the system 2

NF‐P‐09 For response times expected to take longer than 60 seconds, the system shall provide a notification to the user when the process has completed 2

Objective 3: System Security NF‐SS‐01 The platform shall comply with Federal Information Processing Standard (FIPS) 140-2 encryption standards, i.e. AES 256-bit for all data at rest and while in transit between all machines 2

NF‐SS‐02 The platform shall comply with HHS Policy Guidance, HHSAR 304.13 and Homeland Security Policy Directive 12, which includes the use of Personal Identification Verification cards 2

Objective 4: Data Security NF‐DS‐01 The platform shall maintain metadata on all information contained within the platform for use in audit report generation, including all changes made to the data, its sourcing, and its traceability 1

NF‐DS‐02 The platform shall audit, track and store the pedigree, lineage, and tagging/classification of all data 1

NF‐DS‐04 The platform shall have the ability to restrict each user’s access to system modules and information based on data tagging that he or she is cleared to access down to the field level 1

NF‐DS‐05 The platform shall provide CDC administrators and CDC superusers the ability to change users’ access and rights (e.g., full control, add, edit, delete, extract) to information 1

NF‐DS‐06 The platform shall enable the same user or user group to have different access and rights for each public health event response as defined by the CDC administrator and CDC superuser 1

NF‐DS‐07 The platform shall provide cross domain data security (for different user groups and assigning security roles, rights and access) 1

NF‐DS‐08 The platform shall enable multiple types of user authentication mechanisms, including 1 factor and 2 factor, Security Access Management System (SAMS), and Personal Identification Verification cards 1

NF‐DS‐09 The platform shall allow the creation of standardized and customized categories of users (e.g., administrators, superusers, members, visitors) 1

NF‐DS‐10 The platform shall provide a process for requesting authorization to view data from respective data owners 3

Functional Requirements Functional Requirements

ID Requirement Priority Level Objective 1: Data Integration

F‐DI‐01 The platform shall import all commonly used standardized, structured data formats 1

F‐DI‐02 The platform shall import and view unstructured and semi-structured data (e.g., Free text with numeric data/binary responses embedded; mp3, jpeg) 1

F‐DI‐03 The platform shall allow for unstructured data to be linked to any field, observation, or event 1 F‐DI‐04 The platform shall allow for non-technical users to assign incoming data to variables (translational data element map) 1

F‐DI‐05 The platform shall allow for non-technical users to save user-defined data templates for mapping new data elements that will allow automatic integration on ad hoc basis 2

F‐DI‐06 The platform shall have system-suggested mapping or identification of key fields 3

F‐DI‐07 The platform shall integrate with third-party software to add functionality (not used for data editing) in order to have “one-stop shopping” for platform functionality 3

F‐DI‐08 The platform shall allow CDC administrators to define a data refresh interval per event and per data stream 2 F‐DI‐09 The platform shall allow CDC superusers the ability to force a data refresh 2 F‐DI‐10 The platform shall have live connections to data sources for a continual data feed 2 F‐DI‐11 The platform shall allow CDC administrators the capability to connect to new data sources for importing 2

F‐DI‐12 The platform shall allow CDC administrators the capability to connect to new data sources for viewing only (not imported into platform and no ability to edit data) 3

F‐DI‐13 The platform shall have the capability to manually enter data into platform, via key strokes, cut and paste, etc. 1

F‐DI‐14 The platform shall contain open Application Programming Interfaces (APIs) to integrate with external systems and data sources 2

F‐DI‐15 The platform shall have the capability to merge/link data by multiple user-defined key fields, allowing for 1:many and many:1 relationships 1

F‐DI‐16 The platform shall allow the labeling of a data field as a required field 1 F‐DI‐17 The platform shall automatically propagate revised or new data across platform in real time 1 F‐DI‐18 The platform shall allow users the capability to re-map, trace, and edit mapping of data elements within the platform 1

Objective 2.1: Data Visualization: Search and Query F‐DV‐01 The platform shall enable federated search, which accesses all data touched by the system 1

F‐ DV‐02 The platform shall have conditional search and query capabilities based on Boolean search logic (“IFs”, “ANDs”, “ORs” and specify with parentheses) and “fuzzy” matching (likes, contains, starts with, between, etc.) 1

F‐ DV‐03 The platform’s search and query functions shall support operations on all data types, data elements, and file names represented in the data model 1

F‐ DV‐04 The platform’s search function shall search content in foreign language 3

F‐ DV‐05 The platform shall support a link-by feature that allows users to leverage analysis conducted by others, save links among investigations, and save searches and queries 2

F‐ DV‐06 The platform shall have the capability to share and publish saved searches and queries for all users or user groups 1 F‐ DV‐07 The platform shall have an interactive search and query log with associated metadata 2

F‐ DV‐08 The platform shall allow users to set and save search parameters to alert the user to new information as it becomes available 2

F‐ DV‐09 The platform shall allow users to search and query on database names, common names, and other aliases or labels 2

F‐ DV‐10 The platform’s query function shall account for null values (numerical or descriptive) 1

F‐ DV‐11 The platform’s query function shall have error notification of queries that cannot be executed along with a reason for the error 2

F‐ DV‐12 The platform’s search and query functions shall be able to group, multi-layer sort, and rearrange search and query results 1

F‐DV‐13 The platform’s query function shall provide advance notice of number of records that will be returned for queries, with an option to continue with the query 1

F‐ DV‐14 The platform’s query function shall allow the user to cancel out of a query 2

F‐ DV‐15 The platform shall be able to compute and display summary information from queries at the record level, for groups of similar data elements, or for individual data elements 1

F‐ DV‐16 The platform shall allow non-technical users the capability to create, execute, and save a query 1

Objective 2.2: Data Visualization: User Interface F‐ DV‐17 The platform shall use intuitive design principles for the user interface 1 F‐ DV‐18 The platform shall provide a common landing page for all users 1

F‐ DV‐19 The platform landing page shall provide users with access to all applications, data sources and dashboards that are assigned to a user’s given user group in a single platform interface 1

F‐ DV‐20 The platform’s landing pages shall provide one-click access to all approved data sources and applications 1 F‐ DV‐21 The platform shall provide a user navigation pane within the landing page 1 F‐ DV‐22 The platform shall enable users to add links, including commonly used tasks or queries, to the landing page 2 F‐ DV‐23 The platform shall use single mouse clicks for all links and navigation 1 F‐ DV‐24 The platform shall be designed to minimize the number of clicks needed to perform any task 2 F‐ DV‐25 The platform shall be designed to minimize user gestures in navigation 3 F‐ DV‐26 The platform shall be designed to allow use of multiple windows/screens/instances open at the same time 2 F‐ DV‐27 The platform shall provide user help within the system 1 F‐DV‐28 The platform shall allow users the ability to manually enter case data using a data entry view within an event 2

F‐DV‐29 The platform shall have an intuitive user interface to display and edit case, group, or event data (i.e., not a line list or spreadsheet) 2

Objective 2.3: Data Visualization: Analysis F‐DV‐30 The platform shall have a CDC-defined event dashboard 1

F‐DV‐31 The event dashboard shall be designed so that it can be modified by a CDC superuser for each event (e.g., remove/add charts, tables, graphs; edit data labels/legends within graphs, etc.) 2

F‐DV‐32 The platform shall have the capability for users to drill down into data details from dashboard visualizations (e.g., mouse-over, pop-up window, etc.) 2

F‐DV‐33 The platform’s dashboard shall only display data viewable to the particular user group 1 F‐ DV‐34 The platform shall support the creation and display of user-defined descriptive statistics 1

F‐ DV‐35 The platform shall support the creation and display of user-defined inferential statistics (e.g., Correlations, odds ratios, regression analysis) 3

F‐ DV‐36 The platform shall support ensemble methods for object categorization (e.g., bootstrap aggregating, boosting, stacking, or combinations thereof) 3

F‐DV‐37 Users of the platform shall be able to utilize queries, filters, etc. to generate histograms, timelines, epi curves, time wheels, geospatial plots, and heat maps 2

F‐DV‐38 CDC users shall have the ability to create and modify data visualizations (histogram graphs/charts/tables/maps) ‘on-the-fly’ 1

F‐DV‐39 Non-CDC users shall have the ability to create data visualizations (histogram graphs/charts/tables/maps) of their own data ‘on-the-fly’ 2

F‐DV‐ 40 The platform shall be able to perform geospatial analysis to search, view, filter and understand data through time and space 1

F‐DV‐41 The platform shall have the ability for users to create and view data via line lists 1

F‐DV‐42 The platform shall have the ability for users to intuitively and efficiently edit, filter, group, multi-layer sort, rearrange line lists 1

F‐DV‐43

The platform shall link statistical, geospatial, temporal, and network analysis modes such that information can be visualized in each one of these modes without having to move data between applications (i.e., Visualization output should toggle between various output types)

F‐DV‐44 The platform shall have the capability to toggle between modes of content presentation without loss of data or performance delay 1

F‐DV‐45 The platform shall have real-time filters of visualizations based on other linked visualizations such that data shown on one graph is affected by what is displayed or selected in another visualization of the same data 2

Objective 3: Data Sharing F‐DSH‐01 The platform shall have the capability for all users to generate canned reports 1 F‐DSH‐02 The platform’s report function shall have formats that can be produced in MS Office applications and in pdf 2 F‐DSH‐03 The platform’s report function shall have all reports set to standard printing parameters 2 F‐DSH‐04 The platform shall have the capability to export and print all visualizations and reports that users are able to generate 2 F‐DSH‐05 The platform shall generate visualizations that can be edited after being exported 3 F‐DSH‐06 The platform shall allow the export of the underlying data of user-defined visualizations 3 F‐DSH‐07 The platform shall allow the export of filtered, merged, and derived data generated via query 2 F‐DSH‐08 The platform shall allow CDC the capability to export all of the data in all data streams (i.e., total data dump) 1 F‐DSH‐09 The platform shall be able to include either database name or common name, or both, in reports and in exported data 3 F‐DSH‐10 The platform shall be able to sort data during report generation 2

F‐DSH‐11 The platform shall allow selected users to be able to manipulate data during the report and export generation in the same way as the search and query (group, multi-layer sort, and rearrange), including the ability to create new variables and value labels 3

F‐DSH‐12 The platform’s report function shall compute and display summary info on all reports as default (e.g., number of records returned, current date/time, user ID) 2

F‐DSH‐13 The platform’s report function shall have customizable display info on reports 3 F‐DSH‐14 The platform’s report function shall have user-defined layouts 3 F‐DSH‐15 The platform’s report function shall allow a user to save his or her own report parameters 2

F‐DSH‐16 The platform’s report function shall save a copy of every generated canned report, with time stamp and creator information 2

F‐DSH‐17 The platform’s report function shall give non-CDC users the ability to export and generate reports for their data according to their access rights 2

Objective 4: Data Management F‐DM‐01 The platform shall enable users to edit and delete data 1

F‐DM‐02 The platform shall enable a customer-defined business process model and data flow diagram 1

F‐DM‐04 The platform shall implement an extensible CDC core data model 1 F‐DM‐05 The vendor shall develop a core data standards document (i.e. data dictionary and data protocols) 1 F‐DM‐06 The platform shall enable CDC administrators to generate current data dictionaries 2

F‐DM‐07 If multiple users are working on the same data, the platform shall have a mechanism by which it ensures that users will not undercut or overwrite one another’s work 1

F‐DM‐08 The platform shall be able to undo or revert back data manipulations to previous versions 3 F‐DM ‐09 The platform shall enable CDC administrators and CDC superusers to create new events with associated metadata 1 F‐DM‐10 The platform shall enable CDC administrators and CDC superusers to merge and split events 2 F‐DM‐11 The platform shall have a system-assisted data validation process 3 F‐ DM ‐12 The platform shall enable selected users to create computed data elements 2 F‐DM‐13 The platform shall have the ability to build a workflow within the system 2 F‐DM‐14 The platform shall allow CDC administrators and CDC superusers to create new and delete existing user accounts 1 F‐DM‐15 The platform shall have the ability to reset or update passwords for users 1 F‐DM‐16 The platform shall have the ability to view all attributes of a data element 2 F‐DM‐17 The platform shall have a complete user manual 2 F‐DM‐18 The platform user manual shall provide a documented list of CDC administrator procedures 2

F‐DM‐19 The platform shall allow CDC administrators to generate and view notifications when networks, servers, databases, and applications are not up and functional 2

F‐DM‐20 The platform allow CDC administrators to store and view all notifications in system event log 2 F‐DM‐21 The platform shall allow CDC administrators to generate system usage and performance reports 2

Objective 5: Communications F‐C‐01 The platform shall have electronic communications tool/s within the platform 2 F‐C‐02 The platform shall have the ability to send communications to individuals or groups of users 2 F‐C‐03 The platform shall notify recipients of incoming messages 2 F‐C‐04 The messages shall have metadata associated with each message 2 F‐C‐05 The platform shall have a discussion board or an API to link to a CDC-identified tool (i.e. plug-in) 3 F‐C‐06 The platform shall store all communications within the platform 2 F‐C‐07 The platform shall allow CDC administrators to access all stored communications 2 F‐C‐08 The platform shall have the ability to contact a CDC-supported help desk from anywhere in the platform 2