Change Management Flashcards
S2 M4
a system put in for authorizing & monitoring changes related to IT (software implementation, development, application programs, database administration, etc)
change management system
a system that facilitates & streamlines the creation, negotiation, execution, storage, tracking, & management of contracts throughout their life cycle
contract management system
process of modifying the default system parameters to meet a company’s needs
configuration
converting systems components from one information system to another
migration
process of making a system available to intended users & other programs
deployment
practice of integrating software, systems, & processes within an organization to streamline & optimize business processes
business process integration
a system’s original state that can be used as a starting point when performing a recongifuration
baseline configuration
form of documentation that is used in change management to understand changes & trends in asset acquisition or deployment
system component inventory
a set of quantitative or qualitative metrics businesses use to determine whether a newly developed application is satisfactory & meets end-user expectations
acceptance criteria
catalogs which sites a user visits, the time of visit, & how long each page was viewed
proxy logs
continuously monitoring the output from the changes, comparing it with the desired outcome, & calibrating the changes to minimize discrepancies from the acceptance criteria
closed loop verification
developing & testing software on a continuous basis rather than at pre-determined, fixed intervals
Continuous adoption
continual review of change, the identification & solving of problems; keeps stakeholders accountable
continuous monitoring
different teams of employees perform separate tasks in sequence, with each team beginning work from the pre-written authoritative agreement of the preceding team & then ending work when the business requirements for the team have been met
waterfall method
change management method with cross-functional teams, each dedicated to particular functions or improvements of a system drawn from a prioritized list of the customer’s remaining needs
agile method
approach that focuses on continuous improvement through small improvements over time rather than short sprints that have a finite life
Kaizen method
form of project management that identifies the longest sequence of dependent events in a project to determine the earliest point at which a project can be completed
critical path method
an organization tests a new system on a small scale in a non-production environment to establish feasibility
pilot conversion
a business completely stops using a legacy system & immediately cuts over to the new system
direct conversion
implementing a new system while continuing to operate the existing system, allowing both systems to be used simultaneously (safest)
parallel conversion
follows a schedule that gradually or incrementally implements a new system
phased conversion
test that ensures the software works correctly for the intended user in their normal work environment
acceptance test
test that focuses on visible user actions & user-recognizable outputs from the system
validation tests
test that exercises an entire subsystem & ensures that a set of components operate smoothly together
integration tests
