Chapter 10 Information System Lifecycle Flashcards
Data steward
Person who monitors and controls use of an institution’s data
Service level agreements
Manage expectations between software vendors and institution (provide timely updates, response to errors)
Configuration management
Or change control, standard forum to approve and prioritize changes (bugs, requests for new features, etc.)
Systems Development Life Cycle (SDLC)
Analysis -> Design -> Implementation -> Testing -> Maintenance
-Analysis of business needs
-Design the system
-Implementation
-Testing to validate system
-Maintenance to remain healthy
Request for proposal
-System specification document that lists all the requirements an organization has for project
=Technical specifications, intellectual property, licensing, contracting, confidentiality (Business Associate Agreement), Training and support
-Should contain enough information for vendor to make reasonable offer
-When complete, it includes information provided by both the organization and the vendor
Request for Information
less-detailed version of the RFPR
Request for Quotation
When nature of system is already well known and the organization is just seeking a price point
Risk management program
-purpose is to protect organization and ensure it’s able to carry out its mission
-Analysis of risk has to be incorporated into all phases of the SDLC
Elements of System Implementation Plan
-Project management, workflow and process redesign, create implementation plan, issues management, data center, local hardware, network, security risk analysis, super user training, system installation, software configuration, interface development, testing, end user training, go live, lessons learned, monitoring progress, optimization strategies
3 replicated environments to test clinical information systems
-Development environment (dev)
-Test environment
-Production environment (prod)
Static testing
-examine source code, data architecture and wireframes of user interfaces
Dynamic testing
executing software in a variety of environments
-this is overwhelming majority of testing
White-box testing (or clear box testing)
-create tests that evaluate small segments of source code for applicability to a certain purpose
-assumes knowledge of inner workings of program and access to source codeB
Black box testing
tester has no knowledge of how software works but designs tests according to what the software is supposed to do
Unit testing
-verify functionality of a very specific section of code
-most commonly this is a form of white box testing
Integration testing
-form of testing that seeks to test the interaction between 2 or more separate units of code
Performance testing
-assess system’s capabilities when there are a high number of simultaneous users
System testing
-evaluation of the system as a whole as opposed to just a small subsection
Operational acceptance testing
-type of pre-release testing that ensures the product meets all listed requirements
Installation testing
-ensures system is installed correctly and working on customer’s hardware
Compatibility testing
testing system to make sure it works well with the other applications on the same system
Regression testing
focuses on detecting problems that could arise after an upgrade, making sure that old functions still work and that items that have been patched in the past continue to work
Usability testing
User interface is intuitive and easy to use
Accessibility testing
Type of usability testing aimed at users with physical impediments in accordance with accessibility standards such as the Americans with Disabilities Act
Testing in relationship to implementation
Before, during and after implementation
Types of maintenance
-preventive maintenance, corrective maintenance, customized maintenance or tailoring, enhancement maintenance, data quality management and data stewardship
Downtime procedures
often paper-based system, sometimes read-only replica of clinical information system
Disaster recovery
attempts to resuscitate a system after catastrophic data loss, such as an operating system failure or a hard drive crash
Decommissioned
when a system no longer provides a favorable cost-benefit position for the organization
