insy 3305 ch 6 keyterms

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

1/62

encourage image

There's no tags or description

Looks like no tags are added yet.

63 Terms

1
New cards

A-kind-of

Relationship showing that one class is a specialized type of another class

2
New cards

Abstract classes

Classes that cannot be directly instantiated and are designed to serve as parent classes for other classes

3
New cards

Abstraction

Focusing on important characteristics while ignoring unecessary details

4
New cards

Aggregation

Whole-part relationship where the parts can exist indepdently of the whole

5
New cards

API (Application Programming Interface)

A set of rules and functions that allows different software applications or components to communicate

6
New cards

Application Architecture layer

Layer that determines how application software is distributed across hardware and networks

7
New cards

Class

Blueprint defining the attributes and methods shared by objects

8
New cards

Class cohesion

How closely related the responsibilities and methods within a class are

9
New cards

Class library

Collection of reusable classes that prorgrammers can use in applicationsC

10
New cards

Client

Object or system that requests services or information from another object or system

11
New cards

Cohesion

Degree to which the elements of a module or class work together toward a common purpose

12
New cards

Collaboration

Group of objects or classes working together to accomplish a task

13
New cards

Concrete classes

Classes that can be instantiated to create actual objects

14
New cards

Connascence

Measure of how much one component depends on another component’s internal details or changes

15
New cards

Container classes

Classes designed to store and amange collections of other objects

16
New cards

Contract

An agreement defining the responsibilities and expectations between interacting objects

17
New cards

Component

Reusable and replaceable software unit that performs a specific function

18
New cards

Controller

in MVC, the component responsible for handling user input and coordinating actions between the model and view

19
New cards

Coupling

Degree of dependency between different classes or modules

20
New cards

CRUDE analysis

An analysis technique that identifies which classes Create, Read, Update, Delete, and Execute information or behavior

21
New cards

Custom development

Building software specifically designed to meet an organization’s unique requirements

22
New cards

Customization

Modifying existing packaged software meet an organization’s specific needs

23
New cards

Data access and manipulation (DAM) classes

Classes that handle communication between the problem-domain objects and the database or other storage system

24
New cards

Data management layer

Layer responsible for storing, retrieving, and managing system data

25
New cards

Dependency relationship

Relationship where one class relies on another class to perform a function

26
New cards

Design

Process of determining how a system will be built to satisfy business requirements

27
New cards

Design pattern

Reusable solution to a commonly occuring software design problem

28
New cards

Enterprise resource planning (ERP)

Integrated software that manages major business processes, such as finance, inventory, purchasing, and human resources

29
New cards

Exceptions

Unusual conditions or errors that inturrept the normal execution of a program

30
New cards

Factoring

Breaking a system into smaller, more manageable components based on common characteristics or responsibilities

31
New cards

Foundation layer

Layer containing general-purpose classes and services that support the other system layers

32
New cards

Framework

Reusable structure of software components that provides a foundation for building applications

33
New cards

Generalization

Combining common characteristics of multiple classes into a more general parent class

34
New cards

Generalization/specialization cohesion

Cohesion created through inheritance, where specialized classes share and extend the characteristics of a general class

35
New cards

Has-parts

A relationship indicating that an object consists of other objects or components

36
New cards

Human-computer interaction layer

Layer responsible for how users interact with the system through screens, forms, menus, and reports

37
New cards

Ideal class cohesion

A class design in which all attributes and methods contribute to one clear, focused responsibility

38
New cards

Inheritance coupling

Dependency between classes created through inheritance relationships

39
New cards

Interaction coupling

Dependency between classes that communicate or interact with one another

40
New cards

Law of demeter

A design principle stating that an object should communicate mainly with its immediate collaborators rather than navigating through chains of other objects

41
New cards

Layer

Grouping of related classes and responsibilities within a system’s architecture

42
New cards

Message

Request sent from one object to another asking it to perform an operation

43
New cards

Method

Function or operation defined within a class that describes what its objects can do

44
New cards

Method cohesion

How closely the steps within a method work together to accomplish one specific task

45
New cards

Model

In MVC, the component that manages the applications data and business rules

46
New cards

Model-View-Controller (MVC)

An architectural pattern that seperates an application into the Model, View, and Controller components

47
New cards

Module

A seperately organized part of a software system that performs a specific function

48
New cards

Normalization

Restructuring a design to reduce unnecessary duplication and improve organization

49
New cards

Outsourcing

Hiriing an external organization or service provider to develop or manage software

50
New cards

Package

UML grouping used to organize related classes and other model elements

51
New cards

Package diagram

UML diagram showing how packages are organized and how they depend on one another

52
New cards

Packaged software

Prebuilt software developed for use by multiple organizations or customers

53
New cards

Partition

Dividing a system into sperate functional areas or sections

54
New cards

Patterns

Reusable approaches to solving recurring design problems

55
New cards

Problem-domain layer

Layer containing classes that represent the real-world business objects and concepts the system manages

56
New cards

Protocol

A defined set of ruels governing communication or interaction between components

57
New cards

Refinement

Adding detail to an existing design or model to make it more specific and complete

58
New cards

Server

Computer or software application that provides services or resources to clients

59
New cards

Signature

Identifying details of a method, such as its name, parameters, and return type

60
New cards

Smalltalk

Object-oriented programming language known for its use of objects, messages, and dynamic behavior

61
New cards

Utility classes

Classes that provide commonly used supporting functions, such as calculations, formatting, or conversion

62
New cards

View

in MVC, the component responsible for displaying information to users

63
New cards

Visibility

Determines which classes or objects can access an attribute or method