4-Appendix E – Non-Functional Requirements.pdf

Appendix E – Non-Functional Requirements

For each of the requirements shown in the table (beginning on the next page), the Proposer shall indicate for each requirement whether their solution fulfills the requirement and provide any associated comment(s). Failure to use this table or to provide complete information could result in proposal disqualification. For those denoted with an asterisk (*), they are considered desirable, although other than mandatory. Reference also the included separate Business Requirements Document

Req# Requirement Meets?

Y/N Comments

1.0 Usability

1.1 The system shall be designed with a user with

minimal computer skills in mind.

1.2 The system shall have the ability to support different

file formats.

1.3 The system shall have the ability to support robust

search functionality at any level.

1.4 The system shall be accessible 24/7 for users.

1.5 The system shall allow users to complete task

without problems or obstacles

2.0 Reliability

2.1 The system shall be available 24 hours a day, 7 days a

week.

2.2 The proposer shall coordinate maintenance window

with City Change Management.

2.3 The proposer and City shall agree to Service Levels in

an Agreement (SLA) that meets or exceeds City performance standards

3.0 Performance

3.1 Search results shall be displayed/produced according to

standard metrics.

3.2 The system shall have the ability to support multiple

users without visible impact on performance.

3.3 The system shall maintain a steady and reliable

network connection and response time. It must ensure new entries and updates are saved in real time to prevent loss of data.

3.4 Response time when accessing system must adhere to

HR’s, Civil Service, and City Controller’s requirements.

3.5 The time to restore the system following a system

failure must not be greater than 10 minutes.

3.6 The system shall integrate via Transmission Control

Protocol/Internet Protocol with the City’s wide area network and Department local area network infrastructure to demonstrate that the system performs without timing out.

4.0 Supportability

4.1 System support shall be available 7am-10pm central

time.

4.2 The system shall have the ability to cover the

following in the SLA:

4.2.1 Notify/Acknowledge an issue

4.2.2 Diagnose quickly

4.2.3 Repair

4.2.4 Test

4.2.5 Production validation

4.3 The system must be designed in such a manner as to

allow for support of system, connections, integration to other systems/modules, security, and configurations by the City’s Information and Technology Service department.

4.4 All documentation requested by the City of Dallas

Technology Reference Architecture TRA checklist must be provided to the COD by the proposer before project kickoff

4.5 Implementation of web portal that is supported by

browsers such as: IE, Safari, Google Chrome, Firefox, Microsoft Edge and configurable for other browsers.

5.0 Security

5.1 The proposer shall comply with NIST SP800-171R2

security assurance.

5.2 The proposer shall provide System Organization

Controls (SOC2) type 2

5.3 All City data stored at any Data Center or being

transported will be encrypted and will not be transferred to any non-City of Dallas entity or location without the prior written consent of the City of Dallas. Proposer will provide the use of encryption technology to protect City Data from unauthorized access.

5.4 Solution will support the provisioning of sufficient

access and authentication controls.

5.4.1 Super Owner

5.4.2 System Admin

5.4.3 Power User/Report Writer

5.4.4 Contributor

5.4.5 Read Only (at/according to appropriate

access/authentication level(s))

5.5 Proposer will perform nightly, weekly, and monthly

back-up and archiving of City Data.

5.5.1 Nightly from 10:pm to 6:00am

5.5.2 Weekly from Monday to Sunday

5.5.3 Monthly from the first day of the month to the last

day of the month

5.6 Proposer will implement reasonable security

standards that determine necessary, but in no event less than industry standards to protect City of Dallas Data. Proposer will provide data leak prevention.

5.7 Proposer will protect and monitor City of Dallas data

for which they are responsible.

5.8 Proposer will designate an individual to be

responsible for information security program and this individual will respond to City inquiries regarding computer security and will notify the City of Dallas if a breach or an incident occurs.

5.9 City Data shall be encrypted in rest or in transit.

5.10 Proposer will not access and will not permit

unauthorized persons or entities to access City computing systems and/or networks without City’s express written authorization.

5.11 Proposer will take appropriate measures to ensure

that systems connecting to City’s systems, and anything provided to City through such systems does not contain malware, spyware, viruses, worms, trojans that will disable or impair the operations, software, computer system or network of the City of Dallas.

5.12 Any data made available to the proposer, its

employees, or contractors, will not be stored, copied, analyzed, monitored, or otherwise used except for the purposes and benefit of the City of Dallas.

5.13 Proposer will comply fully with all applicable laws, regulations, and government orders relating to Personally Identifiable Information (PII), Sensitive Personal Information (SPI), Health Insurance Portability Accountability Act (HIPAA), Protected Health Information (PHI) and data privacy with respect to any data the proposer receives.

5.14 Proposers will protect PII and will not use, disclose, or transfer across borders such PII except authorized by the City of Dallas.

5.15 Proposer will protect the privacy and legal rights of

City’s personnel, clients, customers, and contractors.

5.16 The proposer and City shall agree to run

vulnerability scans on a quarterly basis.

5.17 The proposer shall sign a HIPAA Business Associate

(BA) contract with the City.

6.0 Serviceability

6.1 System maintenance and upgrades shall be scheduled, and the schedule shall be mutually agreed upon by City of Dallas and Proposer.

7.0 Privacy

7.1 System shall preserve authorized restrictions from

access and disclosure, including protection of personal privacy proprietary information.

7.2 Protect data/information contained in system.

7.3 The system shall be designed with privacy protection

in mind and that protections are appropriate to the level of sensitivity of the data.

7.4 The system shall comply with additional security and

privacy requirements which shall be provided upon request.

8.0 Networking

8.1 The system shall have a stable, high speed and secure

Internet connection.

8.2 The system shall comply with City of Dallas network

requirements which shall be provided upon request.

9.0 Technical Environment

9.1 Proposer shall provide information regarding the

number and type(s) of environments to be provided to the City.

9.2 Proposer shall provide information regarding the

cost(s) of and payment requirements for environments to the City.