Software & Software Engineering Vocabulary

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

flashcard set

Earn XP

Description and Tags

Vocabulary flashcards derived from Chapter 1 slides on Software & Software Engineering concepts, application categories, process activities, and general principles.

Last updated 3:02 AM on 8/25/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

31 Terms

1
New cards

Software

(1) Instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures that enable the programs to adequately manipulate information and (3) documentation that describes the operation and use of the programs.

2
New cards

System Software

A collection of programs written to service other programs, characterized by heavy interaction with computer hardware, heavy usage by multiple users, concurrent operation requiring scheduling/resource sharing/process management, complex data structures, and multiple external interfaces.

3
New cards

Application Software

Stand-alone programs that solve a specific business need by processing business or technical data to facilitate business operations or management/technical decision making, or controlling business functions in real time.

4
New cards

Engineering/Scientific Software

Software characterized by 'number crunching' algorithms used in applications ranging from astronomy to volcanology, automotive stress analysis, space shuttle orbital dynamics, molecular biology, computer-aided design, system simulation, and automated manufacturing.

5
New cards

Embedded Software

Software that resides within a product or system and is used to implement and control features and functions for the end user and for the system itself, ranging from limited keypad controls to complex digital automotive functions.

6
New cards

Product-line Software

Software designed to provide a specific capability for use by many different customers, which can focus on a limited marketplace (e.g., inventory control) or mass consumer markets (e.g., word processing, spreadsheets, graphics).

7
New cards

WebApps

Network-centric software spanning a range of applications from simple sets of linked hypertext files to sophisticated computing environments integrated with corporate databases and business applications.

8
New cards

Artificial Intelligence Software

Software that makes use of nonnumerical algorithms to solve complex problems not amenable to computation or straightforward analysis, such as robotics, expert systems, pattern recognition, artificial neural networks, theorem proving, and game playing.

9
New cards

Open World Computing

A new software category characterized by pervasive, distributed computing.

10
New cards

Ubiquitous Computing

A new software category centered around wireless networks.

11
New cards

Netsourcing

A computing concept where the Web acts as a computing engine.

12
New cards

Open Source

'Free' source code open to the computing community, presenting both benefits and potential risks.

13
New cards

Legacy Software

Existing software systems that must be adapted, enhanced, extended, or re-architected to meet changing business needs, new technology environments, or modern database interoperability.

14
New cards

Software Engineering (Seminal Definition)

The establishment and use of sound engineering principles in order to obtain economically software that is reliable and works efficiently on real machines.

15
New cards

Software Engineering (IEEE Definition)

(1) The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software. (2) The study of approaches as in (1).

16
New cards

Process Framework

A foundational structure for software engineering that establishes framework activities, work tasks, work products, milestones, deliverables, quality assurance checkpoints, and umbrella activities.

17
New cards

Communication Activity

A framework activity focused on communicating and collaborating with the customer and other stakeholders to understand project objectives and gather requirements.

18
New cards

Planning Activity

A framework activity that creates a software project plan (or 'map') describing technical tasks, risks, required resources, work products, and work schedules.

19
New cards

Modeling Activity

A framework activity involving the creation of sketches or models to better understand software requirements and the design that will achieve those requirements.

20
New cards

Construction Activity

A framework activity combining code generation (manual or automated) and testing to uncover errors in the code.

21
New cards

Deployment Activity

A framework activity in which software is delivered to the customer, who evaluates the product and provides feedback.

22
New cards

Software Project Management

An umbrella activity that allows the software team to assess progress against the project plan and take any necessary action to maintain the schedule.

23
New cards

Formal Technical Reviews

An umbrella activity that assesses software engineering work products in an effort to uncover and remove errors before they are propagated to the next activity.

24
New cards

Software Quality Assurance

An umbrella activity that defines and conducts the activities required to ensure software quality.

25
New cards

Software Configuration Management

An umbrella activity that manages the effects of change throughout the software process.

26
New cards

Reusability Management

An umbrella activity that defines criteria for work product reuse and establishes mechanisms to achieve reusable components.

27
New cards

Measurement (Umbrella Activity)

An umbrella activity that defines and collects process, project, and product measures to assist the team in delivering software that meets stakeholders' needs.

28
New cards

Risk Management

An umbrella activity that assesses risks that may affect the outcome of the project or the quality of the product.

29
New cards

George Polya

Known as the father of modern problem solving, who suggested four basic steps: 1. Understand the problem, 2. Plan a solution, 3. Carry out the plan, and 4. Examine the result for accuracy.

30
New cards

Hooker's General Principles

Seven core practice principles: 1) The Reason It All Exists, 2) KISS (Keep It Simple, Stupid!), 3) Maintain the Vision, 4) What You Produce, Others Will Consume, 5) Be Open to the Future, 6) Plan Ahead for Reuse, and 7) Think!

31
New cards

Software Myths

Beliefs affecting managers, customers, and practitioners that often contain elements of truth but invariably lead to bad decisions if not navigated with reality.