INTE 112: Introduction to Software

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

1/20

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards covering core concepts, quality characteristics, classifications, delivery models, licensing, and visual architecture diagrams from Lecture 1.

Last updated 9:37 AM on 9/30/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

Software

A collection of computer programs, data structures, procedures, and associated documentation that instruct a computer system on how to perform specific tasks.

2
New cards

Hardware

The physical and tangible components of a computer system, such as the processor, memory, storage devices, and input/output peripherals.

3
New cards

Functionality

The extent to which software provides features and services that satisfy stated and implied user requirements.

4
New cards

Reliability

The ability of software to perform consistently without failure over a defined period.

5
New cards

Usability

A measure of how easily users can learn, understand, and operate a software system.

6
New cards

Efficiency

How well software utilizes system resources such as processing power, memory, and network bandwidth.

7
New cards

Maintainability

The ease with which software can be modified to correct errors, improve performance, or adapt to new requirements.

8
New cards

Portability

The degree to which software can operate across different platforms or environments.

9
New cards

System Software

Programs that manage computer hardware and provide a platform on which application software can run, operating primarily in the background.

10
New cards

Application Software

Software designed to help users perform specific tasks by interacting directly with users and addressing practical needs.

11
New cards

On-Premise Software

Software installed and operated on local computers or organizational servers, where users or institutions are responsible for installation, updates, security, and maintenance.

12
New cards

Cloud-Based Software (SaaS)

Software hosted on remote servers and accessed via the internet, typically structured on a subscription basis rather than permanent purchases.

13
New cards

Hybrid Software Delivery

A delivery approach combining on-premise and cloud-based models, retaining sensitive data locally while using cloud services for collaboration.

14
New cards

Software License

A legal agreement that defines how software may be used, modified, and distributed.

15
New cards

Proprietary Software

Software owned by a vendor or organization where users purchase usage rights, but source code access and modification rights are restricted.

16
New cards

Open-Source Software

Software that allows users to view, modify, and redistribute source code under defined licensing terms, promoting transparency and collaboration.

17
New cards

Freeware

Software distributed at no cost, typically without access to source code or modification rights.

18
New cards
<p>Usability Evaluation Model</p>

Usability Evaluation Model

A circle diagram listing 12 evaluation criteria for usability, including User Control & Freedom, Recognition Rather than Recall, Mental Model, Clarity, Simplicity & Aesthetic Integrity, Accuracy, Error Prevention & Handling, Consistency & Predictability, User Support, Forgiveness, Feedback, and Accessibility Compliance.

19
New cards
<p>Computing System Layer Architecture</p>

Computing System Layer Architecture

A structural diagram illustrating Hardware (CPU, Memory, I/O) surrounded by System Software (Operating System, Utilities), which is surrounded by Application Software (Office, Photoshop, Calculator, Games, Browser).

20
New cards
<p>On-Premises vs Cloud Base Comparison</p>

On-Premises vs Cloud Base Comparison

A diagram contrasting On-Premises infrastructure (high hardware cost, medium backup cost, high maintenance cost) with Cloud Base infrastructure (low hardware cost, backup & recovery cost, security compliances).

21
New cards
<p>V-Model</p>

V-Model

A development lifecycle diagram matching development phases (Requirement analysis, System design, Architecture design, Module design, Coding) with corresponding testing phases (Unit, Integration, System, Acceptance testing).