Introduction to Management Information Systems - Lecture 3

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/34

flashcard set

Earn XP

Description and Tags

Comprehensive vocabulary flashcards covering Management Information Systems, SDLC phases, organizational change types, and process management methodologies from Lecture 3.

Last updated 4:00 AM on 7/9/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

35 Terms

1
New cards

Systems development

The process of creating or modifying information systems to meet business needs, typically including planning, analysis, design, development, testing, implementation, and maintenance.

2
New cards

Organizational change

Alterations in structure, culture, processes, or strategies within an organization triggered by factors such as new information systems.

3
New cards

Incremental change

Small improvements made to an organization's existing structure or processes.

4
New cards

Transformational change

Major shifts in an organization's operations or strategy.

5
New cards

Automation

A type of organizational change that replaces manual processes with technology, resulting in minimal organizational disruption.

6
New cards

Rationalization of Procedures

The streamlining of standard operating procedures to improve workflow efficiency.

7
New cards

Business Process Reengineering (BPR)

The radical redesign of business processes, characterized by high impact and high risk.

8
New cards

Paradigm Shift

A fundamental change in the business model, such as transitioning to e-commerce.

9
New cards

Systems Development Life Cycle (SDLC)

A structured framework and architectural blueprint used to guide the creation, deployment, and maintenance of information systems from concept to retirement.

10
New cards

System Analysis

An in-depth study of the existing system to determine requirements for the new system from the user's perspective.

11
New cards

Economic feasibility

An evaluation conducted during system design to determine if the benefits of the system justify its costs.

12
New cards

Technical feasibility

An evaluation to determine if reliable technology and training are available to support a new system.

13
New cards

Operational feasibility

An evaluation to determine if managers and users will support the implementation of the new system.

14
New cards

Computer-Aided Software Engineering (CASE) tools

Software-based products, such as diagramming tools and data repositories, designed to help automate the production of information systems.

15
New cards

Build vs. Buy

The decision process of determining whether to develop a new program in-house or purchase it from an outside company.

16
New cards

Module (unit) test

A testing phase where each individual part of the system is tested separately.

17
New cards

Integration testing

Also known as End to End Testing, this phase tests the system as a single integrated unit.

18
New cards

Direct approach

A conversion method, also called plunge or crash, where the entire new system completely replaces the old system in one step.

19
New cards

Parallel approach

A conversion method where both the old and new systems are operated side by side until the new system proves itself.

20
New cards

Pilot approach

A conversion method where a new system is launched for only one group within the business before being implemented company-wide.

21
New cards

Phased approach

An incremental conversion method where individual parts of the new system are gradually introduced over time.

22
New cards

Corrective maintenance

The type of system maintenance involving physical repair or the correction of new bugs found in the software.

23
New cards

Adaptive maintenance

System adjustments made to accommodate environmental changes or the changing needs of users.

24
New cards

Perfective maintenance

Changes made to the system to incorporate better techniques as they become available.

25
New cards

Systems audit

An evaluation method where the system's performance is compared against its original specifications.

26
New cards

Waterfall approach

A traditional systems lifecycle approach where tasks in one stage must be finished before the next stage begins.

27
New cards

Agile methodology

A development approach focusing on flexibility, collaboration, and continuous improvement by delivering work in short cycles.

28
New cards

Iteration (Sprint)

A short time period, usually "14""1-4" weeks, during which Agile teams complete specific tasks including planning, development, and review.

29
New cards

Prototyping

Building an experimental, working but preliminary version of an information system rapidly and inexpensively for user evaluation.

30
New cards

End-user development

A method using fourth-generation languages that allows end-users to develop systems with minimal help from technical specialists.

31
New cards

Request for Proposal (RFP)

A detailed list of questions submitted to packaged-software vendors used to evaluate alternative software packages.

32
New cards

Offshore outsourcing

A type of outsourcing driven by cost-savings where software development or services are contracted to vendors in other countries.

33
New cards

Business Process Management (BPM)

A disciplined approach to identifying, designing, executing, monitoring, and optimizing business processes to achieve strategic goals.

34
New cards

Key Performance Indicator (KPI)

A measurable value that demonstrates how effectively an individual or organization is achieving a specific objective.

35
New cards

KPI dashboard

A visual tool, often using charts and graphs, that displays key performance indicators in an organized format to track progress.