ITAC TO30 SOFTWARE MAINTENANCE

该合同负责维护支持NHLBI内部和外部受众的应用程序组合。信息技术和应用中心（ITAC）保持所有应用程序的最新和无错误，并及时响应最终用户的更改或增强请求，这一点非常重要。这可能包括对内容、结构、代码和图形的更新。 基于服务器的软件和操作系统软件需要得到维护，以保持完全正常运行。NHLBI运行一套需要维护的定制软件系统和应用程序，包括（但不限于）： ·修复软件中断的情况 ·修复新发现的缺陷（bug） ·对政府确定的所有高风险脆弱性进行补救 ·使软件适应不断变化的环境，例如新产品的发布， 与系统操作团队合作，支持操作系统和数据库的更新 ·调整软件以进行改进（例如，对屏幕进行微小更改或添加 新的数据字段，以优化可用性），以及 ·支持遗留系统的退役，以及已经超过 预期寿命周期，不再使用 维护福尔斯分为四类： ·纠正性维护-修复由设计、编码或逻辑导致的已识别缺陷 错误. ·自适应维护-修改网站或软件以支持对网站的更改。 环境，如操作系统、数据库或硬件配置。 完善的维护-在 现有功能的上下文，例如向现有用例添加新的异常流， 修改用户界面以提高可用性，或进行更改以增强系统 性能 ·持续性维护-旨在增加现场或系统的活动 可维护性和可支持性或解决新的安全威胁。

This contract is responsible for maintaining an application portfolio that supports audiences both internal and external to the NHLBI. It is of significant importance for the Information Technology and Applications Center (ITAC) to keep all applications up-to-date and bug free, and respond in a timely manner to end user requests for changes or enhancements. This may include updates to content, structure, code, and graphics. Server-based software and operating system software need to be maintained to remain fully functional. The NHLBI operates a set of custom software systems and applications that require maintenance that includes (but is not limited to): • Fixing cases where software breaks • Fixing newly identified defects (bugs) • Remediation of all high-risk vulnerabilities identified by the Government • Adapting software to changing environments, such as new releases of products, working with the Systems Operations team to support updates to operating systems and databases • Adapting the software for improvements (e.g., making minor changes to screens or adding new data fields to optimize usability), and • Supporting the retirement of legacy systems, as well as systems that that have exceeded the expected life cycle and are no longer in use Maintenance falls into one of four categories: • Corrective maintenance – Repair of identified defects resulting from design, coding, or logic errors. • Adaptive maintenance – Modification of the site or software in support of changes to the environment, such as operating system, database, or hardware configurations. Perfective maintenance – Accommodating new or changed user requirements within the context of existing functionality, such as adding new exception flows to an existing use case, modifying a user interface for improved usability, or changes to enhance system performance. • Preventative maintenance – Activities aimed at increasing the site or systems maintainability and supportability or to address new security threats.