Modern Systems Analysis and Design - Chapter 2: The Origins of Software

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/20

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards generated from Modern Systems Analysis and Design Chapter 2.

Last updated 10:13 AM on 9/22/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

21 Terms

1
New cards

Outsourcing

Turning over responsibilities for some or all of an organization's information systems applications and operations to an outside firm.

2
New cards

IT Services Firms

Companies that employ skilled IT personnel to help organizations develop customer information systems for internal use.

3
New cards

Packaged Software Providers

Producers of prepackaged, off-the-shelf software that is non-customizable and meets approximately 70%70\% of an organization's needs.

4
New cards

Enterprise Resource Planning (ERP) Systems

Software systems that integrate individual traditional business functions into a series of modules so that a single transaction occurs seamlessly within a single information system.

5
New cards

Cloud Computing

The provision of computing resources, including applications, over the Internet, so customers do not have to invest in underlying computing infrastructure.

6
New cards

Software as a Service (SaaS)

A software delivery and licensing model enabled by cloud computing that allows applications to be accessed over the Internet on a subscription or per-use basis.

7
New cards

Open-Source Software

Freely available software whose source code is accessible to the public and developed by a community of interested people.

8
New cards

In-House Development

The method of building software systems from scratch using an organization's own internal IT staff.

9
New cards

Request for Proposal (RFP)

A document provided to vendors asking them to propose hardware and system software that will meet the requirements of a new system.

10
New cards

Software Reuse

The practice of using previously written software resources, especially objects and components, in new applications.

11
New cards

Object-Oriented Development Reuse

An approach to software reuse centered on object classes that encapsulate data and behavior of common organizational entities.

12
New cards

Component-Based Development Reuse

An approach to software reuse utilizing components ranging from small objects to large software modules that handle single business functions.

13
New cards

Abstraction Step

The first basic step of software reuse, which involves designing reusable software.

14
New cards

Storage Step

The second basic step of software reuse, which involves making software assets available for others to use.

15
New cards

Recontextualization Step

The third basic step of software reuse, which involves making reusable software assets understandable to developers.

16
New cards

Ad Hoc Reuse

An approach to reuse characterized by low level reuse and low cost, where individuals are free to find or develop reusable assets on their own without corporate policies.

17
New cards

Facilitated Reuse

An approach to software reuse with low level reuse and low cost, where developers are encouraged to reuse code but are not required to do so.

18
New cards

Managed Reuse

An approach to software reuse with moderate level reuse and moderate cost, where development, sharing, and adoption of reusable assets are mandated with organizational policies.

19
New cards

Designed Reuse

An approach to software reuse with high level reuse and high cost, where code must be designed for reuse during initial development, reuse is mandated, and policies measure reuse effectiveness.

20
New cards
<p>Sources of Application Software Diagram</p>

Sources of Application Software Diagram

A diagram showing the six major sources of software components: IT services firms, packaged software providers, ERP providers, cloud computing, open-source software, and in-house development.

21
New cards
<p>Investments Necessary to Achieve Reusable Components Graph</p>

Investments Necessary to Achieve Reusable Components Graph

A curve illustrating that building reusable components requires higher initial cost and time (e.g., 50%50\% more cost and 100%100\% more time for a 2-project solution), but delivers high value per unit investment across many projects.